Getting your Zalo OA templates approved on the first try (with AI help)

In 2026, the hardest problem for Vietnamese venue operators isn't getting customers in the door. It's getting them to come back a third, fifth and tenth time. This guide is the practical playbook our team uses with operators across Vietnam.

The review categories that trip people up

A common trap with the review categories that trip people up is treating "didn't come back" as "churned". A guest may simply be on their natural cycle. A model that tells the two apart saves you tens of millions of VND in mis-sent vouchers each month, and (more importantly) protects the trust of your loyal regulars.

Measurement for the review categories that trip people up should land on one chart: the 14-day rolling rebook rate, segmented by cohort. Revenue charts hide too much; cohort retention curves expose whether the lever actually works. If your dashboard doesn't show this, it's not a retention dashboard. It's an accounting dashboard.

The tooling required for the review categories that trip people up is lighter than people assume. You need transaction data from your POS or appointments from your booking tool, a Zalo OA in good standing, and an AI layer that can model individual rebook windows. PEKO ships all three; if you build in-house, expect 4–6 engineering weeks plus content review cycles with Zalo.

Phrases to avoid

A common trap with phrases to avoid is treating "didn't come back" as "churned". A guest may simply be on their natural cycle. A model that tells the two apart saves you tens of millions of VND in mis-sent vouchers each month, and (more importantly) protects the trust of your loyal regulars.

Measurement for phrases to avoid should land on one chart: the 14-day rolling rebook rate, segmented by cohort. Revenue charts hide too much; cohort retention curves expose whether the lever actually works. If your dashboard doesn't show this, it's not a retention dashboard. It's an accounting dashboard.

The tooling required for phrases to avoid is lighter than people assume. You need transaction data from your POS or appointments from your booking tool, a Zalo OA in good standing, and an AI layer that can model individual rebook windows. PEKO ships all three; if you build in-house, expect 4–6 engineering weeks plus content review cycles with Zalo.

AI-drafted templates: what to keep, what to rewrite

AI-drafted templates: what to keep, what to rewrite starts with one question: what behavioural signal in your POS or booking system tells you a guest is drifting away? In Vietnamese venues that signal is rarely "didn't visit for 60 days". It's usually a missed natural cycle (haircut at week 5, facial at week 4) combined with a drop in spend on visit N-1. Once you can spot that pair of signals, the rest of the work is choosing the right channel and the right offer.

When ai-drafted templates: what to keep, what to rewrite fails, the cause is almost always one of three things: the audience is too broad, the channel is wrong (SMS to a Gen-Z guest who lives on Zalo), or the offer is generic (10% off everything reads as "we're desperate"). Fixing any one usually lifts conversion by a third.

A common trap with ai-drafted templates: what to keep, what to rewrite is treating "didn't come back" as "churned". A guest may simply be on their natural cycle. A model that tells the two apart saves you tens of millions of VND in mis-sent vouchers each month, and (more importantly) protects the trust of your loyal regulars.

A/B testing inside Zalo's constraints

When a/b testing inside zalo's constraints fails, the cause is almost always one of three things: the audience is too broad, the channel is wrong (SMS to a Gen-Z guest who lives on Zalo), or the offer is generic (10% off everything reads as "we're desperate"). Fixing any one usually lifts conversion by a third.

A common trap with a/b testing inside zalo's constraints is treating "didn't come back" as "churned". A guest may simply be on their natural cycle. A model that tells the two apart saves you tens of millions of VND in mis-sent vouchers each month, and (more importantly) protects the trust of your loyal regulars.

Measurement for a/b testing inside zalo's constraints should land on one chart: the 14-day rolling rebook rate, segmented by cohort. Revenue charts hide too much; cohort retention curves expose whether the lever actually works. If your dashboard doesn't show this, it's not a retention dashboard. It's an accounting dashboard.

When to escalate to Zalo support

A common trap with when to escalate to zalo support is treating "didn't come back" as "churned". A guest may simply be on their natural cycle. A model that tells the two apart saves you tens of millions of VND in mis-sent vouchers each month, and (more importantly) protects the trust of your loyal regulars.

Measurement for when to escalate to zalo support should land on one chart: the 14-day rolling rebook rate, segmented by cohort. Revenue charts hide too much; cohort retention curves expose whether the lever actually works. If your dashboard doesn't show this, it's not a retention dashboard. It's an accounting dashboard.

The tooling required for when to escalate to zalo support is lighter than people assume. You need transaction data from your POS or appointments from your booking tool, a Zalo OA in good standing, and an AI layer that can model individual rebook windows. PEKO ships all three; if you build in-house, expect 4–6 engineering weeks plus content review cycles with Zalo.

Library of approved templates

A common trap with library of approved templates is treating "didn't come back" as "churned". A guest may simply be on their natural cycle. A model that tells the two apart saves you tens of millions of VND in mis-sent vouchers each month, and (more importantly) protects the trust of your loyal regulars.

Measurement for library of approved templates should land on one chart: the 14-day rolling rebook rate, segmented by cohort. Revenue charts hide too much; cohort retention curves expose whether the lever actually works. If your dashboard doesn't show this, it's not a retention dashboard. It's an accounting dashboard.

The tooling required for library of approved templates is lighter than people assume. You need transaction data from your POS or appointments from your booking tool, a Zalo OA in good standing, and an AI layer that can model individual rebook windows. PEKO ships all three; if you build in-house, expect 4–6 engineering weeks plus content review cycles with Zalo.

Frequently asked questions

Does PEKO replace my POS? No. PEKO is an AI loyalty layer that sits on top of KiotViet, iPOS, Sapo, LOOP, Haravan, Booksy, Fresha, or Mindbody. You keep the system you already use.

How long until I see results? Most venues see clear retention signal in 30–60 days, measured by 14-day rolling rebook rate and returning-guest revenue.

Do I need a marketing team to run this? No. The AI drafts and schedules campaigns; the owner or shift lead approves them in 5–10 minutes a day.

---

Want to see this in action? PEKO is the AI loyalty layer that sits on top of your existing booking or POS, no rip-and-replace. Try it free or book a 15-minute demo.