The answer isn't in its knowledge
How you'll know: The question is common, and the handoff happens every time.
Fix: Read the handed-off chats weekly and add the missing answers as sources. Policies that live in someone's head are the usual gap.
"Tidio AI" usually means Lyro, Tidio's AI agent, which answers shoppers in plain language from the knowledge you give it. Next to it sits Flows, the rule-based automation builder, and Lyro Actions, which let Lyro call an API mid-conversation. Here's how each one works, how Lyro is counted, and what to do when it keeps passing questions to your team.
Lyro reads the sources you add (pages, PDFs, CSVs, Q&A you type in) and replies in natural language. When it can't answer, it hands off to a person.
Counting: Lyro is billed by a monthly quota of Lyro conversations. One conversation is any chat with at least one AI reply, counted once however many replies it has. Every account gets its first 50 free, once.
Flows is separate: triggers and steps you build yourself, such as a cart reminder or lead form. It's billed by visitors reached, not by Lyro conversations.
Lyro Actions let Lyro fetch or send data through an API call during a chat. Set them up here:
Lyro AI Agent › Behavior › Actions & MCPsMost stores use both: Flows to start conversations at the right moment, Lyro to answer whatever the shopper actually types.
Each handoff costs an agent's time and still uses a Lyro conversation. These are the usual causes, roughly in the order to check them.
How you'll know: The question is common, and the handoff happens every time.
Fix: Read the handed-off chats weekly and add the missing answers as sources. Policies that live in someone's head are the usual gap.
How you'll know: "Where's my order?" works for some orders and fails for others, usually ones shipped by a 3PL, sold on a subscription, or placed through a second store.
Fix: The Shopify template only sees Shopify. A custom Action can call any API, so the fix is an endpoint that checks the 3PL, subscription app or ERP and returns a plain answer.
How you'll know: Cancel, refund, swap a size. Lyro explains the policy, then hands off.
Fix: Tidio ships a Shopify step for updating a shipping address, but not for canceling or refunding. Those need a custom Action and rules about when they're allowed.
How you'll know: You built a second lookup and couldn't switch it on.
Fix: Active Actions are limited by plan (one on Free, three on the Lyro AI Agent package, ten on Plus). One endpoint that answers several questions can stretch that limit further than several small Actions.
A custom Action is a short sequence: Lyro collects a value such as an email and order number, makes an HTTP request, and reads the fields that come back. The hard part is having something worth calling. Most stores don't have one API that knows the tracking number from the warehouse, the next renewal date from the subscription app and the stock level from the ERP.
Tidio's own help notes it doesn't validate or roll back your integrations, so a request that changes data (a cancellation, an address change) needs checks on your side: is the order already packed, is the shopper who they say they are, has a refund already gone out.
n-frames builds and runs that endpoint: one service that gathers the order, shipment and account details from your systems, answers Lyro in a format it can read, and only carries out cancellations or refunds your rules allow. If you're choosing between chat tools first, our Intercom Fin page and Zendesk AI agents cover how those count and price their AI.
Lyro is the AI agent: it answers in natural language from your knowledge sources. Flows is the automation builder: you set a trigger and script the steps, with no AI involved. They're billed separately, Lyro by conversations and Flows by visitors reached.
Yes, through Lyro Actions. An Action makes an API call during the chat, for example looking up an order or updating a Shopify shipping address, and Lyro uses what comes back. Templates exist for Shopify, Calendly, HubSpot, Mailchimp and Klaviyo; anything else is a custom Action pointed at your own endpoint.
It's as accurate as its sources. Lyro answers from the content you've added, so gaps in your policies or product info show up as wrong answers or handoffs. For anything that changes order by order, it needs an Action reading live data rather than a page of text.
No. Flows is drag and drop with templates for things like cart recovery and lead capture. Code comes in when a step needs to reach a system Tidio doesn't connect to, which usually means an API endpoint someone has to build.
By a monthly quota of Lyro conversations, either on its own or with a Tidio plan. A Lyro conversation is any chat with at least one AI reply, and it counts once even if the shopper comes back. Each account starts with 50 free conversations. Check Tidio's pricing page for current tiers.
Yes. The Shopify order status template asks for the shopper's email and order ID and looks the order up, once your store is connected. Orders whose tracking lives in a 3PL or another platform need a custom Action instead, which is the endpoint n-frames builds.