“Haven’t tried us yet?” The rare restaurant email that notices what you haven’t done

Almost every email a restaurant sends is keyed to the calendar. A welcome fires at signup. A promotion fires on Tuesday. A holiday send fires on the holiday. The subscriber’s own behavior rarely enters into it.

Smalls Sliders wrote to a subscriber about something she had not done yet. A week after she joined, before she had placed a single order, its email opened with a question: “Haven’t tried us yet?”

It is a small line. It is also one of the only emails in our study that responded to the subscriber rather than to a date.

We tried to join more than 300 quick service and fast casual email, loyalty, and lifecycle programs by hand, using one identity and one inbox. This post looks at the brands that wrote to where the subscriber actually was, and why so few do.

What Smalls Sliders sent

Smalls ran a simple, well-paced sequence across its first two weeks.

Three things stand out.

1. The welcome starts her with something. Seeding 100 points at signup means her first view of the program is progress, not a zero balance.
2. The follow-ups are written to her actual state. She had joined and not ordered. Both follow-up emails say exactly that, in the brand’s own voice, without guilt or pressure.
3. The rhythm is weekly. Day one, day eight, day fifteen. Enough space that each message reads as a check-in rather than a chase.

From the outside, a subscriber cannot see whether an email like this is triggered by “no first order yet” or by a timer that happens to fit. What matters is that the copy describes something true about the person reading it. That is rare in this category, and it is why these emails land.

Chipotle wrote the same kind of email

Smalls is not alone, and the second example is one of the largest brands in fast casual.

On day ten, Chipotle sent:

Subject: “Haven’t ordered yet? Here’s what you’re missing.”

Preview: “Real ingredients. Responsibly raised. No shortcuts.”

It is the same idea from a very different brand. Chipotle does not repeat the discount or lead with an offer. It uses the moment to make the case for the food itself.

Two brands of very different size reached the same conclusion: a new member who has not ordered is a specific person in a specific situation, and deserves an email written for that situation.

The most useful signal is one every brand already has

Here is the part that makes Smalls especially instructive. Smalls runs on a loyalty platform where every brand we joined collected an email address and nothing else. No birthday, no ZIP code, no favorite location.

Smalls held almost nothing about the subscriber, and it still wrote her one of the most responsive emails in the study. It used the one fact every restaurant knows about every member: whether she has ordered.

The same goes for offers. A brand that issues a welcome code knows whether that code was redeemed. Peet’s Coffee, Chipotle, Jeni’s, and Firehouse Subs all used that knowledge to follow up before their welcome offers expired. None of them needed a new integration, a new data source, or a model. They needed a rule and a message.

What this means if you run one of these programs

• Write one email for the member who has not ordered yet. It is the most common state a new subscriber is in, and almost nobody addresses it directly.
• Match the tone to the moment. “Haven’t tried us yet?” is friendly, not a guilt trip. “Still thinkin’ about it?” keeps the voice light on the second nudge.
• Start the balance above zero. Smalls seeded 100 points, so the first thing a member sees is momentum.
• Use the signals you already own. First order, first redemption, and an unredeemed code are all behavioral triggers that need no new data.
• Space the nudges. A week between check-ins reads as attention. A day between them reads as pressure.

The gap this points at

Responding to behavior sounds like it should require sophisticated data. The brands in this post show it does not. What it requires is content for more than one situation: one version for the member who ordered, another for the member who did not, and eventually a version for every state in between.

That content has traditionally been the bottleneck, because each new version meant a new build. Blings removes that step. A Dynamic Master is built once, and each variant is generated on demand at the Moment of Open from data that never leaves the brand’s own stack. Build once, personalize forever.