Automated loyalty campaigns: welcome, near-reward, win-back
Three standing campaigns do most of the work of a loyalty program, and none of them can be sent by hand at the right moment. Here is how each one is built.
Almost every useful loyalty message is useful because of when it arrives.
“You’re two stamps away” only works on the day it becomes true. A welcome only works while someone still remembers joining. A win-back only works in the window between someone drifting and someone forgetting you exist. None of these are things you can send by hand. The right moment is different for every customer, and it never coincides with the moment you have time to sit down with the customer list.
That is the entire case for automation in a small shop. Not scale (you do not have a scale problem) but timing.
Key takeaways
- Three standing campaigns cover most of the value: welcome, near-reward, and win-back.
- An automation is a trigger, an optional wait, and a message. That is the whole shape.
- Near-reward is the highest-return one and the one most shops never build.
- Set the win-back delay from your own average visit interval, not a round number of days.
- Cap how many automations one person can be in. Three well-timed messages in a week is still three messages in a week.
What an automation actually is
Strip away the diagrams and it is three parts:
- A trigger. Something the customer did, or something that became true about them: they joined, they visited, they reached the eighth stamp, they have not been in for twenty-one days.
- A wait, optionally. An hour, a day, three weeks.
- A message, on the channel that suits it. A push notification to the card in their wallet, an email, or a text.
Some steps can also move the customer’s progress: a bonus stamp as a welcome, for instance. But the useful mental model is: when this becomes true, wait this long, then say this.
Everything below is a variation on that shape.
1. Welcome
Trigger: someone joins. Wait: none, or an hour. Message: what they are collecting and how far off the reward is.
The most fragile moment in a loyalty program is the week after someone signs up. They scanned a code at a counter, they have a card on their phone, and unless something reminds them what it is for, they will not think about it again.
Say three things and nothing else: what the reward is, in the words they would use; how many visits away it is; and that there is nothing to install. If you can give a first stamp on the house, do. Starting a card already in progress measurably improves the odds it gets finished, which is the endowed progress effect and the most reliable finding in this field.
One message. A welcome series of four is a shop talking about itself.
2. Near reward
Trigger: the customer reaches a set distance from the reward: two stamps off a ten, three off a twenty. Wait: none. Message: that they are close, and what is waiting.
This is the highest-return automation available and the one most shops never build, presumably because it feels too small to bother with.
It works because it is not persuasion. The customer already wants the reward and has already done most of the work; they simply have not looked at the card lately. You are closing an information gap, not changing a mind.
It also lands on people who are already speeding up. A café loyalty-card study by Kivetz, Urminsky and Zheng (Journal of Marketing Research, 2006) found purchase rates rose as customers approached the reward, the goal-gradient effect. Your message arrives on an accelerating customer, which is the cheapest possible audience.
Keep it to once per card. Two “you’re nearly there” messages is nagging.
3. Win-back
Trigger: days since last visit passes a threshold. Wait: built into the threshold. Message: one genuine reason to come back.
The one that needs the most thought, because the threshold is doing all the work.
Set it from your own average interval, not a round number. Thirty days is meaningless in the abstract: it is a catastrophe for a daily café customer and early for a salon. The rule of thumb that travels:
| Your typical interval | Nudge at | Real offer at |
|---|---|---|
| Daily to twice weekly | 10–14 days | 3–4 weeks |
| Weekly | 3 weeks | 6 weeks |
| Fortnightly | 5 weeks | 10 weeks |
| Every 6–8 weeks | 10 weeks | 4 months |
Two stages are better than one. The first is a light nudge with no offer attached: most people have simply not got round to it, and discounting for them is money wasted. The second, for anyone still absent, is where a real offer earns its cost, because the alternative is losing them.
After that, stop. A monthly reminder to someone who left is a monthly reminder that they left.
A fourth, if you collect birthdays
Trigger: birthday, minus a few days.
Worth building if your join form asks for a birthday, and worth keeping that field optional so it does not cost you sign-ups. A birthday message converts well because it arrives on a day someone is already planning to go somewhere, and it is one of the few promotional messages people are actively pleased to receive.
Send it a few days early so it can be acted on, not on the morning itself.
Guardrails
Automations run without you, which is the point and also the risk. Three rules keep them from turning into noise:
One person, one message a fortnight, across every channel. A push, an email and a text in the same week is three interruptions, whatever the dashboard calls them. Build the campaigns separately, then check the overlap. A customer who joined, got near the reward, and lapsed slightly could plausibly be in three at once.
Never during your rush. A push at eight on a Saturday reaches people who were already coming and interrupts a shift that does not need it. Send into the quiet hours you are trying to fill.
Write them as if to one person. The message appears on a lock screen next to messages from friends, and it will be judged on the same terms. The craft of that is writing a message people do not delete.
How the message arrives
A push notification reaches the pass in Apple Wallet or Google Wallet, which is why this works without an app: the customer already has the software, and the card updates in place.
The two platforms handle notifications differently enough to matter when you are writing them. The mechanics, and what each one will and will not show, are in Apple Wallet vs Google Wallet.
Choosing the channel
Push is not the only option, and the automation should use whichever channel suits the moment.
| Channel | What it suits | In these campaigns |
|---|---|---|
| Push | Anything true right now | The near-reward nudge, an offer that ends today |
| Staying in touch between visits | The welcome, a monthly regulars’ offer, anything worth more than a line | |
| SMS | The message that has to be seen | The win-back, an appointment reminder, a last-minute table |
The rule of thumb: if it stops being true tomorrow, push it. If it deserves more than one line, email it. If the visit is worth real money and silence costs you it, send a text.
Email and SMS need consent that push does not, because the customer gave you an address or a number rather than just a card. Ask for it on the join page, and keep the reason obvious.
Measuring them
Judge each automation on the behavior it was built to change, not on opens:
- Welcome: what share of new members reach a third visit.
- Near reward: what share finish the card, against members who were not nudged.
- Win-back: what share return within a fortnight of the message.
Leave each one running unchanged for two full card cycles before you judge it. Automations that get rewritten monthly never accumulate enough evidence to tell you anything, and the underlying numbers are slow by nature. What each of those numbers means when it goes wrong is covered in loyalty program metrics.
Frequently asked questions
How many automations should a small shop run? Three. Welcome, near-reward, win-back. Add a birthday if you collect the date. Past four, the overlap problem gets harder to reason about than the extra campaign is worth.
Should I automate a message on every visit? No. A notification confirming something the customer just did, while they are standing in your shop, is the fastest way to get the pass muted.
Do automations replace one-off campaigns? They cover the recurring moments. One-offs still earn their place for things tied to a date (a new menu, a quiet week, a fixture) aimed at the right segment.
What if someone qualifies for two at once? Decide the priority in advance. Near-reward usually beats win-back, because someone close to a reward has a better reason to return than a generic offer gives them.
How soon after joining should the welcome go out? Within the hour, while they still remember scanning the code.
Where to go next
Automations are the last of the four building blocks: get people onto the card, sort them into groups, send the right thing at the right moment, then read the numbers. Those are enrollment, segmentation, this page, and metrics, all four in order in the complete guide.
Passumo builds these from a playbook picker, so a welcome, a near-reward nudge and a two-stage win-back can be running the same afternoon you set the card up.