Marketing & Growth

How to build lifecycle email flows as Restaurant and Hospitality Founders

Marketing & GrowthFor Restaurant and Hospitality Founders3 apps11 steps~22 min to set up

You collected 400 email addresses from OpenTable reservations and your loyalty sign-up iPad last quarter, but they're sitting in a CSV you haven't touched. When you do send something — usually a 'thanks for visiting' blast — it goes to everyone at once with no timing logic, no segmentation, and no follow-up. Guests who came once six months ago get the same message as regulars who book every Friday. Your reservation platform (OpenTable, Resy) won't let you email guests directly without upgrading to an enterprise tier. Mailchimp has the templates but no idea who ordered what or how long ago someone visited. You're leaving repeat visits on the table because you have no automated way to bring a lapsed guest back before they forget you exist.

Build this on Starch → See the apps used

Marketing & GrowthFor Restaurant and Hospitality Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

An automated welcome sequence that fires when a new guest email lands in your system — intro, a nudge toward their next visit, and a soft ask for a review — without you touching it

A lapsed-guest re-engagement flow that identifies contacts who haven't visited in 60+ days (cross-referenced against reservation data) and sends a targeted 'we miss you' message with a reason to return

A weekly digest that shows you which emails were sent, who opened them, and which segments are converting back to reservations — so you're not guessing whether any of it is working

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM Email Agent Growth Analyst

Data sources & config

Guest contact data is imported from OpenTable and Resy via browser automation — no direct API needed. Square or Toast transaction data is pulled from Starch's integration catalog (live query) to calculate average spend and visit frequency. Gmail is connected as a scheduled-sync provider so Starch reads and sends from your existing restaurant email address. The Growth Analyst app connects to Gmail (scheduled sync) to track open and reply rates and surfaces them in your weekly Monday digest.

Prompts to copy

Build me a guest CRM where each contact has: name, email, last visit date, total visits, average spend per visit, how they first booked (OpenTable, walk-in, or event), and any dietary notes from past reservations. Flag anyone who hasn't visited in 60 days as 'lapsed.'

Create a lifecycle email flow for my restaurant. New guests get a welcome email 24 hours after their first visit, then a follow-up at day 7 asking for a Google review, then silence unless they book again. Lapsed guests (no visit in 60 days) get a re-engagement email with our current seasonal menu and a 10% off their next visit code. Anyone who books after getting the lapsed email should move out of that sequence automatically.

Every Monday morning, email me a summary: how many lifecycle emails went out last week, open rates by sequence (welcome vs. lapsed), and which guests booked a return visit within 14 days of receiving an email. Compare this week's re-engagement bookings to last week.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Export your existing guest email list from OpenTable, Resy, or your loyalty app as a CSV and import it into the Starch CRM app. Tell Starch: 'Each row is a guest — map email, name, last visit date, and number of visits. Flag anyone with a last visit date older than 60 days as lapsed.'

2 Connect your Square or Toast account from Starch's integration catalog so the agent can query transaction history live and calculate average spend per guest and visit frequency.

3 Set up browser automation to pull new reservation guest data from OpenTable or Resy on a nightly schedule — Starch automates the login and data pull through your browser, no API required.

4 In the Email Agent app, describe your welcome sequence: 'When a new guest contact is added to the CRM, send a welcome email from our restaurant Gmail account 24 hours later. On day 7 send a second email asking for a Google review and include a link to our Google Business page. Stop the sequence if they make another reservation before day 7.'

5 Describe the lapsed-guest flow: 'For any contact flagged as lapsed (no visit in 60+ days), send one re-engagement email featuring our current seasonal menu. Include a 10% off code COMEBACK10. If they book within 14 days, mark them as re-engaged in the CRM and stop all outreach.'

6 Write the actual email copy inside Starch by prompting: 'Draft a warm, not-too-salesy welcome email for a neighborhood restaurant. Mention that we noticed it was their first visit and we hope to see them again soon. Tone: like a message from the owner, not a marketing department.' Approve or edit before activating.

7 Connect Gmail as a scheduled-sync provider so Starch sends lifecycle emails from your real restaurant address (not a no-reply), and so it can track replies — a guest who responds gets flagged for personal follow-up rather than continuing through the automation.

8 Set up the Growth Analyst app with the prompt: 'Every Monday at 8am, email me a plain-English summary of last week's lifecycle email performance: how many welcome emails and lapsed emails went out, open rates for each, and how many guests made a reservation within 14 days of receiving any lifecycle email.'

9 Add a CRM filter view: 'Show me all guests who received a lapsed email more than 30 days ago and still haven't returned. Sort by total lifetime visits descending — I want to personally call the top 10.' This gives you a human-touch list for your highest-value lost guests.

10 After 30 days, use the Growth Analyst digest to compare re-engagement booking rates week over week. Prompt Starch: 'Which version of the lapsed email subject line got a higher open rate — the one mentioning the seasonal menu or the one with the discount code?' and use that to refine the copy.

11 When you add a private dining or events inquiry form to your website, set up a new entry point: 'When someone fills out our events inquiry form, add them to the CRM under the Events segment and send them an availability and pricing email within 2 hours.' Starch automates this through browser form monitoring — no additional API needed.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

60-day re-engagement push, April 2026

Sample numbers from a real run

Lapsed guest emails identified	214
Re-engagement emails sent	214
Open rate	38
Click-throughs to menu/booking page	61
Return reservations within 14 days	29
Average cover spend on return visit ($)	74
Incremental revenue attributed ($)	2,146

You had 214 guests in the CRM who hadn't visited since before February — the slow season after Valentine's Day. Starch identified them automatically using the 60-day lapse rule and sent a single re-engagement email with your new spring menu and a COMEBACK10 code. The Growth Analyst Monday digest showed a 38% open rate (well above your old blast average of 19%) and 61 people clicked through to your Resy page. Twenty-nine booked within two weeks. At your $74 average cover spend, that's roughly $2,100 in revenue from one automated flow you set up in an afternoon. The welcome sequence running in the background converted 11 of the 40 first-time guests from the same period into second visits within 30 days — something you had no visibility into before because you weren't tracking it at all.

Measurement

How you'll know it's working

Re-engagement rate: % of lapsed guests who book again within 14 days of receiving an email

Second-visit conversion rate: % of first-time guests who return within 30 days

Email open rate by sequence (welcome vs. lapsed vs. event inquiry)

Revenue attributed to lifecycle emails (cover count × average spend for guests who came back after an email)

Lapsed guest list size week over week — is it shrinking or growing?

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Mailchimp

Good for bulk sends and templates, but has no connection to your reservation or POS data, so you can't automate flows based on visit recency or spend — you'd be segmenting by hand from a stale CSV.

OpenTable Marketing (built-in)

Lets you email guests directly inside OpenTable, but only guests who booked through OpenTable — it can't reach your walk-ins, event inquiries, or loyalty sign-ups, and you can't customize the logic beyond their preset templates.

Klaviyo

Powerful lifecycle tool built for e-commerce; works well if your revenue is online orders, but it's designed around SKUs and carts, not covers and reservation dates — mapping restaurant data into it takes real configuration time.

Manual email from your personal Gmail

Zero cost and fully personalized, but doesn't scale past about 30 guests and leaves no record of who got what or whether anyone came back.

On Starch RECOMMENDED

One platform — crm, email agent, growth analyst all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Can Starch pull guest email addresses directly from OpenTable or Resy?

Both platforms restrict direct API access to guest contact data unless you're on their enterprise plans. Starch works around this through browser automation — it logs into your OpenTable or Resy account and pulls reservation data the same way you would manually. No API deal required. If you already have a CSV export, you can import that directly into the CRM in seconds.

Will these emails come from my real restaurant email address or some generic Starch address?

They come from your Gmail account. Starch connects directly to Gmail as a scheduled-sync provider and sends on your behalf from your existing address. One thing worth knowing: the Gmail OAuth consent screen currently shows the underlying connector's name during setup, not 'Starch' — that's a known issue on the roadmap, not a sign anything is wrong.

What if my restaurant uses Square instead of Stripe or QuickBooks — can Starch still track guest spend?

Yes. Square is available through Starch's integration catalog; the agent queries it live when your CRM needs transaction data. You'd connect Square from the integration catalog and tell Starch how to match transactions to guest records by email or name.

I don't have a loyalty program. Do I have enough contact data to make this worthwhile?

Probably yes if you've been collecting emails from reservations at all. Even 150 contacts gives you a meaningful lapsed-guest list and a welcome sequence worth running. You don't need a loyalty app — reservation emails, event inquiry forms, and a sign-up iPad at the host stand are enough to start. Starch aggregates whatever you have.

Is my guest data stored securely? Are you SOC 2 certified?

Starch is not SOC 2 Type II certified today. If your restaurant is operating under strict data compliance requirements (unlikely for most independent operators, but worth flagging), that's something to weigh. For most independent restaurants and small hotel operations, Starch's security practices are appropriate — but we're being straight with you rather than burying it in footnotes.

Can I set this up once and forget it, or do I need to babysit it?

The welcome and lapsed-guest sequences run automatically once you activate them. The Growth Analyst digest emails you every Monday with what happened last week. The one thing that does need occasional attention: refreshing your seasonal menu content in the re-engagement email when the menu actually changes — Starch doesn't know you added the new lamb dish unless you tell it. That's a two-minute edit, not a rebuild.