Writing good notification messages
Use variables to personalise wallet notifications, see which variables work with which trigger, and get the tone and frequency right.
A wallet notification lands on someone's lock screen next to messages from friends and family. Short, personal and useful gets read. Long, generic or too frequent gets the pass deleted. This page covers the variables you can use and how to write messages customers are glad to get.
Variables#
Variables fill in details for each customer. Write them inside double curly brackets, or click Insert variable under the message box (or type {{) to pick one from the list.
| Variable | What it shows |
|---|---|
{{ store.name }} |
Your store's display name. |
{{ customer.first_name }} |
The customer's first name. |
{{ customer.last_name }} |
Their last name. |
{{ customer.name }} |
Their full name. |
{{ card.name }} |
The name of the loyalty card. |
{{ card.stamps_required }} |
Total stamps needed to fill the card. |
{{ customer_card.stamps_count }} |
How many stamps they have now. |
{{ customer_card.stamps_remaining }} |
How many stamps are left to fill the card. |
{{ location.name }} |
The nearby location's name. Location-based only. |
{{ reward.name }} |
The reward they've just earned. Reward available only. |
{{ reward.stamps_required }} |
Stamps needed for that reward. Reward available only. |
A variable that doesn't apply to a trigger comes out blank. For example, {{ reward.name }} in a birthday message leaves a gap.
Tip
Customers see the notification comes from your pass, and Google Wallet uses your store name as its title, so you rarely need {{ store.name }} in the message itself. Save the space for what matters.
If something goes wrong#
Leal checks the message when you save and rejects it if a variable is broken, for example a missing }}. If a message somehow can't be filled in when it's sent, the customer gets "Your loyalty card has been updated." instead of an error.
Examples#
| Trigger | Example message |
|---|---|
| Stamp earned | "Thanks {{ customer.first_name }}! {{ customer_card.stamps_remaining }} more to go." |
| Stamp redeemed | "Enjoy your treat! You have {{ customer_card.stamps_count }} stamps left." |
| Welcome | "Welcome, {{ customer.first_name }}! Your first stamp is on the card." |
| Stamps milestone | "Halfway there, {{ customer.first_name }}!" |
| Reward available | "Your {{ reward.name }} is ready! Show this card next time you visit." |
| Birthday | "Happy birthday, {{ customer.first_name }}! Pop in this week for a treat on us." |
| Inactivity | "We miss you, {{ customer.first_name }}. You're {{ customer_card.stamps_remaining }} stamps from a reward." |
| Stamps streak | "Three days in a row! You're one of our regulars now." |
| Location-based | "Passing {{ location.name }}? Your next stamp is waiting." |
Writing tips#
- Lead with the point. Lock screens cut long messages short, so put the reward, the number or the reason in the first few words.
- One message, one idea. Don't combine a thank you, an offer and opening hours.
- Use the first name.
{{ customer.first_name }}makes it feel like it came from you, not from a system. - Include a number that changes. On iPhone, a message that's exactly the same as the last one has nothing new to announce. A stamp count keeps each message different.
- Only promise what staff know about. If a birthday message offers a free drink, make sure everyone at the counter knows to honour it.
- Read the preview. The Lock screen notification preview fills in a real customer's details. Check it reads well with a long name too.
How often is too often?#
Every rule you add is another message on someone's lock screen. Customers who feel spammed don't reply to complain, they just remove the pass, and then you can't reach them at all.
- Keep each rule meaningful. A milestone at every single stamp adds noise. One halfway milestone and a "reward available" message usually say all that needs saying.
- Think about streaks. A Stamps streak rule keeps firing each day the streak continues, so pick a number that's a real achievement for your store.
- Space out inactivity. Choose a number of days that's clearly longer than a normal gap between visits for your customers.
- Let automated rules replace system ones. When an automated rule fires, the Stamp earned message is skipped for that stamp, so customers don't get two messages for one visit.
Gotchas#
- Emoji are fine, but test them. Check how they look in the preview and on your own phone.
- Messages don't change after they're sent. Editing a rule only affects future notifications.
- Unsubscribing from campaigns doesn't stop these. Customers who don't want notifications need to switch them off for your pass on their phone.
Still stuck?
Our team answers every message. Contact support