AI Customer Support Chatbot: What to Settle Before Launch
How to choose - - Priya Raman
The Chatfuel documentation answers one launch question in a single word. Can the handoff message be customized? No. The AI generates it from the conversation context, and what a team can set is when the handoff happens, who receives it and the tone the bot uses (Chatfuel's help documentation, as of November 2026). A support lead who finds that out after launch has a customer-facing sentence nobody on the team wrote.
That is the pattern with an AI customer support chatbot. The landing page sells answers. The checks that matter sit in the settings and the pricing terms.
The four checks
- Where the answers come from. Help center articles, uploaded files, past tickets, or the open web. A bot that answers only from approved pages can be wrong only where those pages are wrong. A bot with wider reach needs a rule for what it must not answer.
- When it hands over, and to whom.
- What a billed unit is.
- Who reads the conversations that went badly.
The sections below take them in turn. The website-side version of the same questions, for a bot on a public page, is in the guide to chatbot checks before installing.
Escalation is a set of triggers, not a button
Docs from open.cx show what a complete list looks like. By default, it hands off in four cases: the customer asks for a human, the AI decides it cannot resolve the situation, the customer shows frustration, or the topic is on a "forbidden topics" list. Each trigger can be tuned or turned off in its Handoff Settings (open.cx handoff docs).
That list is a useful yardstick whichever product is under review, since a vendor page that mentions only the first trigger probably handles only the first. For a product like Chatfuel, the rules sit in the Switch to human settings of each automation. The page quoted above does not cover notifications or working hours, so the after-hours case is a question for the vendor: a customer who asks for a person at night should be told when one will answer.
The rehearsal costs an afternoon. It is also the only check that finds a handoff that fires, but lands in an inbox nobody watches.
What a billed unit is
Support bots are often priced by outcome. Intercom's pricing page, as of November 2026, lists its Fin agent at $0.99 per outcome with no seat fees, and counts an outcome when the customer confirms the issue is resolved, does not ask for more help after Fin responds, or Fin completes a workflow, handoffs included. Each conversation is billed once. When Fin runs on top of another helpdesk, a minimum monthly commitment applies, and the page gives 50 outcomes as an example (Intercom pricing).
Two details follow. A silent customer can count as an outcome. And a handoff can count too, so a high bill does not prove a high resolution rate.
For a rough monthly figure, assume 1,000 conversations and that every outcome is one conversation (a simplification, not a vendor rule):
At $0.99, 400 outcomes come to $396, 600 to $594 and 800 to $792. The rates are assumptions for the arithmetic; the rate is the vendor's published list price. The point is that the bill rises with the share of conversations counted, so ask what counts before a pilot, not after.
Checks and where to find them
| Check | What to look for | Where it usually sits |
|---|---|---|
| Answer sources | Which content the bot may use; what it does with no match | Knowledge base or training settings |
| Triggers | Request, bot uncertainty, frustration, forbidden topics | Handoff or escalation settings |
| Handoff message | Whether the team can edit it | Product docs |
| Billing unit | Outcome, resolution, message or seat, and its definition | Pricing page, billing FAQ |
| Failed chats | Whether unanswered or escalated chats can be listed and exported | Reports or conversation log |
Source: the Chatfuel, open.cx and Intercom pages listed under the sources of this guide.
Reading the failures
Launch day does not end the work. The first weeks of conversations that ended in a handoff, a thumbs-down, or an abandoned chat are the cheapest source of fixes: each one points at a missing help article or a trigger set too loose. A product that cannot list them leaves the team guessing, and that is worth knowing before a contract. Cards for related tools, such as DigitalGenius, carry only catalog facts, so confirm anything on this list with the vendor directly.