Restaurant Marketing Automation: 5 Workflows for Operators 2026

Most independent restaurants with a 500-plus email list leave $35,000 to $60,000 a year on the table by not automating five specific flows. This guide fixes that in a weekend.

Restaurant marketing automation is not a philosophy. It is five workflows, built once, that run in the background while the kitchen does its job. The steps below are the ones that actually survive contact with a real POS, a real reservation tool, and a staff that is too busy to babysit software. They are written for independent operators and multi-unit groups setting these flows up themselves, not for a team with a dedicated CRM manager. If the restaurant already has Toast, Square, Klaviyo, Mailchimp, OpenTable, or Marsello in the stack, the setup instructions apply directly. The five workflows, welcome series, lapsed-customer reactivation, birthday, post-visit review request, and online-order follow-up, consistently drive 12 to 20 percent of annual revenue for restaurants that finish building them. Email automation is only half the picture. Restaurant Velocity handles the Google Business Profile half, the review replies, Google posts, photo cadence, and ranking checks, while you build the email flows below.

What restaurant marketing automation actually is (and what it is not)

Restaurant marketing automation is a set of triggered messages, email, SMS, or push, fired by guest behavior or a calendar event, not by a staff member hitting “send.” The trigger might be a new subscriber filling out a form, a guest whose last visit was 45 days ago, a birthday seven days out, or a completed online order. The platform sends the right message at the right time, pulled from a template the operator wrote once.

It is not an AI that writes your voice for you, a chatbot that replaces the host, or a dashboard that invents regulars out of thin air. A 2025 Restaurant Business Online piece surveyed roughly 85 chains using AI and found only 9 percent reported meaningful impact while 43 percent said value was “limited.” The fantasy version of automation is oversold. The practical version, five well-built flows tied to a clean guest list, is underbuilt at most restaurants.

The difference between the two is data hygiene and scope. Operators on r/smallbusiness and r/marketing repeatedly surface the same refrain: data silos are the number one marketing-tool problem. When the POS, the reservations system, and the email tool do not share a guest record, automations fire at ghosts. Before wiring up any flow, make sure the tools talk to each other. That is the real first step.

Fewer than 30 percent of independent restaurants have any marketing automation running, which means the competitive bar to clear is not high. The restaurants in that minority are not necessarily spending more on marketing; they are spending more intentionally, with every message tied to a trigger and a measurable outcome.

Rev Ciancio, hospitality marketing consultant and co-founder of Handcraft Burgers & Brew, frames it bluntly in his Restaurant Coach Podcast appearance: “It’s about email, man, it’s about having contact info.” He estimates that 90 to 95 percent of restaurants do not systematically capture guest data at all, and argues that every social-media effort should have one goal, driving guests onto the email list. “Whatever social media platform gets you into my email list, that’s my favorite one,” he says. “If I’m on Instagram, it’s because I’m trying to get you onto my email list, and if that’s not going to happen, it’s probably not worth doing.” The automation stack described below only works if that list exists and stays clean.

Why start with exactly 5 workflows

The temptation is to map out twelve automations, buy a CDP, and spend six weeks in configuration. That is the mistake. Operators on r/restaurantowners describe the same failure pattern over and over: they started with the most complex workflow, stalled halfway, and came back a year later with nothing live. One automation that is running and measured beats four that are half-configured and forgotten.

Five is the right number because it covers the full guest lifecycle, acquisition, conversion, retention, advocacy, re-engagement, without overlap. Ship them in this order:

1. Welcome series (acquisition to first conversion)
2. Lapsed-customer reactivation (retention to win-back)
3. Birthday and anniversary (highest-ROI calendar trigger)
4. Post-visit review request (advocacy and reputation)
5. Online-order follow-up (second-order nudge and channel conversion)

Give each flow 10 to 14 days of build, test, and QA. In six to eight weeks the full stack is live. That is the plan.

The email flows are yours to build. The Google Business Profile side, the review replies, Google posts, photo cadence, and ranking checks that decide whether new guests find you at all, is the half most operators never get to. That is the part See Restaurant Velocity pricing, so the weekend you spend on email is not undone by a stale profile.

The model assumes a single independent with about 1,500 reachable past guests and a $32 average ticket. Birthday automation wins because it fires on a date the guest already cares about and needs one hour to build once. Lapsed-customer win-back is second because it reaches the biggest segment on most lists, the 30 to 40 percent who have not visited in 90 days. The review-request flow sits outside the dollar ranking on purpose: it earns its slot through review velocity and local ranking, which compound, so build it in parallel rather than waiting. If you only have one weekend, build birthday and win-back, ship them, and add the rest the next week.

Most guides list the five flows and tell you to start with the welcome series. That is backwards. The welcome series only touches new subscribers, so on a list that grows 40 names a month it works a tiny audience while your largest revenue pools, the guests who already love you, sit untouched. Sequence by payback velocity instead: return per hour of one-time setup. Built that way, the birthday and win-back flows pay for the entire project before the welcome series sends its third email.

The build order: which flow pays back first

Workflow 1, The new-subscriber welcome series

A welcome series is the highest-converting email a restaurant will ever send. Aggregated industry data puts welcome-email conversion at roughly 9x typical promotional campaigns, and a three-email series generates about 90 percent more orders than a single “thanks for signing up” note. The restaurant-industry average open rate sits around 43.6 percent overall; a well-built welcome flow should clear 55 to 65 percent on email one.

One useful reality check before building: restaurant marketing consultant Rev Ciancio calls CRM list growth the “number one golden metric” in restaurant marketing, above impressions, above social followers, above everything else. Roughly 15 percent of a restaurant’s customer base will join a loyalty program or email list, but that cohort typically represents a disproportionate share of total spend. The welcome flow is the moment that 15 percent decides whether the relationship is worth maintaining. Get it right once and the compounding starts immediately. Ciancio also suggests a promotional email cadence of roughly every 10 days, frequent enough to stay present, infrequent enough not to train unsubscribes. In his Restaurant Coach Podcast appearance, Ciancio pushed the point further: “I teach a class on email for restaurants and I love to challenge people, can you write three sentences about your business? If you can write three sentences, I will show you five emails that convert guests into money. Email is not hard. It’s just being consistent.”

Trigger logic

The trigger is a new subscriber entering the list, from the website footer, the Wi-Fi captive portal, the loyalty signup, the reservations form, or the online-order checkout. Filter out profiles that already have a purchase in the last 30 days so returning regulars do not get a “welcome, nice to meet you” message after their tenth visit.

Timing and cadence

Three emails, spread over seven to ten days:

• Email 1, Immediate (within 10 minutes of signup). Warm hello, what the restaurant stands for, one concrete reason to come in this week. Small offer optional, a free side or upgraded drink converts better than a 10 percent discount.
• Email 2, Day 3. Social proof. Best-seller menu items, a signature-dish story, a short quote from a regular. No offer, this is the trust-building beat.
• Email 3, Day 7. Soft deadline on the original offer, plus a specific ask: book a reservation, order online, or follow on Instagram. One clear CTA.

Copy templates

Email 1 subject: “Welcome to [Restaurant]. Your free [side/drink] is inside.”
Body skeleton: One sentence on who the restaurant is. Two sentences on what makes the food different. Offer, expiration, and a button that goes to the reservations page or online order link.

Email 2 subject: “The dish regulars order every single time”
Body skeleton: A short story (80-120 words) about one signature dish. Photo. A line from the chef or owner. No discount. No urgency.

Email 3 subject: “Last call on your welcome offer”
Body skeleton: Restate the offer, restate the expiration, one-sentence reminder of what they missed in emails one and two. Single button.

Setup steps by platform

Toast Marketing: In the Toast dashboard, open Marketing, choose Automated Campaigns, select “Welcome Series.” Toast pre-fills three email slots. Edit subject and body, set the delay between sends (0, 3 days, 7 days), map the trigger to “New loyalty enrollment” or “New email capture.” Toggle on.

Klaviyo: Flows tab, Create Flow, Create From Scratch. Name it “Welcome Series.” Trigger: “Subscribed to List.” Add three email steps with delays of 0 minutes, 3 days, 7 days. Build each email in the drag-and-drop editor. Add a flow filter to exclude anyone with a “Placed Order” event in the last 30 days.

Square Marketing: Square Dashboard, Marketing, Automations. Pick the “Welcome” template, which ships as a single email, add a second and third through “Create Automation,” using “Customer joined loyalty program” or “Customer added to directory” as the trigger. Square does not natively support a three-email cadence in one automation, so build them as three sequential automations each filtered to the previous email’s recipients.

Mailchimp: Automations, Build From Scratch, name the journey, choose the subscribed audience, set trigger to “Signup Form Submitted” or “Tag Added.” Drag in three “Send Email” steps with “Wait” delays between them. Turn on.

Workflow 2, Lapsed-customer reactivation

A win-back flow is the single most profitable automation most restaurants never build. The tricky part is defining “lapsed” correctly. Klaviyo’s default win-back trigger fires at 75 days since the last order, a number pulled from e-commerce norms. For restaurants that window is wrong.

Use concept type:

• Fast-casual / counter-service: lapsed = 30 to 45 days
• Casual dining: lapsed = 45 to 60 days
• Fine dining / destination: lapsed = 90 to 120 days
• Coffee / breakfast: lapsed = 14 to 21 days

Operators on r/restaurantowners repeatedly flag the mistake of segmenting too wide, blasting a 90-day-lapsed offer to guests who last visited on Tuesday burns the list and trains unsubscribes. Define the window for the specific concept, not the platform default.

Matt Plapp, CEO of America’s Best Restaurants and author of Restaurant Marketing That Works, illustrates what happens when win-back messages are sent without segmentation in his YouTube series on restaurant email and text marketing. He describes a franchise client that sent a text blast to 4,000 customers promoting opening day of the NBA season, without filtering by gender, location interest, or sports preference. His estimate: only about 500 people on that list actually cared about the message, meaning 3,500 received an irrelevant text and many opted out. “You just burned up the valuable opportunity to send somebody a text,” Plapp says. His segmentation framework for win-back sequences: first divide the list by new, frequent, and lapsed status using a single intake question, then layer demographic data (male/female, kids/no kids, lives near/works near) to tighten who gets which reactivation message.

Timing and offer ladder

Three-message sequence triggered at the lapsed threshold:

• Message 1 (day 0): Soft hook, no offer. A seasonal menu note, a new chef story, a re-introduction. The job is to re-open attention.
• Message 2 (day 5-7): The offer. Free appetizer or dessert works better than a percentage-off coupon because it feels like a gift, not a discount. Expiration inside two weeks.
• Message 3 (day 12-14): Final-chance message. Shorter body, urgency subject line, same offer with the original deadline.

If SMS is in the stack alongside email, add a single SMS to the sequence between message 2 and message 3. Toast data shows a 12 percent reactivation rate for SMS win-back versus 4 percent for email alone. Square’s 2025 operator report found that combining email and SMS on the same campaign drives 2.3x more revenue per campaign than either channel alone. That lift is largely concentrated in win-back and birthday flows, the highest-intent moments where a second-channel nudge tips the decision. Restaurant marketing practitioner Matt Plapp documented one client win-back campaign (May to November 2024) that recovered 476 lapsed customers for $16,660 in attributable profit, a result driven by the combined email plus SMS sequence.

Copy template

Subject (message 1): “We changed the menu. Thought you should know.”
Subject (message 2): “A [signature dish] is on us when you come back.”
Subject (message 3): “Your [dish] expires Sunday.”

Setup in each tool

Toast: Marketing, Automated Campaigns, “Win Back.” Set the inactivity window (days since last visit) to 45, 60, or 90 depending on concept. Toast fires when a guest crosses the threshold and has not visited since.

Klaviyo: Create Flow, trigger “Placed Order.” Add a profile filter: “Placed Order zero times since starting this flow.” Set the first time delay to your concept’s lapsed window (45, 60, 90 days). Add three email steps.

Square Marketing: Use the “Lapsed Customer” automation template. Set the window in the “Days since last visit” field.

OpenTable GuestCenter: Guest Marketing, automated campaigns, choose “We miss you.” Filter by “Last visit more than X days ago.” Messages send through OpenTable’s native email tool.

Workflow 3, Birthday and anniversary offers

Birthday automation is the highest-ROI flow in the restaurant playbook. Paytronix published a regional QSR case study showing a 47 percent redemption rate on birthday rewards, roughly 3x the typical promotional baseline, and a separate Paytronix loyalty dataset puts the visit-frequency lift at 26 percent higher in a guest’s birthday month compared with their non-birthday months. Popmenu’s 2025 restaurant data points to an average $42 per redemption and a 35 percent redemption rate across its client base. Those numbers are not outliers; they are what a correctly timed birthday flow delivers across concept types.

Why birthdays work (and why most restaurants get them wrong)

The guest is already planning a celebration. The competing restaurants within a five-mile radius that are not sending a birthday message are ceding the choice. The most common mistake is timing, sending the offer on the birthday instead of seven to ten days out. Guests need time to plan a reservation, coordinate friends, and decide. A same-day message reaches someone whose plans are already locked.

Timing and offer

Send the first email 7 to 10 days before the birthday. Include a specific redeemable offer, free dessert, complimentary entrée for the birthday guest, or a free bottle of wine with a group of four. Anniversary flows (wedding anniversary, dining anniversary since first visit) follow the same pattern and convert almost as well for fine-dining concepts.

Send a single reminder 3 days before the birthday if the first email was not opened. Do not send after the date passes.

Setup by platform

Toast Marketing: Automated Campaigns, Birthday. Toast requires month and day on the guest profile (capture at loyalty signup or reservation). Set the send window to -7 days.

Klaviyo: Flow trigger “Date Property,” select birthday field, choose “X days before.” Add a second conditional email 3 days before, with a split that excludes anyone who opened email one.

Square Marketing: Loyalty signup must capture birthday. Build an automation with “Customer birthday” trigger, send 7 days before.

OpenTable: Guest Marketing, automated campaign, “Birthday.” OpenTable offers a 7-day pre-send by default.

Marsello: Marketing, Automations, Birthday Flow. Schedule relative to the birthday field captured at loyalty enrollment.

Workflow 4, Post-visit review request

Automated review requests are where most restaurants miss easy Google Business Profile lift. SevenRooms data suggests restaurants automating post-visit feedback recover roughly 8 percent of dissatisfied guests before they leave a public negative review. That is not a vanity stat, that is reputation insurance that pays for the whole automation stack.

Timing

For dine-in, SMS within 1 to 2 hours of the check closing consistently outperforms next-morning email. Practitioners on reputation-management forums report roughly 3x review-volume lift after moving from next-day email to same-evening SMS. For online orders and delivery, wait 2 to 4 hours after the delivery confirmation, not immediately after, so the guest has actually eaten the food.

A compliant feedback flow (not “satisfaction gating”)

You may have read about “satisfaction gating” or an “NPS fork”, a pattern where happy guests get routed to Google and unhappy guests get routed to a private form instead of Google. Do not build that. Google explicitly prohibits selectively soliciting reviews only from satisfied guests, and the FTC finalized a rule in 2024 making the practice unlawful. Building that flow exposes the restaurant to a Google penalty and federal enforcement risk.

The compliant approach is simpler and still recovers dissatisfied guests before they go public:

1. Initial message asks: “How was tonight?” with a 1-5 tap.
2. All guests, regardless of score, receive the Google review link in the next step.
3. Guests who scored 1-3 also receive a second message: “We’re sorry it fell short. Here is how to reach us directly.” This is an additional channel, not a gate that replaces the public review link.

This approach still recovers roughly 8 percent of dissatisfied guests (SevenRooms data) because most guests who feel heard privately choose not to post publicly. The difference is the unhappy guest always has the Google link available, the internal feedback form is offered alongside it, not instead of it. That is the line Google and the FTC draw.

Setup

Toast: Toast Reviews (separate module from Marketing) fires post-check. Enable SMS and set the delay to 2 hours post check-close. Integrates with Google directly.

OpenTable: Guest Feedback, automated post-visit email. OpenTable triggers off the reservation completion rather than the POS check.

Marsello: Automations, “Post-visit Review,” triggered by order completion in Lightspeed Restaurant.

Third-party: Birdeye, SevenRooms, and GatherUp all integrate with Toast, Square, and most reservation systems for more advanced satisfaction gating. If reviews are a top-three priority, a dedicated tool often outperforms the native POS flow.

For deeper tactical coverage on this specific flow, see our guide to Google reviews for restaurants and how a compliant post-visit feedback flow integrates with a broader local-SEO play.

Workflow 5, Online-order follow-up and third-party conversion

Every DoorDash, Uber Eats, or Grubhub order is a missed email capture unless the restaurant has a sequence designed to pull that guest into its direct channel. Olo’s operator framing is the clearest on this: third-party delivery is a leaky bucket, and the only way to stop the leak is to convert those guests to direct orders. Operators on r/smallbusiness describe third-party-to-direct conversion as the single highest-leverage move most restaurants never make.

The trick is that third-party platforms mask customer emails. The capture has to happen on the packaging or the in-bag insert, then the automation carries the conversion.

The physical capture

Every delivery order ships with an in-bag card that offers a small incentive (free side, 15 percent off, a free drink) in exchange for joining the email list through a branded QR code that goes to the restaurant’s direct-order page. This is the single most important offline-to-online automation trigger in the stack.

The automation sequence

1. Email 1, Signup confirmation (immediate). Deliver the promised incentive, and frame the direct-order benefit (5-10 percent cheaper than third-party, better tips to the kitchen, loyalty points).
2. Email 2, Day 7. Second-order nudge. “We noticed you haven’t tried the [dish]. Here is 10 percent off your next direct order.”
3. Email 3, Day 21 if no second order. Final nudge, stronger incentive ($10 off $30, or free delivery through the direct platform).

Setup

Most restaurants build this flow in their direct-ordering platform’s email tool (Toast Online Ordering, Olo, ChowNow, Square Online) rather than a standalone ESP, the attribution is cleaner. Trigger the sequence on “First online order completed” and filter subsequent messages on “Placed Order zero times since starting this flow.” The copy and incentive ladder matter more than the platform; the sequence is what drives the second order.

For restaurants using Klaviyo with an online-ordering integration, a browse-abandonment or cart-abandonment trigger can be added upstream of this sequence, fire when a guest opens the online menu but does not complete checkout. Klaviyo’s case study with specialty roaster Grind (UK) reported a 12.3 percent conversion rate on abandoned-cart flows and attributed 71 percent of their email-driven repeat revenue to automated flows rather than campaigns. The food-service context is different from retail, but the principle holds: the triggered sequence targets guests at maximum purchase intent, where broadcast sends cannot reach them.

For operators expanding their overall stack beyond these five flows, our roundup of the best restaurant marketing tools covers POS, reservations, reviews, and loyalty platforms that play well with this workflow. If email is going to do heavy lifting, start with our deeper tactical piece on restaurant email marketing.

Tool comparison: Toast, Square, Klaviyo, Mailchimp, OpenTable, Marsello

There is no universally right tool, the right one depends on the POS, the concept type, and whether the operator wants marketing inside the POS or as a separate stack. The comparison below is the honest version, not the vendor-deck version.

The shortest decision path: if the POS is Toast, start with Toast Marketing. If it is Square, start with Square Marketing. If it is Lightspeed, start with Marsello. If reservations are the primary channel, add OpenTable’s automation layer. Layer Klaviyo on top only when the list crosses ~5,000 contacts or the group is managing multiple concepts.

An honest take, where restaurant marketing automation fails

The glossy version of this topic says “set it and forget it.” The practitioner version is more honest: automation amplifies whatever the underlying data and copy are doing. If the guest list is messy, the flows are messy at scale. If the welcome email reads like a vendor wrote it, the welcome flow loses trust at scale.

Three specific failure modes show up across most of the restaurants we audit:

1. Data fragmentation. The POS has one guest record, the reservation tool has another, the email platform has a third. A guest who visited last Friday gets a 45-day “we miss you” message because the reservation write-back never hit the email tool. The fix is a single source of truth, usually the POS CRM, and a weekly sync audit. Without that, automation fires at ghosts.

2. Over-automation. The restaurant adds a welcome flow, a win-back, a birthday, a post-visit review, an online-order nudge, an abandoned cart, a reservation reminder, a no-show recovery, and an anniversary all in the first 60 days. None of them get measured. Unsubscribes spike. The solution is to ship five, measure for 30 days, then decide what to add.

3. AI-speak in templates. Automation templates shipped by platforms are generic, “We value your business” energy. Every template needs a 20-minute rewrite in the operator’s actual voice before it goes live. The AI-flavored hospitality copy is a tell; guests feel it even when they cannot name it.

The 2025 Restaurant Business Online piece cited earlier, 9 percent of AI-using chains reporting meaningful impact, should be read as a caution, not a reason to skip automation. The flows above are not AI. They are rules plus copy plus clean data. That combination works today. The pure-AI layer on top (predictive send time, AI-generated subject lines, AI chatbots) is still more promise than proof.

Where operators do break through: segmenting by RFM (Recency, Frequency, Monetary value) rather than blasting the whole list. Pablo & Rusty’s, an Australian multi-location coffee group, reported a 10.8 percent increase in visits from their highest-value loyal segments after switching from broadcast campaigns to RFM-based triggered flows. The lift came entirely from personalizing the trigger logic, same tools, same list, different segmentation. On the SMS channel specifically: Omnisend’s 2024 benchmark data shows automated SMS averaging $0.74 revenue per send versus $0.15 for broadcast SMS campaigns. The 5x premium is the compounding effect of send-time relevance, the guest is in the right mindset when the message arrives.

Benchmarks every operator should track

Five flows, five numbers. If a flow is under the low end of these ranges for two months straight, it needs a rebuild, not a tweak.

Total revenue attribution across the five flows should land between 12 and 20 percent of total annual revenue for a restaurant that has run them for at least six months with a clean list. Below 10 percent usually means data hygiene is off. Above 25 percent usually means the list is small and the numbers are compressed, still a good sign, just less comparable to industry averages.

Pair these automations with a seasonal campaign cadence, new menus, holiday sends, events, and plan that cadence on a real calendar. Our 2026 restaurant marketing calendar maps monthly promotional beats that slot around the triggered flows without overlapping.

Common mistakes we see

Sending birthday offers on the birthday. Guests need 7 to 10 days to plan. Same-day sends catch people whose evening is already booked.

Using a 75-day default for win-back. Klaviyo’s default is tuned for e-commerce. A fast-casual restaurant should fire at 30 to 45 days; a coffee shop at 14 to 21.

One big welcome email instead of three. A single “thanks for signing up” email under-converts a three-email series by roughly 90 percent in aggregate order volume.

Building a hard satisfaction gate on review requests. Routing happy guests to Google and blocking unhappy guests from the review link is prohibited by Google’s ToS and was codified as unlawful by the FTC in 2024. The compliant version offers internal feedback alongside the Google link, not instead of it. The recovery rate is similar; the legal exposure is not.

Not capturing third-party delivery guests. Every DoorDash order without an in-bag capture card is a lost email. That guest is DoorDash’s customer until the restaurant gives them a reason to be direct.

Copy that sounds like the platform wrote it. “We value your business” does not convert. Specific, voice-matched copy does. Every template needs a rewrite.

These five workflows are a tactical layer inside a broader plan. For the larger strategic frame, how automation fits alongside SEO, paid, and local marketing, see our pillar on digital marketing for restaurants.

Frequently asked questions