A guest deciding between your hotel and the one down the road asks the same few things every time. Is breakfast included? What time is check-in? Can we bring the dog? How far is the beach? Then, once they have booked, a second set arrives: how do we get there from the station, is there parking, what should we pack for the hills in December. Most of those answers are already on your website, or should be.
A chatbot that reads your pages can answer both sets at one in the morning, when the guest is actually planning the trip. What it must not do is quote a rate, confirm a room or promise an upgrade. The product steps are TailGPT's, and the plan figures are as of 4 October 2026.
Which questions can a hotel chatbot answer before a guest books?
Every question whose answer is written on a page or document the chatbot has read, and nothing beyond it. TailGPT answers only from the pages you tick and the files you upload, with no general knowledge mixed in. That is the point for a hotel: a policy quoted wrongly at the booking stage is a dispute at the front desk.
| What guests ask before booking | Where the answer has to be written |
|---|---|
| What rooms do you have? How many people fit? | One page per room type: beds, size, view, maximum occupancy, extra bed |
| Is breakfast included? Are taxes extra? | Room pages or a tariff page, saying what each plan includes |
| What time is check-in and check-out? | A policies page, including what early check-in and late check-out depend on |
| What is the cancellation policy? | The same policies page, in plain sentences with the number of days |
| Are pets allowed? Children? | House rules or FAQ, with any charge or condition |
| Is there parking? | Contact or facilities page: free or paid, covered, space for a tempo traveller |
| How far is the beach, the fort, the airport? | A location page with distances and travel times you have checked |
| What ID do guests need? | Policies page, stating exactly what you ask for at check-in |
The last two rows deserve a note. A chatbot that answers only from your pages will not estimate that the beach is "about 2 km away" from general knowledge, so if your location page does not say it, the guest hears that the website does not cover it. Write the distances you would give on the phone: "1.2 km to Calangute beach, about 15 minutes on foot". And ID and stay policies are exactly the questions a guest is shy to ask a person, so they get asked in a chat window. If your hotel has a rule about local IDs or who may share a room, state it plainly on the policies page so the answer is yours, not a guess.
What can it answer after a guest has booked?
Everything about getting there and staying there that your website already publishes. The chatbot does not know who has booked: visitors need no account, and it cannot look up a reservation. But a guest who has booked comes back to your website with practical questions, and those are often the ones that land on the owner's phone at night.
- Directions. From the airport, the railway station and the bus stand, with the last turn described in words. "After the petrol pump, take the second left; the road is unpaved for the last 400 metres" is worth more than a map embed, which a chatbot cannot read.
- Arrival. Check-in process, where to park, what happens if they arrive after the reception closes, whether luggage can be left before check-in.
- What to bring. Warm clothes for the hills, trekking shoes, a torch for a homestay where the power goes in the monsoon, cash if the nearest ATM is 8 km away.
- Meals. Breakfast hours, whether lunch and dinner are served and need ordering ahead, vegetarian and Jain meals.
- House rules. Quiet hours, smoking, alcohol, visitors, pool timings.
- Wi-Fi. Only if it is published, and it should not be. A Wi-Fi password on a public page is public. Write "Wi-Fi is free in all rooms; the password is on the card in your room" instead, and the chatbot will say exactly that.
That last point applies generally. A chatbot on your website only ever knows what any stranger could already read there, so nothing private belongs on the pages or in the documents you give it: no guest lists, no booking sheets, no door codes.
What must a hotel chatbot never do?
Quote live rates or availability, confirm or change a booking, or promise anything that depends on the day. TailGPT is a chat window on your website that answers from your pages. It is not connected to a booking engine or a channel manager, does not take guests' details, and does not hand a conversation to your staff.
| A guest asks | What the chatbot can honestly do |
|---|---|
| "What is the rate for 14 to 16 November?" | Explain how pricing works as your pages describe it, and name the page where the dates can be checked |
| "Do you have a room free this weekend?" | Nothing live. It can name your booking page or reservations number |
| "Please confirm my booking" | Nothing. It cannot see or change bookings |
| "Can you upgrade us for our anniversary?" | Repeat your published policy on upgrades, if there is one. It cannot promise one |
| "Can we check in at 8 am?" | Quote your early check-in policy. It cannot guarantee it |
Rates need one decision from you. If your website has a tariff table, the chatbot will quote it, because that is what the page says. That is fine for a homestay with fixed rates. For a hotel whose prices move with the season and the booking engine, either remove the static table or put a sentence beside it: "Rates vary by date; the Book Now page shows the price for your dates." Then the chatbot gives that sentence instead of a stale number.
Write the day-dependent policies as policies: "Early check-in depends on availability on the day and cannot be confirmed in advance." The chatbot quotes that, and nobody arrives at 8 am believing they were promised a room.
Answers appear as plain text, without clickable links. When the chatbot sends a guest to book, it names the page in words, and it can give a phone or WhatsApp number only if that number is written on a page it has read. Put your booking route in a sentence on the contact page, and make sure that page is ticked.
Can guests ask in Hindi?
Yes, in beta. A guest can ask in Hindi and get an answer built from your English pages, phrased in the language they asked in. The answer still comes only from your pages; the language changes, the facts do not. For a hill station or a pilgrimage town with many Hindi-speaking families, that is worth testing before you go live: ask your three commonest questions in Hindi and read what comes back.
How do you keep seasonal policies current?
Change the page, then have TailGPT read the website again. A chatbot quotes what it last read, and TailGPT has no automatic refresh: the website is re-read when you ask, from a monthly allowance. As of 4 October 2026, Starter includes 2 re-reads a month and Growth includes 8.
Hotels have a calendar of changes, which makes this easy to plan:
- Publish the season a week early. A peak-season minimum stay, a compulsory New Year's Eve dinner, monsoon closure dates, winter check-in times. Edit the pages, read the site once, and the chatbot is right before the first guest asks.
- Put dates in the sentence. "From 20 December to 5 January, the minimum stay is three nights" stays correct even if a re-read is late, and nobody applies it in March.
- Use documents for the guest handbook. A house-rules or arrival guide as a PDF or Word file is answered from like a page. Uploading a corrected file with the same name replaces the old one within seconds and does not use a re-read.
- Untick last season's offers. An expired package page keeps answering until it is unticked and the site is read again.
The full routine is in how to keep your chatbot's answers up to date, and the restaurant side of the same problem, menus and timings, is in AI chatbot for restaurants.
Is it worth it for a homestay owner who runs everything alone?
It is worth it when the same questions take up time you do not have, and you have a website you can add a line of code to. A homestay owner is the reception, the kitchen and the driver. The questions about directions arrive while breakfast is on the stove.
Setting it up is short. You add your website, tick the pages worth reading, try the finished chatbot with real questions in the dashboard, and paste one line of code before </body>. It works on any site that lets you add a script, including WordPress, Wix, Squarespace and Webflow. How it works shows each step.
Two honest limits. First, it needs a website of your own. A homestay that exists only as a listing on a booking platform has nowhere to put it. Second, it is a fixed monthly cost:
| As of 4 October 2026 | Starter | Growth |
|---|---|---|
| Price | ₹4,000 a month | ₹8,000 a month |
| Websites live at once | 1 | 3 |
| Pages read | 1,000 | 7,500 |
| Questions a month | 4,000 | 10,000 |
| Website re-reads a month | 2 | 8 |
If your website gets a handful of enquiries a week, answering them yourself may be the better use of ₹4,000. If guests ask the same ten things over and over, and some book elsewhere because nobody answered at midnight, the sum looks different. Every question counts towards the month, including one your pages do not cover; only refusals, such as attempts to give the chatbot orders, are free. A small group with three properties on three websites is what Growth is for. The full table, including Enterprise, is on the pricing page.
What should you test before it goes on your website?
The questions your phone already gets, checked against your own pages. The free trial needs no card: one website, up to 500 pages read, one chatbot and 20 test questions in the dashboard. It cannot upload documents or go on the website until you choose a plan.
- What time is check-in, and can we come early?
- Is breakfast included?
- What is your cancellation policy?
- Can we bring our dog?
- How do we get there from the railway station?
- What is the rate for next weekend?
- Can you confirm my booking?
- One of the above, in Hindi.
Each answer should come from your page, say plainly that the website does not cover it, or name your booking route. Question six should never produce a number you did not publish, and question seven should never sound like a confirmation. After launch, read the conversations in Show chats every week; the dashboard also lists the questions your pages could not answer, with how often each was asked. What to do when your chatbot says it does not know covers turning those into pages.