A fast-casual brand launches loyalty with a free entrée for every new member. Sign-ups climb, and the dashboard looks great for months. Then someone asks a simple question: how many of those members came back and paid for a second meal without an offer attached? No report can say. The guests who joined for the free entrée and never returned are counted as “active members” and receive the weekly promotion alongside the regulars who order twice a week. Both groups get the same discount. One group doesn’t open it. The other would have ordered anyway.
The data to separate those guests existed the whole time. What was missing was an agreed definition of who a new guest is, who a regular is, and what should happen when someone drifts from one to the other.
Why restaurant marketing struggles with the lifecycle
Restaurants have more behavioral data than most businesses. Every order carries a time, a location, a channel, a basket and a spend. Volume is rarely the issue. The data lives in several places, each guest appears in it under different identities, and marketing still runs on a calendar: the new menu item, the holiday promotion, the slow-Tuesday offer.
Calendar campaigns have their place. In a lot of brands, though, they’re the only thing running, so the moments that actually decide whether a guest becomes valuable go unnoticed. The second visit. The regular whose visits start to space out. The guest who had a bad experience and hasn’t been back.
The guest lifecycle, stage by stage
First order
The first order is mostly about identity and consent. Can you tie this order to a person you can recognize next time, and do you have permission to contact them? Digital orders usually carry an email or phone number. Dine-in guests paying by card at the counter often remain anonymous unless they scan a loyalty code or give a phone number. Orders that come through third-party delivery marketplaces typically arrive with limited guest data and no marketing consent for your brand, so those guests are hard to bring into the lifecycle at all.
That’s why many brands treat “convert a marketplace guest into a direct guest” as a goal of its own. It’s also why the welcome message after a first direct order matters. It should introduce the brand and the reasons to order direct, rather than immediately teaching a new guest to wait for discounts.
Second visit
For most concepts, the second visit is the conversion that matters most. A guest who comes back once has shown the meal fits their routine. A guest who never comes back is an acquisition cost with nothing to show for it.
The question is when to step in. The right window depends on your concept and daypart. A coffee and breakfast brand might expect a returning guest within a week or two. A pizza brand’s natural rhythm is often weekly or every other week. A sit-down concept might see guests monthly at best. We look at your own order history to see when returning guests usually come back, then trigger a second-visit message a little after that point for guests who haven’t.
Regular
Regulars don’t need persuading, and discounting them is mostly a margin leak. They need recognition: a reward that feels earned, early access to a new menu item, a note when their favorite item comes back seasonally. They also need protection from over-sending. A guest who orders four times a week can easily end up in a dozen campaigns in a month unless something is counting.
We define “regular” by frequency over a recent window, sometimes adjusted for spend, and build a frequency cap so the most valuable guests hear from you least often but most relevantly.
Lapsed
A guest is lapsed when they’ve gone noticeably longer than their own normal gap between orders. A weekly guest who hasn’t ordered in a month is a much stronger signal than a quarterly guest who hasn’t ordered in a month. Brand-wide cutoffs such as “no order in 60 days” miss the first and wrongly flag the second.
Before sending anything, it’s worth checking why the gap appeared. Their usual location might have closed or changed hours. A favorite item might have come off the menu. They might have moved. Some of those are fixable with a message, and some mean the guest should be steered to a different location instead of offered a discount.
Win-back
Win-back works best as a short ladder with an end. A reminder first, then perhaps an offer, then a stronger offer for guests whose past value justifies it, and then a stop. Guests who don’t respond after the ladder should move to a low-frequency state instead of receiving promotions forever, which protects your email deliverability and your SMS opt-out rate.
- No order past guest's usual gap
- Location still open and serving their items?
- Past value above threshold?
- Send reminder, then offer, then stop
Where restaurant guest data comes from
A useful guest profile is usually assembled from several sources, and each one has its quirks.
- Online ordering (website and app) is normally the richest source: identified guests, full order detail, channel, location and time.
- POS transactions cover dine-in and counter orders but are often anonymous unless linked to a loyalty account or a phone number.
- Loyalty holds membership, points or visits, rewards issued and rewards redeemed.
- Marketplace orders add volume to reports but rarely add marketing-ready guests.
- Feedback and surveys add sentiment, which should be able to stop a promotion and start a service-recovery message.
The hardest part is identity. The same guest might order online with a work email, join loyalty with a mobile number and pay in store with a card. Before building any segment, we decide which identifier is primary, how profiles are matched, and which system holds the master guest record. If your brand uses Olo, its guest engagement products bring much of this together; if loyalty, email or SMS run on separate platforms, we work out how status and consent stay consistent across them.
How should loyalty and marketing work together?
Loyalty and marketing should work from the same guest states and the same calendar, so a guest never receives a reward and a contradictory promotion in the same week. In practice they’re often run by different people or vendors, and that’s where the trouble starts.
A few rules prevent most problems. Agree which offers can stack with rewards and which can’t. Exclude guests who’ve just redeemed a large reward from discount campaigns for a short period. Use loyalty milestones, such as a tenth visit, as lifecycle triggers rather than just point balances. And measure loyalty by whether members visit more often than comparable non-members, not by how many people signed up.
Not sure who your regulars actually are?
We'll review your guest segments, journeys and loyalty rules and show which guests are being misclassified or over-messaged.
Multi-location and franchise realities
Restaurant brands with many locations have lifecycle questions a single site doesn’t. Each guest usually has a home location, and their messages should reflect its menu, hours and promotions. When a location closes, its guests need a deliberate handoff to the nearest open one, not silence followed by a win-back offer for a restaurant that no longer exists. When a new location opens, existing guests nearby are often the best first audience.
Franchise systems add ownership questions. Who can see guest data, who decides on local offers, and how brand-wide journeys respect local promotions? We document those rules alongside the automation, because they change what the system is allowed to do.
How do you measure whether guest marketing is working?
Measure what guests do after a message, not what they do with the message itself. Open rates and click rates tell you very little about whether a guest came back for dinner.
The measures that matter are lifecycle movements: the share of first-time guests who return within the expected window, visit frequency among regulars, the share of lapsing guests who order again, and revenue per guest over time. Where volume allows, a holdout group, a small slice of each audience that doesn’t receive the journey, is the most honest way to see whether a win-back offer brought guests back or simply discounted orders that would have happened anyway.
How we approach restaurant work
By the time a restaurant brand thinks about its guest lifecycle, ordering is usually live, loyalty is running and campaigns are already going out. So we start by reviewing what exists: data sources, guest identity, segments, active journeys, loyalty rules, consent handling and reporting. Then we agree the guest lifecycle with your team, usually in a working session with marketing and operations together, and rebuild the journeys that matter most first. The second-visit and lapsed-guest journeys are typically where we begin.
This is lifecycle automation applied to guests instead of leads, and it often starts with a CRM Audit adapted for guest data. We focus on the marketing and data side. Ordering configuration, menus and POS setup stay with your existing technology partners.
What counts as a regular guest?
A regular is a guest who orders at or above your brand’s typical repeat frequency over a recent period, for example several times in the last month for a quick-service concept. The exact threshold should come from your own order history, and it’s often worth a separate definition per daypart or channel.
Should win-back messages always include a discount?
No. Start with a reminder or a reason to return, such as a new menu item or a reward they already have. Reserve offers for guests whose past value justifies them, and stop after a set number of attempts so lapsed guests aren’t trained to wait for a discount.
Can dine-in guests be part of the lifecycle?
Yes, if they can be identified. Linking POS transactions to a loyalty account or phone number brings dine-in visits into the guest profile. Anonymous card payments generally can’t be used for individual marketing, and shouldn’t be.
Do you work with franchise brands?
Yes. Franchise work adds decisions about data access, local promotions and which journeys run brand-wide versus by location. We document those rules as part of the build.
Will you change our ordering or POS setup?
No. We work on guest data, segments, loyalty logic and automated communication. Ordering, menus and POS connections stay with your ordering provider and technology partners.
Which platforms do you work with for restaurants?
We work with Olo and with the email, SMS and loyalty tools restaurant brands commonly connect to their ordering data. The lifecycle approach doesn’t depend on the platform, so we’ll review your current stack before recommending any changes.