Comparison
Ada vs Lyro
Compare documented workflows and implementation requirements using attributed public sources. Facts last checked , the earlier of the two records. Machine-readable record.
Start with your setup
These are documented product differences and requirements. A feature list or a single customer report does not establish which agent will perform better for your team.
Deployment model
Ada
Ada documents setup through its dashboard and a website or mobile chat integration, with connected knowledge and configured workflows.Vendor-reported
- Source
- Key concepts (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-deployment
Lyro
A hosted agent added to a website via the Tidio widget; the vendor states it can be added in a few clicks without technical knowledge.Vendor-reported
- Source
- Lyro AI Agent (Tidio)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
lyro-cmp-deployment
Actions in backend systems
Ada
API tools, formerly called Actions, retrieve or send data through configured endpoints. Playbooks and Processes organise those calls into workflows.Vendor-reported
- Source
- API tools (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-actions
Lyro
Tidio describes Smart Actions covering order updates, lead qualification and product recommendations as the actions Lyro performs beyond answering.Vendor-reported
- Source
- Lyro AI Agent (Tidio)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
lyro-cmp-actions
Human handoff
Ada
Configured live transfers or follow-up tickets, with off-hours and error paths. Up to five active handoff configurations are documented.Vendor-reported
- Source
- Handoff management (Ada docs)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
ada-handoff
Lyro
Tidio states users can set flexible handoff and escalation rules and that Lyro creates a ticket in the connected support solution for a human agent.Vendor-reported
- Source
- Lyro AI Agent (Tidio)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
lyro-cmp-handoff
Side by side
Product attributes first, then what the sources establish for each customer workflow, then the industries they place each agent in. Open any claim to see its source, the date it was checked, and how to request a correction. Two agents are rarely documented to the same depth, so read a difference between the two columns as a difference in the public record before reading it as a difference in the products.
What this agent was judged by
No independent source has been found for any fit area, so every state here rests on vendor material or nothing.States rest on 0 independent sources. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
What this agent was judged by
The independent evidence behind these states comes mainly from other independent sources.States rest on 2 independent sources across other independent sources, end-user review sites. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
| Attribute | Ada | Lyro |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Ada documents setup through its dashboard and a website or mobile chat integration, with connected knowledge and configured workflows.Vendor-reported
| A hosted agent added to a website via the Tidio widget; the vendor states it can be added in a few clicks without technical knowledge.Vendor-reported
|
| Channels | Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Tidio defines a billable conversation as a customer interaction initiated through any channel integrated with Tidio that gets at least one reply from the agent, but does not enumerate the individual channels on its Lyro or pricing pages.Vendor-reported
|
| Languages | 60 languages are documented for messaging and email; voice supports a subset. English remains the fallback language.Vendor-reported
| Unknown |
| Help desk and CRM integrations | The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Tidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution.Vendor-reported
|
| Knowledge sources | Knowledge can come from help centres, websites, articles created in Ada and custom sources through the Knowledge API.Vendor-reported
| Tidio states Lyro automatically scrapes a business's support content and uses it as its knowledge base.Vendor-reported
|
| Actions in backend systems | API tools, formerly called Actions, retrieve or send data through configured endpoints. Playbooks and Processes organise those calls into workflows.Vendor-reported
| Tidio describes Smart Actions covering order updates, lead qualification and product recommendations as the actions Lyro performs beyond answering.Vendor-reported
|
| Human handoff | Configured live transfers or follow-up tickets, with off-hours and error paths. Up to five active handoff configurations are documented.Vendor-reported
| Tidio states users can set flexible handoff and escalation rules and that Lyro creates a ticket in the connected support solution for a human agent.Vendor-reported
|
| Target customer size | Ada presents an enterprise-focused sales process with a tailored demonstration and implementation plan. This positioning does not establish a minimum viable company size.Vendor-reported
| Published self-serve pricing runs from 50 free lifetime conversations and $32.50 a month up to 1,000 conversations a month, above which Tidio directs buyers to sales, indicating a small-business entry point.Vendor-reported
|
| Vendor-reported performance claims | Ada reports that Dott’s automated resolution increased from 32% to 77% after adopting Ada and connecting backend automations. This is one customer’s vendor-published result, not a platform-wide average or a comparable benchmark.Vendor-reported
| Tidio claims customers automate around 67% of customer inquiries with Lyro on average, and cites one case study with a 97% decrease in average response time.Vendor-reported
|
| Workflow evidenceBilling Illustrative scenario I was charged twice for the same order. Can you refund the extra payment? What to verify: Verify identity, inspect payment records, apply the refund policy, and confirm the payment-system result. If no authorized refund action is connected, hand off with the evidence. | Vendor-documented Illustrative scenario, not a test: explain a duplicate charge using the customer’s payment records. Ada documents billing inquiries; verify identity checks, access to the payment system and the route for a disputed charge. Answering a question and reversing a payment are separate operations. 1 cited claim for billing on AdaAda lists billing and payment questions among its email workflows, using information retrieved from connected business systems.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceOrders Illustrative scenario My order has not arrived. Where is it? What to verify: Retrieve the correct order and current carrier status. Distinguish a real tracking update from an estimate; do not invent a delivery date. | Vendor-documented Illustrative scenario, not a test: retrieve shipment status for a customer’s order and give the carrier’s tracking link. Validate customer ownership, missing orders and stale tracking data. A lookup does not demonstrate that lost parcels are resolved. 1 cited claim for orders on AdaAda documents API-driven order-status lookups, so live order answers depend on connecting the order system.Vendor-reported
| Vendor-documented No independent report of Lyro executing order-status or order-modification actions was found; the capability rests on vendor description alone. 1 cited claim for orders on LyroTidio states Lyro can automate order updates and lead qualification through a feature it calls Smart Actions.Vendor-reported
|
| Workflow evidenceReturns Illustrative scenario I bought this 12 days ago and opened the box. Can I return it? What to verify: Check the actual return window, product exclusions, and order record. A policy answer and an executed return are different capabilities. | Vendor-documented Illustrative scenario, not a test: check whether an unopened item is inside the return window, then request a label from the order system. Confirm the label was created before saying the return is arranged, and route policy exceptions to a person. 1 cited claim for returns on AdaAda describes returns workflows that check order eligibility, offer permitted options and create a return label through connected systems.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceProduct questions Illustrative scenario Does this adapter work with my exact laptop model? What to verify: Use a current, approved compatibility source. Ask for the model when missing and distinguish documented compatibility from an assumption. | Vendor-documented Illustrative scenario, not a test: answer whether a product works with a specific phone model from the compatibility guide. Check that the reply uses the correct product version and asks for missing details instead of inventing compatibility. 1 cited claim for product questions on AdaAda uses imported knowledge to answer questions; its documentation explains that relevant passages are retrieved from that content.Vendor-reported
| Caveat documented The independent evidence is genuinely mixed: several Shopify merchants report Lyro handling the bulk of product questions, while a Trustpilot reviewer reports it failing on Tidio's own site. Contrary evidence outranks capability claims under the rubric, so this reads poor; both sides are listed so a reader can weigh them. 4 cited claims for product questions on LyroTidio states Lyro automatically scrapes a business's support content to use as its knowledge base and can provide product recommendations.Vendor-reported
A Shopify merchant wrote that Lyro has learned their product range, delivery options and returns and can handle the bulk of their questions.Independent report
Another Shopify merchant wrote that Lyro solved many queries before they became an email ticket.Independent report
A Trustpilot reviewer reported that Lyro, as deployed on Tidio's own site, can barely answer any help questions.Independent report
|
| Workflow evidenceAccount issues Illustrative scenario I lost access to my email. Change the address on my account. What to verify: Follow the approved identity-recovery process before accessing or changing account data. Escalate when identity cannot be verified. | Vendor-documented Illustrative scenario, not a test: update the signed-in customer’s contact details through an authorised account API. Verify that another customer’s records cannot be changed and that failed updates are not reported as complete. 1 cited claim for account issues on AdaAda documents account updates through external APIs and sign-in tokens for sensitive actions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceComplaints Illustrative scenario I have contacted you three times and the problem is still unresolved. What to verify: Recognize the repeat complaint, retain relevant history, and route it to the right team. Do not promise compensation outside the policy. | Vendor-documented Illustrative scenario, not a test: a customer says repeated delivery problems remain unresolved. Configure a route to the complaints team with the case details. Routing is documented; the reviewed sources do not measure successful complaint resolution or de-escalation. 1 cited claim for complaints on AdaAda documents routing to human support based on conversation context and configured handoff descriptions.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceHuman handoff Illustrative scenario Please connect me to a person who can approve this exception. What to verify: Transfer to an available team with the conversation and relevant records. Outside working hours, explain the actual follow-up path rather than promise immediate contact. | Vendor-documented Illustrative scenario, not a test: a customer requests a person after an unsuccessful answer. Verify that the receiving team gets the conversation and that, outside working hours, the customer receives a clear follow-up path. 1 cited claim for human handoff on AdaAda documents live transfers, follow-up tickets, off-hours paths and error fallbacks across its handoff setup.Vendor-reported
| External report Tidio states users can set flexible handoff and escalation rules and that Lyro creates a ticket in the connected support solution so a human agent can answer. 2 cited claims for human handoff on LyroTidio states users can set flexible handoff and escalation rules and that Lyro creates a ticket in the connected support solution so a human agent can answer.Vendor-reported
A Shopify merchant described the agent as able to answer repetitive questions automatically and escalate questions when needed.Independent report
|
| Workflow evidenceSmall businesses Illustrative scenario A two-person support team wants to launch without a dedicated engineer. What to verify: Validate setup effort, existing help-desk support, required integrations, and ongoing maintenance. A small customer's story alone does not establish suitability for every small business. | Not established Illustrative buying scenario: a small shop needs only shipping FAQs and occasional order lookups. Ask Ada to demonstrate that limited scope and the work needed to maintain it. Demo-led procurement does not establish that every small business is a poor fit. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | External report Independent evidence for the small-business segment is unusually dense here because Lyro is distributed through the Shopify App Store, where reviewers self-identify as small merchants. 3 cited claims for small businesses on LyroTidio sells Lyro self-serve with a no-credit-card seven-day trial, 50 lifetime free conversations and entry pricing from $32.50 a month, with no minimum seat or annual commitment stated.Vendor-reported
A small Shopify store reported an AI resolution rate of around 90% after six months on the app.Independent report
A small Australian merchant wrote that Lyro has learned their product range, delivery options and returns and can handle the bulk of their questions.Independent report
|
| Workflow evidenceMid-market Illustrative scenario A growing support team needs separate queues and connected order and account systems. What to verify: Validate routing, permissions, integration ownership, and handling of each team's policies in the intended configuration. | Not established Illustrative buying scenario: a growing retailer wants email and chat support connected to an existing help desk. Evaluate the exact connectors, workflow ownership and conversation volume. Employee count alone does not establish suitability. No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceEnterprise Illustrative scenario A multi-brand support organization needs controlled access across regional teams. What to verify: Validate data boundaries, audit records, escalation ownership, and the specific deployment requirements. A vendor's enterprise positioning is not proof of these controls. | Vendor-documented Illustrative buying scenario: a multi-brand support team needs shared knowledge with brand-specific policies and handoff routes. Request a demonstration of those boundaries. Enterprise positioning is documented; successful performance for that configuration is not established here. 1 cited claim for enterprise on AdaAda’s demo page explicitly targets enterprise customer-experience teams and proposes a tailored demonstration and implementation plan.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceRetail and e-commerce | Vendor-documented Ada's own retail and ecommerce page is the only source placing the product here. It describes returns workflows against connected commerce systems; no independent report of a retail deployment was found. 1 cited claim for retail and e-commerce on AdaAda describes returns workflows that check order eligibility, offer permitted options and create a return label through connected systems.Vendor-reported
| External report The independent evidence is Shopify App Store reviews written by merchants running the product. That is first-hand and unpaid, and it is also self-selected: reviewers are the merchants who chose to write. 3 cited claims for retail and e-commerce on LyroA Shopify merchant using the app for six months reported an AI resolution rate of around 90%.Independent report
A Shopify merchant wrote that Lyro has learned their product range, delivery options and returns and can handle the bulk of their questions.Independent report
A Shopify merchant described the agent as able to answer repetitive questions automatically and escalate questions when needed.Independent report
|
| Industry evidenceFinancial services | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceTelecommunications | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceTravel and hospitality | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceHealthcare | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidencePublic sector and education | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Industry evidenceLogistics and delivery | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Channels | ||
| Web and in-app chat | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for web and in-app chat on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Vendor-documented A hosted agent added to a website via the Tidio widget; the vendor states it can be added in a few clicks without technical knowledge. 1 cited claim for web and in-app chat on LyroA hosted agent added to a website via the Tidio widget; the vendor states it can be added in a few clicks without technical knowledge.Vendor-reported
|
| Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for email on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | |
| Voice and phone | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for voice and phone on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| SMS | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | |
| Social messaging | Vendor-documented Chat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration. 1 cited claim for social messaging on AdaChat, voice, email and social messaging are documented. Voice and social connections use supported external platforms; confirm the intended channel integration.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Help desks | ||
| Zendesk | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for zendesk on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Vendor-documented Tidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution. 1 cited claim for zendesk on LyroTidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution.Vendor-reported
|
| Salesforce | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for salesforce on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Vendor-documented Tidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution. 1 cited claim for salesforce on LyroTidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution.Vendor-reported
|
| ServiceNow | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for servicenow on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Freshdesk | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for freshdesk on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Intercom | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Tidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution. 1 cited claim for intercom on LyroTidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution.Vendor-reported
|
| HubSpot | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Kustomer | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Gorgias | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Gladly | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Help Scout | Vendor-documented The integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support. 1 cited claim for help scout on AdaThe integrations directory includes Zendesk, Salesforce, ServiceNow, Freshworks, Genesys and Help Scout. Check each entry for knowledge, messaging, email or voice support.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Front | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Microsoft Dynamics 365 | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
Change history
Open the changelogEvery change to this record is in the public changelog, with what it changed and why.
· Structure
Channels and help desks become evidence rows, and records gain bylines
Ada: 9 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · EmailNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Channel · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · ServiceNowNot established→Vendor-documented
- Help desk · FreshdeskNot established→Vendor-documented
- and 1 more
Lyro: 4 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · IntercomNot established→Vendor-documented
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Ada: Added to the catalog with 24 claims and 9 rows with evidence.
Lyro: Added to the catalog with 27 claims and 5 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
Ada: Added editorial product positioning with its scope, rationale, and vendor source. Source
Ada: Rechecked current documentation; replaced merchant-review extrapolations and unsupported fit verdict inputs with scoped capabilities, named vendor examples and clearly labelled illustrative scenarios. Source
Lyro: Added the star distribution behind the Shopify App Store rating and stated what the rating covers, so it is not read as a measurement of Lyro itself. Source