Concept illustration of a support team sorting customer inquiries into human support, AI chat, and automated flows to plan usage

Tidio's public annual-billing view starts at $24.17 per month for Starter and $49.17 per month for Growth. Lyro starts at $32.50, and Flows at $24.17. These are USD monthly equivalents with annual billing. Choose Monthly on the pricing page to check month-to-month costs. Plus is listed from $300 per month plus usage; Premium requires a quote. Official pricing · Billing FAQ

You don't need to add every starting price together. First decide what your team wants to do: handle conversations in Tidio, have Lyro answer questions, or run rule-based Flows. Those jobs have different usage counters.

This guide is for a small team that already answers customer questions and wants a realistic support budget, including busy months. It uses official documentation checked September 7, 2026. The planning examples are fictional; they aren't measured results from a Tidio account.

If you're still deciding what the product does, start with our Tidio and Lyro overview.

What are you paying for?

Part of TidioPublic starting allowanceBudgeting question
Starter100 billable conversationsHow much support will our team handle in Tidio?
GrowthFrom 250 billable conversationsWhat allowance and team features do we need?
Lyro AI AgentFrom 50 AI conversationsHow many threads will Lyro answer?
FlowsFrom 2,000 visitors reachedHow many people will our automated paths reach?

These are starting tiers, not unlimited bundles. Select your expected allowance before comparing prices. Lyro and Flows are also offered as standalone products; check how the product you want connects to your current support setup. Plan and product options

For example, adding AI to an existing help desk is a different buying decision from moving your team's inbox into Tidio. A greeting Flow is another choice. Buying all three without a clear role for each makes the budget harder to control.

Next step: Compare the Tidio products you actually need.

Three counters, three different definitions

Human conversations: count threads your team handles

Tidio's conversations-limit guide describes a handled thread as counted when an agent finishes and solves it. The number of individual messages doesn't determine the count. Tickets and supported social inbox conversations also use this allowance. It is separate from the AI and Flows counters. How human conversations are counted

When collecting your current workload, include the channels you plan to bring into Tidio. A website-chat total alone will understate the budget if your team also plans to handle email tickets there.

Lyro: count the first AI response in a new thread

Lyro's allowance is used when it first replies in a new conversation or ticket thread. Several responses in the same conversation don't each use another conversation. After 15 minutes of inactivity, a visitor's new message starts another thread; a new Lyro response uses another unit. An immediate handoff without a Lyro response doesn't use its quota. Lyro's counting rules

For an illustrative chat, suppose Lyro answers at 10:00 and again at 10:05 in the same active thread. Treat that as one AI conversation. If nothing else happens until the visitor returns at 10:30 and Lyro answers a new thread, that adds another. This example explains the documented rule; it isn't a billing test.

Don't apply that 15-minute rule to every other Tidio counter.

Flows: count the visitors reached

Flows are rule-based automations. Their monthly allowance counts unique visitors reached, rather than the number of messages or Flow designs. The same visitor can trigger several Flows in that period and still count once. How the Flows allowance works

That makes targeting a budget decision. A Flow greeting every new visitor can reach far more people than one triggered only when someone opens the chat. Estimate the audience for the Flow you're actually planning.

Which free limits renew?

The free human-support allowance is 50 conversations per month, and the free Flows allowance reaches 100 unique visitors per month. The first 50 Lyro conversations are different: they are a one-time allowance. A paid Lyro package provides a renewable monthly quota. Human limit · Flows limit · Lyro limit

Use the free AI allowance to learn which questions need better answers and when a person should step in. Don't build an ongoing monthly support budget around those first 50 conversations renewing.

Check the reset dates shown in your account, too. The help guides describe different reset schedules for different counters, so don't assume they all restart together.

Build a normal-month and a busy-month estimate

Start with the work you already see, then record each counter separately. Here's a fictional planning worksheet for a small team considering Tidio:

InputNormal-month assumptionBusy-month assumptionWhat to compare
Human-handled conversations180330Select a human allowance covering each estimate
Lyro conversations120220Select an AI allowance separately
Unique visitors reached by Flows9001,800Check the selected visitor allowance

These figures are independent workload assumptions. They don't claim that AI will remove a particular percentage of your team's work.

For the human row, Growth’s 250-conversation entry tier covers the normal-month assumption but not the busy-month assumption. Price the larger allowance as well. For the AI row, the entry allowance of 50 is below both estimates. The Flows entry allowance of 2,000 covers both visitor assumptions, but it is only relevant if you intend to use Flows. Verify the selected combination in the pricing tool before deciding.

Don't add the three rows and call the result “total customers.” A shopper might trigger a Flow, speak with Lyro and then need an agent. Equally, don't assume every shopper uses all three. Your estimate needs the events counted by each product, including any handoffs that lead to human work.

Next, record the price of one selected configuration for the normal month and one for the busy month. Don't add Starter and Growth together as though they were two required support subscriptions. Don't add an allowance again if your quoted package already includes it.

Try your own numbers: Check the selected allowances and billing period in Tidio's pricing tool.

Check what happens when the budget gets tight

An allowance needs an owner. Decide who checks usage during a promotion, who can authorize a larger plan, and what the team will do if it chooses not to upgrade. Check the current product-specific limit behavior before that happens.

Tidio also documents automatic upgrades for eligible standard monthly subscriptions on newer projects. The help page says the option is enabled by default where available, with an alert at 80% usage and an upgrade at 95%. It excludes annual plans, Plus plans, free accounts and trials. Check your own account rather than assuming either automatic spending or automatic protection from a limit. Automatic-upgrade conditions

For an annual quote, record the amount due, the included allowances and the process for changing them during a busy period. A monthly-equivalent headline is useful for comparison, but it doesn't tell you the full payment due today. For a monthly quote, check the renewal amount and any enabled upgrade setting.

Choose the smallest setup that covers a real job

If your current inbox works well, start by checking the AI option and integration you need. If you want your team to work in Tidio, estimate human conversations and required collaboration features first. Add paid Flows only if the visitor allowance supports a specific automation you want to run.

Before committing, write down four things: the selected products, their separate allowances, the payment due and the person responsible for checking usage. That gives your team a usable budget to review after a normal month and after a promotion.

Ready to compare a configuration? Review the current plans and selected quantities.

Share this article

XFacebookLINELinkedIn

Related articles