BotSupport vs Tidio: which AI chat assistant fits your store?

What is Tidio, exactly?

Tidio started life as a lightweight live chat widget and has grown into a broader service platform. As of August 2026 its own site positions it as a complete service platform built for human and AI alignment, with four distinct products sitting behind one widget: Live Chat for real-time human conversations, a Help Desk for ticketing and workflow, Flows for rule-based no-code automations, and Lyro, its AI agent.

That combination matters, because people often assume Tidio is only a chatbot. It is not. If your team already answers email, Instagram and Messenger enquiries and wants those in one inbox with assignment rules and macros, Tidio genuinely does that job. It is a support operations tool with AI attached, rather than an AI product with support bolted on, and that shapes almost every difference described further down this page.

Lyro is the AI layer. Tidio's Lyro page describes it as automatically scraping your support content and using that as its knowledge base, and states that Lyro "works only with the content and guidance you provide". The same page carries Tidio's own performance figures, including an average resolution rate of 67 per cent, and its homepage says Lyro can eliminate up to 90 per cent of low-level support questions. Both are vendor-reported figures taken from Tidio's marketing in August 2026, and both depend heavily on how complete your source content is. Treat them as the vendor's claims rather than as independent measurement.

Tidio is also an established product. Its own marketing says it is trusted by more than 300,000 businesses, which is a vendor-reported number rather than an audited one, and third-party review sites such as Capterra and G2 carry a large volume of feedback rated in the high 4s out of 5 at the time of writing. Those ratings and counts move constantly, so check the current ones rather than relying on this page. The broader point stands whatever the exact numbers say: this is mature, widely used, well-supported software with a long track record behind it.

BotSupport is a much narrower proposition. It is a fully managed AI chat assistant for ecommerce. There is no help desk, no shared inbox, no social channel routing and no Flows builder. It answers customer questions about your products, prices, stock, delivery and returns, built on your live catalogue, and it passes anything it cannot answer to a human. It is at Early Access stage, so it has no meaningful installed base yet, and nothing on this page should be read as a claim about how many stores are running it.

Who actually does the building and the upkeep?

Every AI support tool needs the same raw material: accurate, well-structured answers about your products, prices, delivery, returns and edge cases. The question is not whether that material is needed, it is who assembles it and who keeps it current.

Tidio's answer is that you do. Getting the widget on the page is genuinely quick, and reviewers consistently praise how easy installation is. Getting Lyro to answer well is a different exercise. Reviewers commonly report the same pattern: the widget goes live in minutes, while getting the AI answering real customer questions well takes longer, sometimes considerably longer, depending on how much usable support content you already have. If you have a well-maintained help centre, you are most of the way there. If your policies live in someone's head, you are writing them down first.

That work does not stop at launch. Prices change, lines sell out, delivery cut-offs move at Christmas, a returns policy gets tightened. This is true of any self-serve knowledge base, whichever vendor you use: if nobody updates it, the answers drift out of date. In a self-serve model somebody at your business has to own that job, and it is usually the first thing to slip when the week gets busy.

BotSupport inverts that. A person builds the assistant on your store's actual products, prices and policies, tests it against real questions, and hands it over working. You do not write a knowledge base, you do not configure intents, and you do not maintain flows. Fixes and updates to the assistant are included in the subscription, so if it is answering something badly you tell us and we handle it rather than it becoming a ticket in your backlog. We agree response expectations with you at handover so that commitment is a written one rather than a slogan.

Tidio does offer a managed option, but its published managed AI service sits at the top of the range. Its Premium tier, which is quoted rather than listed, is marketed alongside SSO and compliance features, a guaranteed Lyro resolution rate and outcome-based billing. Those are negotiated terms, so confirm anything specific directly with Tidio. On the lower self-serve plans, expect to do the configuration yourself unless you arrange something separately with them.

Does Tidio work as well on WooCommerce as it does on Shopify?

Tidio's own Shopify page describes these as Shopify-exclusive features and Shopify-specific actions. They are substantial: refunds and cancellations from the inbox, address changes, cart previews for personalised recommendations, order history without leaving the dashboard, and a large library of no-code automation templates for things like cart recovery and discount offers. Some order actions are only available from Tidio's higher plans, so check the current plan comparison on its pricing page rather than assuming everything shown in a demo is included at entry level.

The WooCommerce integration is a smaller thing. Tidio documents installing via WordPress, linking the store, auto-syncing active products, browsing the catalogue in the inbox and sending individual product cards into a conversation, with click notifications when a customer engages with one. When we checked the WooCommerce integration page in August 2026, order modification, refunds and address changes were not among the documented features. That may change, and it is exactly the sort of gap a vendor closes without announcement, so treat it as a question to ask rather than a permanent state of affairs.

If you run WooCommerce and you were sold on Tidio by a demo of an AI cancelling an order, verify that specific capability against your own platform before committing. It is a common and expensive mismatch, and it is not unique to Tidio. Plenty of ecommerce AI tooling is built Shopify-first and reaches WooCommerce later.

BotSupport takes a different approach to platform fit. Because it is built and configured by a person against whatever your store actually exposes, the approach is designed to work on WooCommerce, Shopify and most bespoke sites, and we confirm fit with you before the build rather than after. That is a genuine advantage on WooCommerce in particular, where AI chat tooling tends to be treated as the second-class integration.

In fairness to Tidio, if you are on Shopify and you want agents taking order actions inside the chat inbox, Tidio's integration is deeper than what BotSupport does today. BotSupport is focused on answering questions accurately from the live catalogue and handing off cleanly, not on performing back-office order operations. If the value you are buying is the assistant doing things to orders rather than answering questions about products, that is a straightforward argument for Tidio on Shopify.

How well does each one answer questions about live products and stock?

This distinction gets lost in feature lists but it decides how the assistant performs on the questions shoppers actually ask. Most pre-sale chat traffic is catalogue traffic: does this come in a wider fitting, is it in stock in navy, what is the difference between these two models, will it arrive before Friday.

A knowledge-base-driven assistant handles those well to the extent that someone has written them down. Tidio is explicit that Lyro works only with the content and guidance you provide, which is a sensible design choice for reducing invented answers. Its marketing goes further, saying that other AI agents make things up and Lyro does not, and that with strong guardrails and your knowledge base every response is accurate and helpful. That is the vendor's claim rather than an independent finding, and we would treat any absolute accuracy claim from any vendor, ourselves included, with some caution. The structural trade-off is coverage: what is not in the content is not answerable, and the assistant escalates instead of guessing.

Tidio does offer product sync on both Shopify and WooCommerce, feeding a product recommendations feature that requires Lyro to be active alongside a Lyro package or trial. It is a real capability and it works. The limitation flagged in third-party reviews is depth of query rather than existence of the feature: recommending products is not the same as searching a catalogue against several attributes and a price ceiling at once.

BotSupport's design goal is the opposite starting point. The assistant is built against your live catalogue first, so answers about prices, variants and availability come from current store data rather than from a document someone wrote in March, and the human build step is about layering your policies and tone on top of that. We would expect that difference to matter more the larger and faster-moving your catalogue is, and the right way to settle it is to test both against your own product questions.

Neither approach is magic. An assistant built on a live catalogue will still get things wrong if the catalogue data itself is thin or inconsistent, and any integration has some sync interval behind it, so nothing is instantaneous to the second. That is one of the reasons a person builds and tests BotSupport before it goes live rather than leaving you to discover the gaps in front of customers.

How do the pricing models compare?

Tidio's published structure, as of August 2026, runs Free, Starter, Growth, Plus and Premium. The free tier includes a small monthly conversation allowance, a limited number of Flows visitors and a one-off batch of Lyro conversations. Starter is listed at roughly USD 25 per month on the annual-equivalent rate. Growth starts at around USD 50 per month on the same basis and scales with conversation volume, adding advanced analytics and macros. Plus is listed as starting from around USD 300 per month plus usage, with custom limits and a dedicated success manager. Premium is quoted rather than listed. Monthly billing costs more than the annual-equivalent rates shown on the pricing page. Exact allowances and prices are on tidio.com/pricing and change periodically, so treat every number in this paragraph as a starting point for your own check.

The important structural point is that Tidio bills by conversation volume rather than by seat. Its help documentation describes billable conversations as those involving a reply from a human agent, with Flows and Lyro replies not counted as agent replies, so AI-only conversations do not consume that pool. Confirm the current counting rules in Tidio's billing documentation before you model your costs, because that definition is the whole basis of the bill. Its self-serve plans also cap agent seats, so if you are growing a support team check the current plan comparison rather than assuming seats scale with spend. Some third-party pricing write-ups describe automatic tier upgrades as conversation limits are approached; we could not verify that against Tidio's own documentation, so check their current terms directly if predictable billing matters to you.

Where buyers most often get caught out is the stacking. Lyro is a separate meter from billable conversations, Flows is a third, and branding removal is a further line. Because those meters are billed separately, the entry plan price is not the whole bill. Add up the meters you will actually use, at the volumes you actually expect, before comparing headline prices with anything else on your shortlist. This is a structural feature of usage-based pricing rather than a criticism: it is the same arithmetic you would do for any metered SaaS product.

BotSupport is deliberately simple by comparison: one managed subscription, roughly GBP 79 a month at Early Access pricing, with a trial period. There is no per-conversation meter to forecast, no separate AI add-on and no branding surcharge. Early Access pricing is exactly that, and it is fair to expect it to change as the product matures. Early Access pricing, trial terms and setup arrangements may all change before general release, and we would rather say that plainly here than surprise you at the first invoice.

The honest caveat is scope. Tidio's higher tiers buy you a genuine multi-channel help desk with seats, macros, routing and analytics, and a free tier to test on before you spend anything. BotSupport's subscription buys you one well-built assistant and the work that goes into building and maintaining it. Comparing the two purely on headline price compares different things, which is why the next section is about the cost that never appears on either invoice.

What does each option really cost in staff time?

Put a number on your own time and the comparison changes shape. If a competent person in your business spends two days writing and structuring content, configuring flows and testing the AI, then half a day a month keeping it accurate, that is a real cost that never appears on the subscription invoice. Price that at whatever an internal day costs you and add it to the licence fee before you compare anything.

This is not a criticism of Tidio specifically. It is the nature of self-serve software, and plenty of businesses prefer it precisely because they want that control and have someone who enjoys the work. A marketing manager who likes building flows will get more out of Tidio than they would out of a managed service, and will be able to change things at midnight without asking anyone. The mistake is not choosing self-serve, it is budgeting only for the licence and assuming the configuration happens by itself.

There is also a quality dimension. Knowledge bases written under time pressure by someone doing it alongside their normal job tend to cover the obvious questions and miss the awkward ones, and the awkward ones are exactly what make a chat assistant look unreliable in front of a customer. Testing against real customer language, rather than against the questions you imagine customers ask, is the step most commonly skipped, and it is the one that decides whether the assistant is trusted internally after week three.

BotSupport's answer is that the build and the testing are the product rather than a service wrapped around it. A person does the work, tests the assistant against real questions, and hands it over ready. We aim to do that within one working day of the briefing. Your input is a short briefing and a review before it goes live.

If you have in-house capacity and want to own every rule yourself, that is a legitimate reason to choose Tidio and accept the hours. If you do not, a managed build takes away one of the most common reasons AI chat projects stall, which is that nobody had time to finish setting it up. Half-configured assistants are worse than no assistant at all, because customers learn quickly that the chat window is not worth using.

When should you honestly choose Tidio instead?

There are several situations where Tidio is clearly the better buy, and it would be dishonest to pretend otherwise on a page we have written about our own product.

If you have a support team rather than one or two people, you need ticketing, assignment, macros and analytics. Tidio's self-serve plans include multiple agent seats and a genuine help desk behind them. BotSupport does not compete here at all. It hands conversations to a human and stops, which means you still need somewhere for those conversations to land.

If you are on Shopify and the value you want is the AI doing things rather than answering things, Tidio's Shopify-specific actions are ahead of us. Cancelling orders, refunding, changing shipping addresses and previewing carts from within the conversation are documented capabilities on their Shopify integration page, and they are not something BotSupport offers today.

If you want to run several channels through one place, including Instagram, Messenger, email and web chat, Tidio's inbox and its integration library, which covers well over a hundred tools by Tidio's own count, are a stronger fit than a website assistant. A single assistant on your storefront does not solve a multi-channel routing problem.

If a free tier matters, Tidio has one and BotSupport does not, beyond a trial period. A small monthly conversation allowance is not a business plan, but it is a genuine way to put the widget in front of real customers at no cost and see whether chat changes anything for your store before you commit budget.

And if buying from a pre-launch supplier is a problem for your business, that is an entirely reasonable position and we are not going to argue you out of it. BotSupport is at Early Access stage with essentially no installed base. Tidio has been trading since 2013 according to its own about page and carries thousands of public reviews. If you need references, longevity and a procurement-friendly vendor today, take Tidio and revisit us later.

How do you trial both, or move from Tidio to BotSupport?

Start by collecting your last 50 real chat or email enquiries. Not hypothetical questions, actual ones, including the awkward ones about sizing, stock, delivery timing and returns. This list is the only benchmark that matters, and most buyers skip it in favour of a vendor demo, which is a test the vendor has already passed.

With Tidio, install the widget, connect your store, and give Lyro whatever support content you already have. Note honestly how long that takes and how much of it had to be written from scratch, because that is the number that predicts your ongoing cost. Then run your question list and record how many are answered correctly, how many are answered vaguely, and how many escalate to a human.

With BotSupport, the equivalent step is a briefing rather than a build. The assistant is built on your live catalogue and policies and handed back working, so you spend the trial testing rather than configuring. Run the same question list and score it the same way. If the scores are close, choose on the other factors in this article rather than on a handful of sample answers.

Migration itself is straightforward because there is little to migrate. Any FAQ content you wrote for Lyro is useful input for a BotSupport build rather than wasted effort, and the chat widget itself is a script change. If you are moving away from Tidio's help desk rather than just its AI, plan that separately, because BotSupport does not replace ticketing and you will want somewhere for escalated conversations to land, whether that is email, a shared inbox or another help desk.

Many stores will conclude they want both kinds of capability, and there is nothing wrong with that conclusion. Nothing prevents running a managed assistant for pre-sale catalogue questions and a separate help desk for post-sale tickets, although running two chat widgets on the same page is a poor customer experience and worth avoiding. The comparison to make is not which brand wins in the abstract, it is which of the two jobs, pre-sale answering or post-sale ticketing, is currently costing you the most.

Sources

1. Tidio pricing page — Plan tiers (Free, Starter, Growth, Plus, Premium), conversation and seat allowances, Lyro AI add-on, Flows add-on, branding removal add-on, and the guaranteed Lyro resolution rate marketed at Premium. Retrieved August 2026; figures quoted in this article are rounded and indicative.
2. Tidio Shopify integration — Documents Shopify-exclusive features: cancel orders, process refunds, change shipping addresses, cart previews, order history in the inbox, and a library of no-code automation templates. Retrieved August 2026.
3. Tidio WooCommerce integration — Documents quick plugin setup, auto-sync of active products, catalogue browsing in the inbox, product cards and click tracking. No order management features were documented on the page when retrieved in August 2026.
4. Tidio Lyro AI Agent page — Source of the vendor-reported 67 per cent average resolution rate, the statement that Lyro scrapes support content, the quoted line that Lyro works only with the content and guidance you provide, and Tidio's own accuracy claim. Retrieved August 2026.
5. Tidio homepage — Product positioning, four-product structure, vendor-reported 300,000+ businesses, 120+ integrations, and the up-to-90-per-cent low-level question claim. Retrieved August 2026.
6. Tidio about page — Source for the founding year and location (2013, Szczecin, Poland) and the vendor-reported customer count. Retrieved August 2026.
7. Tidio help centre: the monthly conversations limit — Tidio's own definition of a billable conversation, including that Flows and Lyro replies are not counted as agent replies. Referenced August 2026; confirm current wording directly, as our fetch of this page was blocked and the definition was read from indexed summaries.
8. Tidio reviews on Capterra — Independent user reviews and aggregate rating, in the high 4s out of 5 when checked in August 2026. Ratings and review counts change continually.
9. Tidio AI (Lyro): Features, Pricing and Limits 2026, MyAskAI — Third-party analysis of Lyro limits, knowledge-base setup effort and multi-meter billing. Note: published by a competing vendor, so treat its criticisms with the same caution you should apply to this page.
10. Tidio Pricing 2026, Chatarmin — Third-party breakdown of the billing meters, seat caps and reported tier-upgrade behaviour. Also published by a vendor in an adjacent market; we could not verify its automatic-upgrade claim against Tidio's own documentation.

Details on Tidio reflect its public documentation and independent reviews as of August 2026 and change frequently. This comparison is published by BotSupport, so read it as a vendor comparison and check the alternative for yourself. If something here is out of date, tell us and we will correct it.