A reservation voice agent that stopped a Dubai restaurant group losing 35% of its calls

Industry

Restaurants

Market

UAE

Client

Restaurant and hospitality group in Dubai

Sponsor

COO

What we built

Voice AI agent

The situation

The phones ring hardest when a restaurant can least afford to answer them. For this Dubai hospitality group, the peak was dinner service: hosts seating walk-ins, managers on the floor, and the reservation line ringing out. The COO measured it: 35% of incoming reservation calls were going unanswered during dinner service.

Every one of those calls was a guest trying to give the restaurant money. Some called back. Many booked somewhere else. In a market with as many options as Dubai, a missed call is rarely a delayed booking; it is usually a lost one.

What we built

An inbound voice agent that answers the reservation line on the first ring, at any hour, and books the table.

It takes the booking into the real system. Date, time, party size, name, phone number, seating preference and occasion go straight into the group's reservation system against live availability. If the requested slot is full, the agent offers the nearest alternatives rather than a callback.

It handles dietary questions properly. Guests ask about vegetarian and vegan options, gluten, nuts, halal, and children's menus. The agent answers from the restaurant's own menu and allergen information, records dietary requirements on the booking so the kitchen sees them, and never guesses. When a guest describes a serious allergy, the agent notes it prominently and tells the guest the team will confirm with the kitchen.

It speaks to Dubai's guests. Callers use English and Arabic and switch between them. The agent follows the caller's language rather than forcing a choice. We wrote about the design behind this in Arabic-English voice agents for UAE businesses.

It knows when to hand over. Large parties, private dining, event enquiries, complaints and anything unusual are transferred to the host stand or captured as a callback for the manager, with the details already taken.

It confirms. Every booking triggers the confirmation the group already sends, so the guest experience after the call is unchanged.

How it went live

We started where the pain was sharpest. The agent first took the calls that would otherwise have rung out during dinner service and after hours, while the host team kept answering when they could. That let the team see bookings arriving from the agent in the same system they already used, with the same detail they would have captured, before it took the line full time.

The menu, allergen and policy content the agent answers from is maintained by the restaurant team, so a menu change is a content update rather than a development request.

Results

The agent answers every reservation call, including during dinner service, and takes the booking or routes the enquiry. The COO reported that revenue from recaptured reservations paid for the whole project within six weeks.

What made the difference

Booking into live availability. An agent that takes a message and promises a callback does not save the booking. Writing into the reservation system during the call is the whole point.

Treating dietary questions as data, not small talk. Recording requirements on the booking is what makes the kitchen trust the agent.

Starting with overflow. Letting the agent catch the calls the team was missing, rather than replacing the team on day one, made adoption easy and the value obvious within weeks.