Skip to content

Restaurant email automation

Set the signal, wait, and check when to stop. Copy these workflows into your existing email platform and test them with a small list you control.

Welcome confirmed subscribers

Give new regulars one useful introduction to the menu, location, or booking page.

  1. T+0

    Confirmed opt-in

    Trigger after confirmed permission. Keep one welcome flow per address.

  2. Same day

    Send the welcome

    Tell guests what they signed up for and link to one helpful page.

  3. T+3 days

    Share a menu or favorite

    For guests who are still subscribed, offer one next step with the current menu.

Fields to have ready

  • Confirmed subscribe time
  • Marketing permission
  • Welcome sent date
  • Menu URL

Manual option

Use your sender’s confirmed signup list and a welcome-sent tag. Review only new confirmed signups, then apply the tag after sending.

When to exit

  • Stop on unsubscribe, hard bounce, or withdrawn permission.
  • Skip repeat entries after a welcome was recorded.

Repeat entry

One automatic series per address. Reset only when the guest explicitly requests a new subscription and your policy calls for it.

Set it up in your email platform
  1. Select the restaurant’s audience and a confirmed signup trigger. Limit it to contacts who have accepted email marketing.
  2. Add the welcome email, record a welcome-sent tag or date, then wait three days.
  3. Before the second send, check permission again. Route suppressed contacts to the end of the flow.
Before enabling, test these cases
A guest submits the hosted form and leaves it unconfirmed.
No email from this series.
A new guest confirms and has no welcome-sent record.
The welcome is sent once. The day-three message is queued for a permission check.
A confirmed guest unsubscribes after the first message.
The day-three step is skipped.

Email drafts

Confirmation-day welcome

Welcome to [Restaurant]

Preview: Find our menu, hours, and what you’ll hear from us.

Thanks for joining the [Restaurant] list. We’ll write when there’s a new menu, an event, or another good reason to make a plan. If you’re thinking of visiting, our menu page has the current hours and seating details.

See the menu and hours · [Menu URL]

Day-three menu follow-up

Planning your first visit to [Restaurant]?

Preview: Check the latest menu before you visit.

Here’s a handy link for the next time you’re deciding where to eat. It has what we’re serving now and the details you’ll need to plan your visit. We look forward to seeing you at [Restaurant].

Explore the current menu · [Menu URL]

Follow up after a completed visit

Thank the guest and give them one way to share private feedback.

  1. T+0

    Service completed

    Trigger from an actual attended reservation or fulfilled pickup.

  2. T+1 day

    Review the latest state

    Check for refunds, cancellations, an open complaint, or an earlier send for the same order.

  3. If eligible

    Send a short thank-you

    Invite honest feedback. Keep this version about the completed visit.

Fields to have ready

  • Unique order or reservation ID
  • Completed service time
  • Order state
  • Marketing permission if adding promotions

Manual option

Review yesterday’s completed service records in your own system and mark the records that were contacted. Leave open service issues in the existing support queue.

When to exit

  • Exclude no-shows, refunded orders, open complaints, and cancelled orders from the automated thank-you.
  • Route service issues to the team that can address them.

Repeat entry

One send per order or reservation. Add a short repeat-visit cooldown for guests with clustered orders.

Set it up in your email platform
  1. Map the fulfilled order or attended reservation in your provider and keep its unique ID with the contact.
  2. Wait one day, then verify the order state and feedback status. Suppress duplicate order IDs and skip cancelled, refunded, and open cases.
  3. Send the service-only feedback draft with a private response link. If your platform cannot see the order state, use the manual option.
Before enabling, test these cases
The same completed reservation is reported twice.
One eligible follow-up.
A pickup is refunded before the day-one check.
Normal follow-up skipped. Use the service-recovery process if needed.

Email drafts

Day-after thank-you and feedback

How was your visit to [Restaurant]?

Preview: Tell our team how yesterday went.

Thank you for visiting [Restaurant]. We’d like to hear what worked and where we can improve. If you have a minute, send a note through the link below. Your response goes to our team.

Share feedback with the team · [Private feedback URL]

Invite a previous guest back

Use a verified gap since an actual visit to invite an opted-in guest back.

  1. T+45/60/90 days

    Reach a visit-gap threshold

    Choose a gap that fits the restaurant. Use confirmed visits or orders as the event.

  2. Same day

    Give a clear reason to return

    Share a seasonal addition, returning favorite, or a valid offer with terms.

  3. T+7 after invite

    Optional final reminder

    Re-check permission, offer validity, and whether the guest returned. Send one reminder at most.

Fields to have ready

  • Last completed visit or order
  • Marketing permission
  • Previous win-back date
  • Current destination URL

Manual option

Filter opted-in guests with a dated completed order or attendance record. Leave guests with unknown dates out.

When to exit

  • Leave the sequence as soon as a completed return visit is recorded or permission changes.
  • Pause an offer once it expires or can no longer be honored.

Repeat entry

Start with a 90-day cooldown after the invitation. Check preferences before permitting another entry.

Set it up in your email platform
  1. Map the completed visit date from a reliable restaurant report. Build a segment of subscribed contacts who passed your chosen gap and are outside the cooldown.
  2. Send the invitation when the guest enters the segment. Wait seven days before an optional reminder.
  3. Use a fresh segment check just before the reminder. A new visit, changed permission, or expired offer ends the sequence.
Before enabling, test these cases
A guest opens the first email but does not visit.
The visit date stays unchanged. All other reminders still follow the checks.
A guest books and attends before day seven.
Final reminder skipped.

Email drafts

Return invitation

A few new things to try at [Restaurant]

Preview: See what changed since your last visit.

We’ve updated the menu at [Restaurant]. If you’re making plans, take a look at [confirmed menu highlight] and the rest of what we’re serving. The menu below has our current hours and details.

See the current menu · [Menu URL]

Optional day-seven reminder

A quick note from [Restaurant]

Preview: Take a look before you make your next dinner plan.

If you haven’t had a chance to see our new menu, here’s a quick link. It has the latest dishes, hours, and ways to visit. We’d be glad to see you when it fits your plans.

See the menu and plan a visit · [Menu or booking URL]

Celebrate a birthday or anniversary

Plan a once-a-year greeting for guests who chose to share their occasion and receive email.

  1. D−7 days

    Match the occasion date

    Begin about a week ahead. Use a documented rule for February 29 in non-leap years.

  2. D−7 days

    Send the invitation

    Provide booking instructions and clear terms for any real benefit.

  3. D−1 day

    Review any reminder

    Send only if the offer is still useful and the guest has not redeemed it.

Fields to have ready

  • Opted-in birthday or anniversary month/day
  • Marketing permission
  • Year last sent
  • Offer expiration and redemption state

Manual option

Review the next seven days in your authorized birthday group. Check the year-last-sent and redemption fields before exporting a segment in your provider.

When to exit

  • Stop when a guest redeems, withdraws permission, or the offer expires.
  • Exclude records with unconfirmed dates.

Repeat entry

Once per guest per occasion per calendar year. For two dates in one household use the contact preference recorded by the restaurant.

Set it up in your email platform
  1. Use an opt-in birthday or anniversary field that your sender can evaluate. Document how the segment handles February 29 before activating it.
  2. Set the first send seven days ahead and record the occasion year. Add a six-day wait before the optional reminder.
  3. Check subscription state, redemption and terms just before the reminder. Use a manual segment if your sender cannot check these fields.
Before enabling, test these cases
An opted-in guest redeems the benefit on D−4.
The D−1 reminder is skipped.
A February 29 record appears in a non-leap year.
Uses the chosen February 28, March 1, or skip rule consistently.

Email drafts

Seven-day occasion invitation

Make a celebration plan at [Restaurant]

Preview: Find a table and check the details for your date.

Planning something special? We’d love to host you at [Restaurant]. The booking page shows available dates and times, including any current celebration options and terms. If you’d like to join us, pick a time that works for you.

See celebration availability · [Reservation URL]

One-day offer reminder

A reminder before your [Restaurant] offer ends

Preview: Check availability and terms before [offer cutoff].

If you still want to use your [confirmed offer], it is available through [offer cutoff] under the terms on our booking page. The link below shows whether a table is available and how to book it.

Check the offer and book · [Offer terms and booking URL]

Configure the workflow in your sender

Check the trigger fields available on your plan. Pick the right list, add each delay, test suppression, and send to your own inbox before activating the flow. Keep service-only reservation reminders separate from promotional offers. Plan promotional messages for subscribers whose permission you have recorded.

See reservation reminder templates