Tidio Chatbot (Flows)

Flows is Tidio's no-code visual chatbot builder. It is not the same thing as Lyro, Tidio's AI agent -- Flows is purely rules-based. You define triggers, map out decision trees, and the bot follows the script exactly as written. There is no natural language understanding, no AI interpretation. What you build is what runs.

That distinction matters because a lot of users land on Tidio expecting one "chatbot" product and find two very different tools. Flows handles structured automation -- qualifying leads, routing conversations, recovering abandoned carts. Lyro handles open-ended questions from your knowledge base. In practice, most Tidio users end up using both, and the two complement each other well.

What Flows does

At its core, Flows is a drag-and-drop builder for automated conversation sequences. You pick a trigger (what starts the flow), add actions (what the bot does), and connect them with conditions (branching logic). The visual canvas makes it easy to see the entire path a conversation can take.

A typical flow might look like this: visitor lands on your pricing page, the bot waits 15 seconds, then pops up asking if they have questions about plans. If the visitor responds, the bot asks a qualifying question, tags the conversation based on the answer, and either routes to a sales agent or sends a help article link.

Nothing about this requires AI. It is scripted automation, and for many use cases that is exactly what you want -- predictable, consistent, and easy to troubleshoot when something goes wrong.

Template library

Tidio provides 35+ pre-built Flow templates organized by use case. This is one of the features reviewers consistently praise -- you do not have to build everything from scratch.

The ecommerce templates are particularly strong if you run a Shopify or WooCommerce store. The cart recovery template, for example, comes pre-configured with Shopify product data variables so it can reference the actual items in a visitor's cart. I see reviewers on G2 and Capterra regularly mention this template as a direct revenue driver.

Triggers

Triggers are what start a Flow. Tidio offers a solid range:

• First visit -- fires when a new visitor lands on your site
• Returning visitor -- fires for visitors who have been before
• Page visit -- fires on specific URLs or URL patterns
• Time on page -- fires after a visitor spends X seconds on a page
• Exit intent -- fires when the cursor moves toward closing the tab (desktop only)
• Custom events -- fires based on JavaScript events you define (requires some technical setup)
• Visitor clicks -- fires when a specific element is clicked
• Form abandoned -- fires when a visitor starts filling a form but stops

The exit intent and time-on-page triggers are the most popular based on what I see in review threads. Ecommerce stores use exit intent heavily for last-chance discount offers, while SaaS companies tend to favor time-on-page triggers for pricing page engagement.

One limitation: trigger conditions can only be combined with basic AND logic. You cannot build complex compound triggers like "visitor is returning AND on the pricing page AND has viewed 3+ pages" in a single trigger configuration. You have to use conditions inside the flow to narrow things down, which works but makes the canvas more cluttered.

Actions and conditions

Once a flow triggers, you chain together actions:

• Send a message -- text, images, cards, or buttons
• Ask a question -- open text, multiple choice, email, phone, or number input
• Add/remove tags -- for segmentation and routing
• Set contact properties -- store data on the visitor profile
• HTTP request -- call external APIs (webhooks)
• Transfer to operator -- hand off to a live agent
• Transfer to Lyro -- pass the conversation to the AI agent
• Delay -- wait before the next action
• Close conversation -- end the chat

Conditions let you branch based on visitor data (country, device, tag, contact property) or their responses to questions. The branching is visual -- you draw lines from condition outcomes to different action paths.

The HTTP request action is worth noting. It opens up Flows to external integrations beyond what Tidio natively supports. I have seen reviewers use it to push data to CRMs, trigger Zapier webhooks, and pull product inventory from custom backends. It is not as seamless as a native integration, but it works.

Ecommerce capabilities

Flows shines brightest in ecommerce. The Shopify and WooCommerce integrations give flows access to:

• Cart contents and value
• Product catalog data
• Order history and status
• Customer purchase data

This means your flows can reference real product names, show actual cart totals, and personalize recommendations based on browsing history. The abandoned cart flow in particular is a standout -- it can fire when a visitor has items in their cart and is about to leave, show them exactly what they are leaving behind, and offer a discount code to close the sale.

Reviewers on Capterra frequently cite measurable revenue recovery from these ecommerce flows. One recurring theme in reviews is that the cart recovery template alone justified the subscription cost.

Limitations

Flows is not without frustrations, and reviews are fairly consistent about where it falls short:

Complex flows get unwieldy. The visual builder works great for simple 5-10 step flows. Once you get beyond 15-20 nodes with multiple branches, the canvas becomes difficult to navigate. There is no way to collapse sections or create sub-flows, so large automations turn into a spaghetti diagram. Several G2 reviewers mention this as their primary pain point.

No AI or NLU. Flows cannot interpret what a visitor means -- it can only match exact inputs or multiple-choice selections. If a visitor types something unexpected in an open question, the flow either fails to match or falls through to a catch-all. For flexible conversation handling, you need Lyro.

Testing is basic. You can preview a flow, but there is no robust testing environment. You cannot simulate different visitor profiles or test edge cases systematically. Most users end up testing in production with a test tag.

Version history is limited. If you break a working flow while editing, rolling back is not straightforward. Reviewers recommend duplicating flows before making changes.

Pricing

Flows visitor limits scale with your plan:

"Flows visitors" means unique visitors who interact with a flow -- not the number of flows you can create. You can build unlimited flows on any plan. The 100-visitor cap on Free and Starter is tight for any site with meaningful traffic, and this is a common complaint in reviews. Growth plans scale the cap with price, starting at 250 visitors for $59/month.

What reviews say

Across G2, Capterra, and Trustpilot, the sentiment around Flows is largely positive but with a clear ceiling.

Praised consistently:

• Template library saves significant setup time
• Visual builder is intuitive for non-technical users
• Ecommerce templates (especially cart recovery) deliver measurable ROI
• Easy to get a basic bot live in under an hour

Criticized consistently:

• Complex flows become hard to manage and debug
• The 100 Flows visitors cap on lower plans is restrictive
• No sub-flows or modular flow components
• Bot-triggered conversations count toward your conversation limit, which feels punitive

That last point is a recurring frustration. If a Flow initiates a conversation proactively (like an exit intent popup), it counts against your monthly conversation allowance -- even if the visitor never responds. On the Free and Starter plans with 50-100 conversation limits, aggressive proactive flows can burn through your quota fast.

Bottom line

Flows is a capable chatbot builder for structured, rules-based automation. The template library and ecommerce integrations are genuine strengths, and for small to mid-size stores the ROI case is straightforward. Where it struggles is at scale and complexity -- large flows become unwieldy, and the lack of AI means it cannot handle anything outside the script.

For most Tidio users, the best approach is pairing Flows for structured tasks (lead capture, cart recovery, routing) with Lyro for open-ended support questions. That combination covers a lot of ground.