Choose which message types to turn on
Ten types are ready in the list, each with a sensible default trigger. Turn on whichever fit your venue.
Features
Automated messages: 10 message types run themselves , you approve once
The full list of PEKO's 10 automated message types — new member, birthday, lapsed guest, points expiring, voucher expiring, and more — with their trigger conditions.
AUTO SEND
Updated August 2026 — PEKO ships 10 built-in guest-care message types over WhatsApp: welcome for new members, thank-you after an order, birthday, special occasions, receipt-scan confirmation, tier-up congratulations, lapsed-guest reminder, points-expiring warning, voucher-expiring warning, and a recurring weekday message. You approve the wording once, and the rest runs on its own.
Updated: 2026-08-09
Quick facts
- Number of types
- 10 built-in, each with its own trigger condition.
- Who writes it
- AI drafts by guest segment; you approve once.
- Channel
- WhatsApp in Singapore, Malaysia, and the Philippines; Zalo in Vietnam.
- Anti-spam
- A message cap per guest within a period, adjustable.
How it works
Approve the wording once
AI drafts the copy in your venue's voice, tailored to each guest segment. You read it, edit if you like, and approve.
Messages send themselves at the right moment
Messages fire when their condition is met — birthday 3 days ahead, lapsed guest at 21 days, points expiring 7 days out. Every threshold is adjustable.
The 10 automated message types
| Message | When it sends | What it is for |
|---|---|---|
| New member welcome | Immediately after a customer joins by check-in QR or receipt scan | Deliver the joining reward while the customer is still in the venue |
| Order completed | After a scanned receipt is approved and points are credited | Confirm the points landed, so the balance never feels invisible |
| Birthday | 3 days before the member's birthday (default) | Give a reason to book the celebration at your venue, not elsewhere |
| Special day | On a date you set — anniversary, festival, venue birthday | Fill a known-quiet or known-busy date on purpose |
| Receipt scan result | When a scan is approved, held for review, or rejected | Tell the customer what happened instead of leaving them guessing |
| Tier upgrade | The moment a member crosses into a higher tier | Make the new benefits visible while the win still feels fresh |
| Haven't been back | 21 days without a visit (default) | Catch silent churn while the customer still remembers your venue |
| Points about to expire | 7 days before points expire (default) | Turn a balance the customer cannot see into a concrete reason to return |
| Voucher about to expire | 3 days before an issued voucher expires (default) | Recover rewards that would otherwise be spent nowhere |
| Weekly on a chosen weekday | Every week on the weekday and hour you pick | Build a habit around your quiet day rather than your busy one |
Customers cannot open a points balance the way they open a bank app. The two expiry reminders are how a balance becomes visible anyway: a message that reads "340 points expire in 7 days" tells the customer exactly what they hold and what they lose — the same problem invisible points create, solved from the other direction.
Which venues this fits best
- Venues with no dedicated marketing person and no one who remembers a send schedule.
- Venues that already have a guest base but have never followed up after the first visit.
- Multi-branch chains that need one consistent guest-care standard everywhere.
Check your own venue
- When did your venue last proactively message a guest who hadn't been back in three weeks?
- How many guests are sitting on points or vouchers about to expire without knowing it?
- If the staff member who handles this called in sick today, would these messages still go out?
What this does not solve on its own
- Too many messages and guests mute notifications — every guest has a message cap within a given period, and that cap is adjustable.
- Automated messages can't rescue a bad dish or bad service — the post-visit survey catches those issues before they become a public review.
- WhatsApp template messages carry a per-message fee and template rules — PEKO defaults to free channels first and only uses paid templates when a message truly needs to reach the guest.
Questions owners ask
Is it exactly 10 message types?
Yes. New member, order completed, birthday, special occasion, receipt scan, tier-up, lapsed guest, points expiring, voucher expiring, and a recurring weekday message. The full table with trigger conditions is on this page.
Who writes the wording?
AI drafts each message by guest segment and in your venue's voice. You approve once per message type; after that it runs on its own, and AI refines it over time based on results.
What's the point of a points-expiring warning?
Most guests never check their own balance. A message like '340 points expire in 7 days' both gives them that information back and gives a concrete reason to return.
Which channel does it send through?
WhatsApp in Singapore, Malaysia, and the Philippines (Zalo in Vietnam). Email and SMS supplement it when needed.
Can I change the timing?
Yes, all of it. The defaults — birthday 3 days ahead, lapsed guest at 21 days, points expiring 7 days out — are just a starting point for you to tune to your venue's real cycle.
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