Key takeaways
- Start a support chatbot on the questions your team answers the same way every time, such as FAQs, status lookups and bookings.
- Keep complaints, refunds, policy exceptions and anything with legal, medical or financial weight with people.
- Ground every answer in your own content, with the source shown, and have the bot say so when your content doesn’t cover a question.
- Design the handover first: a person should get the whole conversation, and the customer should never have to repeat themselves.
- Judge it by questions resolved without a repeat contact, not by how many conversations it closed.
A chatbot on your support desk can answer the same twenty questions at any hour, or it can frustrate customers who only wanted a person. Which one you get depends less on the technology than on four decisions: what it is allowed to answer, where its answers come from, how it hands over to a person, and how you measure it. This guide covers each of them, and what drives the running cost.
Should you put a chatbot on customer service?
Put a chatbot on customer service when a large share of your incoming questions repeat, have one right answer and are already answered somewhere in your own content. Pull a month of tickets, emails or chats and sort them. If the same questions keep coming back (where is my order, can I change my booking, what is your returns policy), a chatbot can take them and give your team time for the conversations that need a person.
If most of your contacts are complaints, one-off problems or questions that need someone to look into an account and decide, a chatbot will mostly pass them on, and you pay for a step that adds little. Fix the help content or the self-service pages first.
What should a support chatbot automate, and what should stay human?
Automate the questions that are repetitive and have one right answer, and keep with people anything that needs judgement or carries risk. The line is not about how hard a question sounds. It is about what happens if the answer is wrong.
Repetitive, with one right answer
- FAQs with stable answers, such as opening hours, delivery areas and returns policy
- Order, booking or ticket status lookups
- Appointment booking and rescheduling
- Collecting a customer’s details and problem before a handover
- Out-of-hours triage, so urgent issues reach a person first thing
Needs judgement or carries risk
- Complaints and upset customers
- Refunds and exceptions to policy
- Questions with legal, medical or financial consequences
- Anything the bot can’t answer from your own content
Write this split down before any build starts, and make it the bot’s instructions. When a question falls on the human side, the bot’s job is to collect the details and pass it on, not to try.
Which kind of chatbot do you need?
You need a hybrid for most support work: fixed flows for tasks such as status lookups and bookings, AI for questions phrased in many different ways, and a person for everything else. A purely rule-based bot is enough when a handful of scripted tasks covers almost everything customers ask.
If you are weighing a chatbot against an agent that takes actions on its own, our guide to what an AI agent is sets out the difference.
Planning a support chatbot?
Bring your top questions and where the answers live today, and we’ll talk through what to automate and how the handover should work.
How do you stop a chatbot from making things up?
You stop a chatbot from making things up by making it answer only from your own content, show the source with every answer, and say plainly when your content doesn’t cover a question. The common technique is retrieval-augmented generation: the system finds the passages in your help articles and policies that match the question and asks the model to answer from those alone. Our guide to what RAG is explains how it works and why answers can still go wrong.
Four habits matter as much as the technique:
- Refuse what’s out of scope. A support bot should not offer opinions, legal or medical advice, or answers about competitors’ products. Tell it what it may answer, and test that it declines the rest.
- Keep the content current. A bot quoting last year’s returns policy is worse than no bot. Give one person the job of updating the content when policies, prices or products change.
- Keep personal data out of it. Send the model only what a question needs, and keep details such as card numbers, ID numbers and health information out of prompts and logs where you can. Check what the model provider can see, how long your logs and theirs are kept, and the provider’s data-use terms for the plan you use, including whether your data may be used to train their models.
- Log what it can’t answer. Every question it couldn’t answer is a gap in your content, and the list shows the team what to write next.
The NFTR Assistant we built (on the NITI Aayog Frontier Tech Repository portal) works this way: it answers from the knowledge base, cites its sources and reports unanswered questions to admins, so the gaps show up for the team to fill.
How should the handover to a person work?
The handover should be quick, available at any point, and pass the whole conversation to the person, so the customer never repeats themselves. It is the part of a support chatbot to design most carefully, because it is where customers decide whether the bot helped them or got in their way.
Decide three things in advance:
- What triggers it. The customer asks for a person; the question is on the keep-human list; the bot has failed to answer twice; the customer sounds upset.
- What the person sees. The conversation so far, the customer’s details and order or account, and the bot’s short summary of the problem.
- What happens outside staffed hours. The bot says when someone will reply, takes the details and creates a ticket. It never pretends a person is about to join.
How do you roll out a support chatbot?
Roll it out in small steps: pick the repeating questions, fix the content behind them, design the handover, test on real past questions, then launch on one channel and review every week.
Testing deserves its own plan before launch. Keep a set of real questions with the right answer and source for each, add the questions it should refuse, and run every version of the bot against the whole set, so you see when a change helps one answer and quietly breaks another. If you plan to build it yourself, start with how to build a chatbot in Python.
How do you measure whether a support chatbot is working?
Measure a support chatbot by how many questions it resolves without the customer coming back, and by how satisfied those customers are compared with customers your team helped. The deflection rate (the share of conversations it closed on its own) is the easy figure to report, and on its own it misleads: a customer who gives up on the bot also counts as closed.
Track these together:
- Resolved without a person, and without a repeat contact. Count a conversation as resolved only if the same customer doesn’t come back about the same issue within a few days, by chat, email or phone.
- Satisfaction after bot conversations. Ask one short question at the end, and compare the answers with the same question after conversations your team handled.
- Handover rate and reasons. How often it passes to a person, and why. A rising “couldn’t answer” share means the content needs work.
- Wrong answers. Read a sample each week and count any answer that states something your content doesn’t say. One is worth fixing that day.
- The unanswered list. The questions it couldn’t answer, ranked by how often they come up. This is the week’s content plan.
What does a support chatbot cost to run?
A support chatbot’s running cost depends on how many conversations it handles, how long they run, how much of your content is sent with each answer, which model answers, and whether you built it or pay for a tool. People’s time to review conversations and update content belongs in the estimate too.
Where else can AI help customer service?
Beyond the chatbot, AI can help the people who answer customers. It can sort and route incoming messages to the right team, flag messages that read as angry or urgent so a person sees them first, draft a reply from your help content for an agent to check and send, and point out customers who have gone quiet after a problem. Each of these works from data you already hold, such as past tickets and order history. Keep the decision with a person until you have measured how often the AI gets it right, and start with whichever one takes the most repetitive work off your team.
How we’d approach a support chatbot
Our AI chatbot development page covers how these builds are planned and run. If what you need is a chatbot for your website built from your own content, TailGPT is the website chatbot product Tailwebs makes.
