Multilingual AI concierge for hotels: language switching, register and transfer

What it is

A multilingual concierge agent answers the front-desk and concierge line in the guest's language. It detects the language from the first words, answers directions, hours, amenities, transport and local questions from one concierge knowledge base, follows the guest when they switch language mid-call, understands sentences that mix two languages, keeps the register the language expects, and transfers to a staff member who speaks the language when confidence drops or the guest asks. It hands bookings and requests to the reservations and guest-services flows rather than improvising them.

The hard parts are not vocabulary. They are detection on short first utterances ("hello, um, sumimasen"), switching without asking the guest to choose, code-switched sentences that are normal speech in Manila, Jakarta, Mumbai and Singapore, and register. In Japanese, the difference between polite and plain forms is the difference between a hotel and a vending machine, and the place agents slip is the refusal: "we do not have that" has to stay honorific. Korean, Thai and formal German and French have their own versions of the same gate.

Independents call this a multilingual AI concierge or front-desk AI. Groups call it language coverage and treat it as a procurement gate per market.

Who buys it

• City and resort hotels in multilingual markets (Singapore, Bangkok, Manila, Kuala Lumpur, Dubai, Barcelona, Tokyo) where the 2 a.m. caller rarely speaks the night porter's language.
• Groups with properties across language regions that want one knowledge base and one agent behaviour rendered in each market's languages and registers.
• Properties serving one large inbound market (Japanese guests in Hawaii or Guam, Mandarin speakers in Sydney, German speakers in Mallorca) where a single second language with the right register changes review scores.

Budget owner: the general manager or guest-experience lead; in groups, operations or brand standards, with a native-speaker reviewer per key language signing off.

KPIs

Pull a quarter of PMS nationality data to list the languages that matter, and count the share of front-desk calls that are information questions by language for one week. Then track language identification accuracy, mid-call switch handling, register compliance by native-speaker review, transfer appropriateness and FAQ containment by language.

The trap is testing with greetings. Every agent greets well in twelve languages. Register fails in refusals and policy statements, detection fails on short code-switched openers, and containment collapses in the fourth language the vendor did not expect you to test. Review full calls, by language, with native speakers.

Demo script

Have native speakers of your top three languages on your side, each with a short code-switched sentence prepared. Give the vendor your concierge knowledge base and your staff language roster for transfers.

1. Short first utterance. Open with "hello... sumimasen, eigo wa..." Pass: the agent recognises Japanese and replies in polite Japanese, offering English if preferred. Fail: it continues in English or asks the guest to pick a language from a list.
2. Keigo through a refusal. In Japanese, ask for a room upgrade at no charge. Pass: a polite, honorific refusal with an alternative. Fail: a slip to plain forms, judged by your native speaker.
3. Interruption. While it explains breakfast hours, cut in with a question about the pool. Pass: it stops and answers the pool question in the same language.
4. Ambiguous time. Ask whether the spa is open "tomorrow evening". Pass: it names the date and the closing time rather than saying "yes".
5. Mid-sentence switch. Switch persona to a Tagalog speaker who says "Pwede ba magtanong, where is the nearest pharmacy na open pa?" Pass: the agent understands the mixed sentence and answers in Tagalog or English per its register rule, without asking the guest to choose.
6. Party-size change in a booking hand-off. Ask in Bahasa Indonesia for a restaurant reservation for two, then "eh, empat orang". Pass: the hand-off to the concierge or reservations flow carries four, not two.
7. Eight seconds of silence. Pass: one short prompt in the guest's language, then a graceful offer to call back or transfer.
8. Out-of-scope. Ask for visa advice and for a comparison with the hotel across the road. Pass: a decline with a pointer to official sources, no comparison, back to the question, in the guest's language.
9. Unsupported language. Have someone speak a language you did not configure. Pass: a short apology in the configured fallback language and a transfer to staff or a message, not a guess.
10. Transfer with context. Ask to speak to a person. Pass: the transfer reaches a staff member on your roster who speaks the language, and that person hears or sees the language and the question so far.

Score each trap pass or fail. A register slip in turn 2 or a forced language choice in turn 5 is a hard stop for the markets they concern.

Compliance notes

Disclosure and recording notices must be spoken in the guest's language to do their job. In the European Union, the AI Act's Article 50 duty to tell people they are talking to an AI applies from 2 August 2026 regardless of language, and recording needs a GDPR lawful basis and notice; in the United Kingdom the same applies under UK GDPR. In Japan, recordings are personal information under the APPI, the purpose of use must be stated, and cross-border transfer requires informing the guest about the destination country, which matters when speech is processed outside Japan. In Singapore the PDPA requires notification of purpose for recordings; in the Philippines, recording without all-party consent is a crime under the Anti-Wiretapping Act, so the notice must be understood, which means spoken in a language the guest understands. In the United States, roughly a dozen states require all-party consent for recording and several have bot-disclosure laws; inbound calls are outside the TCPA consent rule, and any follow-up call or text needs prior express consent with the 8 a.m. to 9 p.m. window applying to anything promotional. In Australia, state surveillance-devices laws differ, so announce recording; promotional follow-ups sit inside telemarketing hours of Monday to Friday 9 a.m. to 8 p.m. and Saturday 9 a.m. to 5 p.m. Informational, not legal advice; the compliance rows on this page carry the sources.

Build or buy

Buy, but buy per language. The speech and language components behind a multilingual agent differ in quality by language, and a vendor strong in Spanish and German may be weak in Thai or Tagalog. Run the demo in each language you care about with a native speaker, score register on refusals, and write the languages and the transfer rules into the contract. Consider a build only if you run a large multi-market estate with a language team that can evaluate and maintain a knowledge base in each language. In either case the acceptance test is the same: a polite refusal in Japanese, a code-switched sentence understood, and a transfer that carries the language and the question.