For

Restaurants with a Zalo OA

Zalo OA broadcasts and ZNS open at 90%+ — but only pay back when sent to the right person at the right hour. PEKO is the targeting layer Zalo OA doesn't ship with.

Connect your Zalo OA in minutes →

Symptoms you're seeing

01.You broadcast to your entire OA list and pay ZNS for everyone, including people who'd never redeem.
02.Open rate is high but redeemed-revenue per send is shrinking.
03.You have no way to tell which segment actually responds.
04.ZNS template approvals slow you down — and the templates you have don't fit every segment.

Root cause

Zalo OA is a megaphone, not a CRM. It can broadcast, but it can't tell you who deserves the next ZNS and who'd be wasted spend. Without segmentation, ZNS becomes the most expensive way to message people who'd have come anyway.

How PEKO fixes it

1.RFM-segment your OA list
Connect your POS once; PEKO matches transactions to Zalo IDs and produces RFM cohorts (champions, at-risk, hibernating, new).
2.Send ZNS only where it pays back
Use ZNS for high-intent cohorts (champions + at-risk-high-value); use free OA broadcast for the rest. PEKO picks the mix to minimise cost per redeemed offer.
3.Schedule at peak intent hours
AI learns when each cohort opens and redeems (e.g. lunch-decision window 10:30–11:15) and schedules sends there.

What you get

Same Zalo OA, same ZNS templates — fewer sends, more redemptions, lower cost per redeemed offer. ZNS open rates of 90%+ start to mean something.

Common questions

Do I keep my existing ZNS templates?

Yes. PEKO uses the templates already approved on your Zalo OA — no re-approval needed.

Can PEKO send broadcasts on my behalf?

Yes — once you connect the Zalo OA, PEKO orchestrates broadcast, ZNS and miniapp messages from one calendar.

What about PDPD / Decree 13?

Consent is tracked per channel per customer. Customers who opt out of ZNS still appear in your CRM but are excluded from sends.

See the full product spec: /product · Related vertical