Which chatbot does your hotel need?

"Hotel chatbot" is a label that covers very different things today. Under the same name you'll find little widgets that answer four questions, AI assistants that hold a real conversation, and platforms that actually get things done. Choosing well starts with knowing which one you're looking at.

What a hotel chatbot is

A hotel chatbot is an assistant that serves guests or would-be guests over chat. It lives on the website, on WhatsApp, in the hotel's app or on social media. What changes from one to the next is what it can do: some only answer, others also open tasks, report issues, take bookings or charge.

The three kinds that really exist

1. The FAQ chatbot

The most common one. It answers the usual: opening hours, directions, house rules, what's included at breakfast. It runs on pre-written answers or on AI limited to the hotel's documents. It's useful for taking repeat questions off the front desk. Its limit: it doesn't do anything. No tickets, no bookings. If the guest wants more, a person has to take over.

2. The AI concierge that acts

This is what makes the difference. It doesn't just answer: it opens the request with the right department, places the booking, alerts maintenance or sends the room service order. Talking to it is like talking to the front desk, in the guest's own language. For anything that affects the stay, it identifies the guest by room and PIN.

That's where Estevano fits: every message that asks for something becomes a task in the hotel's console.

3. Voice, the chatbot that talks

The same concierge on the phone, able to do the same things. It covers the silence of calls nobody picks up and serves people who don't type: older guests, urgent situations, tricky languages. A well-built AI voice receptionist works just like the chat concierge: same job, spoken out loud.

What a good chatbot solves

• Before booking: questions about availability, pets, parking or how far the beach is.
• Before arrival: check-in information, preferences, special requests and transfers.
• During the stay: towels, air conditioning, noise, restaurant or spa bookings, room service and issues.
• After: invoices, lost property and anything left pending.

An FAQ chatbot covers the before-booking stage well and some of the pre-arrival one. For the stay and day-to-day operations you need a concierge that acts.

Where typical chatbots fall short

• They don't know the hotel. They repeat generic answers because nobody keeps the hotel's own information alive. Without it, no AI answers well.
• They don't know who the guest is. Without room and PIN they can't authorize anything. They stay stuck at informing.
• They live in silos. Website chat here, WhatsApp there, the app somewhere else. The team ends up juggling three inboxes.
• They don't touch operations. If the chatbot doesn't open tickets, the sticky notes stay.

How to choose without getting it wrong

Five questions to ask before you sign:

• Does it act or only answer? If it doesn't open tickets or take bookings, it's still an FAQ bot.
• How is the hotel's information kept up to date? If every change means asking IT, it won't scale.
• Does it really speak several languages? Try it in German or French and you'll learn a lot.
• Is it connected to the team's console? If what the guest asks for never reaches the team, the guest never gets an answer.
• Does it cover voice too? The phone is still a main channel for hotels. Without voice, there's a gap.

When an FAQ bot is enough, and when it isn't

If your hotel's problem is too many repeat questions on the website, a good FAQ chatbot may be enough, and it's cheap. If the problem is a team spending the day putting out fires across WhatsApp, calls and the corridor, what you need is a concierge that acts and one shared console. The difference between the two isn't sophistication: it's which problem you're trying to solve.

To see an AI concierge in production, the Santo Domingo Bay case shows how it runs on Estevano. The modules are on the product page and the plans on their own page.