A 24-table boutique restaurant in Antalya's Kaleiçi old town wanted to move beyond SMS for QR-menu follow-up. Goals: order confirmation, a "your dish will be ready in 8 minutes" status nudge, and a post-meal NPS prompt. Twilio's WhatsApp Business API integration delivered all three at $6.60/month for 1,200 messages, achieving a 72% read rate — three times what SMS produced. This guide walks through Twilio onboarding, Meta-approved template messages, GDPR-style consent, and the unit economics.
Twilio + WhatsApp Business API Setup
Step one is business verification on Meta Business Manager: tax ID, bank info and ownership documents are reviewed within 3-5 business days. Then Twilio Console creates the WhatsApp Sender and Meta approves the display name (another 24-48 hours). Total go-live time: one week.
Template messages must be pre-approved by Meta. Three templates were prepared — order confirm, ready alert, NPS — each with at most 4 variables (order #, table, total, ETA). Approval takes 2-12 hours per template.
Three-Stage Message Flow
When a guest places an order from the QR menu, the POS posts a webhook to Twilio and the confirmation message arrives on the guest's phone in 3-5 seconds. The kitchen's prep estimate triggers the second message automatically.
- Confirmation: "Order received. Order #4821 — Total: 248 TL. Estimated ready time: 18 minutes."
- Ready alert: "Your dish will be ready in 8 minutes. Our server will bring it to your table."
- NPS prompt: Sent 2 hours after the bill closes — "Rate us 0-10." Response rate: 38%.
Cost, Compliance and ROI
Twilio's per-message rate for Turkey is $0.0055. 24 tables × 1.7 sittings/day × 30 days × 3 messages ≈ 1,200 messages/month, total $6.60. No fixed monthly fee — pure usage-based.
GDPR/KVKK compliance requires a clear opt-in checkbox in the QR menu: "I'd like to receive WhatsApp order updates." A data-controller notice and retention policy (6 months) are mandatory. NPS responses surfaced an 18% repeat-visit lift, paying back the integration cost within a quarter.
FAQ
Why WhatsApp instead of SMS? WhatsApp penetration in Turkey is 92%; SMS open rate sits at ~20%, while WhatsApp read rate runs 70-85%. Per-message cost is also a quarter of SMS.
What if a guest declines consent? They simply see order status on the QR menu screen. The POS sets an opt-out flag so no WhatsApp message is queued for that guest.
What if a template is rejected? Usually due to promotional tone or excessive emojis. Transactional language, one emoji max, and natural local-language phrasing yields ~85% first-pass approval.
Found this helpful? Share it.
Related articles
The Complete Guide to Running a Multilingual Restaurant Menu
Serving international guests? Learn how to set up a menu that automatically spea…
What Is a QR Code Menu? The Complete Guide for Restaurants
A QR code menu lets customers access your full restaurant menu instantly on thei…
Understanding Your Restaurant's Data: A Practical Analytics Guide
Your menu generates data every day. Learn how to read it, act on it, and use it …