AI for Hospitality.

Hospitality is a 24-hour reservation desk

Friday brunch chaos at 11 AM. A 7 PM dinner rush at a Marina rooftop. A late suite booking at 1 AM from a Palm Jumeirah resort. Hospitality serves the world, in every language, around the clock. Reception teams cannot match that demand without a second pair of ears that never sleeps.

Restaurant phones ring while walk-ins pile up at the host stand. Hotel front desks juggle late check-ins, concierge requests, and outbound calls to tomorrow’s arrivals. The phone always loses.

Why front-desk reception loses revenue

Hospitality reception breaks at the intersection of walk-in service and inbound demand.

What Edah does on every hospitality call

Restaurant tables booked with the right preference

Window seat. Outdoor terrace. Booth for six. Edah captures preferences inside the conversation, checks live availability, and confirms the booking before the call ends.

Hotel rates quoted and rooms booked instantly

Date range, room type, occupancy, view preference, and add-ons. Live rates from your property management system, seasonal pricing and promotions applied, reservation created in the same call.

Special requests captured on the record

Dietary restrictions, allergies, anniversary occasions, accessibility, late check-in. Logged against the reservation so the host, the chef, and housekeeping see it before the guest arrives.

Cancellations handled with policy enforcement

Edah applies your cancellation and modification policy automatically, calculates refunds where applicable, and updates the reservation in real time.

Experiences cross-sold in the same conversation

Spa, transfers, dining add-ons, kids club, beach club access. Edah cross-sells experiences relevant to the booking, increasing average revenue per guest without pressure tactics.

A real call, in 60 seconds

Caller: Hi, I would like to book a table for two tomorrow at 8 PM. It is our wedding anniversary.

Edah: Congratulations. I have a terrace table with a marina view available at 8 PM. Anything I should flag for the chef?

Caller: My wife is allergic to seafood. Could you arrange a dessert?

Edah: Noted. Terrace table for two at 8 PM, seafood allergy flagged in the kitchen, anniversary dessert with the pastry team. Shall I add a bottle of champagne to start?

Caller: Yes, the house champagne is fine.

Edah: Confirmed. Total estimate before mains is 380 dirhams. SMS confirmation now with directions and parking.

What happened in the background

• Checked terrace availability against the reservation system.

• Locked the table for two, flagged the allergy in the kitchen, scheduled the dessert with the pastry chef.

• Added the house champagne to the cover, calculated the pre-mains charge.

• Created or updated the guest profile with anniversary date for future visits.

• Sent an SMS confirmation with map link and valet instructions.

Built for the stack you already run

No PMS migration. No parallel reservation book. Hosts, concierge, and housekeeping see the same guest profile they always did. The phones just stop dropping.

Compliance, built in

Guest profiles, dietary preferences, and payment information all fall under PDPL, and hospitality is one of the most cross-border industries in scope.

• Recording consent captured at call start in the guest’s language.

• Consent events timestamped and stored for seven years in a tamper-evident audit chain (SHA-256).

• All guest data processed and stored in Azure UAE North.

• PDPL data subject rights, including erasure, are first-class workflows in the dashboard.

• Outbound confirmation, post-stay survey, and loyalty re-engagement campaigns pass a synchronous TDRA pre-dial gate.

What changes after Edah

The tools running on this call

Six tool calls per reservation. Each logged, retried on failure, visible in your dashboard. No black boxes.

check_availability(resource_type: "table", filters: { covers, section: "terrace", time })
create_booking(guest_profile, table_id, time, covers, requests[])
update_crm_field(object: "guest", id, patch: { tags: ["anniversary"], allergies: ["seafood"] })
notify_team(channel: "kitchen", payload: { allergy: "seafood", reservation_id })
notify_team(channel: "pastry", payload: { occasion: "anniversary", reservation_id })
send_sms(to, template_id: "reservation_confirmation", variables)

check_availability(resource_type: "table", filters: { covers, section: "terrace", time })
create_booking(guest_profile, table_id, time, covers, requests[])
update_crm_field(object: "guest", id, patch: { tags: ["anniversary"], allergies: ["seafood"] })
notify_team(channel: "kitchen", payload: { allergy: "seafood", reservation_id })
notify_team(channel: "pastry", payload: { occasion: "anniversary", reservation_id })
send_sms(to, template_id: "reservation_confirmation", variables)

check_availability(resource_type: "table", filters: { covers, section: "terrace", time })
create_booking(guest_profile, table_id, time, covers, requests[])
update_crm_field(object: "guest", id, patch: { tags: ["anniversary"], allergies: ["seafood"] })
notify_team(channel: "kitchen", payload: { allergy: "seafood", reservation_id })
notify_team(channel: "pastry", payload: { occasion: "anniversary", reservation_id })
send_sms(to, template_id: "reservation_confirmation", variables)

Going live

1. Share inventory, rates, booking rules, loyalty program, and service hours.

2. Edah drafts your reservation scenario for the venue or property.

3. Connect your PMS or reservation system, payments, and messaging.

4. Go live in 24 to 72 hours. Add post-stay surveys and loyalty re-engagement in week two.

Guests choose hotels, restaurants, and experiences in the language they were greeted in. The property that picks up the phone in French, Russian, Mandarin, or Arabic is the property they remember. Book a 30-minute walkthrough.