Lyro AI Chatbot Review: Is It Right for Small SaaS Teams?

A Lyro quota can cover several replies in one conversation, but a new thread after 15 minutes of inactivity may count again under Tidio’s quota rules. For a small SaaS team, that difference can change whether the starting allowance handles a month of support. This Lyro AI chatbot review explains what the agent offers, how its limits work, and how it compares with tools for account-specific support.

Lyro is Tidio’s AI support agent for answering questions from support content and passing conversations to people. It fits teams that want AI responses within Tidio or alongside an existing helpdesk. Its published pricing describes knowledge-based answers and human handoff, but does not establish a ready-made workflow for reading or changing SaaS account records. Teams should select it for supported answer-and-handoff work, not assume it can execute account operations.

Lyro AI chatbot review: the short verdict

Lyro is a strong candidate when a small team wants to automate repeat questions using support content and keep human support in the same customer-service operation. It can be purchased as a standalone AI agent or bundled with Tidio’s helpdesk and Flows products. Tidio also says Lyro can work with other customer-service tools, including Zendesk and Salesforce. (Tidio pricing)

The central trade-off is between answering a question and resolving an account-specific request. Lyro’s published product description confirms knowledge-based responses and human handoff. The material used here does not establish that Lyro can, out of the box, look up a SaaS user’s subscription, change an account setting, or issue a credit. That makes Lyro a more straightforward fit for documentation-led support than for a team whose common tickets require controlled changes to customer records.

Tidio displays an average 75% Lyro resolution-rate claim on its pricing page, but does not publish a calculation methodology for that figure. It should not be treated as a verified prediction of how many tickets a particular SaaS team will resolve. Premium separately lists a guaranteed 50% Lyro AI resolution rate; that plan-specific figure is not the same as a measure of answer accuracy.

What Lyro is—and how it fits into Tidio

Lyro AI Agent is one part of Tidio, not a synonym for the entire platform. Tidio sells Lyro on its own and in plans that combine AI support with Tidio’s customer-service tools. Its pricing page lists live chat and ticketing on Starter, while Growth adds features such as automatic chat assignment and advanced analytics. Those human-support features belong to the wider Tidio offering, not to Lyro’s knowledge-based answering alone. (Tidio pricing)

Flows is another distinct Tidio product. Tidio describes Flows as rule-based workflows created with a drag-and-drop builder, while Lyro uses AI to understand customer questions. Both can be used together. For example, a Flow can collect information along a configured path; Lyro can respond to a customer’s free-form question using support content. This distinction matters when evaluating which product is responsible for a particular step in a support process.

Lyro can also be purchased for use with another helpdesk, according to Tidio’s pricing page, which names Zendesk and Salesforce as examples of customer-service tools. That may suit a team that wants to add an AI responder without changing its existing support platform. The page does not provide an exhaustive list of compatible integrations, so those two examples should not be read as a complete integration catalog.

How Lyro answers questions and handles uncertainty

Tidio describes Lyro as answering customer questions using support content and lists knowledge-based responses as a core feature. For a SaaS team, that maps well to questions such as “How do I invite a teammate?” or “Which plan includes audit logs?”—provided the underlying documentation contains current, clear answers. A knowledge answer does not, on its own, establish that the agent has checked the customer’s account or applied a change.

Tidio also promotes an average 75% resolution rate, but does not publish how it calculates that average. Resolution rate and accuracy are different measures: a conversation can be counted as resolved without demonstrating that the answer was correct, and a correct answer can still require a human to complete the request. Teams should therefore evaluate sample conversations against their own support cases rather than use the headline as an accuracy benchmark.

A practical review set can include three types of questions:

• Documented facts: “Does the Pro plan include SSO?” The answer should match the current plan documentation.
• Missing information: “Can you restore the workspace I deleted?” If support content does not cover the case, the team should confirm how Lyro handles it and whether a person can take over.
• Account-specific requests: “How many seats are on my account?” This requires customer context beyond a general help article.

For the first category, a team can compare replies with its documentation and note omissions or outdated policy details. The second tests the boundary between a useful answer and an unsupported guess. The third distinguishes content retrieval from access to live customer data. Tidio lists human handoff with Lyro, giving teams a route for cases that need a person; the specific handoff behavior should be evaluated in the team’s intended setup.

Setup, channels, and human handoff

Tidio’s pricing page describes Lyro as an AI agent that can be purchased alone or alongside Customer Service and Flows. It lists human handoff with the standalone Lyro AI Agent, and live chat and ticketing in the Customer Service plans. This gives a small team a documented path to combine AI responses with human support without assuming that the AI agent itself replaces an inbox or ticketing system. (Tidio pricing)

Tidio also describes Flows as having a drag-and-drop builder, but that does not establish that every Lyro configuration is no-code or requires no technical setup. The published pricing information identifies integrations with other customer-service tools, including Zendesk and Salesforce, but does not offer a complete list of channels or setup prerequisites. A buyer should distinguish the documented workflow builder from Lyro’s separate configuration and integration requirements.

For a small team evaluating handoff, useful test cases include a customer explicitly asking for a person, a request the support content does not answer, and a request that needs account verification. The team can confirm where each case goes, what context is available to the human, and whether the customer receives a clear response while waiting. Those operational details matter as much as the AI’s first reply when there is no round-the-clock support coverage.

What Lyro can do beyond answering FAQs

The key dividing line is whether a request can be completed from support content alone. “How do I cancel?” can be answered with a documented procedure. “Cancel my subscription” requires the system to identify the right account and perform a change. “What is your refund policy?” is a policy question; “Refund my last payment” is a transaction. Those are separate capabilities, and a team should not treat one as evidence of the other.

Tidio’s pricing page says Lyro can integrate with other customer-service tools, including Zendesk and Salesforce, and describes knowledge-based responses. It does not document a specific Shopify order-verification action or establish that Lyro can retrieve order status, process a refund, or make changes in a SaaS account. For buyers searching for a Lyro Shopify integration, the practical question is which exact store data and operations the intended connection supports—not simply whether an integration is available.

A support team can map its top requests to the required capability before adopting an agent:

1. Answer: Use current documentation to explain a policy or product feature.
2. Look up: Retrieve information specific to an authenticated customer, such as a plan or usage total.
3. Act: Make a change, such as updating a setting or issuing a credit, with appropriate authorization and controls.
4. Escalate: Pass the conversation to a human when the information or authority to proceed is missing.

Lyro’s published description supports knowledge-based answers and human handoff. For account lookups or changes, the team needs evidence about its particular integration and workflow before treating those jobs as covered. This is especially relevant for SaaS: an ecommerce order example, even if available in another configuration, would not prove that a subscription-management or workspace-administration action works in the same way.

Pricing, plans, and AI conversation limits

Tidio lists the standalone Lyro AI Agent from $32.50/mo. for 50 Lyro AI conversations, with a 7-day free trial. At that starting price, the 12-month total is 32.50 × 12 = $390. Starter is $24.17/mo. with annual billing and includes 100 billable conversations plus 50 Lyro AI conversations as a one-off allowance. Growth starts at $49.17/mo. with annual billing and from 250 billable conversations; its listed features do not include a Lyro conversation quota. These are separate usage measures, not interchangeable allowances. (Tidio pricing)

A Lyro conversation is an interaction through a channel integrated with Tidio that has at least one AI Agent reply. Multiple replies, or returning to the chat later, still count as one conversation under the pricing FAQ. Tidio’s quota rules add a thread boundary: after 15 minutes of inactivity, a conversation closes, and a later visitor message can start a new thread and use another quota. An immediate Lyro handoff does not deduct from the quota. (Lyro quota rules)

The first 50 Lyro conversations on a new project are free and non-renewable. Paid Lyro packages start at 50 and extend to 1,000 conversations, with larger quotas available through custom Plus subscriptions. For a team expecting 50 Lyro conversations a month, the standalone starting package matches the starting allowance. For 1,000, the standalone starting package covers only 50; the pricing page presents larger usage options, but does not give a single public price for every quota. Plus starts at $300/mo. plus monthly usage and offers custom billable-conversation limits and discounted usage rates. Premium is contact-for-pricing, lists from 3,000 Lyro conversations, and includes pay-per-resolution billing and a guaranteed 50% Lyro AI resolution rate.

The starting-point comparison is not simply “lowest monthly price wins.” Tidio counts AI conversations; other tools may meter credits, messages, or active users. For example, AssistLoop Starter is $39/month and includes 3,000 credits per usage cycle, while Peopleloop Grow is $25/month and includes 500 messages, with an estimated 63–100 chats per month. These units are not directly comparable with Lyro conversations. (AssistLoop pricing; Peopleloop pricing)

Pros and cons for small SaaS teams

Pros

• A distinct AI allowance: Tidio separates Lyro AI conversations from human-agent billable conversations, making the usage model easier to assess once the team knows its likely thread volume.
• Human handoff is included: The standalone Lyro AI Agent lists human handoff, so automation does not have to mean removing a person from support.
• Can sit beside other helpdesks: Tidio names Zendesk and Salesforce as examples of tools Lyro can work with, which may help teams that are not ready to replace their current platform.
• A low-volume entry point: The standalone offer starts at $32.50/mo. for 50 Lyro AI conversations and includes a 7-day free trial.

Cons

• The first free allowance does not renew: The first 50 Lyro conversations on a new project are a one-time quota, not an ongoing free monthly plan.
• Thread boundaries can affect usage: A new thread after 15 minutes of inactivity may use another quota, even if the same customer returns with a follow-up.
• A resolution-rate headline is not an accuracy benchmark: Tidio does not publish the calculation methodology for its average 75% Lyro resolution-rate claim.
• The published feature description is strongest on answers and handoff: It does not establish a ready-made SaaS account lookup or transaction action.

For teams that need customer-data operations as well as documentation answers, Zealoop describes a different support-agent model: customer-data tables, guarded read-and-write actions on Starter, Growth, and Scale, and multi-step procedures on Growth and Scale. Its plans include answers with citations, grounding validation that turns a validation failure into abstention, signed identity (HMAC), an escalation inbox, and turn-level traces. (Zealoop’s documentation-bot and guarded-agent comparison)

Zealoop’s Free plan includes a real documentation-answering agent without a credit card, while its plans are flat-priced with no per-seat or per-resolution charges. At its conversation limit, the agent stops answering until the next month or an upgrade, with no overage bill; visitors receive a holding reply and the conversation goes to the inbox. Those are concrete cost and operating differences, not a claim that every workflow fits every team. (Zealoop comparison of RAG chatbots and AI support agents)

Lyro vs. alternatives: when to choose each

The most useful comparison is the unit being metered and whether the product describes customer-specific actions. Lyro uses AI-conversation quotas; AssistLoop lists credits and Agent Actions; Peopleloop and LoopReply list messages and other usage measures. A high limit in one unit does not imply a greater allowance in another. The table summarizes published plan details rather than implying that each allowance buys the same amount of support.

For an ecommerce operation, product-specific support depends on what its store integration actually exposes; the Tidio pricing details cited here do not verify Shopify order lookup or refund execution. For a SaaS team choosing among these products, the more useful test is whether it can authenticate the customer, retrieve the required record, and control any write operation. Zealoop explicitly lists guarded read-and-write actions on paid plans; AssistLoop lists Agent Actions, but not action-specific approval controls in its pricing details.

Who should choose Lyro—and who should look elsewhere?

Choose Lyro when a team’s leading requirement is documentation-based customer support, it wants an AI agent that can hand off to people, and Tidio or a compatible existing helpdesk suits its wider operation. The starting 50-conversation allowance can make a small pilot practical, and the 7-day free trial gives the team a defined evaluation period. A useful pilot tracks which questions Lyro answers, which require a person, and how many distinct threads consume the quota.

Look elsewhere when support depends on regularly retrieving or changing SaaS account data and the chosen Lyro setup cannot demonstrate those operations. A team should use a representative test such as “How many seats are on this account?” followed by “Add a seat.” The first requires a customer-specific lookup; the second requires an authorized write. If the expected result is only a help article explaining how to add a seat, that is not the same workflow.

Zealoop is worth comparing when the team needs documentation answers alongside customer-data tables and guarded read-and-write actions. Its Free plan includes citations, signed identity, an escalation inbox, human replies, and turn-level traces; the company describes setup as a 20-minute quickstart. For SaaS operations where safe actions and visible traces matter, that is a more directly relevant evaluation than comparing chatbot response rates alone.

FAQ

How does Tidio count a Lyro AI conversation?

Tidio’s pricing FAQ counts an interaction through a Tidio-integrated channel when Lyro gives at least one reply. Multiple replies and returning to the chat later count as one conversation. Its quota rules say a thread closes after 15 minutes without activity; a later message may start a new thread and use another quota.

What happens when the Lyro conversation quota runs out?

Tidio says Lyro stops working after the project’s free 50-conversation quota is used. Paid Lyro packages provide renewable monthly quotas, and the limit refreshes according to the paid package’s cycle. A team expecting usage above its allowance should choose an appropriate package or custom option rather than assume replies will continue as metered overage.

Does Lyro have a free trial?

Tidio lists a 7-day free trial for the standalone Lyro AI Agent. New projects also receive a free, non-renewable quota of 50 Lyro conversations. The trial and the initial quota are different offers: the first is time-limited, while the second is a usage allowance that does not renew.

Is Lyro a better fit than a documentation-only bot for a SaaS team?

It can be, when the team wants Lyro inside Tidio’s wider customer-service platform or needs its listed human handoff. A documentation-only tool may be sufficient if the main workload is explaining product behavior. For account-specific work, compare published access and action capabilities rather than assuming either category can modify customer records.

Sources

• www.tidio.com/pricing/
• help.tidio.com/hc/en-us/articles/13924459295900-The-Lyro-AI-agent-limit
• assistloop.ai/pricing
• peopleloop.io/pricing
• peopleloop.io/docs/getting-started
• loopreply.com/pricing
• www.zealoop.com/compare/ai-customer-support-chatbot-docs-vs-agents
• www.zealoop.com/compare/rag-chatbot-customer-service-vs-ai-support-agents