Birthday and milestone messages worth sending
The two automated messages nobody minds getting, why they still need a channel and a cap, and what to send on a customer's birthday and their fifth visit.
Most of what a loyalty program sends needs a judgment call first. Has this person actually lapsed, or are they just on a longer cycle? Is this the right segment for a message, or noise for everyone else on the list?
Two messages skip that step entirely. A birthday and a milestone visit do not need segmentation, a threshold, or a guess about whether the moment is real. Everyone qualifies, on a date nobody has to infer.
That makes them easy to get right and, just as easily, easy to send badly: generic, over-timed, or piled on top of everything else a customer already gets that week.
Key takeaways
- A birthday and a milestone visit are the two automations that need no targeting judgment. Every member qualifies, on a date the program already knows.
- Collecting a birthday at signup should stay optional. It is a bonus channel, not a condition of joining.
- A milestone visit is not just a nice gesture. Research on goal-gradient behavior finds people act faster as they near any tracked goal, and marking the goal itself is part of what keeps that pull working.
- Birthday suits SMS. Milestone suits push, with a small reward attached. Neither earns a discount-first framing.
- Both still count against the same messaging cap as everything else. A birthday does not buy an exemption from it.
Why these two need no judgment call
Win-back messages only work once you can tell a customer who has actually gone quiet from one who is simply on a longer cycle. Segmentation exists because that distinction is not obvious from the visit count alone.
A birthday carries none of that ambiguity. It happens once a year, on a date the customer supplied. A milestone visit is a plain count: the fifth stamp, the fifth visit, however the program marks it. Neither needs a model of behavior, just a calendar and a counter.
That is also why both are worth automating first. Automated loyalty campaigns covers the welcome message and the near-reward nudge, the two triggers that fire while the relationship is still new. Birthday and milestone are the pair that keep firing for years after that, on their own, without anyone deciding anew each time whether this customer deserves one.
The birthday message
Collecting a birthday costs a field on the join form, and it should stay optional. Passumo’s join page asks for it as one line among several, not a requirement. That matches getting opt-in’s case against any signup field that is not load-bearing. Every extra required box is a reason someone abandons the form before joining at all.
For the customers who do give it, the message writes itself. Something short, timed to the day, that names the trade rather than reading like a template:
Happy birthday! Your cake's on us this week.
Passumo’s default birthday automation fires once a year, on the date the customer gave you, and sends it over SMS.
That fits the channel’s job. A birthday message is not urgent in the way a same-day offer is. It is personal enough, though, to earn a text rather than sit in an inbox until it is opened, if it is opened. Push, email or SMS covers the general case; a birthday is one of the clearer examples of a message worth paying to send.
Keep the reward proportionate. A free item or a meaningful discount on something the customer already buys reads as a genuine thank you. A percentage off their entire bill starts to look like every other promotional text they get once a month. A birthday message that reads as routine promotion has lost the one thing that made it worth sending.
The milestone message
A milestone automation watches the visit count and fires once, at a set number, most commonly the fifth visit. Passumo’s default pairs a push notification with a small bonus on the card itself, usually a stamp, though points or a discount work too if that is what the card runs on. A single automation can also cover several milestones at once (the 5th, 10th and 25th visit, for example), each getting the same thank you.
Nothing about the number 5 is fixed: a business on a slower cycle, a salon or a barbershop, can move it further out and it still lands as a real milestone rather than a stretch.
The reason to bother is not just goodwill. Ran Kivetz, Oleg Urminsky and Yuhuang Zheng tested the goal-gradient hypothesis, the finding that people accelerate their effort as they get closer to a tracked goal, using field data from a café stamp card among other studies (“The Goal-Gradient Hypothesis Resurrected: Purchase Acceleration, Illusionary Goal Progress, and Customer Retention”, Journal of Marketing Research, Vol. 43, No. 1, February 2006, pp. 39 to 58). The pull toward a visible goal is what a stamp card is already using. A milestone message adds a second one: reaching the milestone itself becomes a marker worth noticing, not just a step on the way to the reward at the end of the card.
That argument does the work only if the notification still lands close to the moment. Passumo checks for a milestone once a day rather than the instant a visit is logged, so the message can trail the visit itself by up to a day, not by a week. A “you hit five visits” message that arrives the next morning still reads as recognition. One that turns up after the customer’s next two visits does not.
Which channel carries each one
| Message | Channel | Why |
|---|---|---|
| Birthday | SMS | Personal enough to be worth paying to send, and not urgent enough to need a lock-screen push |
| Milestone visit | Push | True the moment it fires and stops being interesting a day later |
Neither belongs on email. Push, email or SMS makes the general case that email suits staying connected between visits, not marking a single moment. A birthday and a milestone are both moments.
Both still count against the cap
How often should you message customers? sets the rule that matters here: one message a fortnight per person, added up across every campaign and automation running at once, not per channel. A birthday text does not get a pass because it is personal, and a milestone push does not get one because it was earned rather than sent unprompted.
In practice this rarely collides. A birthday happens once a year and a milestone visit, by definition, happens on a visit the customer chose to make. The case worth planning for is a birthday landing in the same week as a near-reward nudge or a scheduled campaign. When that happens, let the milestone or birthday message take priority. It is the one the customer will notice was missing.
What not to do with either one
Do not lead with a discount. A meaningful reward reads as a thank you. “20% off everything” on your birthday reads like every other promotional blast that happens to mention the date.
Do not send a birthday message with no offer attached. Wishing someone a happy birthday and stopping there is a missed moment, not a lighter touch. The whole reason a birthday message performs is that it is one of the few promotional messages a customer is glad to get; an offer is what makes it promotional rather than merely polite.
Do not treat a milestone as a discount, either. Points, a stamp, or a small free item all read as recognition. A discount code reads as a coupon that happened to arrive on the fifth visit.
Frequently asked questions
Do I need to collect a birthday at signup to use this? Yes, the automation needs the date to fire, but the field should stay optional on the join form. Customers who skip it simply never get a birthday message. Nothing else about the program depends on it.
Does the milestone bonus have to be points? No. A stamp, a small free item, or points all work. Match whatever the card already uses so the bonus looks like part of the same program rather than a separate gesture.
What if a customer’s birthday and a milestone visit land the same week? Send both if the totals stay under the fortnight cap; hold one back if they would not. Either message on its own is welcome. Two personal messages in one week starts to feel like attention rather than a coincidence, which is the good problem to have, but the cap still applies.
Is a milestone worth setting up if most customers never reach the fifth visit? That is worth checking before assuming the automation is not pulling its weight. Loyalty program metrics covers how to read repeat-visit rate, which is the number that answers this directly.
Where to go next
The welcome message and the near-reward nudge that run alongside these two are in automated loyalty campaigns. The cap both messages share with every other automation is the fortnight rule, and the case for SMS specifically is in push, email or SMS.
Passumo can fire both automatically, off each member’s own birthday and visit count, so neither depends on anyone remembering to check. The full set of nine triggers, including these two, is on the automations page.
Source: Ran Kivetz, Oleg Urminsky and Yuhuang Zheng, “The Goal-Gradient Hypothesis Resurrected: Purchase Acceleration, Illusionary Goal Progress, and Customer Retention”, Journal of Marketing Research, Vol. 43, No. 1 (February 2006), pp. 39 to 58. Mixed method, including field data from a café “buy 10, get 1 free” program.