Comparison
Agentforce 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
Agentforce
Service Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type.Vendor-reported
- Source
- Agentforce Service Agent (Salesforce Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
agentforce-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
Agentforce
Actions can use Salesforce workflows, code and external APIs. A refund is a configured sequence with eligibility checks and payment confirmation, not a universal action available on every installation.Vendor-reported
- Source
- Agentic integration patterns (Salesforce Architects)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
agentforce-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
Agentforce
Omni-Channel Flow routes complex or sensitive requests from the Service Agent to service representatives or another configured destination.Vendor-reported
- Source
- Agentforce Service Agent (Salesforce Help)
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
agentforce-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 | Agentforce | Zendesk AI Agents |
|---|---|---|
| Review basis | Source-based review | Source-based review |
| Deployment model | Service Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type.Vendor-reported
| Vendor-hosted service within Zendesk Support and Suite. Feature access and advanced integrations vary by package.Vendor-reported
|
| Channels | Salesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering.Vendor-reported
| Zendesk advertises web, mobile, social, email, and voice. Check channel-specific documentation and availability for the selected agent.Vendor-reported
|
| Languages | The current supported-language table includes English, French, German, Japanese, Polish and others, with some additional languages marked beta. Voice support differs; use the table for the chosen channel.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 | The reviewed deployment uses Salesforce service records and routing. External business systems can be connected through configured agent actions; this does not establish a turnkey connector for every other help desk.Editorial assessment
| 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 | Agentforce Data Library indexes knowledge articles, uploaded files or web sources. It requires Data 360 setup; the library must be assigned to the agent.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 | Actions can use Salesforce workflows, code and external APIs. A refund is a configured sequence with eligibility checks and payment confirmation, not a universal action available on every installation.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 | Omni-Channel Flow routes complex or sensitive requests from the Service Agent to service representatives or another configured destination.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 | Salesforce markets Agentforce for enterprise-scale support. Our editorial assessment is that existing Salesforce data, administrator capacity and integration needs are more useful selection criteria than employee count.Editorial assessment
| 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 | Salesforce’s customer story reports about 76% of queries resolved without a human on its own Help site. This vendor-operated deployment is not a controlled comparison, and its resolution definition and workload should not be assumed equivalent to other vendors’ figures.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, not a test: explain a disputed charge from an authenticated customer’s billing records. Confirm the licensed service offering, billing connection and approval path. The employee-facing Communications example cannot establish that the general Service Agent can resolve this independently. 1 cited claim for billing on AgentforceSalesforce describes billing-detail and dispute actions for Agentforce for Communications. That page labels its prebuilt subagent employee-facing and includes an availability disclaimer; it does not establish an included customer-facing Service Agent billing flow.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, not a test: look up a shipment by order number and return its status. Prove customer verification and order access first; separately test cancellations, missing parcels and stale tracking. The partner demonstration listed above covers lookup, not all order support. 1 cited claim for orders on AgentforceSalesforce’s Service training gives order lookup and cancellation as configurable workflow examples, with a lost-package request routed to a person.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, not a test: request a refund within the return window. The payment connection must return confirmation before the case is closed, and retrying a request must not issue a second refund. Confirm which actions your team must implement. 1 cited claim for returns on AgentforceSalesforce’s architecture guide illustrates a refund chain: retrieve order details, check eligibility, call the payment gateway and update the case after confirmation. It is an implementation pattern, not a measured deployment result.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, not a test: explain a warranty’s coverage from the approved article. Verify that the answer matches the customer’s model and region and asks for clarification when those details are missing. A knowledge source does not guarantee a correct answer. 1 cited claim for product questions on AgentforceSalesforce documents a knowledge-answering action for questions such as return policies and warranty information.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, not a test: help a locked-out customer recover access. Verify identity using the intended authentication flow before exposing account data or initiating a reset. Demonstrate the actual identity-provider integration, not just a helpful-sounding reply. 1 cited claim for account issues on AgentforceSalesforce’s Service training includes customer-detail retrieval and password-reset examples, with verification instructions and additional configuration for private actions.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, not a test: a customer objects to repeated unresolved charges. Route the case to a person with context and a clear next step. This source documents escalation, not reliable emotion detection or successful resolution of complaints. 1 cited claim for complaints on AgentforceSalesforce documents escalation of complex or sensitive Service Agent requests through Omni-Channel Flow.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, not a test: a customer asks to speak to a person. Confirm the destination queue is staffed, the conversation reaches it and the customer receives an off-hours path when nobody is available. 1 cited claim for human handoff on AgentforceService Agents use configured Omni-Channel Flow routing to transfer support requests to service representatives or other destinations.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. | Not established Illustrative buying scenario: a small team already using Salesforce wants to answer common support questions. Assess the required setup, data access and ongoing ownership. Neither team size nor an analyst’s view of implementation skills establishes that the product will fail for this team. 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 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 Illustrative buying scenario: a company with Salesforce support records wants order lookup connected to a separate fulfilment system. Evaluate integration effort and administrator capacity. This is a configuration and operating-model decision, not a verdict based on headcount. 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. | Vendor-documented Illustrative buying scenario: a global support organisation needs customer-specific access across multiple business systems. Request evidence for permissions, routing and language coverage in that configuration. Enterprise positioning alone does not establish successful deployment. 1 cited claim for enterprise on AgentforceSalesforce positions Agentforce for enterprise-scale support and documents building agents with its platform tools and integrations.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 | 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 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 Salesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering. 1 cited claim for web and in-app chat on AgentforceSalesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering.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
|
| 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 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 | Vendor-documented Salesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering. 1 cited claim for voice and phone on AgentforceSalesforce describes messaging, web, mobile and voice service experiences. Channel availability and setup should be checked for the specific Service Agent offering.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 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. |
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | |
| Social messaging | 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 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 | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | 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 Service Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type. 1 cited claim for salesforce on AgentforceService Agents are configured in Salesforce and connected to customer channels, with a default service template or specialised templates. Confirm the required editions for the chosen agent type.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 | 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. |
| 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.
· Structure
Channels and help desks become evidence rows, and records gain bylines
Agentforce: 3 evidence states moved
- Channel · Web and in-app chatNot established→Vendor-documented
- Channel · Voice and phoneNot established→Vendor-documented
- Help desk · SalesforceNot 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
Agentforce: Added to the catalog with 24 claims and 8 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.
Agentforce: Added editorial product positioning with its scope, rationale, and vendor source. Source
Agentforce: Rechecked product-specific documentation; removed promotional and unrelated reports from fit evidence, corrected outdated language coverage, and added scoped workflow examples and implementation conditions. 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