Comparison
Lyro vs Zendesk AI Agents
Compare documented workflows and implementation requirements using attributed public sources. Facts last checked , the earlier of the two records. Machine-readable record.
Fact-checked by Gosia Madej
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
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
Zendesk AI Agents
Vendor-hosted service within Zendesk Support and Suite. Feature access and advanced integrations vary by package.Vendor-reported
- Source
- Zendesk plans and AI agent availability
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-deployment
Actions in backend systems
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
Zendesk AI Agents
Zendesk documents API calls for live order lookups, with a different implementation path for AI Agents Advanced. Confirm required write actions and permissions separately.Vendor-reported
- Source
- How can I link my AI agent with my customer orders? (Zendesk help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-cmp-actions
Human 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
Zendesk AI Agents
Escalates to human teams with context according to Zendesk. Confirm queue routing, contact details, and reply-channel behavior in the intended setup.Vendor-reported
- Source
- Zendesk AI Agents product overview
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
zendesk-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
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.
What this agent was judged by
The independent evidence behind these states comes mainly from practitioner forums and buyer reviews.States rest on 1 independent source across practitioner forums and buyer reviews. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
| Attribute | Lyro | Zendesk AI Agents |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | 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
| Vendor-hosted service within Zendesk Support and Suite. Feature access and advanced integrations vary by package.Vendor-reported
|
| Channels | Tidio documents Lyro answering on the website chat widget by default, and optionally on Facebook Messenger, Instagram and WhatsApp once those are integrated with Tidio, and on incoming email tickets from connected mailboxes.Vendor-reported
| Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
|
| Languages | Tidio lists 48 supported languages for Lyro, says it detects the customer's language and replies in it natively rather than translating through English, and lets a business restrict Lyro to a chosen subset with a default fallback language.Vendor-reported
| Zendesk advertises support for 80 languages. Confirm the required channel separately; the voice announcement describes an early access rollout rather than identical availability everywhere.Vendor-reported
|
| Help desk and CRM integrations | Tidio states Lyro can connect with Zendesk, Intercom, Salesforce and more than 20 platforms and can run alongside an existing support solution.Vendor-reported
| Native Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately.Vendor-reported
|
| Knowledge sources | Tidio states Lyro automatically scrapes a business's support content and uses it as its knowledge base.Vendor-reported
| Zendesk help centres and external content brought in through crawlers or knowledge connectors. External content reflects its most recent sync.Vendor-reported
|
| Actions in backend systems | Tidio describes Smart Actions covering order updates, lead qualification and product recommendations as the actions Lyro performs beyond answering.Vendor-reported
| Zendesk documents API calls for live order lookups, with a different implementation path for AI Agents Advanced. Confirm required write actions and permissions separately.Vendor-reported
|
| Human handoff | 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
| Escalates to human teams with context according to Zendesk. Confirm queue routing, contact details, and reply-channel behavior in the intended setup.Vendor-reported
|
| Target customer size | 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
| Support and Suite plans span different service needs, with enterprise options available. Company size is not a tested suitability criterion.Vendor-reported
|
| Vendor-reported performance claims | 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
| Zendesk's Babbel story reports more than 50% AI automation. This is a vendor-published customer result, not our benchmark or an expected rate for another business.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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Illustrative scenario: a subscriber asks when renewal is due. Connect the authenticated account to the billing record and limit allowed changes. Babbel provides a concrete vendor-published example; a disputed charge would require different rules and human review. 1 cited claim for billing on Zendesk AI AgentsZendesk's Babbel case study describes subscription-status answers and self-service subscription management through Babbel's backend APIs. It does not establish general invoice, refund, or charge-dispute performance.Vendor-reported
|
| 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. | External report Two merchant reviews describe Lyro answering order and delivery-status questions; neither says how the store connected its order data. A 2024 review reporting that order tracking did not work is listed under weaknesses rather than here, because it does not make clear whether the tracking it meant was Lyro's. 3 cited claims for orders on LyroTidio states Lyro can automate order updates and lead qualification through a feature it calls Smart Actions.Vendor-reported
A UK merchant two years on the app wrote that, with Actions, customers can check the delivery status of their orders through Lyro.Independent report
A US Shopify merchant wrote that Lyro handles the bulk of repetitive questions about shipping and orders, keeping their support inbox cleaner.Independent report
| Vendor-documented Illustrative scenario: a shopper asks whether an order has shipped. The workflow needs an authorised order lookup and a response for missing or stale tracking data. Integration work is a prerequisite, not evidence that Zendesk is a poor fit for orders. 1 cited claim for orders on Zendesk AI AgentsZendesk documents an order-status use case and a separate integration path using API calls to retrieve order data. Implementation differs for AI Agents Advanced.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 No independent report of Lyro handling a return or refund was found. The vendor's own handoff examples also show refund and cancellation requests escalated to a human, so how much of a refund flow Lyro completes depends on how the merchant configures it. 1 cited claim for returns on LyroTidio documents Procedures, step-by-step workflows Lyro follows for a specific situation, naming refund requests as the example; a step can call the merchant's systems through Actions or create a ticket for the team.Vendor-reported
| Vendor-documented Illustrative scenario: a customer wants to return an item outside the normal window. Connect the order record, encode the policy, and route exceptions to the appropriate person. Confirm any refund action and duplicate-request handling in the chosen package. 1 cited claim for returns on Zendesk AI AgentsZendesk lists returns and refund requests as topics that can trigger a configured procedure, dialogue, or reply. Defining the topic alone does not implement a return or issue a refund.Vendor-reported
|
| 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. | 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
| Vendor-documented Illustrative scenario: a customer asks about a feature available only on one plan. Use current plan-specific content and verify that the answer includes the relevant restriction. The email reports in the limitations section are reasons to check response length and context handling, not proof that this entire use case fails. 1 cited claim for product questions on Zendesk AI AgentsZendesk documents generated answers from connected help centres and external knowledge sources, with article permissions applied to restricted content.Vendor-reported
|
| 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Illustrative scenario: a customer cannot sign in. A reset guide can be answered from documentation; changing an email address or unlocking an account needs identity checks and an authorised backend action. Evaluate those as separate tasks. 1 cited claim for account issues on Zendesk AI AgentsZendesk's industry guidance lists password resets and subscription updates as AI-agent use cases. It does not provide evidence that every identity or account-recovery flow is preconfigured.Vendor-reported
|
| 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Illustrative scenario: a customer disputes a repeated failed delivery. Check that the complaint becomes a ticket for the correct team, with context and a clear next step. Confirm the required intelligent-triage entitlement and triggers rather than assuming the AI agent enables them automatically. 1 cited claim for complaints on Zendesk AI AgentsZendesk documents platform triggers that route negative-sentiment tickets to a selected group and set priority. This supports complaint routing; it does not demonstrate autonomous complaint resolution.Vendor-reported
|
| 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. | 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
| External report Illustrative scenario: a customer asks for a human after troubleshooting. Verify contact capture, transcript transfer, destination queue, and the ability to reply on the intended channel. The cited community workaround shows one implementation path, not a general handoff success rate. 2 cited claims for human handoff on Zendesk AI AgentsZendesk states that its AI agents can escalate to human teams with conversation context.Vendor-reported
Kārlis Stenders describes collecting an issue description conversationally so it appears in the transcript during an Advanced AI Agent messaging handoff. The same post reports form limitations and corrects a custom workaround; it does not quantify reliability.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. | 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
| Vendor-documented Illustrative scenario: a small team uses an existing Zendesk inbox for FAQs and human escalation. Assess setup ownership, expected usage, and required features. Plan availability is not proof that the package is affordable or appropriate for every small business. 1 cited claim for small businesses on Zendesk AI AgentsZendesk includes AI-agent access in Support and Suite plans; advanced features and add-ons depend on the selected package.Vendor-reported
|
| 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 No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Illustrative scenario: a growing support team needs one process across email and messaging. Confirm whether knowledge, routing, and actions behave consistently on both channels. Company size alone does not establish this operational fit. 1 cited claim for mid-market on Zendesk AI AgentsZendesk describes Suite as a multi-channel service package with ticketing, messaging, help-centre content, and AI agents.Vendor-reported
|
| 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Illustrative scenario: several business units require separate permissions and approval paths. Confirm how those controls apply to the selected AI agent, connected systems, and data. Validate operational boundaries before expanding to sensitive workflows. 1 cited claim for enterprise on Zendesk AI AgentsZendesk lists enterprise options with approval workflows, sandbox access, and custom roles. These are package capabilities, not a guarantee that every AI workflow meets enterprise requirements.Vendor-reported
|
| Industry evidenceRetail and e-commerce | 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| 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 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 Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for web and in-app chat on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
|
| External report Tidio documents Lyro answering on the website chat widget by default, and optionally on Facebook Messenger, Instagram and WhatsApp once those are integrated with Tidio, and on incoming email tickets from connected mailboxes. 2 cited claims for email on LyroTidio documents Lyro answering on the website chat widget by default, and optionally on Facebook Messenger, Instagram and WhatsApp once those are integrated with Tidio, and on incoming email tickets from connected mailboxes.Vendor-reported
A German merchant wrote that Lyro answers their emails, social media messages and website live chats.Independent report
| Vendor-documented Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for email on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
| |
| 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. | Vendor-documented Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for voice and phone on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
|
| 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. |
| Vendor-documented Tidio documents Lyro answering on the website chat widget by default, and optionally on Facebook Messenger, Instagram and WhatsApp once those are integrated with Tidio, and on incoming email tickets from connected mailboxes. 1 cited claim for whatsapp on LyroTidio documents Lyro answering on the website chat widget by default, and optionally on Facebook Messenger, Instagram and WhatsApp once those are integrated with Tidio, and on incoming email tickets from connected mailboxes.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 | External report Tidio documents Lyro answering on the website chat widget by default, and optionally on Facebook Messenger, Instagram and WhatsApp once those are integrated with Tidio, and on incoming email tickets from connected mailboxes. 2 cited claims for social messaging on LyroTidio documents Lyro answering on the website chat widget by default, and optionally on Facebook Messenger, Instagram and WhatsApp once those are integrated with Tidio, and on incoming email tickets from connected mailboxes.Vendor-reported
A German merchant wrote that Lyro answers their emails, social media messages and website live chats.Independent report
| Vendor-documented Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent. 1 cited claim for social messaging on Zendesk AI AgentsZendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
|
| Help desks | ||
| Zendesk | 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
| Vendor-documented Native Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately. 1 cited claim for zendesk on Zendesk AI AgentsNative Zendesk deployment is the scope of this profile. Zendesk also markets Forethought agents for other service platforms; confirm those connectors and capabilities separately.Vendor-reported
|
| Salesforce | 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| 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 | 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. |
| Intercom | 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| 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 | 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.
· Evidence
Lyro: languages, channels, refund procedures and new merchant reports
Lyro: 8 claims added · 1 claim edited · 1 claim removed · 5 evidence states moved
- OrdersVendor-documented→External report
- ReturnsNot established→Vendor-documented
- Channel · EmailNot established→External report
- Channel · WhatsAppNot established→Vendor-documented
- Channel · Social messagingNot established→External report
· Structure
Channels and help desks become evidence rows, and records gain bylines
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
Zendesk AI Agents: 5 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
· Catalog
Launch: 22 AI customer service agents and 532 claims, every one sourced and dated
Lyro: Added to the catalog with 27 claims and 5 rows with evidence.
Zendesk AI Agents: Added to the catalog with 28 claims and 10 rows with evidence.
Recorded before launch
Notes the profile carried when it went live, from research before launch.
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
Zendesk AI Agents: Added editorial product positioning with its scope, rationale, and vendor source. Source
Zendesk AI Agents: Rechecked product documentation, a named customer example, and firsthand community reports. Removed launch coverage as independent success evidence, replaced blanket fit judgments with conditional scenarios, and distinguished setup prerequisites from failures. Source