Tidio Plan Fit Guide: Add-Ons, Support Needs, and How to Choose

Affiliate disclosure: This article may contain affiliate links. If you purchase through one, we may earn a commission at no extra cost to you. Commission does not influence our recommendations.

Direct verdict: Tidio Free is the right starting point for validation, Starter fits a small human-support volume, and Growth is the practical default when routing, automation and a larger conversation allowance become operational needs. Plus makes sense only when a team can name the governance, support or capacity requirement that justifies custom packaging.

The important shift is that Tidio is not priced by one simple usage number. Human conversations, Lyro AI conversations and Flows have separate allowances. A low monthly price can therefore be misleading if the team has not estimated how visitors will move among automated answers, flows and human agents.

If that sounds like more forecasting than a chat tool should require, do not worry: the useful estimate can fit on one page. Start with the questions customers ask most often, mark which ones need judgment, and count the busiest realistic month. The goal is not a perfect forecast. It is to avoid discovering during a launch that the human-support allowance was sized for an ordinary Tuesday.

Need help deciding?

Not sure which tool is best for your case?

Use our Marketing Software Advisor to get a personalized recommendation.

Find the right tool

Tidio pricing at a glance

Tidio Starter and Growth annual plan prices and billable conversation allowances
Starter and Growth are the main self-serve decision point. Compare the human-conversation allowance with the busiest support month, not the average month.

With annual billing selected on July 19, 2026, Tidio displayed Free at $0, Starter at $24.17 per month for 100 billable conversations, Growth from $49.17 per month with capacity starting at 250 billable conversations, Plus from $300 per month plus monthly usage, and Premium with custom pricing.

A billable conversation is not every website visit and not every automated reply. It becomes billable when a human agent initiates or responds in the conversation. Flow and Lyro replies do not consume the live-conversation allowance, but they use their own meters. That distinction should drive the forecast.

Which Tidio plan fits which operating model?

Tidio inbox and website chat widget showing the same customer conversation
Tidio’s operating value is the shared conversation flow between the support inbox and the visitor-facing chat widget, not the plan label alone.

Free — validate the channel

Use Free to confirm that live chat belongs in the customer journey and to learn what visitors actually ask. It is a proof-of-value tier, not a durable answer for a store or service business with recurring human support.

Starter — low-volume human support

Starter works when one small team answers a controlled number of conversations and needs a professional live-chat foundation without advanced routing. The 100-conversation allowance is the first hard planning constraint.

Growth — the practical operating tier

Growth is the better default when service is recurring, more than one person participates, or automation and routing need to reduce manual work. The displayed starting price covers a starting allowance; capacity expansion changes the real monthly cost.

Plus or Premium — governed scale

Tidio Plus and Premium enterprise-oriented plan cards
Plus and Premium move the decision from simple self-serve pricing toward custom capacity, support and governance.

Plus adds custom seats and a more tailored service layer. Premium is a managed, high-volume decision. Neither should be selected because it sounds safer; require a documented need for volume, support, governance or implementation help.

Estimate the three usage meters separately

Start with human conversations: count only threads in which an agent is expected to intervene. Then estimate Lyro conversations for natural-language automated support and Flow visitors for rule-based paths such as qualification, lead capture or routing. Do not add those numbers into one undifferentiated traffic estimate.

A realistic store scenario

Suppose a store receives 1,000 chat openings in a promotion month. A Flow routes 600 routine visits, automated answers resolve 250 questions, and 150 conversations reach a person. The plan decision should be built around those 150 human conversations plus separate automation capacity—not all 1,000 openings and not the quiet-month average.

The official pricing page also indicated an initial one-time allowance of 50 Lyro conversations and 100 Flow visitors. These introductory allowances are useful for validation but do not represent the ongoing capacity of a mature deployment.

The current Tidio structure lets a team combine a core plan with automation add-ons. That flexibility is useful, but it creates a common budgeting error: choosing the core plan first and treating automation capacity as an afterthought. Model both before committing to annual billing.

Costs and limits that deserve a second look

  • Conversation seasonality: promotions, launches and holiday peaks can exhaust a human-conversation allowance much faster than a normal month.
  • Agent seats: self-serve plans were presented with support for up to 10 agents, while Plus supports custom seating.
  • Automation add-ons: Lyro and Flows have independent capacity and can change the effective monthly total.
  • Annual commitment: use the busiest realistic month and leave modest headroom before selecting an annual tier.
  • Implementation time: weak routing and an incomplete knowledge base can make a higher plan feel less effective than a well-configured lower plan.

The handoff is where the experience succeeds or fails

A polished automated answer is not enough if the visitor must repeat the problem when a person joins. During the trial, check whether the agent receives the question, page context, customer details and previous answers in one usable view. Decide who owns unanswered conversations, what response-time promise is realistic, and when a thread becomes a CRM or help-desk record.

Also test the uncomfortable cases: a refund request, an angry customer, an address change after purchase and a question the knowledge base cannot answer. These are the moments that reveal whether automation is helping the team or merely postponing work.

Do not buy capacity to compensate for unclear ownership.

A smaller plan with a maintained knowledge base, clear routing and one accountable owner can create a better customer experience than a larger plan nobody reviews.

A short selection protocol

  1. Map the five customer questions that create the most service effort.
  2. Decide which questions a Flow can route, which Lyro can answer, and which require a human.
  3. Estimate the three monthly usage meters for a peak month.
  4. Choose the lowest plan that covers human volume, agents and required controls.
  5. Run the seven-day trial without a card and measure deflection, response time and handoff quality.

Need help deciding?

Not sure which tool is best for your case?

Use our Marketing Software Advisor to get a personalized recommendation.

Find the right tool

Frequently asked questions

Does every automated reply count as a billable conversation?

No. The official definition centers the live-conversation allowance on human-agent participation. Lyro and Flows have separate meters.

Is Growth automatically better for a small team?

No. Growth is justified when its added capacity or workflow controls remove a measured constraint. A low-volume team can remain on Starter if the limits fit.

Should a team choose annual billing immediately?

Only after a trial or a representative pilot. Annual savings do not compensate for choosing the wrong capacity model.

How we verified this page: We checked the current official pricing cards, billing view, conversation definition, trial terms, agent limits and separate automation allowances on July 19, 2026. We did not trigger a merchant route or run a long production benchmark.

Final recommendation

Start on Free when the channel is still unproven, choose Starter for a genuinely small human-support workload, and treat Growth as the default candidate for a recurring team workflow. Choose Plus only when custom seats, support or governance has a clear operational value. Before committing, use the Tidio plan logic against one peak-month forecast and test the handoff from automation to a person.