# Customer Service Chatbot: How to Pick One That Answers Right

> A customer service chatbot needs five parts: knowledge, channels, handoff, actions and a meter. See which tools cover which part, and how to combine them.

_Source: https://professionalstoolkit.com/articles/customer-service-chatbot — The Professional's Toolkit · updated November 2026_

---

A customer service chatbot is an AI agent that answers customer questions in chat, email or messaging from knowledge you control, and passes the conversation to a person when it is unsure. No single tool solves the whole job. A setup that works has five parts: the knowledge it reads, the channels it answers on, a clean handoff to your team, actions on real records, and a meter you check. Pick the product by which part your customers lean on hardest.


**5 parts** — Knowledge, channels, handoff, actions and a meter: what a complete customer service chatbot needs



- **Clear and conspicuous** — How California's bot law says a bot must be disclosed
- **30 seconds** — LiveChat's AI Agent can open a ticket when no teammate answers in that time
- **No rollover** — Unused AI resolutions at Zendesk and AI sessions at Freshdesk do not carry over


## What a complete customer service chatbot needs

Most chatbot projects fail on the parts around the bot, not on the bot itself. The AI writes fluent sentences on day one. What it cannot do on day one is know your return window, reach the order system, or tell when an angry customer needs a person. Each of those is a separate piece of work, and each product covers them differently. Map the five parts first. Then look at tools.

1. **Knowledge.** The articles, pages, files and short answers the bot reads. A chatbot knowledge base is only as good as its weakest article, and the bot will repeat outdated text with confidence.
2. **Channels.** Website chat, email, Messenger, Instagram, WhatsApp, SMS. A bot that answers only one of them leaves the rest to your team.
3. **Handoff.** The moment the bot stops and a person takes over, with the conversation history attached.
4. **Actions.** Looking up an order, changing an address, opening a ticket. Without actions, the bot can only explain policy.
5. **Meter and report.** AI answers are counted and billed by a unit. You need to see what it resolved, what it escalated and when the allowance runs out.

Here is how each tool in our catalog covers the first two parts.

| Tool | Where its AI answers | What it answers from |
|---|---|---|
| Zendesk | Messaging, email, web forms, voice | Connected knowledge sources |
| Help Scout | Beacon chat and email | Docs, web pages, files, Google Docs, text snippets |
| Tidio | Live chat, Messenger, Instagram, WhatsApp, first email of a new thread | The knowledge you supply |
| LiveChat | Website chat, WhatsApp, Messenger, Instagram, SMS | Websites, files, Articles |
| Gorgias | Email, chat, Instagram DMs, Messenger, WhatsApp, SMS with an add-on | Guidance, help center, website, documents, Shopify data |
| Freshdesk | Email, portal and web-form tickets | Solution articles, files, public URLs, Q&A pairs |
| Zoho Desk | ASAP widget and messaging chatbots (Enterprise); Answer Bot from Standard | Knowledge base articles |


> 💡 **Audit articles before launch:** Read every help article the bot will use and delete or fix the outdated ones. The bot repeats old text with the same confidence as new text.


## The handoff is the part customers remember

A customer forgives a bot that says *I'm not sure, let me get someone*. They do not forgive one that invents a refund rule or loops the same answer three times. So judge every tool on how it lets go. Exits matter most. Tidio's AI agent, Lyro, shows its sources and hands off or opens a ticket when unsure. LiveChat supports human takeover and can open a ticket when no teammate answers within 30 seconds. Gorgias has built-in handovers when a shopper gets angry or asks for a human.

Email bots need a gentler handoff. Freshdesk's Email AI Agent adds a fixed footer saying an AI wrote the reply. A Helpful click closes the ticket, while Not helpful hands it to a person with a summary in a private note. Help Scout's reports split conversations into resolved, unresolved and escalated, so you can see where Scout gives up. That split matters more than any accuracy promise. Read it weekly.

Tell customers they are talking to a bot. In California it is unlawful to use a bot to mislead people about its artificial identity in order to push a sale, and the law asks for a disclosure that is clear and conspicuous [1]. **Disclosure protects you.** Under that statute, a person who discloses the bot is not liable. Tidio's AI terms also require that end users be told they are talking to AI.


> ⚠ **The meter can switch the bot off:** At Zendesk the AI agents pause at the included limit unless overage is allowed; Freshdesk's AI agents stop answering at zero sessions; Help Scout's spending cap disables Scout until the next cycle. Plan for who answers when that happens.


## Online stores: a customer care chatbot that can act on orders

For a shop, most questions are about one order: where it is, whether it can change, how to send it back. A customer care chatbot that only quotes the shipping policy pushes those people to your inbox anyway. The tools below let the AI read order data and act on it, which is what turns a polite bot into a resolved ticket.


### Gorgias — solves this

The AI Agent answers from your guidance, help center and Shopify data, and with Actions it cancels orders, edits addresses, refunds or reships. It hands over to a person when a shopper gets angry or asks for a human.

- Where it stops: AI Agent, Shopping Assistant and Order Management need a connected Shopify store; each AI Agent resolution also counts as a billable helpdesk ticket.
- Plan: AI Agent add-on on any Helpdesk plan; Actions from Basic
- How Gorgias does it: [Set up skills and Actions](https://professionalstoolkit.com/articles/gorgias-ai-playbook)
- More: [Gorgias](https://professionalstoolkit.com/tools/gorgias)


Gorgias builds its AI Agent around the store. It answers from your guidance and help center, and with Actions it can cancel an order, edit an address, refund or reship. Our [Gorgias AI Agent playbook](/articles/gorgias-ai-playbook) shows how to set up skills and guardrails. Rules run before the AI Agent, so you can keep it away from topics you want people to handle.


### Tidio — solves this

Flows handle predictable moments by rule first, then Lyro answers from the knowledge you supply, shows its sources, and hands off or opens a ticket when unsure.

- Where it stops: Free gets a one-time Lyro allowance that never refreshes; Lyro answers only the first email of a new thread, and a customer reply goes to a person.
- Plan: Free to start; Lyro Connect on Plus
- How Tidio does it: [Build Flows and Lyro](https://professionalstoolkit.com/articles/tidio-chatbot-flows)
- More: [Tidio](https://professionalstoolkit.com/tools/tidio)


Tidio suits a smaller shop that wants to start on the Free plan. Rule-based Flows run first: a greeting on a product page, a form that collects the order number, a coupon node for Shopify. Lyro then answers what the Flows miss, and agents take the rest. Our guide to [building Tidio Flows and Lyro](/articles/tidio-chatbot-flows) covers the order of those layers.

## Website chat first: an AI chatbot for business that also sells

Some businesses get their questions in the chat window while a visitor is still deciding. Here the bot answers support questions and pre-sale ones in the same thread, and the handoff goes to whoever is online. Speed and takeover matter more than email depth. Visitors leave fast. An AI chatbot for business in this setting is half support desk, half sales assistant.


### LiveChat — solves this

The AI Agent answers website chats and messaging from your websites, files and Articles, with human takeover. Its skills collect details, call external services by API and create or update tickets.

- Where it stops: Works in chats only, not in tickets; AI resolutions are capped per account.
- Plan: Every Text plan; Essential has 1 AI Agent, Growth has multiple
- How LiveChat does it: [Configure the AI Agent](https://professionalstoolkit.com/articles/livechat-ai-playbook)
- More: [LiveChat](https://professionalstoolkit.com/tools/livechat)


LiveChat (now sold as Text) puts an AI Agent on every plan. It answers chats from your websites, files and Articles, and its skills can collect details, call external services by API, and create or update tickets. Our [LiveChat AI Agent playbook](/articles/livechat-ai-playbook) explains the skills. For pre-sale questions, LiveChat also offers product recommendations from a live Shopify catalog and cart recovery in the chat. Note that it works in chats only, not inside tickets.

## Email and ticket teams: an AI chatbot with knowledge base articles

If most of your support arrives by email or web form, and you already keep help articles, you want an AI chatbot with knowledge base access that drafts or sends replies inside the ticket queue. Here the key questions are testing and control. Can you watch the bot write before it sends? Can you see which article it used? Can you cap the spend?


### Help Scout — solves this

Scout answers in Beacon chat and email from your Docs, web pages, files, Google Docs and text snippets. Test mode checks answers first, and reports split resolved, unresolved and escalated conversations.

- Where it stops: Scout takes no actions and does not answer on Messenger, Instagram, WhatsApp or SMS; Free has no AI features.
- Plan: Billed per resolution through the Envoy add-on on Standard, Plus and Pro
- How Help Scout does it: [Set up Scout step by step](https://professionalstoolkit.com/articles/help-scout-ai-playbook)
- More: [Help Scout](https://professionalstoolkit.com/tools/help-scout)


Help Scout's Scout answers in Beacon chat and email from your Docs, web pages, files, Google Docs and text snippets. Test mode lets you try both channels before going live. Scout does not take actions, so it explains rather than changes records.


### Zendesk — solves this

AI agents answer on messaging, email, web forms and voice from connected knowledge, and with use cases they follow procedures and call APIs. A simulator and test widget let admins check them before launch.

- Where it stops: Included resolutions do not roll over; at the limit AI agents pause unless overage is allowed. AI-only conversations stay outside SLAs and routing until escalated.
- Plan: Every Suite and Support plan; Copilot for agents on Suite Professional and higher
- How Zendesk does it: [Plan your AI agent rollout](https://professionalstoolkit.com/articles/zendesk-ai-playbook)
- More: [Zendesk](https://professionalstoolkit.com/tools/zendesk)


Zendesk runs AI agents across messaging, email, web forms and voice from connected knowledge. With use cases they can follow procedures and call APIs; without them, they answer only from knowledge. Admins can test in a simulator and a test widget before launch.


### Freshdesk — partly solves this

The Email AI Agent answers new email, portal and web-form tickets from your solution articles. In shadow mode it writes a private note instead of emailing, so the team checks its answers first.

- Where it stops: Standalone Freshdesk has the Email AI Agent only; chat AI agents and chatbots need Freshdesk Omni. At zero sessions the AI agents stop answering.
- Plan: Growth, Pro and Enterprise
- How Freshdesk does it: [Roll out the Email AI Agent](https://professionalstoolkit.com/articles/freshdesk-ai-playbook)
- More: [Freshdesk](https://professionalstoolkit.com/tools/freshdesk)


Freshdesk fits a team that wants AI on email tickets but wants to check every answer first. In shadow mode the Email AI Agent writes a private note and never emails the customer, until you trust it.


### Zoho Desk — partly solves this

Answer Bot answers customer questions from your knowledge base articles. On Enterprise, customer-facing bots in the ASAP widget and chatbots in messaging answer customers, and Zia auto-reply actions can send the first email response.

- Where it stops: No generative AI on Free; customer-facing chatbots wait for Enterprise.
- Plan: Answer Bot from Standard; chatbots on Enterprise
- How Zoho Desk does it: [See the Zia AI options](https://professionalstoolkit.com/articles/zoho-desk-ai-playbook)
- More: [Zoho Desk](https://professionalstoolkit.com/tools/zoho-desk)


Zoho Desk is a fit for teams already on Zoho. From Standard, Answer Bot answers from your articles. The customer-facing bots in the ASAP widget, chatbots in messaging and Zia auto-reply actions sit on Enterprise.

## Pairing a chatbot with your docs and help desk

### Three ways to layer a support bot

You do not have to buy one tool for all five parts. Three combinations fit well together:

- **Docs first, AI second.** Draft your answers in Google Docs, publish them as help articles, then let Help Scout's Scout read them. Scout can take Google Docs and Sheets as sources one at a time.
- **Rules first, AI second.** In Tidio, keep Flows for the predictable moments, such as a greeting, a form or a Shopify coupon, and let Lyro take the typed questions. Turning Lyro on switches off Flows that react to what the visitor types, so plan the two layers together.
- **A bot on top of your help desk.** Tidio's Lyro Connect, on the Plus plan, puts Lyro on top of an existing help desk, so your ticket queue stays where it is.

If you are not ready for an AI agent at all, start with the free rules in our [customer support automation guide](/articles/customer-support-automation). For how AI agents decide, escalate and learn, read our overview of [AI customer support](/articles/ai-customer-support).


> 💡 **Read the escalation report weekly:** Each conversation the bot hands off points to a missing or unclear article. Write that article, and the same question stops reaching your team.


### Which chatbot fits your busiest channel

- **You sell on Shopify and most questions are about orders:** Gorgias, or Tidio if you start small.
- **Your questions arrive in website chat and you sell there too:** LiveChat or Tidio.
- **Email is your main channel and you have help articles:** Help Scout or Freshdesk.
- **You need one AI across messaging, email, forms and voice:** Zendesk.
- **Your company runs on Zoho:** Zoho Desk, planning for Enterprise if customers should chat with the bot.

Whatever you pick, run the bot on your last month of real questions before you switch it on. Read every answer it gets wrong.


## FAQ

**What is the difference between a rule-based chatbot and an AI chatbot?**

A rule-based bot follows a flow you draw: a trigger, conditions and fixed answers. An AI chatbot reads the question and writes an answer from your knowledge base. Many teams run rules first and let the AI take what the rules miss.

**How do I build a chatbot knowledge base?**

Start from your most frequent questions, write one short article per question with the exact policy and steps, and keep each article current. Then connect those articles, plus key web pages and files, as the bot's sources.

**Do I have to tell customers they are talking to a chatbot?**

In California, using a bot to mislead people about its artificial identity in order to drive a sale is unlawful, and a clear, conspicuous disclosure removes that liability. Telling customers up front is the safe default everywhere.

**Can a customer care chatbot handle refunds and order changes?**

Only if it can act on your order system. Gorgias's AI Agent can cancel, edit an address, refund or reship for Shopify stores; bots without actions can only explain the policy and hand off.


## The bottom line

A customer service chatbot works when its five parts work together: clean knowledge, the right channels, a quick handoff, actions on real records and a meter you watch. Choose by your hardest part. Stores need order actions, chat-first sites need fast takeover, and email teams need testing and control. Write and fix the articles first, tell customers it is a bot, and treat the escalation report as your to-do list.



## Sources

[1] California Legislative Information — https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=BPC&sectionNum=17941 (Nov 2026)

