Client case study Restaurant & F&B WhatsApp enquiry routing

How a UAE restaurant gave every WhatsApp enquiry a route and an owner

The restaurant serves dine-in guests and direct takeaway customers while also taking orders through delivery marketplaces. Guests write in Arabic and English, menus change for special service periods, and before Zena every enquiry landed in the same unstructured chat: menu requests, table bookings, order questions and complaints, all waiting on whoever picked up the phone.

Zena mapped the front-of-house routine and built routing around it. Menu requests answer from one approved source. Reservations go to the host for a human confirmation. Order-status questions route by channel. Everything lands in a shared inbox where an owner is always identifiable.

Published with the client's consent. The restaurant asked not to be named in marketing material, so identifying details are generalised.

1 source approved current menu

2 languages Arabic and English flows

4 routes menu, booking, order, support

See what your business can automate → Talk to the Zena team

Restaurant enquiry routing

Live in WhatsApp

Incoming enquiry routes

Language choice firstGuests pick Arabic or English and get equivalent instructions.

Menu answered from one sourceThe manager approves a single current menu destination.

Reservations host-confirmedNo auto-confirm. The host checks the floor before saying yes.

Order updates routed by channelDirect orders go to the counter. Marketplace orders refer to the platform.

The pain point was not volume. It was enquiries without owners.

Every restaurant WhatsApp number fills up. The problem for this team was what happened next: a menu question from Tuesday answered with an outdated PDF attachment, a booking request read by two people and confirmed by neither, an order-status question about a marketplace order that the counter could not see.

Staff were not slow. The enquiries simply had no defined route, so every message depended on who happened to open the phone and what they happened to know.

System Built

The front of house stayed in charge. Zena became the routing layer.

The system gives each enquiry type a defined route and a named owner, without changing how the restaurant actually confirms tables or prepares orders.

Enquiries

One approved menu source

The friction

Menu PDFs circulated as old attachments, so guests received outdated menus and prices.

The solution

The manager approves a single current menu destination. Menu replies point there instead of staff digging through old attachments.

Chatflow builder ↗Team inbox & handover ↗

The guest selects the menu route.
The reply points to the approved menu source.
Questions the menu cannot answer go to the restaurant team.

Your team's role

The manager owns menu updates. Staff check allergens, availability and any question that needs judgement.

Enquiries

Bilingual entry flow

The friction

Arabic and English enquiries were handled inconsistently depending on who answered.

The solution

A language choice leads to equivalent Arabic or English instructions, built in the chatflow builder.

Chatflow builder ↗Team inbox & handover ↗

Offer Arabic or English at the start.
Present the relevant menu, reservation, order or support choices.
Keep the chosen language with the conversation for the handover.

Your team's role

The team reviews both language paths and takes over when a message or request is unclear.

Operations

Host-confirmed reservations

The friction

Reservation requests sat unread during service, or were double-handled by two staff members.

The solution

Booking requests collect party size, time and contact, then wait for the host. A change or cancellation updates the record before any reminder goes out.

Chatflow builder ↗CRM & custom fields ↗Team inbox & handover ↗

Collect the party size and preferred date and time.
Put the request in front of the host.
Send the host-confirmed outcome and a route to change it.

Your team's role

The host checks the floor and says yes. A completed form is not a confirmed table.

Operations

Order routing by channel

The friction

Order-status questions mixed direct takeaway orders with marketplace orders the counter could not look up.

The solution

Direct takeaway orders go to the counter with their reference. Marketplace orders are checked in the authorised platform interface or referred to that platform's support.

Chatflow builder ↗CRM & custom fields ↗Team inbox & handover ↗

Identify the order channel and relevant reference.
Send direct-order questions to the counter.
Check marketplace orders through the authorised interface or refer to platform support.

Your team's role

The responsible team verifies the actual order status. No native marketplace connection or delivery ETA is assumed.

Follow-up

Shared inbox and feedback

The friction

No one could say, for a given enquiry, who owned it and whether it was resolved.

The solution

Conversations land in the team inbox with internal notes, cover procedures for absences and a feedback request after service.

Team inbox & handover ↗CRM & custom fields ↗Message templates ↗

Assign the conversation to the appropriate team.
Keep notes and a clear next action for shift cover.
Route feedback and unresolved questions to the responsible person.

Your team's role

Staff handle complaints and follow through on the next action. Feedback follows the applicable messaging permission and template rules.

Why this matters for restaurants and cafes

Restaurant WhatsApp automation fails when it promises things the system cannot know: a reserved table it has not checked, a delivery time it cannot see, a dish availability it is guessing at. This implementation draws the line deliberately. Automation handles what has one true answer, and people handle what needs judgement.

The restaurant claims no native integration with delivery marketplaces, and the workflow does not pretend to one. Marketplace order questions route to the authorised interface or the platform's own support. That honesty is what keeps the automated answers trustworthy.

Since the rollout the team reports the operational effects the design aimed at: fewer enquiries left without an owner, faster useful replies and quicker menu updates when hours or dishes change. The restaurant has asked us not to publish identifying details or figures, and the workflow above is the part any UAE restaurant can evaluate for itself.

Every enquiry has a route. The menu has one source. The host still says yes.

Zena implementation takeaway

Custom Workflow Systems

Is your restaurant's WhatsApp number an unrouted queue?

Zena can map your menu, reservation and order enquiries into defined WhatsApp routes with human confirmation where it matters, a shared inbox and clear ownership for every conversation.

See what your business can automate → Talk to the Zena team