Stamps
Café Sonnig
Name
Mara L.
Reward
Free coffee
#10472
Marketing that runs itself
The message you no longer have to remember.
One guest has not been in for a while. Another has a birthday tomorrow. A third is one stamp away from a reward. Those are three moments nobody thinks about in the middle of a shift, and exactly the ones that bring guests back. tapja spots them and gets in touch, right on the card in the wallet.
Runs in the background · with anti-spam protection · switch off anytime
9:41
Friday, 14 March
Walletnow
Just 1 stamp to your free coffee
In short
- tapja spots nine moments by itself: welcome, birthday, “almost full”, “reward waiting”, away for a while, regular at risk, tier reached, tier at risk, and the request for a Google review.
- The transactional ones are live from your very first card. There is nothing to configure before you start.
- Every message is an update of your wallet card with a short note: no newsletter, no SMS, no email campaign to your guests.
- Protection is built in: a frequency cap per guest, quiet hours at night, and when several moments coincide, only the most important one goes out.
- Marketing messages only ever reach guests who opted in separately. The server enforces that, not a good memory.
The moments
Nine moments nobody else remembers.
Each one switchable on its own, with your own wording and your own incentive.
Welcome
The first impression after the card is created. Once only, and only on young cards: the moment a guest is most likely to come back a second time.
Birthday
The classic: a personal occasion every guest has only once a year. You set how many days ahead it goes out, what the guest gets and how long it is valid. Without a date of birth nothing happens; it is voluntary.
Almost full
One stamp to go. This is the cheapest visit you will ever get: the guest already wanted to come, they just forgot. How close “almost” is, is up to you.
Reward waiting
The card is full, the reward is ready, the guest has forgotten. Transactional, so it is allowed even without marketing consent.
Away for a while
The win-back automation gets in touch in three steps, by default after 14, 30 and 60 days. If the guest comes in between, the count starts over.
Regular at risk
Not on a fixed number of days, but on each guest’s usual rhythm. Someone who normally comes weekly shows up after two weeks. Someone who comes every eight weeks does not.
Tier reached and tier at risk
With loyalty tiers: moving up is announced, and anyone about to lose their status hears about it in time (from Home Base).
Asking for a Google review
After a redeemed reward, after a certain number of visits, or on moving up a tier, in other words, when a guest is happy. Off by default.
And your own campaigns
Immediately, scheduled, or as a series. With templates such as “Slow Tuesday”, “Rainy day offer” or “Away for a while”, which you adapt instead of starting from nothing.
Guests refer guests New
Your regulars share a personal code. Only once the new guest actually visits and gets a stamp do both receive a bonus. Self-referrals and repeat codes are blocked. Off by default, you switch it on.
The part others leave out
Not being annoying is a feature, not an intention.
A loyalty programme that sends three messages in one evening loses the guest faster than it won them. So at tapja it is not each automation deciding for itself: one shared layer decides what actually goes out, with limits that hold even when you forget about them.
Only the most important message
When several moments land on the same guest, one wins. The rest drop out instead of stacking up.
Frequency cap and quiet hours
By default at most one message a week and three a month, and nothing is delivered at night. Anything that falls into quiet hours is postponed, not discarded.
Consent, enforced server-side
Marketing only reaches guests with a separate opt-in. Card balance updates and “your reward is waiting” are independent of that, because they belong to the programme the guest signed up for.
Reporting that does not flatter
You see how often it triggered and how many guests came back afterwards, explicitly labelled as a correlation, not a proof. For review requests you see sends and clicks; whether anyone actually reviewed is something only Google knows.
Worth knowing
What automations are not.
The channel is the wallet card. That is a strength (the message lands on the lock screen without anyone installing an app), but it sets limits worth knowing.
No newsletter to your guests
tapja sends no marketing emails and no SMS to your guests. Every message is an update of the card with a short note.
No free-form push messages
Apple and Google do not allow arbitrary promotional pushes on a wallet card. A note always hangs off a real event on the card.
Location notice on iPhone only
The reminder when a guest is nearby comes from the Apple pass and runs on the device, with no server tracking. Google Wallet has no equivalent. Up to ten places per card, and from the larger plan (from Home Base).
Automations depend on the plan
The transactional moments run everywhere. Birthday, win-back, regulars at risk, the review request and freely combined audiences belong to the larger plan (from Home Base).
Questions about automations.
Question not listed?
Write to us, a person will answer.
How does the message reach my guest?
As an update to their card in Apple or Google Wallet, with a short note. On iPhone that note appears on the lock screen. It is not an email and not an SMS, and your guest needs nothing installed for it.
Do I need consent for this?
For marketing yes, and tapja collects it separately: when the card is created there is a dedicated, voluntary checkbox that starts out empty. Every grant and every withdrawal is logged. Card balance updates and “your reward is waiting” belong to the programme itself and need no extra consent.
Can I spam my guests with this?
Deliberately hard. There is a frequency cap per guest, nothing is delivered at night, and when several moments apply at once only the most important goes out. Those limits sit above the individual automations and cannot simply be clicked away.
Do I have to write the wording myself?
Only if you want to. Every automation comes with a suggestion you can keep or replace. For your own campaigns there are templates such as “Slow Tuesday” or “Rainy day offer” to start from.
How does tapja know who is a regular at risk?
From the usual gap between that guest’s visits, not from a fixed number of days. Someone who normally comes weekly shows up after two weeks; someone who comes every eight weeks much later. That avoids false alarms in businesses with rare but regular visits.
Will I see whether it worked?
Yes, and honestly: you see how often an automation triggered and how many guests came back afterwards, explicitly as a correlation, not a proof. For the review request, sends and clicks are measurable; whether a review was actually left is something only Google knows.
Can I switch it all off again?
At any time, and individually. Every automation has its own switch, and you set the frequency caps and quiet hours centrally.
Create a card, and the first automations run straight away.
Start free for good, no credit card. Welcome, “almost full” and “reward waiting” are live from your first card.