The conversation with the guest, from first contact to return.
It talks to the guest on the channels they already use. It answers the questions, sends what needs sending, and logs everything.
A channel is switched on, not bought separately. What changes is the moment, not the agent behind it — and the list keeps growing.
Message it before you decide.
Nothing to install, no appointment needed.
Ask the question a guest would ask. It is the same bubble that sits in the corner of the hotel’s site.
Write as a guest
Send the message you would send at midnight and watch the reply reach your phone.
The same agent, another channel
Scan the code with the camera or open the conversation on your computer. It answers exactly the same.
Each channel solves a different moment.
They share the agent, the knowledge and the conversation log. You switch on what the operation needs, and add the rest when it is needed.
Site bubble
Before bookingIt is the only channel that talks to a stranger. Whoever is on the site has no booking yet and has concrete questions: pets, parking, breakfast, late arrival. Without an answer on the spot, the booking ends up on an OTA, with commission.
There is one bubble. With Voice on the site active, the same bubble also answers out loud, and the transcript sits in the same thread as the written conversation.
- Measured in conversion. A question answered on the spot keeps the booking in the direct channel.
- Contact captured for the CRM. The anonymous visit becomes a qualified lead, with intent on record.
- Unlimited messaging. No meters, no cost per conversation, no surprises on the invoice.
- Installs in a snippet of code. Without rebuilding the site or touching the booking engine.
WhatsApp, Telegram and SMS
The channels for guests who already have a booking. They talk to the guest where they already write every day, from pre-check-in to a towel request, and each request reaches the operation with a department and a deadline.
We are a Meta Tech Provider. We connect the hotel directly to the WhatsApp Business API and messages are billed by Meta to the hotel, at Meta’s own list price. We add no margin on sending, unlike most guest-messaging tools.
- The number belongs to the hotel. The account lives on the WhatsApp Business API, off the personal phone of whoever is at the desk.
- Telegram for markets where it is the preferred channel. Same agent, same knowledge base.
- SMS when there is no internet. It reaches any phone, with no apps and no mobile data, for critical alerts and roaming.
- Measured in operations. The message becomes a request in the Service Desk, with an owner and the clock running.
- The moment is set in the automations. When the agent speaks, and on which channel, is configured in Journey Hub.
The channel for what has to be in writing and found later: confirmations, documents, group requests and post-checkout follow-up. It works before and after the stay, and it is where the conversation stops getting lost in a shared inbox.
- Answers the repetitive. Hours, policies and confirmations go out without passing through anyone.
- Routes the rest. What needs a person goes to the right team, with the conversation thread in front of them.
- Sits in the guest’s history. Next to the conversations from the other channels, not in a separate folder.
- Serves the post-checkout. Review request, invoice, whatever was left unresolved.
One base, one layer per channel.
The hotel’s knowledge, hours, services and policies, is configured once and inherited by every channel. Cada canal pode depois acrescentar a sua camada: the agent answering before booking needs the cancellation policy and conversion arguments; the in-room concierge needs the spa and room-service hours. What this avoids is the worst case: the same information kept in four places, drifting apart over time, giving different answers depending on the channel.
An unanswered question ends up on an OTA.
After hours, in another time zone or with the front desk busy, the visitor does not wait: they close the tab and book where they get an answer. Text AI always answers and turns the rest into operations.
- Writes from the hotel’s knowledge. Hours, services and policies, trained by you.
- Over 100 languages. Automatic translation, with no per-language agent to set up.
- Routes and opens operations. The message creates the right request, with the clock running.
- Hands over to a person when needed. In the same thread, with the whole history in front of them.
Four steps, from message to operations.
Receives
The message arrives on any channel and is read in the language it was written in.
Understands
It identifies the request in natural language and asks for what is missing, such as the dates or the room number.
Answers or routes
It answers what it knows and passes the rest to the right department, or to a person, with a deadline.
Records
It stores the conversation, the contact and the intent in the guest’s history.
What hotels ask about Text AI.
What is the difference between the site bubble and the messaging channels?
Do we have to switch on every channel?
How does WhatsApp billing work?
Is the WhatsApp number ours?
How is it installed on the site?
Is there a message limit?
In how many languages does it answer?
Does the agent know when to stop and call a person?
See the assistant answer with your hotel’s knowledge.
In the demo we configure the agent with your property’s policies and services and show the conversation capturing the contact and opening the request.