The maths
The language a guest gets served in should not depend on the rota
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.
List the languages your guests arrived speaking last quarter, then list the languages on duty last Tuesday at 2am, and the problem states itself. Staffing every language on every shift is arithmetic no property survives: the fluent hire is expensive, the need moves with seasons and events, and the guest who needs the language most — confused, late, holding a problem — arrives precisely when the roster is thinnest. So the coverage becomes chance, and the guest experience in a given language depends on who happened to clock in.
The design that works accepts the arithmetic instead of fighting it. Language competence moves into the system: the routine exchange — questions, requests, confirmations — is carried by AI in the guest’s own language, and the staff console shows every thread in the employee’s language with the original alongside. The people on shift stop being a language barrier or a language lottery; they are the judgement in the loop, in whichever conversation needs judgement.
The options
Three ways to cover guest languages, priced by the night shift
Every property already runs one of these, usually by default rather than decision. The honest comparison is at the hard hour — 2am, full house, a guest with a problem in a language nobody on duty speaks.
| Option | Coverage at every hour | Cost shape as demand moves | Quality of the Arabic | Path to a person | Best for |
|---|---|---|---|---|---|
| Hire for each language | Only while that person is on shift; leave and turnover reopen the gap overnight. | Fixed and high, paid whether the language is needed that week or not. | Excellent, from the right hire — for the hours that hire works. | The person is the service; when they are absent there is no path at all. | The one or two languages that dominate your guest mix year-round. |
| Outsource to a call centre | Broad on paper, but the agent answering has never seen your property or your guest. | Per-interaction pricing that climbs with exactly the volume you were trying to absorb. | Varies by contract and shift; hospitality tone in Arabic is rarely the centre’s strength. | A person, but an outside one — escalation back into the hotel adds a second handover. | Overflow on voice lines, where any answer beats a ring-out. |
| AI-assisted, anchored by your team | Every hour and every supported language at once, because the system does not roster. | A platform cost that stays flat while conversation volume moves with the season. | Arabic built as a first language of the system, not the output of a translation layer. | Your own staff join any thread with the context translated in front of them. | The long tail of languages and hours no roster was ever going to cover. |
In practice
A city property in event season, answering in four languages
A typical engagement, described not named
A city hotel whose base business is domestic and Gulf — served well in Arabic — takes on international event blocks several times a year. For those weeks, the front desk fields questions in languages nobody on the rota speaks, response times stretch, and the reviews from precisely the highest-profile guests dip.
- 01Guest messaging on the website and WhatsApp is made AI-assisted, with Arabic and English as first languages and the event languages enabled as assisted ones with a tighter escalation threshold.
- 02The front-desk console shows every thread in Arabic or English regardless of the guest’s language, with the original text kept alongside so nothing rests on a translation the staff cannot see.
- 03Complaints and anything sensitive route to a person from the first message, in every language — the assisted tier carries directions, requests and confirmations, not apologies.
The property answers event-week guests in their own language at the speed it answers Arabic, without hiring for languages it needs a few weeks a year — and the staff spend those weeks on the conversations that needed them.
Our role
What the system carries in each language and what your people still own
- 01
Arabic as a first language
The Arabic conversations are designed and reviewed as originals — tone, courtesy forms, Gulf phrasing — because a Saudi property whose Arabic reads machine-made has failed its largest audience in its own country.
- 02
The assisted tier, bounded
For lower-volume languages we are explicit about what runs assisted and what routes straight to a person, and the thresholds are yours to review — the system’s reach is set by policy, not by optimism.
- 03
The console your team works in
Staff read and answer every thread in their own language with the guest’s original beside it, so joining a conversation in any language takes the same skill: hospitality.
What good service sounds like is your standard to set in every language; we build the system that holds that standard at 2am in a language nobody on shift happens to speak.
Common questions
What buyers ask
Is machine translation good enough to put in front of hotel guests?+
Raw machine translation is not, which is why the design does not rest on it. Arabic and English are built as first languages: the conversations are authored and reviewed in each, not translated between them. The assisted tier for lower-volume languages does use translation, but inside guardrails — routine, factual exchanges only, the original text always kept, and sensitive conversations routed to a person from the first message. The failure to avoid is not an awkward phrase in a routine reply; it is trusting translation with a conversation that needed judgement.
Which languages should a Saudi property cover first?+
The ones your own message and call logs name, in the order they name them — which is why the engagement starts with that map rather than an assumption. Arabic and English are the fixed floor for any Saudi property. Beyond them the answer is genuinely local: a Makkah-corridor property, a Riyadh business hotel and a Red Sea resort see entirely different language mixes, and the mix moves with seasons and event calendars. The advantage of the AI-assisted approach is that the follow-on decision is small: adding an assisted language is a configuration and review exercise, not a recruitment round.
Do we still need multilingual staff if the system translates?+
Yes — the system changes what you hire for, not whether you hire. Fluency stops being the scarce gatekeeping skill for routine service, because the assisted tier carries that; what remains scarce is hospitality judgement, and the console lets whoever has it join any conversation. Properties still benefit from fluent staff in their dominant guest languages, where a human voice carries warmth no assisted exchange matches. What disappears is the trap of hiring adequate hospitality for the sake of a language, or losing excellent hospitality for the lack of one.
In this cluster
Talk it through with us
A map of your guest conversations by language, channel and hour, and the shortest honest route to covering the gaps it shows.
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

