ops
ZNS template portfolio: the 6 templates every F&B venue should approve first
ZNS template approval takes 3–7 business days each. Operators who request 12 templates upfront wait weeks; operators who launch with the right 6 are live in two weeks with ~85% of use cases covered.
When it fires
Trigger: any venue activating Zalo Business beyond basic OA. PEKO surfaces ZNS recommendation when transaction volume justifies it (typically >500 identified transactions/month).
Message copy that works
The 6 templates: (1) Booking confirmation; (2) Booking reminder T−24h; (3) Order ready for pickup; (4) Birthday greeting + voucher; (5) OTP for high-value transactions; (6) Anniversary / membership milestone. Each template uses 2–4 variables, no free-text fields (rejection risk).
Cadence + timing
Submit all 6 in week 1 of ZNS activation. Approval typically 3–7 business days each — most operators see 4–5 live by day 10. Don't launch promotional ZNS in this batch (use OA for promo).
Expected lift
Venues launching with these 6 see ZNS deliverability 96%+ and use ZNS for ~85% of transactional needs within 30 days. Operators who launch ad-hoc templates one at a time take 2–3 months to reach comparable coverage.
Guardrails — don't skip these
Don't submit promotional templates — they'll be rejected and harm your sender reputation. Don't use free-text variables — high rejection. Don't pay extra for 'fast-track' approval services unless ZNS partner; usually not faster. Don't send ZNS for content that fits OA (waste of ZNS cost).
Want the 6-template portfolio configured? Book a 30-minute ZNS launch session.
Book a demoRelated playbooks
ops
Stylist/server tip attribution: how to reward the staff your loyalty data identifies as drivers
ops
Monthly cohort review: the 30-minute meeting that compounds retention quarter over quarter
ops
Bubble-tea chain rollout: how to launch loyalty across 10+ branches without breaking each store's voice
ops
AOV uplift via combo + upsell: the 3-lever playbook that adds 12–18% to every ticket