Live chat looks like good service: a friendly box in the corner, a promise that someone is there. In a small business, that someone is also serving the counter, running the class, seeing patients or packing orders. The chat box pings, nobody sees it for forty minutes, and the visitor has already left, with the impression that you are slow to reply.
This guide is for businesses where nobody is free to sit on live chat. It covers why an unwatched chat box costs more than it seems, what an AI chatbot can take on with no one on shift, how to set it up so visitors still reach a person when they need one, and what it cannot do. The setup is TailGPT's, with figures as of 4 October 2026.
What goes wrong with live chat when nobody is free?
The visitor waits, and then gives up. Live chat sets an expectation of a reply in a minute or two. When the reply comes in forty minutes, or the next morning, the visitor has found the answer elsewhere, called a competitor, or decided not to bother.
The common workarounds each have a cost:
- An offline form. When nobody is online the chat turns into "leave a message". That is a contact form with extra steps, and visitors know it.
- Hours on the chat. "We are online 10 to 6" means the chat is closed when many visitors arrive: evenings and weekends.
- Answering from a phone. The owner answers between other jobs. Replies are slow at busy times, which are exactly when visitors come.
None of this is anyone's fault. Live chat assumes a person whose job is the chat window, and most small businesses do not have one. AI chatbot or live chat: which does your website need? sets out the choice in general.
What can an AI chatbot answer with nobody on shift?
Everything your website already says. Most live chat messages in a small business are repeats: the same twenty questions about timings, prices, delivery, location and policies. If the answer is written on a page, an AI chatbot that reads the page can give it, at once, at 11 at night.
A yoga studio in Ahmedabad, for example, might find its chat messages break down like this over a month:
| Kind of question | Example | Can a bot answer from the site? |
|---|---|---|
| Timings and batches | "is there an evening batch on weekdays" | Yes, from the schedule page |
| Fees | "monthly fee for beginners?" | Yes, from the fees page |
| Location and parking | "where exactly is it, is there parking" | Yes, from the contact page |
| Policies | "can I pause my membership if I travel" | Yes, if the policy is written down |
| Their own account | "did my payment go through" | No; needs a person |
| A judgement call | "I have a knee injury, is it safe for me" | No; needs a person |
The figures will differ for your business, but the pattern is common: most messages are in the first four rows. Those are the ones a chatbot takes off your hands.
TailGPT answers from the pages you tick and the documents you upload, with no general knowledge. When the pages do not cover a question, it says so plainly instead of guessing. A follow-up such as "and on Saturdays?" works, because it is given the last three exchanges of the conversation. Visitors can ask in Hindi and get an answer from English pages, which TailGPT marks as beta.
What happens to the questions that need a person?
The bot points the visitor to you, using the contact details written on your pages. TailGPT has no hand-off to a person and no live chat inbox, so plan the route in advance.
- Write your contact routes on a ticked page. Phone, email, a WhatsApp number if you use one, and the hours each is answered. The bot can give a phone or WhatsApp number only if it is written on a page it reads; one that appears on none of your pages is removed from an answer.
- Say what needs a person. One line on your contact or FAQ page, such as "For payments, injuries or changes to your membership, call the studio", gives the bot something to quote.
- Make the route realistic. If the phone is answered 7 to 9 in the morning, say so. A visitor who knows when to call is much less frustrated than one who calls at noon and gets no answer.
This is the same route a visitor would take today if they read your contact page. The bot just gets them there faster.
How do you set the right expectations in the first line?
With the greeting. TailGPT lets you write the greeting visitors see when they open the chat, and it is the most useful sentence in the setup. It should say what the bot can help with, and where to go for anything else.
Hello. I can answer questions about our classes, fees and timings. For payments or anything about your own membership, please call the studio.
Compare that with "Hi, how can we help?", which implies a person is there. Visitors who know they are talking to a bot that reads your website ask better questions and are not disappointed when it sends them to the phone.
The role helps too. Support is calm and factual, FAQ is short and direct, and Sales leads with products and pricing and points to the next step. The role changes the manner, never what the bot is allowed to say. How to set your chatbot's role covers the four options.
How do you set one up without anyone technical?
In an afternoon. The full journey is on how TailGPT works:
- Sign up with an email or Google; the free trial needs no card.
- Add your website. TailGPT lists its pages and ticks a sensible set; make sure your contact, fees, timings and policy pages are among them.
- Create a chatbot, choose a role, and write the greeting.
- Ask it your commonest questions with Try demo. The trial allows 20 test questions.
- Choose a plan and paste one line of code just before
</body>. If you had a live chat script on the site, remove it, so visitors see one bubble, not two. - Check the chatbot shows as Live in the dashboard, which means TailGPT has seen the bubble load on your site.
As of 4 October 2026, Starter is ₹4,000 a month with 4,000 questions and one chatbot, and Growth is ₹8,000 a month with 10,000 questions and three chatbots. Plans are not priced per person. The full table is on the pricing page.
How do you keep an eye on it without watching it?
Read the conversations once a week instead of watching the window all day. That is the trade: no live replies, but a complete record you can read when you have time.
Show chats lists every conversation each chatbot has had, as chat bubbles, with search across every word and filters for the last 7, 30 or 90 days. The Home dashboard shows the answer rate and a list of the questions your chatbot could not answer, with how often each was asked. A question that turns up ten times a week is a page worth writing. Add the answer to your website and read it again, or upload it as a document.
Fifteen minutes a week is usually enough. Reading every conversation your bot had covers the page, and an after-hours customer support chatbot covers the evening and weekend side in more detail.
When do you need a person in the chat after all?
When most of your messages are in the last two rows of the table: questions about a visitor's own order, booking or account, or questions that need judgement. A chatbot that answers from your pages cannot look up an order, take a booking, or decide whether a class suits someone's injury. It also cannot collect a visitor's email address or phone number for you to call back.
If your messages are mostly like that, live chat with a person, or a phone line answered promptly, is the right tool, and the chatbot is a supplement at most. If they are mostly the first four rows, the chatbot does the job live chat was meant to do, without needing anyone to sit by it. From scripted chat flows to AI answers covers another common setup, where a scripted menu stood in for the person.