Multilingual Guest Messaging
One agent across WhatsApp, OTA inboxes and email, answering guests in their own language from the PMS reservation and house rules. Refunds, upgrades and complaints go to the desk.
Open pageAnswers in the guest's language. Staff decide. AI for hotels means systems that answer guests in their own language, draft review replies and support pricing decisions from the hotel's own data, connected to the PMS it already runs. Anything that commits the hotel goes to a person.
AI for hotels means systems that answer guests in their own language, draft review replies and support pricing decisions from the hotel's own data, connected to the PMS it already runs. Anything that commits the hotel, such as a refund, an upgrade or compensation, goes to a person.
The hospitality systems we build follow one rule. The model answers only from what the hotel has told it: the guest's own reservation in the PMS, the house rules, the policies, today's opening times. When the answer is not there, it says so and passes the question on. Anything that commits the hotel, such as a refund, an upgrade, a compensation offer or a complaint about safety, is drafted for a member of staff rather than sent.
We are a small studio in Barcelona, a city where one front desk can serve guests from forty countries in a week. That is the real shape of the problem: not a chatbot on a website, but every channel, in every language, joined to the systems that hold the answer. Language quality is tested per language on the hotel's own past conversations, because a model that is fluent in English and approximate in Korean is a different product in each.
One agent across WhatsApp, OTA messaging, email and web chat, answering pre-arrival and in-stay questions in the guest's language from the reservation and the house rules, and handing anything else to staff.
SEE GUEST MESSAGING →Demand signals, pickup and competitor rates gathered into a daily brief with a recommended move and the reason for it. The revenue manager sets the price; the system explains the case.
SEE REVENUE MANAGEMENT →Replies to Google, Tripadvisor and Booking.com reviews drafted in the reviewer's language and the hotel's voice, with complaints routed to the department that can fix them before anyone publishes.
SEE REVIEW RESPONSE →Integrations that read and write across the PMS, channel manager, housekeeping and maintenance tools, so a guest request becomes a ticket in the right place rather than a message someone forwards.
SEE CROSS-PLATFORM WORKFLOWS →These are engineering controls we build into the architecture, not certifications. QQuantum.ai holds no security certifications, and the legal determinations your property needs, under GDPR, the EU AI Act transparency duties or national guest-registration rules, remain yours to make — see our trust centre.
One agent across WhatsApp, OTA inboxes and email, answering guests in their own language from the PMS reservation and house rules. Refunds, upgrades and complaints go to the desk.
Open pageDemand forecasts and rate recommendations back-tested on the hotel's own history, with the reasons written down. The revenue manager approves every rate before it reaches the channel manager.
Open pageReplies to Google, Tripadvisor and Booking.com reviews drafted in the reviewer's language and the hotel's voice, with the complaint routed to the team that can fix it. Sensitive replies wait for a manager.
Open pageMostly in three places. Guest messaging, where an agent answers routine pre-arrival and in-stay questions across WhatsApp, OTA inboxes and email. Revenue management, where models forecast demand and suggest rate moves. And reputation, where replies to reviews are drafted for a manager to approve. Behind those sit operational uses such as housekeeping scheduling and maintenance tickets. The useful ones are connected to the PMS; the disappointing ones answer from a generic model with no access to the reservation.
Current models handle the major European and Asian languages well and smaller ones less reliably, so we test each language the hotel actually receives on its own past conversations before switching it on. The agent replies in the guest's language, keeps the staff view in the language the desk works in, and passes a conversation to a person when its confidence in either the language or the answer drops.
Not in the systems we build. What it removes is the repetitive part of the job: the tenth question about parking, the check-in time, the Wi-Fi password, the airport transfer. Staff keep the conversations that need judgement, and every commitment the hotel makes, from a refund to an upgrade, is approved by a person. The realistic gain is a desk that has time for the guest standing in front of it.
It has to, because the reservation, the room and the guest's preferences live there. Oracle Opera Cloud, Mews, Cloudbeds and Apaleo all expose APIs, and we start with read access only. Older on-premise systems without an API take longer and sometimes need a middleware layer. The PMS integration is usually the largest part of the build and sets the realistic timeline.
Make the facts consistent and machine-readable everywhere they appear. AI search tools and assistants assemble answers from the hotel website, the Google Business Profile and the OTA listings, and they repeat contradictions. Keep amenities, policies and opening times identical across all of them, publish them as structured data on the website, and answer the common questions in plain text on the pages themselves.
Guest messages contain personal data, so the system needs a lawful basis, processor terms with any model provider and a retention period. Under the EU AI Act transparency duties, guests should be told they are talking to an AI system. We also keep identity documents out of chat entirely: national guest-registration rules, such as Spain's Real Decreto 933/2021, belong in the check-in process. Whether a deployment meets these rules is the hotel's determination.
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
Start with a sample of last month's guest conversations. We will show which questions can be answered from your own systems, and which should stay with the desk.
30-minute technical call · no deck