WhatsApp ordering and reservations for Dubai restaurants

Friday at 7:30 is when the phone and the WhatsApp Business app ring together. One guest wants to move a table of six from 8 to 9. Another asks whether the terrace is free. A third wants to confirm the dessert is nut-free. The host is also seating walk-ins. That is the window where a booking is lost for a straightforward reason: nobody was free to take it.

Diners in Dubai pick WhatsApp because it is already on the phone, it replies like text from a person who knows the place, and the conversation stays attached to a number they use every day. No app install, no hold music. For a restaurant that channel is either staffed around the clock or it is not staffed at all.

The same diners order through delivery apps, and each order through them carries a commission in the 15 to 30% range. That is why more operators push the direct channel. A WhatsApp order pays no aggregator cut, and the guest stays in a channel the restaurant controls: the menu the restaurant wrote, the hours it set, the follow-up it decides to send.

We build these flows on the official WhatsApp Business Platform for UAE operators. The reservation build runs on the same system we use for lead qualification and order intake, with one difference: the guest is already in the room, so the bot's job is to make the room easy to run, not to chase a lead.

The reservation flow

The entry point is usually a QR code on the counter, a click-to-WhatsApp button on the website, or the number already on business cards and the Google Business Profile. The first message starts the intake. The bot asks in the guest's language, for Dubai that usually means Arabic and English side by side, and it accepts voice notes and transcribes them. It collects name, party size, date and preferred time, and occasion, because the occasion decides the table note the floor sees.

Availability is the part that has to be honest. The bot checks the real table schedule. If the slot is free, it offers the time and writes the booking. If it is not, it offers the next free window or puts the guest on a waitlist and confirms when a table opens. In every case the restaurant calendar stays the source of truth, and a host can override any booking from the same screen they already use.

Hours, parking, terrace or not, the price of the set menu, which dishes contain nuts: the bot answers these from the menu and venue data you maintain, in both languages, at 2 a.m. as well as 8 p.m. The guest's occasion rides along into the handoff, so the floor already has the note when the party walks in.

That conversation keeps going into orders. The guest picks items, adds a delivery address or chooses pickup, and gets a payment link in chat. The order lands as a structured record, items, quantities, modifiers, address, ready for the kitchen screen or an export your existing tools can read. Complaints, confusion, or a request the flow does not recognize hand off to a person with the whole thread attached (what happens at handoff).

A reminder goes out before the booking. A day after the visit the bot asks whether the dinner is worth repeating and offers a booking. A returning guest carries the occasion and preferences from the last chat, so the second reservation takes seconds.

What a build costs

A focused build, reservations plus menu answers plus order intake plus post-visit follow-ups, runs 15,000 to 40,000 AED and ships in 3 to 6 weeks on the official WhatsApp Business Platform. The low end assumes one language and a clean entry point. Arabic and English with voice-note transcription, or a connection to an existing reservation tool, moves it toward the top of the range.

Channel costs are a separate line. Meta charges per delivered template message, with the rate set by message category and the recipient's country code, and replies inside the 24-hour customer service window are free (Meta pricing docs). A Business Solution Provider adds a platform fee or a per-message markup. The rates change each quarter, which is why we point clients at the live pricing breakdown before they sign a yearly budget.

Running the system sits in the 500 to 5,000 AED a month band, driven by model usage and message volume. That range is what we quote for a build; a written spec sets the exact number. What moves a project up the range is the same list as any WhatsApp build: language coverage, integrations without an API, and approval steps.

A reservation takes the bot seconds to complete. A complaint should reach a person in under a minute. We build the second rule with the same engineering weight as the first.

Who handles it: the bot or a person?

We draw the line as a rule table the flow applies to every message. Some requests a system can confirm in seconds. Others carry money, an allergy, or a night that is already going badly, and those go to a person with the full thread.

Situation	The bot does	A person takes over
Changing a reservation (time or party size)	Re-checks availability, offers alternatives, updates the booking	A conflict the guest disputes, or a date the schedule cannot resolve
Complaint about food or service	Flags the thread and hands off	Every complaint, immediately, with the full context
Group enquiry for 10 or more	Captures the date, size and contact	Confirming the booking and any deposit or set-menu terms
Allergen or dietary question	Answers from the approved allergen data you maintain	Anything the data does not cover, routed with the question attached
Payment problem, an expired link, a refund	Does nothing with the money	Every payment issue, with the order summary attached

The reservation intake collects a short field set, and each field earns its place:

• Guest name and phone, taken from the WhatsApp account itself
• Party size
• Date and preferred time
• Occasion, a birthday or a business dinner, because it decides the table note
• Seating preference, inside, terrace or high-top

Anything else, a cake request, a child seat, a question the list does not fit, is caught as free text and passed to the floor as a note.

How do promotions stay inside Meta's rules?

Automation on the official platform is the sanctioned path, but it has conditions. Marketing templates, offers, launches, re-engagement, face a stricter review than utility messages, and every one requires opt-in: the guest actively agreed to receive business messages from you on WhatsApp. Meta's opt-in guidance is explicit that a number collected for another purpose, a bought list or a scraped dataset is not consent, and messaging it is the fastest route to a ban (Meta: getting opt-in).

The record is what carries you through a review. A timestamped checkbox that names WhatsApp, a QR code the guest scans into the thread, a click-to-WhatsApp ad, an inbound first message: each leaves evidence you can show if a rating drops or Meta asks where a contact came from. We document the full checklist in what counts as opt-in.

The chat logs themselves are personal data under Federal Decree-Law No. 45 of 2021, the UAE's data protection law. The consent record is therefore both a Meta requirement and the PDPL record of why you hold the contact. A reservation system spends most of its traffic inside the customer service window, which is the free, low-risk part of the channel. Broadcasts are the part you plan separately, with an opt-in list and approved templates.

Can it take orders without touching my POS?

Depends on what the POS exposes. On a delivery or kitchen system with an API, an order writes straight in: structured line items, modifiers, the guest's address, the payment link result. If there is no API, the order still arrives structured, on a kitchen screen or in an export your staff clicks through. Integrations get named in the spec before we quote.

The closest shipped proof is our vitamin marketplace, where order intake runs on chat rails and the first hundreds of orders went through without manual help. The shelf is different, the intake mechanics are the same: structured capture, a clean handoff, a terminal that accepts the output. It is adjacent proof, not a restaurant deployment, and we say so flatly.

The takeaway

A restaurant WhatsApp build takes the load at peak, confirms a table of six in seconds, answers the nut-free question every evening without a human, and lands orders on the kitchen screen. It costs 15,000 to 40,000 AED to build and 500 to 5,000 AED a month to run, and it only holds the table if a person stays one message away on the cases that matter. Book the free audit and bring the workflow that eats the most hours; we will map how much of it the platform can take.