Tidio costs: human conversations vs Lyro AI and Flows quotas
Separate Tidio billable human conversations, Lyro AI conversations and Flows visitors. Understand one-time free AI access and recurring capacity.
In this guide
Three activity counts need three definitions
Tidio’s checked pricing page distinguishes billable human conversations, Lyro AI conversations and visitors reached by Flows. Human billable conversations include an agent reply; a Lyro conversation includes at least one AI reply.
These units should not be added together and priced at one assumed rate. A request can move from automated help to a person, and the relevant product definitions determine what capacity it consumes.
Map the customer journey before choosing quota
| Request | Activity to review | Budget question |
|---|---|---|
| Visitor leaves without an answer | No human reply | Does it enter any paid usage unit? |
| Lyro supplies the answer | AI reply | Which Lyro allowance applies? |
| Person answers directly | Human reply | Which support-conversation quota applies? |
| AI hands over to a person | AI and human activity | How are both applicable units recorded? |
| Flows reaches a visitor | Automation visitor event | Which Flows capacity applies? |
The table is an evaluation brief, not a measured Tidio invoice. Review the account’s actual usage report after an authorised synthetic test.
Keep lifetime free AI access out of the recurring budget
The checked page describes the first 50 Lyro conversations as a one-time allowance. A paid Lyro quota is needed for recurring refresh. Do not multiply that introductory allowance by twelve when estimating a year of operation.
For a fictional store expecting 80 AI-handled conversations and 120 human-answered conversations monthly, record two separate needs. Compare them with the retained quotas, not with a combined 200-conversation headline. Confirm how an AI-to-human handover is counted under the actual terms.
Read the annual equivalent alongside the payment term
The checked annual view displays Starter at US$24.17/month and Growth from US$49.17/month; Lyro and Flows have separate pricing. These are dated starting references, not a package quote for the fictional workload.
Record the annual commitment, support quota, Lyro quota, Flows reach and any custom usage. Keep plan seats distinct from billable conversations. Adding a colleague and receiving more customer requests need not have the same effect on the bill.
Test the boundary and escalation cases
Use a supported question, an unknown question and a customer who needs a person. Check answer quality, retained context and the usage units shown. Leave outcomes blank until the trial runs.
Use the Tidio profile, HelpCrunch budget guide and session-versus-resolution guide. Price the actual request mix instead of a generic chatbot count.
Frequently asked questions
Do Tidio’s first 50 Lyro conversations reset free every month?
The checked page describes the initial 50 as one-time. Confirm the paid recurring quota and refresh schedule for ongoing use.
Is a Tidio billable conversation the same as a Lyro AI conversation?
No. The definitions distinguish human-agent replies from AI replies, with separate allowances and pricing.
Put the guide into practice
Explore help desk tools, then compare your shortlist.
Explore the category →