Tidio Lyro AI Agent Pricing: Costs, Quotas & Help Desk Plans

The first 50 Lyro AI conversations are free for the lifetime of a Tidio account, not a monthly recurring allowance. After that, the entry price differs by billing option, while teams that add Tidio Help Desk also need to budget for a separate human-support meter.

Tidio Lyro AI Agent pricing is easiest to assess by separating the AI agent from Tidio’s help-desk plans. This guide explains the published starting prices, how AI and human conversations are counted, and what a small SaaS team can estimate before asking Tidio for a higher-volume quote.

Lyro AI Agent is available standalone or with Tidio Help Desk. Tidio’s pricing page lists the standalone starting price at $32.50 per month with annual billing for 50 Lyro AI conversations; a separate Tidio blog page lists $39 per month with monthly billing for the same starting volume. The first 50 conversations are a one-time lifetime allowance, and paid Lyro quotas refresh on a 30-day cycle from payment.

Tidio Lyro AI pricing at a glance

The standalone option is designed for teams that want Lyro’s knowledge-based responses and human handoff while keeping an existing help desk. Tidio also sells its customer-service platform, which combines AI usage with human-agent conversations. The two routes therefore have different cost components, even before a team considers a larger AI quota.

The $32.50 figure appears on Tidio’s pricing page under annual billing, which Tidio labels “2 months free.” The $39 monthly-billing figure is listed separately on Tidio’s AI customer service agent page. They are two published starting prices, not a complete price schedule for every conversation bucket.

At the starting 50-conversation limit, the annual-billing calculation is 32.50 × 12 = $390/year; the monthly-billing calculation is 39 × 12 = $468/year. The annual-billing difference over that 12-month comparison is (39 × 12) − (32.50 × 12) = $78/year. These totals cover standalone Lyro only, not a help desk or additional usage.

Starter’s listed price is annual billing; Tidio does not state a separate Starter monthly-billing price on its pricing page. Growth has a separate monthly-billing starting price, discussed below. The price schedules for the two bundles should not be treated as if they include a recurring paid Lyro quota: Tidio lists the first 50 Lyro conversations with Starter and Growth as a one-time lifetime allowance.

Lyro AI Agent pricing tiers and conversation limits

Tidio’s pricing selector lists standalone Lyro conversation buckets from 50 through 1,000 per month. Those available quantities do not amount to a published price for every bucket: Tidio does not provide a complete current price-and-bucket schedule for both monthly and annual billing. The table shows the available limits without assigning unsupported prices to higher tiers.

For a team forecasting 300 AI-handled interactions per month, the 300-conversation bucket is listed as an option, but the public price for that specific bucket is not stated in a full monthly-versus-annual schedule. A team forecasting 500 should use the 500 bucket as its volume reference and request the applicable quote rather than extrapolating a price from the 50-conversation entry tier.

For more than 1,000 Lyro AI conversations, Tidio directs buyers to contact it for a custom plan. The Lyro quota is separate from Tidio’s human billable-conversation limits, so a higher AI bucket alone does not establish how much a team will pay for agent-handled support.

Lyro-only vs. Lyro with Tidio Help Desk

Standalone Lyro is relevant when a SaaS team already has a help desk and wants to add an AI agent without moving its human-support workflow. Tidio says Lyro can be added to Zendesk, Salesforce, or other help desk software. The standalone package lists knowledge-based responses, customizable communication style, and human handoff.

A bundle can make sense when a team also needs live chat, ticketing, and a place for human agents to answer. Starter includes live chat and ticketing, 10 seats, and 100 billable conversations at its listed annual price. Growth starts at $49.17 per month with annual billing and $59 per month with monthly billing; it includes advanced analytics, automatic chat assignment, and 10 seats. Its billable-conversation selection starts at 250 and can be set up to 2,000.

Tidio Growth does not list a recurring paid Lyro quota as a standard plan benefit. It includes the one-time free allowance, and a team can buy Lyro separately or as part of a bundled plan. A team choosing Growth should therefore distinguish the help-desk price and its human-conversation allowance from any paid Lyro usage.

Plus starts at $300 per month plus monthly usage. It offers custom billable-conversation limits and custom Lyro limits, with AI and human usage charged separately at discounted usage rates. Tidio says to contact it for a custom plan above 2,000 billable conversations. Premium has custom pricing and custom limits; it lists from 3,000 Lyro AI conversations, pay-per-resolution billing, and personalized support 24/5. Tidio says complex issues are resolved within 24 hours and feature requests receive priority handling.

What counts as a Lyro conversation—and what counts as billable?

Tidio measures Lyro AI conversations and human-agent billable conversations separately. A Lyro conversation is a customer interaction through a channel integrated with Tidio that receives at least one Lyro AI Agent reply. Multiple AI replies in the same interaction count once, even if the customer leaves and returns later. (Tidio pricing)

A billable conversation is a live chat, ticket, email, or social-media conversation that includes a message from a human agent. A customer message that receives no human reply does not count as a billable conversation, and replies from Lyro or Flows are not treated as human-agent replies. Multiple human messages in one conversation count as one billable conversation.

For instance, 300 AI-replied interactions and 180 threads that receive a human reply would represent two distinct usage forecasts, not 480 units on one shared meter. This distinction matters when comparing a standalone AI plan with a bundle: AI volume can rise without the same increase in human billable conversations, while an escalated thread can use both measures.

Free Lyro conversations, renewals, and over-limit costs

Every Tidio account starts with 50 Lyro conversations, free for the lifetime of the account. This is a one-time allowance, not a monthly quota. Tidio’s Lyro limit guidance says the free allowance does not renew and Lyro stops working when those free conversations are used, until the project upgrades to a Lyro AI Agent package.

On Lyro AI Agent and Plus, a paid conversation limit refreshes 30 days from the moment of payment. That timing is not the same as a fixed first-of-the-month reset. A team should forecast demand against the account’s payment date and usage cycle rather than assume every account renews on a calendar-month boundary.

Tidio offers a 7-day free trial for the standalone Lyro AI Agent plan. The trial allows customers to test Tidio features and plans without providing credit-card information; at the end, the account is automatically downgraded to Free unless the subscription is upgraded. The trial is separate from the one-time 50-conversation allowance.

Tidio’s published guidance explains what happens when the one-time free allowance is exhausted, but does not specify the paid-plan behavior after a recurring paid quota is exhausted. A team should not build a budget that assumes either automatic overage billing or uninterrupted answers at the cap; the paid-plan limit and handling should be confirmed for the chosen offer.

Estimate the real monthly cost

A useful forecast separates three figures: AI interactions expected to receive a Lyro reply, conversations expected to receive a human reply, and the support platform already used by the team. The first helps select an AI quota; the second informs the human-agent allowance or usage charge. The third determines whether standalone Lyro is an add-on or a platform change.

Consider a small SaaS team expecting 300 Lyro-replied interactions and 180 human-replied threads in a month. The team can compare the 300 Lyro bucket against its expected AI use, then compare 180 human billable conversations with a Tidio Growth allowance starting at 250. With Growth, the published monthly starting price is $59, while the specific cost of adding a 300-conversation Lyro quota is not in a complete public bucket schedule. The proper estimate is therefore the published Growth starting price plus the quoted Lyro amount, not an invented combined total.

A second team might forecast 500 AI conversations and 350 human-replied threads. It would need to price the 500 Lyro bucket and choose a Tidio human-conversation allowance that covers its own expected replies. Growth permits selection up to 2,000 billable conversations, but the exact combined price depends on the selected plan and Lyro usage. If human volume exceeds 2,000 billable conversations, Tidio directs the buyer toward a custom plan; Plus also has custom limits and separately charged AI and human usage.

A short budget worksheet can use these steps:

• Count interactions likely to receive at least one Lyro reply, not the total number of AI messages.
• Count threads with at least one human-agent reply separately.
• Compare the forecast with standalone or bundled limits, then request a quote where the exact bucket price is not published.
• Include the existing help desk cost if the team keeps its current platform, or the selected Tidio plan if it moves human support into Tidio.

This method yields a usable range without treating an advertised resolution rate as a guarantee of savings. A team pays for a quota, but the business value depends on how many customers get a correct answer without needing to return or contact a person.

Is Lyro worth the price for a small SaaS support team?

Lyro is a stronger fit when repetitive questions have dependable answers in the team’s support knowledge and a human can take over cases that need judgment. For a SaaS product, a practical pilot might include plan-feature questions, account-access instructions, and a multi-step setup problem. It should also include a case where the answer depends on a customer’s account, because documentation alone may not resolve that request.

A useful pilot is not just a collection of simple FAQ prompts. Select a representative batch of recent tickets and compare Lyro’s answer with the eventual support outcome. Track whether the customer returned with the same issue, whether a human had to correct or complete the answer, and whether the handoff gave the agent enough context to continue.

A pilot scorecard can include:

• Resolution without a follow-up from the customer.
• Correctness and completeness against the current product behavior.
• Human handoffs, including whether the agent needed to repeat discovery questions.
• AI conversations used per durable resolution, rather than per message sent.

This approach helps assess value without relying on a vendor’s headline resolution figure as a cost guarantee. Tidio Premium lists a guaranteed 50% Lyro AI resolution rate, but an individual SaaS team still needs to determine whether its own ticket mix produces durable resolutions and less human work. A pilot on common cases gives that claim context without assuming the result transfers unchanged to another support queue.

Setup and channel fit should be assessed against the team’s actual workflow, not assumed from a feature checklist. Tidio describes Lyro as available through integrated channels and lists human handoff, but a team should confirm that its current support routes and escalation process fit the plan it is considering. If account lookups, controlled actions, or product-specific procedures are central to support, the pilot should test those requirements directly rather than scoring only documentation answers.

How Lyro pricing compares with other support-agent options

The useful comparison is not simply which vendor has the lowest entry price. It is whether the vendor charges for AI conversations, human conversations, resolutions, seats, platform access, or a combination—and what the chosen plan does at its usage boundary. Tidio makes the distinction explicit between Lyro AI conversations and human billable conversations; Premium also lists pay-per-resolution billing, while Plus separates AI and human usage.

The difference in conversation allowances is a starting point, not proof that one plan is cheaper per resolution: products may define a conversation differently, and the teams’ ticket mix and human handoffs affect workload. Zealoop’s pricing page lists Starter at $29 per month for 300 conversations, while Lyro’s standalone entry allowance is 50. A SaaS team should compare the definitions and test the same representative cases in each workflow before treating those volumes as equivalent.

The broader product distinction matters too. Zealoop answers from company documentation and can look up customer data and perform guarded actions; its plans include citations, abstention instead of guessing, an escalation inbox, and turn-level traces. That combination may be relevant when SaaS support depends on both documentation and customer-specific context. A team comparing options can also review Zealoop’s alternatives overview and weigh data access, human escalation, and action controls alongside the charging unit.

FAQ

Does Tidio Growth include a recurring paid Lyro quota?

Tidio Growth includes the one-time 50-conversation Lyro allowance, but its listed plan benefits do not include a recurring paid Lyro quota. A team can purchase Lyro separately or as part of a bundle. For a forecast above that free allowance, the Growth help-desk price and the selected Lyro quota should be treated as separate budget items.

What happens if a SaaS team needs more than 1,000 Lyro conversations?

Tidio directs customers with a need above 1,000 Lyro AI conversations to contact it for a custom plan, without publishing a fixed custom price. Plus offers custom Lyro limits, and Premium lists from 3,000 Lyro AI conversations with custom pricing. A team should bring its expected monthly AI volume and human-replied volume to that discussion because they use separate meters.

How should a team compare Lyro if resolution claims are uncertain?

Use a sample of real support cases and count customers who stay resolved without returning, alongside handoffs and corrections. For example, include both an easy plan-feature question and a multi-step setup case, then compare the answers with the support outcome. That test measures the team’s own ticket mix rather than treating a published resolution percentage as a guaranteed reduction in support cost.

Sources

• www.tidio.com/pricing/
• www.tidio.com/blog/ai-customer-service-agent/
• help.tidio.com/hc/en-us/articles/13924459295900-The-Lyro-AI-agent-limit
• www.tidio.com/live-chat/
• www.tidio.com/tidio-premium/
• www.zealoop.com/pricing
• www.zealoop.com/compare/