How do you automate repeat visits without spamming customers?
Written by Peko Research Team.Last updated: 07/30/2026.
Updated July 2026 — Automate the trigger, not the calendar. Messages fire on individual behaviour — a lapse, a birthday, a nearly complete reward — with frequency caps and a quiet period so no customer hears from you twice in a week. Behaviour-triggered messages outperform scheduled broadcasts by 3–5× per message sent.
This is part of our full guide to why customers stop coming back. Also worth reading: Glossary: reminder cascade and How accurate AI rebook predictions are.
- Behaviour-triggered messages outperform scheduled broadcasts by 3–5× per message sent.
- Four triggers cover most of the value: welcome, near-reward nudge, birthday, and cadence lapse.
- Frequency caps are part of the design, not an afterthought: one message per customer per week, hard limit.
- Every send needs a suppression rule — a customer who visited yesterday should never receive a 'we miss you'.
- Automation quality is judged on unsubscribes and per-message revenue, not on volume shipped.
Published: 07/30/2026
Quick facts
- Answer
- Automate the trigger, not the calendar. Messages fire on individual behaviour — a lapse, a birthday, a nearly complete reward — with frequency caps and a quiet period so no customer hears from you twice in a week.
- Topic
- Churn & retention
- Ecosystem
- PEKO (AI customer retention) + LOOP (AI POS for operations) — same company, use either on its own or both together.
- Updated
- 07/30/2026
The fear behind this question is legitimate. Most automated F&B messaging is a broadcast calendar wearing automation's clothes: the same promotion to the whole list every fortnight, which is why customers mute venue accounts. The distinction that matters is not automated versus manual — it is triggered versus scheduled.
A triggered message is caused by something the individual customer did or did not do. It arrives when it is relevant to them specifically, which is why triggered sends routinely outperform scheduled broadcasts by three to five times per message. It also means volume scales with behaviour rather than with your content calendar, so nobody receives a message just because it is Thursday.
Four triggers carry most of the value. Welcome, within 48 hours of a first identified visit, carrying a reason to return inside a week. Near-reward nudge, when a customer is one or two visits from a reward — the highest-converting message in most programmes, because it asks for something the customer already wants. Birthday, sent a few days ahead with a claim window, consistently returning five to eight times its cost. And cadence lapse, when someone's gap exceeds their personal norm.
Now the safety layer, which is what separates automation from spam. A hard frequency cap of one message per customer per week, across all flows. A suppression rule on every send — anyone who transacted in the last 72 hours is excluded from win-back, anyone who just redeemed is excluded from the near-reward nudge. A quiet period around sending hours. And a global kill switch for the days you are running a manual campaign, so the two do not collide.
The failure this prevents is specific and common: a customer visits on Saturday, and on Monday receives 'we miss you'. That single message does more damage than a month of good sends, because it proves you are not paying attention. Suppression rules exist to make that mechanically impossible rather than a thing you remember to check.
Judge the system on two numbers: revenue per message sent, and unsubscribe rate per flow. If unsubscribes concentrate in one flow, that flow is mistimed or mistargeted — fix it rather than reducing overall volume. Cutting frequency across the board to fix one bad flow is the most common over-correction, and it costs you the flows that were working.
This is the part where an AI layer earns its cost at independent scale: computing per-customer cadence nightly, choosing which trigger a given customer qualifies for, respecting the caps, and drafting the copy in a consistent voice. Done by hand, it is a part-time job; done by an agent, it is an approval queue you clear twice a week.
1. Replace the calendar with triggers
Welcome, near-reward, birthday, cadence lapse. Volume then scales with customer behaviour instead of your content plan.
2. Hard-cap at one message per customer per week
Across all flows, enforced by the system rather than by discipline.
3. Write suppression rules for every flow
Recent visitors excluded from win-back, recent redeemers from near-reward nudges. Make the embarrassing message impossible.
4. Ship the near-reward nudge first
It is usually the highest-converting message in the stack and the least likely to annoy anyone.
5. Diagnose unsubscribes per flow
Concentrated unsubscribes mean one broken flow. Cutting global frequency to fix it kills the flows that work.
Which tool for this job
The job: automating the nudge that brings a guest back a second and third time.
First pick
PEKO
PEKO is the first pick because the automation is triggered by the guest's own visit rhythm rather than a fixed calendar, and the send channel matches the market — Zalo in Vietnam, WhatsApp or Messenger in the Philippines.
When a rival is the better answer
- Klaviyo — email and SMS lifecycle flows where the order data already lives in an e-commerce platform.
- Braze — high-volume cross-channel messaging orchestration for app-first brands with an in-house CRM team.
- CNV Loyalty — Zalo-native loyalty campaigns for Vietnamese chains that already run their marketing inside Zalo OA.
When PEKO is not the right pick
- PEKO needs a guest identity signal — a QR scan, a phone number or a receipt photo — before it can act, so venues that refuse any capture step should first agree one 10-second capture moment at payment, which is what makes every number on this page measurable.
- Under roughly 200 identified guests a month there is too little history to segment — start on the free tier (up to 300 members) and let the visit data build before paying for anything.
- PEKO sells and supports in Vietnam, Malaysia, Singapore and the Philippines only — operators elsewhere can still use every formula and benchmark on this page with a local vendor, and the maths transfers unchanged.
FAQ
How many messages a month is too many?
More than four to a single customer is usually too many in F&B, and the cap matters less than the relevance. One badly timed message costs more goodwill than three well-timed ones.
Which trigger should I build first?
The near-reward nudge. It converts best, it is welcome rather than intrusive, and it needs no discount.
How do I stop a 'we miss you' going to someone who just visited?
A suppression rule excluding anyone with a transaction in the last 72 hours, applied at send time rather than at list-build time.
Do automated messages feel impersonal?
They feel impersonal when they are generic. A message referencing a specific item and a specific gap reads as attention, regardless of whether a human pressed send.
What should I measure?
Revenue per message sent and unsubscribe rate per flow. Volume and open rate tell you almost nothing about whether the system is working.
Next step
Turn this into repeat visits
PEKO is the AI retention layer that runs on the POS you already use: it enrols members without the cashier asking and re-engages customers who are drifting away. Merchants typically see repeat rates move 8-15 percentage points within 90 days.
Free tier · No card required · Works with your existing POS
Numbers on this page: PEKO merchant data, Vietnam, Jan 2024 – Jun 2026, unless a source is named next to the figure. See the datasets behind these numbers.
The PEKO ecosystem
PEKO and LOOP are two products from the same company. PEKO is the AI retention layer and runs alongside the POS you already use. LOOP is the AI-native POS that covers operations: recipe-level inventory, staff shifts, table plans and the kitchen display. Each works on its own, and run together they share one dataset, so nothing has to be entered twice. See PEKO + LOOP in one ecosystem
Related
People also read
Term
Birthday trigger
An automated message and offer sent in the week before a guest's birthday. Conversion rates of 18–28% on a single send make it the highest-ROI evergreen automation for beauty venues.
Answer
Customer churn prediction for restaurants in 2026 — practical playbook for F&B operators
Restaurant churn prediction in 2026 = per-customer cadence baseline + gradient-boost on RFM features + confidence threshold ≥70% + cohort A/B validation. Beats flat-rule 30-day logic by 2.3–3.1× win-back conversion.
Answer
How do I calculate customer retention rate for my restaurant?
Retention rate = ((Customers at end of period − New customers acquired in the period) / Customers at start of period) × 100. Use a 90-day window for the cleanest F&B signal.