- 01
Market
Saudi Arabia
- 02
Written for
Commercial Director, Head of CX, COO
- 03
Decision
Apply AI to guest operations without degrading service or data control
- 04
Languages
EN · AR
The operating problem
The front desk is busiest exactly when the guest needs it most
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
A hotel's service load is not evenly distributed. Check-in and check-out compress into two windows, arrivals cluster around flight schedules, and in Saudi properties the seasonal swing on top of that can be several times baseline. The result is predictable: the enquiry that arrives at four in the afternoon during a coach arrival does not get answered well, and a proportion of those enquiries were people trying to book.
Most hotel technology conversations start in the wrong place — with a channel, usually a chatbot on the website. The more useful starting point is the guest record. If a system can answer questions but cannot see whether the guest has a reservation, cannot hold a room, and cannot raise a housekeeping task with an owner, it has moved work rather than removed it. Guests notice quickly, and staff stop trusting it.
The second thing that decides success is language handling that is genuinely bilingual rather than a translated interface. Guests move between Arabic and English within a single message, give names whose spelling has to match the existing reservation, and ask about things — prayer times, family room configurations, dietary arrangements — where a generic hospitality model trained elsewhere gives confidently wrong answers. Property knowledge has to come from your own documents, with the source recorded.
The guest journey
Where a system helps, stage by stage
Read the right-hand column first. If the systems listed are not reachable at your property, the intervention in that row is not available yet — and that is the honest place to start planning.
Discovery
Comparing properties, checking whether the hotel suits a family, a business trip or a pilgrimage stay.
Answering specific questions from property knowledge — room configurations, distances, facilities — in the guest's language, with the source recorded so a supervisor can audit an answer.
- Website
- Knowledge base
Enquiry
Asking about availability and rates, often on WhatsApp or by phone, frequently outside office hours.
Live availability and rate lookup rather than a promise to check, with a held option where the booking engine supports it. Out of hours this is the difference between a booking and a competitor.
- Booking engine
- Telephony
Reservation
Completing the booking, or asking one more question before committing.
Completing the booking in the engine and confirming in writing. Payment and identity steps stay in the systems built for them — the agent hands over rather than handling card details.
- Booking engine
- PMS
- Payment gateway
Pre-arrival
Arranging an airport transfer, an early check-in, a room preference or a special occasion.
Capturing the request against the reservation and routing it to the team that owns it, so it exists as a task rather than in a message thread somebody has to remember.
- PMS
- Task system
- CRM
Check-in
Arriving, often in a cluster with other guests, sometimes late and tired.
Pre-arrival detail collected in advance so the desk interaction is shorter. We would not automate the greeting itself — at a good property that moment is the product.
- PMS
During the stay
Requesting housekeeping, extra items, maintenance, restaurant bookings or local information.
Requests become tasks with an owner and a time, visible on the same board the team already works from. The measurable gain is usually response time, not headcount.
- Task system
- PMS
Checkout
Settling the folio, querying a charge, arranging a late departure.
Answering folio questions from the record and raising a late-checkout request against availability. A disputed charge goes to a person — it is a commercial conversation, not a lookup.
- PMS
- Folio
Post-stay
Leaving feedback, chasing an invoice, asking about a lost item, considering a return visit.
Routing feedback to the right department with the stay context attached, and resolving invoice and lost-property enquiries without a queue.
- CRM
- Task system
Guardrails
What the system must never do on its own
Hospitality has a low tolerance for automated mistakes because the guest is already in your building. These boundaries are set in the design, not in a policy document.
A complaint or service failure
Escalates immediately with the full context and the guest's stay record attached.
Why: Recovery is a hospitality skill; an automated apology makes it worse
Payment or card details
Hands to the payment flow built for it. The agent never captures card data in a conversation.
Why: Keeps card data out of transcript storage and out of scope
A rate or commercial exception
Offers only published rates and routes anything discretionary to revenue or the duty manager.
Why: Discounting authority belongs to a person with commercial accountability
Safety, medical or security
Immediate transfer to duty staff, with no attempt to advise.
Why: Outside what any automated system should handle
It does not know the answer
Says so and hands over, rather than generating something plausible from general knowledge.
Why: A confidently wrong answer about your property is worse than no answer
How we approach it
Journey first, channel second
Map the journey
Walk the actual guest journey with your team, including what happens today when it goes wrong.
Test the integrations
Establish what your PMS and booking engine actually expose. This determines what is possible and is the step most often skipped.
Start with one stage
Usually enquiry handling out of hours, because the volume is real and the failure mode is visible.
Measure against the desk
Compare resolution and response time against how the same enquiries are handled today, not against a target.
Extend where it earned it
Add stages only where the previous one is working and the team trusts it.
Common questions
What buyers ask
Will this replace our front desk team?+
No, and a property that deploys it hoping for that will be disappointed. What it changes is which work reaches the desk: routine availability questions, repeated pre-arrival requests and out-of-hours enquiries stop consuming the team's attention during arrival peaks. The greeting, the recovery when something has gone wrong, and the judgement calls stay with people, because those are the parts guests actually remember.
Our PMS is old. Is this still possible?+
Sometimes, and the honest answer needs a look at the specific system. Where a PMS exposes an API, integration is straightforward. Where it does not, options narrow to whatever the vendor supports, and some of the journey stages become unavailable — a system that cannot read availability cannot hold a room, and pretending otherwise produces a bad guest experience. We check this in the first session rather than after a proposal.
How do you handle guest data?+
Guest records stay in your systems. The conversational layer reads what it needs for the request and writes back to the PMS or CRM, rather than building a parallel guest database. Transcripts are retained to your policy and the retention period is a decision you make, not a default we set. Card data never enters a conversation — it goes to the payment flow built for it.
What does a first phase usually cover?+
One journey stage on one or two channels, with real integration rather than a demonstration. Enquiry handling on WhatsApp and the website, connected to live availability, is the most common starting point because the volume justifies it and success or failure is measurable within weeks.
In this cluster
Review your guest journey with us
A working session mapping your guest journey against your actual system estate — PMS, booking engine, channel manager, CRM — to establish what is reachable before anything is proposed.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

