Flow builders answer the questions you predicted, which is fine until a visitor types something the tree has no branch for — and most of them do. Retrieval takes the other route: read the customer's actual question, find the relevant passages in your own content, and answer from those. Below: what Tidio does well, why teams leave anyway, and who the other alternatives suit.
Worth saying first, because a comparison that pretends the incumbent is bad is no use to anyone deciding.
If you have people staffing a chat queue and the flow builder is earning its keep, stay where you are. The rest of this page is for the other case.
Six reasons, roughly in the order they come up. The first one accounts for most of the searches that land on this page.
The complaint that comes up most. When AI resolutions are charged on top of the plan, your bill rises exactly as the thing starts working — which is a strange incentive to live with. Check the current terms; this is the number worth modelling before you commit.
Trees start tidy and end up sprawling. Every unanticipated phrasing is another branch, and eventually somebody owns that diagram as a part-time role.
If most of your volume is questions your site already answers, retrieval over your own content covers phrasings nobody predicted — without a branch for each one.
A live-chat-first tool assumes somebody is there. If your reality is one person answering between other work, you are paying for an inbox to get a widget.
Maintaining a flow per language multiplies the work by the number of markets. Worth asking how any tool on your shortlist handles this before you expand.
Look at the next plan up, plus AI charges, at the volume you expect next year rather than this month. Do it before you migrate, not after.
You draw a decision tree. The visitor picks from buttons. Each branch ends in a message you wrote.
Strengths
Limits
You point it at your pages and documents. It finds the relevant passages for whatever was asked, then answers from them and cites the source.
Strengths
Limits
Retrieval is not universally better. If any of these describe your main use case, a flow builder will serve you better and you should use one.
Your existing flows are not wasted work. They are a tested corpus of answers, which is exactly what you need to train on.
Every branch that ends in a written answer is a Q&A pair waiting to happen. That copy is already tested on real customers — it is the best training data you have.
Flows tend to end in “see our shipping page”. Train on those pages directly and the assistant answers instead of redirecting.
The safety a decision tree gave you by construction now comes from the system prompt and handover. Name what it must not attempt.
The questions your flows never had a branch for will show up immediately. Most teams find three or four themes and close them in an afternoon.
A decision tree needs translating branch by branch, and every future edit has to be made in every language. Retrieval reads your one English knowledge base and answers in whatever language the visitor wrote in — more than ninety-five of them — with nothing extra to maintain.
How that worksWe are one narrow option on this list. Saying which of the others fits you is quicker than pretending we fit everyone.
The usual like-for-like swap. Live chat plus AI at SMB pricing, with a broader toolset than a widget.
The free option people actually name. Genuinely free live chat, with the trade-offs you would expect.
Mature live chat with a separate AI product alongside it. Sensible if the staffed inbox is the point.
Built around ecommerce order data. The obvious pick if you are a store rather than a service business.
Shared-inbox first. Right when email is your real channel and chat is the secondary one.
Docs-trained assistants like this one. No inbox, no flows — just answers from your own content.
Retrieval over your own site and documents, flat monthly pricing with a conversation allowance, 95+ languages from one knowledge base, and no tree to maintain.
Positioning only — deliberately no feature ticks or prices for anyone else, because those change monthly and a stale table misleads. Check each vendor's own site.
What this page compares. Two approaches — scripted flows and retrieval — rather than two products. Individual tools change what they offer frequently, and several now do some of both, so check any vendor's current capabilities on their own site. The approach question is the durable one, and it is the one worth deciding first.
It depends what you are replacing. If you want the same shape at similar pricing, Crisp. If free matters more than features, tawk.to. If the staffed inbox is the point, LiveChat or Help Scout. If you run a store, Gorgias. And if the honest answer is that most of your volume is questions your website already answers and nobody is staffing a queue, a retrieval-based assistant like CustomerBot does that one job without a flow builder or a per-conversation AI charge. Test your shortlist against ten real questions from your inbox — that settles it faster than any table.
Lyro is Tidio’s AI, layered onto their live-chat platform, and it answers from your content much as this does. The differences are structural rather than about answer quality: Lyro assumes you are on Tidio and has typically been billed per resolved conversation on top of the plan, whereas CustomerBot is standalone, flat-priced with a conversation allowance, and has no inbox underneath it. Check their current pricing directly — it changes, and it is the number that decides most of these migrations.
Several, and they differ a lot. tawk.to is the well-known genuinely-free live chat. Ours has a free plan too — one assistant, 50 conversations a month, no card — which is enough to crawl your real site and judge the answers before paying. Worth checking on any free tier whether the cap is on volume or on quality; those are very different offers.
Rarely the base plan. It is usually the combination — a monthly subscription plus AI charged per resolved conversation — which means the cost rises in step with the automation succeeding. That can be perfectly fair value, but it is worth modelling at next year’s volume rather than this month’s, because it is the thing people say caught them out.
No. It is a retrieval-based assistant: you train it on content and it composes answers from what it retrieves. If a drag-and-drop decision tree is a hard requirement — for a legally fixed script, for instance — that is a genuine reason to choose a flow-based tool instead.
Not a staffed real-time agent console. Handover collects the visitor’s details and passes the conversation to your team with the transcript attached. For teams without someone watching a queue all day, that is usually the more honest arrangement — but if you are staffing live chat, you need a tool built around that.
Substantially. The system prompt sets the role, tone and refusals; Q&A pairs pin exact wording for the answers that matter most; and the knowledge base bounds what it can draw on at all. What you give up is guaranteed identical strings, in exchange for coverage of questions you never scripted.
This is where the difference is largest. A flow builder needs a translated tree per language. Retrieval detects the language of each message and answers in it — over 95 languages — from one knowledge base you maintain once.
Minutes to a working assistant: paste a URL, pick the pages, wait for indexing. The part worth spending real time on is the system prompt and a handful of Q&A pairs in your own voice.
Yes — it is a script tag on your own pages, so it coexists with anything else. Some teams keep a flow for one transactional path and put the assistant on everything else.
That is the whole test. Train it on your site and type the awkward question you know your tree cannot handle.
Start free