Comparison
Fin 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
Fin
Vendor-hosted service used with Intercom or a supported existing help desk. Configuration and integration work depend on the task.Vendor-reported
- Source
- Fin pricing and deployment options
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
fin-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
Fin
Configured Procedures can combine conditions, code, and data connectors or MCP access to external systems. Actions execute sequentially and require the appropriate integration permissions.Vendor-reported
- Source
- Fin Procedures explained (Intercom Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
fin-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
Fin
Escalation rules and guidance control handoff; workflows set the human destination. A bot-only workflow without a human routing target does not offer escalation.Vendor-reported
- Source
- Manage Fin AI Agent's escalation guidance and rules (Intercom Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
fin-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 | Fin | Lyro |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Vendor-hosted service used with Intercom or a supported existing help desk. Configuration and integration work depend on the task.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 | The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.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 | Intercom lists supported languages and regional variants, including Polish, French, Japanese, and Arabic. Enable the required workspace languages; cross-language knowledge fallback requires real-time translation.Vendor-reported
| Unknown |
| Help desk and CRM integrations | Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.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 | Help articles, internal support content, PDFs, and webpages; audience settings control which content Fin can use for a customer.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 | Configured Procedures can combine conditions, code, and data connectors or MCP access to external systems. Actions execute sequentially and require the appropriate integration permissions.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 | Escalation rules and guidance control handoff; workflows set the human destination. A bot-only workflow without a human routing target does not offer escalation.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 | Fin has an explicit enterprise offering. Assess required integrations and operating controls instead of using company size as a proxy for fit.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 | Fin's homepage reports a 76% average resolution rate across 12,000+ customers. This is a vendor aggregate, not our result or a forecast for a particular workload.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: a customer asks for an invoice copy. Give the workflow authenticated access to the correct account and a permitted retrieval action. A disputed charge needs separate policy and escalation rules; the source does not demonstrate reliable dispute adjudication. 1 cited claim for billing on FinFin advertises invoice requests and subscription management through connected systems on its enterprise page. This is a configured workflow capability, not access to a buyer's billing account by default.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: a shopper asks where an order is. The reply needs a verified customer-to-order match and current delivery data. Check that lookup in the intended channel; shopping features in web Messenger do not establish equivalent functionality elsewhere. 1 cited claim for orders on FinFin for Ecommerce documents a native Shopify connection for catalogue and order data, plus APIs and draft Procedures for post-purchase requests.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: a customer returns an eligible item. Configure the return window, exclusions, permitted refund action, and human review for exceptions. Listing a returns capability does not establish that a particular store policy is implemented correctly. 1 cited claim for returns on FinFin for Ecommerce lists returns, refunds, and order changes as supported conversational workflows. These rely on the connected store and configured post-purchase 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 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: a customer asks whether their subscription includes an export feature. Supply current plan-specific documentation and check that Fin distinguishes plans rather than combining incompatible answers. Documentation establishes the answering mechanism, not an accuracy rate. 1 cited claim for product questions on FinFin builds answers from help articles, internal support content, PDFs, and webpages. Audience rules can limit which content applies to a customer.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: an authenticated customer changes an account detail. Restrict which fields the workflow may update and route failed identity checks to a human. A support article explaining a password reset is different from permission to change credentials. 1 cited claim for account issues on FinIntercom describes account troubleshooting and identity verification as Procedure use cases, with configurable system access and branching logic.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: a customer says repeated answers have not helped. Check that the configured guidance triggers handoff and preserves the issue history. Detecting frustration does not demonstrate that the complaint was resolved. 1 cited claim for complaints on FinFin documents escalation for explicit human requests, detected frustration, and repeated loops. Custom guidance can override default escalation behavior.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: a customer asks for a person after an unsuccessful answer. Verify the destination inbox, transcript transfer, and after-hours response. A handoff event alone does not show how quickly a human replies. 1 cited claim for human handoff on FinFin uses configured workflows to route escalations. Intercom states that no escalation offer is shown when no human routing target exists.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. | Vendor-documented Illustrative scenario: a small team starts with common support questions and one monitored human inbox. Compare expected use and ongoing content maintenance with available staff. Programme eligibility and a product trial do not prove affordability or suitability for every small business. 1 cited claim for small businesses on FinFin publishes an early-stage startup programme with eligibility requirements. This establishes an offer for some small teams, not an exclusion of other small businesses.Vendor-reported
| 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. | Vendor-documented Illustrative scenario: a growing team keeps its help desk and adds one authenticated order lookup. Confirm connector coverage, ownership of failed actions, and routing before expanding. Team size alone is not evidence of a successful deployment. 1 cited claim for mid-market on FinFin is sold with Intercom or for use with an existing help desk; the deployment options do not impose a single published company-size category.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 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 scenario: several brands need different knowledge access and approval rules. Evaluate those boundaries and operational reporting in the planned workspace structure. An enterprise offering does not establish that all data-residency, retention, or approval requirements are met. 1 cited claim for enterprise on FinFin markets an enterprise offering with workspace permission controls, activity logs, deployment services, and integrations with existing help desks.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 | Caveat documented Fin for Ecommerce is a documented product with a native Shopify connection, and the same vendor documentation states the ecommerce features are limited to the web Messenger. Read the capability and the channel limit together before assuming coverage of an email or social queue. 2 cited claims for retail and e-commerce on FinFin for Ecommerce documents a native Shopify connection for catalogue and order data, plus APIs and draft Procedures for post-purchase requests.Vendor-reported
Full ecommerce shopping features are documented for web Messenger. Mobile receives support-only responses; email, social, voice, and Slack are not currently supported for the ecommerce role. This limit does not describe every Fin service capability.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 The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for web and in-app chat on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.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 The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for email on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.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 | 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. |
| SMS | Vendor-documented The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for sms on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Vendor-documented The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for whatsapp on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.Vendor-reported
| 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 The FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment. 1 cited claim for social messaging on FinThe FAQ lists web and mobile Messenger, email, WhatsApp, SMS, Facebook, and Instagram. Confirm separate voice or other channel access and feature coverage for the intended deployment.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 Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for zendesk on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.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 Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for salesforce on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.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 | 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. |
| Freshdesk | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for freshdesk on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and 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. |
| Intercom | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for intercom on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.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 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 | Vendor-documented Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions. 1 cited claim for hubspot on FinIntercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and 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. |
| 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 | 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. |
| 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
Fin: 10 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · EmailNot established→Vendor-documented
- Channel · SMSNot established→Vendor-documented
- Channel · WhatsAppNot established→Vendor-documented
- Channel · Social messagingNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · FreshdeskNot established→Vendor-documented
- and 2 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
Fin: Added to the catalog with 28 claims and 11 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.
Fin: Added editorial product positioning with its scope, rationale, and vendor source. Source
Fin: Rechecked the profile against current product documentation. Replaced broad fit claims with scoped workflows and illustrative examples, corrected billing and Procedure limitations, and removed unsupported acquisition and anecdotal verdict claims. 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