Skip to content

Wallet push notifications for lapsed customers

Loyally Team9 min read
Wallet push notifications for lapsed customers

A customer visits your coffee shop four times in six weeks, then disappears. Their loyalty card is still sitting in their Apple Wallet or Google Wallet. They haven't deleted it. They just drifted. Wallet push notifications give you a direct line back to that person's lock screen, no app required, no email open rate to worry about.

This post covers how to use those notifications strategically, not just blast a generic "we miss you" message and hope for the best.

Why lapsed customers are worth chasing

Before getting into tactics, it helps to understand the economics. According to Harvard Business Review, acquiring a new customer can cost five times more than retaining an existing one. A lapsed customer already knows you. They've been in your shop, sat in your chair, eaten your food. The barrier to returning is much lower than convincing a stranger to try you for the first time.

The probability of selling to an existing customer is 60-70%, compared to 5-20% for a new prospect, according to Marketing Metrics (Paul Farris et al.), as reported by Forbes. A lapsed customer sits somewhere in between, but they're much closer to the "existing customer" end of that range than a cold lead is.

The problem most local businesses have is they have no reliable way to reach these people. Email lists go stale. Social posts get buried. But a loyalty card in someone's wallet? That's a persistent channel you already own.

What wallet push notifications actually are

When a customer adds your loyalty card to Apple Wallet or Google Wallet, they're granting your business permission to send lock screen notifications tied to that pass. These aren't in-app messages. They appear the same way a text message or calendar alert does.

The notification can include a short headline, a supporting line of text, and it links directly to the customer's loyalty card when tapped. No login required. No friction. The card is already there.

This is meaningfully different from email or SMS. The customer doesn't need to open an inbox or remember a password. The message lands in a context they already check constantly, and one tap shows them exactly where they stand with your rewards.

For a deeper look at how the pass infrastructure works on Android, this guide to Google Wallet loyalty passes covers the mechanics well.

Defining "lapsed" for your business

Not every business has the same natural visit cadence, so "lapsed" means different things depending on what you run.

Business type Typical visit frequency Lapsed threshold
Coffee shop 2-4x per week 14 days without a visit
Barbershop Every 3-4 weeks 6 weeks without a visit
Nail studio Every 3-6 weeks 8 weeks without a visit
Gym 2-4x per week 21 days without a check-in
Restaurant 1-2x per month 45 days without a visit
Car wash Every 2-4 weeks 6 weeks without a visit

Set your own threshold based on what's normal for your regulars, not industry averages. If your best customers come in every two weeks, someone who hasn't visited in five weeks is lapsed. If you run a spa where monthly visits are typical, six weeks might still be within normal range.

The point is to define the threshold before you start sending notifications, so you're not guessing. Most wallet pass platforms let you filter customers by last stamp or last scan date, which makes this segmentation straightforward.

Crafting the message

The biggest mistake businesses make with win-back notifications is being vague. "We miss you! Come visit us soon!" tells the customer nothing they couldn't ignore. A good win-back notification does three things: acknowledges the gap, gives a specific reason to return, and makes the next step obvious.

The structure that works

Headline (under 40 characters): Lead with something concrete. "Your 3 stamps are waiting" or "Double stamps this week only" beats "We miss you" every time.

Body line (under 80 characters): Add the specific offer or context. "Bring this card in by Friday for a free coffee" is actionable. "We'd love to see you again" is not.

The tap destination: When they tap the notification, they see their loyalty card. Make sure the card itself reflects the offer you mentioned, whether that's a bonus stamp, a discount coupon, or a reminder of how close they are to a reward.

Examples by business type

A barbershop might send: "It's been a while, [Name]. Book this week, get $5 off your next cut." A gym could try: "You're 3 check-ins from a free month. Come back and finish strong." A coffee shop might go simpler: "Your stamp card misses you. Double stamps all day Saturday."

The specificity is what makes these land. Customers respond to messages that feel like they were written for them, not broadcast to a list.

For more on why progress-based messaging works psychologically, this piece on stamp card psychology explains the mechanics behind goal completion and return visits.

Timing your notifications

Sending a win-back notification at the wrong time wastes it. A few principles that apply across most local business types:

Send when they can act on it. A coffee shop notification sent at 9 PM on a Tuesday is less useful than one sent at 7:30 AM on a Saturday. Think about when your lapsed customer could realistically walk through your door within the next few hours.

Don't send too soon or too late. If someone visited three days ago and you send a win-back, it feels pushy. If they've been gone six months and you send one, the card might feel irrelevant to them. The sweet spot is usually one to two weeks past your lapsed threshold.

Limit frequency. One win-back notification per lapsed period is enough. If they don't respond to the first, wait before sending another. Sending multiple notifications to someone who isn't engaging will get your pass deleted.

Pair with a real event. Notifications tied to something specific, a seasonal menu change, a new service, a limited-time offer, feel more legitimate than a generic nudge. "We just added cold brew on tap. Come try it, your stamps are waiting" gives the customer a genuine reason to return.

Building a segmented win-back sequence

A single notification is a starting point. A short sequence, timed thoughtfully, tends to perform better than one-and-done.

Here's a simple three-step structure for a lapsed customer:

Week 1 past threshold: Soft reminder. Acknowledge they haven't been in, remind them of their progress, no hard offer yet. "You're halfway to a free haircut. Don't let those stamps expire."

Week 3 past threshold: Add an incentive. This is where you attach a specific offer. "Come back this week and we'll add two bonus stamps to your card."

Week 6 past threshold: Last attempt. Keep it light, not desperate. "We're keeping your card active for another 30 days. After that, we'll archive your stamps." This creates mild urgency without being aggressive.

After that, let it go. Continuing to message someone who isn't responding does more harm than good. It trains them to ignore your notifications, which affects deliverability and perception.

What to do when they come back

A win-back notification that actually works brings someone through the door. What happens next determines whether they stay or drift again. This is where a lot of businesses drop the ball.

When a lapsed customer returns, the experience should feel like a welcome back, not just a normal transaction. If your staff knows a customer hasn't been in for a while (a quick note on the POS or loyalty platform can flag this), a simple "Good to see you again" goes a long way.

Make sure the offer you promised in the notification is honored without friction. If you said double stamps, the stamps should be there when they scan. If you promised a discount coupon, it should appear on their card. Any gap between the notification promise and the in-store reality will cost you the customer again.

After the return visit, consider sending a follow-up notification within 48 hours. Something short: "Great to have you back. Your next reward is just two visits away." This reinforces the habit loop before it breaks again.

For more on the broader tactics that keep customers returning consistently, 10 actionable ways to keep customers coming back covers the full retention picture beyond notifications alone.

Avoiding common notification mistakes

Even with good intentions, businesses make a few predictable errors with wallet notifications. Knowing them ahead of time saves you from learning the hard way.

Sending the same message to everyone. A customer who visited last week doesn't need a win-back. A customer who hasn't been in for three months does. Segmentation isn't optional if you want notifications to feel relevant.

Ignoring what's on the card. If the notification says "you're close to a reward" but the card shows only one stamp out of ten, the message feels dishonest. Keep the notification and the card state in sync.

Over-promising. Don't offer a free item in the notification if you're going to ask the customer to jump through hoops to redeem it. Simple offers with clear redemption paths work better than complicated ones.

Treating it like email marketing. Wallet notifications are not a broadcast channel for weekly promotions. They're a targeted tool for specific moments, like win-backs, milestone alerts, and time-sensitive offers. Overusing them trains customers to dismiss them.

For a broader look at the loyalty program mistakes that erode repeat business, this post on loyalty mistakes that cost you repeat customers is worth reading alongside this one.

How Loyally fits into this

Loyally.ai is a digital loyalty card platform built for local businesses. It supports stamp cards, reward cards, membership cards, cashback cards, and more, all living in Apple Wallet and Google Wallet with no app for customers to install. The platform lets you send push notifications to cardholders, segment by activity, and track redemptions.

If you want to see what the notification and card experience looks like before committing, there's a 14-day free trial on every plan. Starter starts at $17 per month (or $12 per month billed annually), which is a reasonable entry point for a single-location business testing win-back campaigns for the first time.

The strategy in this post works regardless of which platform you use. But having the right tool makes the segmentation and timing much easier to execute consistently.


Frequently asked questions

How often should I send win-back notifications to lapsed customers?

Once per lapsed period is the right starting point. If a customer doesn't respond after one or two well-timed notifications, pause and wait before trying again. Sending too frequently increases the chance they'll delete the pass entirely, which ends the relationship for good.

Can I send wallet push notifications without the customer installing an app?

Yes. When a customer adds your loyalty pass to Apple Wallet or Google Wallet, you can send lock screen notifications tied to that pass. The customer doesn't need a separate app. The notification links directly to their card when tapped.

What's the best offer to include in a win-back notification?

Specific beats generic every time. A concrete offer tied to their existing progress, like bonus stamps, a discount on their next visit, or a free add-on, outperforms a vague "we miss you" message. The offer should be easy to redeem in one visit with no complicated conditions.

How do I know if my win-back notifications are working?

Track return visits from lapsed customers over the 30 days after a notification is sent. Compare that to your baseline return rate without notifications. Most loyalty platforms that support wallet passes will also show notification open rates and card interactions, which give you a signal on whether your messaging is resonating.

What if a customer deletes their loyalty card after receiving a notification?

It happens, and it's useful information. If a segment of customers consistently deletes after a certain type of notification, that's a sign the message or timing is off. Adjust the offer, the frequency, or the threshold before sending to the next cohort. A deleted card is a closed channel, so the goal is always to stay useful rather than persistent.