Tidio pricing: free plan, limits and paid options in 2026

The table below reflects the current official plan page. It is a research reference, not a checkout quote. If you have an older account, check its own terms too. Today's public offer may differ from the one you bought.

Compare the free plan and paid Tidio pricing

Tidio's official pricing separates support plans, AI conversations and Flows usage. The page displays a monthly/annual selector. The paid entry figures below are the displayed annual-billing monthly equivalents unless the row says otherwise. Confirm the full charged amount and currency at checkout.

Do not add the three entry prices and assume that sum is the correct bill for your account. The page includes package choices and a usage selector. The suitable setup depends on the support plan, the automation you choose and the current offer for that combination.

The total for a larger Growth quota is not established by the entry figure. Likewise, a Plus base amount is not a full fixed bill when usage is added. Keep the unknown part visible until the chosen quote defines it.

What the free plan includes

The current plan comparison lists a Free support tier with finite human conversation scope and staff seats. Tidio's help explains that the free basic plan remains after the trial ends. The trial can expose features beyond that ongoing tier.

Check the account's real usage and plan screen before relying on a trial feature. A trial may show routing or an AI reply. Check whether that feature stays on the free plan when the trial ends.

The official page also describes a one-off allowance of 50 Lyro conversations and 100 Flows users in the entry offer. Do not call a one-off AI allowance monthly free AI. The refresh rule is part of the product choice.

For a small site, the free support tier may be enough to assess a defined human-chat task. That is a conditional fit, not a guarantee about future demand. Set an offline route and monitor the allowance under the vendor's definition.

Human chat, Lyro and Flows use different limits

Human-handled billable conversations

Tidio defines a billable conversation around a conversation with a human agent message. The current page includes live chat, tickets and connected channels in that definition. Read the full current wording rather than treating the allowance as a count of website visits.

A user can view a page without starting such a conversation. A message can also come from a channel beyond the website. Read the usage screen with the vendor's unit in mind. A count of people who opened the launcher may measure a different thing.

Keep staff access separate from volume. The listed entry tiers include seats, but a seat does not grant an unlimited conversation allowance. Adding people to the team and handling more conversations are distinct planning questions.

Lyro AI conversations

Lyro is the AI product. The current offer distinguishes the first one-off allowance from a paid monthly refresh. A site owner should know which state the account is in before describing the bot as continuously available.

The AI allowance does not prove the bot's answer quality. You still need an approved source, a no-answer boundary and a human or contact fallback. A larger allowance does not fix a missing returns policy or an unsupported account action.

Flows visitors reached

Flows uses a user-reach unit in the current pricing display. That is distinct from a human-handled conversation and from a Lyro response. A website can need one of these products without needing the others at the same level.

Define the flow's task before choosing volume. A short inquiry path and a broad proactive campaign can reach distinct audiences. This guide does not assume a flow produces a lead or a sale merely because it reaches someone.

Illustrative usage scenarios

These examples show how to think about the units. They are fictional workloads, not observed user data, forecast traffic or complete bill calculations.

A modest human-only queue

A fictional service site wants people to answer during office hours. It does not need an AI answer source yet. The owner should compare the human conversation allowance and staff access first, then keep the bot and flow choices separate.

The free tier may be sufficient to assess that narrow task within its listed allowance. The owner still needs to monitor the real usage definition and know the upgrade boundary. The example does not prove that every small site stays within the free quota.

Routine FAQ help plus human exceptions

A fictional shop has a maintained public FAQ and staff who handle unusual questions. The owner should estimate the AI task and the human queue as separate workloads. A bot handoff can create work for a person even if the first reply was bot.

Check how the current product counts the useful events. Do not subtract every AI interaction from an assumed human bill without evidence. Count the task mix using the vendor's rules and retain uncertainty where a transition is not clear.

A team using several channels

A fictional support team handles website messages and connected-channel requests. A website-only traffic count will not describe the full billable workload if the current definition includes those other channels.

List the channels, the staff who use them and the applicable product scope. Compare the chosen quota rather than the lowest advertised entry amount. If the package needs a custom quote, keep the total as not verified until the quote is available.

What to check before paying

Record the billing period. A monthly equivalent shown for an annual commitment is not the same cash payment as a month-to-month plan. Check renewal and cancellation terms on the current offer and in the account.

Record the chosen quota and its unit. If you use the interactive selector, preserve the chosen support, AI and Flows values with the quote. Otherwise a later screenshot of the entry plan may not describe what you bought.

Check which features are actually needed. A larger package can include controls that a small workflow does not use. Conversely, a low usage estimate does not make a required routing or access feature available on every tier.

Inspect the current data terms and staff roles. A support system can hold conversation content and connected details. Check fit as well as cost.

Who should consider an alternative

Consider another route when the vendor's unit or package does not match a verified need. A staffed chat product may fit a person-led queue. An ongoing free base chat service may fit a narrow task. A CRM route may fit a team already working there.

Use the Tidio alternatives comparison to compare those reasons separately. It does not invent equivalent monthly bills between seats, conversations and other units.

If the question is whether to use a bot at all, read chatbot vs live chat. Choose the support model first. A person or form may handle the task without a paid bot allowance.

Keep a copy of the selected unit

When checking an offer, record the chosen quota as well as the plan name. The same page may later show a different default. The useful record is the actual support, AI and flow scope you chose.

Do not infer a larger allowance from the number of staff seats. Count the unit under the vendor's rule and leave any custom part of the quote open until it is stated. This keeps a neat plan comparison from becoming a false fixed bill.

Check the renewal as well as the entry offer

Read the chosen renewal terms before paying. Keep the package, quota and billing period together so a later account review compares the same offer.

Read an older invoice on its own terms

Keep the invoice period beside the plan name when comparing an old charge with a new offer. Check whether it covered the same products and quota. A changed total may reflect a different term or scope. If the account does not explain the difference, ask the vendor before treating the public entry amount as the renewal bill.

Continue with the right task

• live chat widget
• website widgets