When a Guest Writes in a Language Your Team Cannot Read: A Practical Hotel Guide
A guest sends a WhatsApp message in a language nobody on shift can read. What should the hotel do? Preserve the original message, use translation only to understand the likely request, classify it by consequence, and route it to someone qualified to answer. For a routine question, a carefully checked translated reply may be enough. [ ]
By Gaurav Sharma · · hotels
A guest sends a WhatsApp message in a language nobody on shift can read. What should the hotel do? Preserve the original message, use translation only to understand the likely request, classify it by consequence, and route it to someone qualified to answer. For a routine question, a carefully checked translated reply may be enough. For anything involving money, a booking change, health, safety, legal terms, accessibility, or a serious complaint, get human review before promising an outcome.
The key is to treat machine translation as a bridge to understanding, not as proof that the hotel has understood the guest correctly. If nobody can verify a consequential reply, acknowledge the message, explain that a team member is checking it, and make the handoff explicit.
Why this is an operating problem, not a translation problem
Language coverage changes by shift. A property may have someone who reads a guest’s language during the day but no such person at night. At 11 p.m., an unfamiliar-language message can sit unseen, or prompt a confident guess from a staff member who catches only a few words.
Neither silence nor a guessed reply resolves the request. The operational question is: who owns the next step, and what can they safely tell the guest while they check?
Set a process that works when the right language speaker is not on duty. That may mean using an approved translation tool for triage, contacting an on-call colleague or language professional, or acknowledging the message and giving a realistic update time. Choose the method based on your staffing and the risk of the request.
The four tiers of language handling
Classify the message by what could go wrong if it is misunderstood, not by its length or apparent simplicity.
| Situation | Who handles it | What is safe | What must not happen | Suggested outcome metric |
|---|---|---|---|---|
| Routine information, in a language covered on shift | Staff member who can read it; another team member may help with the approved reply | Answer using current property information; clarify if the request is ambiguous | Guess about availability, policy, or an exception | Correct resolution without repeat contact |
| Routine information, in a language nobody on shift reads | Designated language owner or staff member using an approved translation workflow | Use translation to identify the question; send only a simple, verified factual reply | Let a rough translation turn into an unverified commitment | Time to a clear answer |
| Consequential message: payment, cancellation, refund, complaint, safety, medical, legal, or accessibility | The relevant human owner, such as reservations, finance, duty manager, or the designated safety contact | Use translation for initial triage; preserve the original; have a qualified person verify meaning and response | Approve, refuse, diagnose, interpret rights, or promise a remedy based only on machine translation | Time to accepted human ownership; unresolved cases |
| Mixed-language or partially understood message | Staff member who owns the request, with language help if needed | Ask a short clarifying question; handle only the part clearly understood | Treat partial comprehension as full confirmation | Repeat-contact rate; clarification resolved |
These metrics are suggestions for your property, not industry benchmarks. If a message indicates immediate danger, follow the hotel’s established emergency procedures and contact the appropriate emergency service. Do not rely on translation as a substitute for emergency response.
What machine translation can and cannot be trusted with
Machine translation can help staff triage a message or draft a reply to a simple, routine question. For example, it may help identify that a guest is asking about breakfast hours. But fluent wording is not the same as verified meaning.
Pay particular attention to names, room types, dates, times, amounts, currencies, cancellation terms, and booking references. A 2025 research paper tested how translation systems preserved entities such as phone numbers, email addresses, and URLs across four languages. It identified cases where these details were changed or omitted. The study used a specific test dataset; it is not a test of hotel conversations. Still, it illustrates why exact details should be checked rather than trusted to survive translation unchanged. Read the research paper.
Food allergies, dietary needs, medication, symptoms, legal language, consent, and accessibility requests require even greater caution. A translated phrase can miss a key distinction or fail to capture the guest’s intended tone. Guidance from the National Center for State Courts is written for courts, not hotels, but it similarly cautions against relying on machine translation alone for complex or high-consequence information, and recommends human review. Read the NCSC guidance.
For consequential messages, a human should review both what the guest wrote and what the hotel plans to say. If the hotel cannot verify a promise, do not make it through a chain of translations.
Where the guest gets lost
A handoff can fail even when the right department is contacted. If the guest has to repeat everything to a second person, they lose time and may feel that nobody has understood them. Tone and context can also disappear in a brief summary.
Give the next owner a handoff packet containing:
- The original message in the guest’s language.
- The working translation, clearly marked as unverified if it has not been checked.
- The guest’s channel and the time the message arrived.
- Relevant booking or room context, shared only through approved channels.
- What the hotel has already told or promised the guest.
- The named person or team responsible for the next update.
Keep the request, accepted ownership, decision, guest notification, and completed action distinct. “I’ve sent this to reservations” does not mean the change has been approved.
Decide your language coverage deliberately
Start with the languages guests actually use in messages, not assumptions based on nationality or market. Review real, appropriately handled message data and booking patterns. Then decide which languages need written coverage, spoken coverage, or both.
A realistic 24/7 plan does not have to mean a fluent employee for every language on every shift. It does need a dependable fallback: who can review an important message after hours, which translation tools are approved for initial triage, and what staff should tell a guest while human help is arranged. Make coverage commitments that match the people and services you can actually reach.
A five-step setup checklist
| Step | Action | Owner | Prerequisite data |
|---|---|---|---|
| 1 | Identify the languages guests use from real message records | Front-office or guest-relations lead | Message-language records, channel, shift, and message category |
| 2 | Classify messages by consequence, not length | GM or front-office manager with department leads | Examples of routine, financial, safety, medical, legal, and accessibility requests |
| 3 | Decide which categories may receive an automatic or staff-checked reply, and which require a person | GM and relevant policy owners | Approved property answers, authority limits, and escalation rules |
| 4 | Assign the escalation path, including who owns it out of hours | Duty manager or operations lead | On-call contacts, backup owner, approved communication channel, and acknowledgement process |
| 5 | Review translated conversations monthly for recurring errors and unclear replies | Front-office manager with language support | Original messages, translations, replies, handoff records, and privacy-approved review access |
Before adopting a translation tool, check how it handles guest data and who may access conversation records. Keep health, payment, identity, and other sensitive details out of unapproved tools and broad staff channels.
Worked example: illustrative assumptions
All details below are illustrative assumptions, not a Voxido or customer result.
At 11 p.m., a guest sends a WhatsApp message in a language nobody on shift reads. A translation suggests they want to change their dates and mentions a food allergy.
- The night-shift employee preserves the original message and uses the hotel-approved method to understand the likely request.
- They treat the date change as unconfirmed. Reservations must check availability, policy, and any price difference before accepting it.
- They treat the allergy as a safety-related disclosure. The message goes to the designated food-and-beverage or duty owner for human confirmation. No dish is described as safe until the hotel has verified it.
- The employee sends a brief, approved acknowledgement in a language the hotel can verify, or uses the agreed fallback to arrange language support. It should say that both requests have been received and are being checked, not that either has been approved.
- The guest is updated once a responsible person accepts the handoff. The hotel records the date-change decision separately from the food-safety confirmation.
The essential outcome is not a fast translation. It is a verified decision and a clear update that does not claim more than the hotel knows.
What to measure
Track response time by language, the share of messages needing human review, repeat-contact rate, reported mistranslation incidents, and whether guests indicate that they understood the final answer. Review examples monthly to spot recurring confusion, for instance, a room-type name that is routinely misread or a reply template that needs clearer wording.
Use these measures to improve the process, not to pressure staff into answering beyond their confidence or authority.
Make language coverage a service standard
A guest should not have to rely on luck, the right person happening to be on shift, to receive a careful response. Define what staff can answer, when translation is only for triage, and who takes ownership when the meaning or consequences are uncertain.
Hotel teams considering technology for guest messaging can review Voxido’s hotel offering as one option for phone and messaging workflows with human escalation. Check current language coverage, supported actions, data handling, and fit for your property before relying on any provider.