What it does

Tidio makes more sense today as an AI customer service platform than as a simple website chat. It combines the Lyro AI Agent, inbox, help desk, live chat, and lightweight automation flows in one support loop. It fits ecommerce and service teams that want routine questions handled automatically and the harder conversations handed to a person fast.

Plans

Free

Up to 2,000 conversations/month

Paid

from $29/month

Pricing page

Access

Free plan: up to 2,000 conversations/month. Paid plans from $29/month.

Screenshots

Lyro AI Agent screen in Tidio — Lyro's main screen. It makes clear that Tidio is built around AI support, not just a basic website chat widget.

Lyro analytics dashboard in Tidio — The analytics view shows what Lyro resolved on its own, where handoff happened, and how complete the knowledge base is. For support teams, this matters more than a polished homepage.

Tidio inbox with the conversation queue — The inbox is where a human takes over. You can see the queue, open chats, and ongoing support work in one place.

Actions panel in the Tidio Flows builder — Flows is Tidio's visual scenario builder: greet, ask a question, send an email, wait, or hand off to an agent. For small teams, this is easier than wiring logic by hand.

Usage examples

Auto-replies for an online store

A store uploads its FAQ, shipping rules, and return policy to the knowledge base. Customers ask about delivery, payment, or order status - Lyro handles the common questions and hands unusual ones to a human.

Documentation

Lead capture via chatbot

With Flows, you can build a simple lead intake flow for a service website: greet the visitor, ask what they need, collect an email, and pass the lead forward. It's not a full CRM, but it's solid for first-step qualification.

Documentation

Application scenarios

Scenario: a Shopify store uses Tidio so routine questions don't pile up overnight or on weekends. Lyro handles shipping and return questions, and the team only reviews the conversations that actually need a person.

Scenario: a service company uses Flows as the first filter for inbound requests. The bot asks about budget, timeline, and project type, so the manager gets a short structured lead instead of a messy chat log.