Stripe / GoCardless / Klarna payment links · native WhatsApp Payments UK roadmap — and Royal Mail / DPD UK / Hermes / Parcelforce tracking pushed live to WhatsApp. Every integration is a real connector, not a Zapier bridge with per-task fees.
English-first with strong Polish / Urdu / Arabic pockets in London, Birmingham, Manchester — our auto-translate covers all of them. Customer writes in Polish, your agent sees English. Agent replies in English, customer gets their language — both sides see their own.
Coverage cities: London · Manchester · Birmingham · Leeds · Edinburgh · Glasgow · Bristol · Newcastle.
UK GDPR + PECR compliant opt-in handling, GBP invoicing, ICO-aware consent logs, Record of Processing Activities (ROPA) export on request.
Pricing: GBP billing available at PRO and Enterprise. PRO is ≈ £110/mo equivalent to AED 499. Meta conversation fees are passed through at Meta's public rate card — we do not mark them up.
BSP onboarding: Direct Meta Business Partner — BSP transfer in 24–48h. UK data-residency options available at Enterprise tier via EU West datacentre routing.
WhatsApp is not a replacement for your POS or your delivery-partner integration — orders still flow through the POS and delivery happens via Zomato/Swiggy or your in-house rider. WhatsApp sits on top as the customer-conversation layer. Meta does rate-limit high-frequency marketing broadcasts to the same customer (once per day, typically), so don't stack birthday + anniversary + weekend-special on the same day. Catalog + in-thread payments work best for menus under ~40 items — larger menus belong on a proper ordering site.
We are a Meta Business Partner, not a law firm — our platform supports your compliance posture but cannot substitute for local data-protection counsel on contract language, retention policies, or specific regulator filings.
Yes — both have native connectors. Bill-closed event triggers the feedback flow, order-ready event triggers pickup alerts, and menu changes sync to the WhatsApp Catalog automatically.
Each booking source gets a different consent flow but lands in the same WhatsApp inbox. Walk-ins get an optional "Save for future bookings?" offer at the bill closing; OpenTable bookings arrive pre-consented.
Meta-priced utility conversations (reservation reminder, order confirmation, feedback) are ~₹0.11–0.80 in India, AED 0.021–0.040 in UAE — Go4whatsup passes through without markup. Cheaper than SMS and dramatically more effective.
Partially. Direct WhatsApp orders (via Catalog or menu PDF) for existing regulars work well and save the 20–30% aggregator cut. For net-new customers, aggregators still bring discovery — use WhatsApp to retain, not acquire.
Route to the on-duty manager with full order context (tables, orders, time, any staff assignments). Manager outreach within 2 hours of the meal catches ~80% of situations before a bad review gets posted.
Yes — with consent. Once-a-week weekend-special or new-menu broadcast works well. Daily promotional broadcasts hurt conversation quality and Meta will rate-limit. Birthday / anniversary triggers are the highest-engagement message we see.
Very well. Order confirmation, delivery partner ETA, re-order prompt, and feedback loop all fit cloud-kitchen operations. Cloud kitchens typically see 30–50% direct-order growth in the first quarter on WhatsApp.
We support UK GDPR obligations around lawful basis, consent, subject rights, and ROPA. We also respect PECR direct-marketing rules for electronic channels. For a DPA under UK GDPR, ask our team — we use ICO-referenced SCCs for any cross-border transfers.
Yes. PRO is ≈ £110/mo, invoiced from our registered entity. VAT-reverse-charged where applicable. Annual contracts available.
Default cloud region is closest-to-customer. UK customers can request EU West (Ireland) for latency and GDPR adequacy. Full data flow map available under NDA.
7 business days from first call to live WhatsApp number. £110/mo. GBP invoicing. UK-aware.