Comparison
Fin 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.
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
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
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
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
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
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
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 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 | Fin | Zendesk AI Agents |
|---|---|---|
| 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
| Vendor-hosted service within Zendesk Support and Suite. Feature access and advanced integrations vary by package.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
| Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.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
| 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 | Intercom, Zendesk, Salesforce, Freshdesk, and HubSpot are documented deployment options. Confirm the connector supports the required channel and actions.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 | Help articles, internal support content, PDFs, and webpages; audience settings control which content Fin can use for a customer.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 | 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
| 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 | 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
| 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 | Fin has an explicit enterprise offering. Assess required integrations and operating controls instead of using company size as a proxy for fit.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 | 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
| 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. | 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
| 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. | 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 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 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
| 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. | 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
| 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. | 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
| 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. | 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
| 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. | 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 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. | 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
| 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. | 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
| 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. | 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
| 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 | 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
| 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 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 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
|
| 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
| 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 | 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
| 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 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 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 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
| 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 | 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| 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
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
Fin: Added to the catalog with 28 claims and 11 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.
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
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