Comparison
Agentforce vs Crescendo
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
Crescendo
Crescendo is delivered as a vendor-hosted managed service rather than self-hosted software, and the vendor claims 30 days to go live with back-end integrations in under 30 minutes.Vendor-reported
- Source
- Crescendo — homepage
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
crescendo-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
Crescendo
Documented assistant actions are lead qualification, meeting scheduling via Calendly and HubSpot Meetings, custom form completion and data collection, resource/link presentation and customer tagging; the vendor separately claims status lookups, account updates and order changes, and describes a "Safe Action Framework that determines what AI can do autonomously and what requires human approval".Vendor-reported
- Source
- Introduction to AI Assistants — Crescendo Docs
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
crescendo-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
Crescendo
Unlike software-only vendors, Crescendo can supply the humans on the receiving end of an escalation: it acquired outsourcing provider PartnerHero in October 2024, PartnerHero's site states "PartnerHero is now powered by Crescendo" and offers "Exceptional outsourced teams ... Fully managed end-to-end service", so handoff can mean transfer to Crescendo-managed specialists rather than only to the buyer's own agents.Vendor-reported
- Source
- PartnerHero — homepage
- Checked
- History
- First published
- Correct this
- Request a correction with a public source. Claim ID
crescendo-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 analysts and trade press.States rest on 1 independent source across analysts and trade press. This is not the same yardstick for every agent, and that asymmetry is a known limitation.
| Attribute | Agentforce | Crescendo |
|---|---|---|
| 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
| Crescendo is delivered as a vendor-hosted managed service rather than self-hosted software, and the vendor claims 30 days to go live with back-end integrations in under 30 minutes.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
| Crescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented.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
| Unknown |
| 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
| Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.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
| Crescendo documents ingestion of uploaded PDF, DOCX, Markdown and text files plus external sources including Zendesk, Freshdesk, Confluence, SharePoint, Notion, Genesys, Front and web discovery.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
| Documented assistant actions are lead qualification, meeting scheduling via Calendly and HubSpot Meetings, custom form completion and data collection, resource/link presentation and customer tagging; the vendor separately claims status lookups, account updates and order changes, and describes a "Safe Action Framework that determines what AI can do autonomously and what requires human approval".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
| Unlike software-only vendors, Crescendo can supply the humans on the receiving end of an escalation: it acquired outsourcing provider PartnerHero in October 2024, PartnerHero's site states "PartnerHero is now powered by Crescendo" and offers "Exceptional outsourced teams ... Fully managed end-to-end service", so handoff can mean transfer to Crescendo-managed specialists rather than only to the buyer's own agents.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
| Crescendo positions itself for enterprise and mid-market CX operations, and third-party research describes it as a "fully-managed AI-native contact center that combines software licensing with human-in-the-loop services" serving 200+ customers with over $50M ARR after the PartnerHero acquisition.Independent report
|
| 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
| Crescendo publishes that "approximately 70% of customer issues are resolved from day one", that its customer dissatisfaction rate "has fallen from 5.8% to 0.68% in under a year", and that AI-handled volume on the platform has grown 600% with AI customers up 200%.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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceOrders Illustrative scenario My order has not arrived. Where is it? What to verify: Retrieve the correct order and current carrier status. Distinguish a real tracking update from an estimate; do not invent a delivery date. | Vendor-documented Illustrative scenario, not a test: 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 No independent confirmation of order-modification actions was found; the developer documentation lists lead qualification, meeting scheduling, form completion and tagging as actions, without order operations. 1 cited claim for orders on CrescendoCrescendo states its Concierge agent performs "status lookups, account updates, order changes" and closes issues without involving a human.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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceProduct questions Illustrative scenario Does this adapter work with my exact laptop model? What to verify: Use a current, approved compatibility source. Ask for the model when missing and distinguish documented compatibility from an assumption. | Vendor-documented Illustrative scenario, not a test: 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
| External report Crescendo's Shopify assistant is described as a "dual-purpose AI assistant" that "guides customers to products, answers questions, and helps them complete purchases", with chat and voice support. 2 cited claims for product questions on CrescendoCrescendo's Shopify assistant is described as a "dual-purpose AI assistant" that "guides customers to products, answers questions, and helps them complete purchases", with chat and voice support.Vendor-reported
CX Today reported that Crescendo launched an AI shopping assistant on the Shopify App Store covering "product discovery, personalized recommendations, and customer support", unveiled at NRF 2026.Independent report
|
| Workflow evidenceAccount issues Illustrative scenario I lost access to my email. Change the address on my account. What to verify: Follow the approved identity-recovery process before accessing or changing account data. Escalate when identity cannot be verified. | Vendor-documented Illustrative scenario, not a test: 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceComplaints Illustrative scenario I have contacted you three times and the problem is still unresolved. What to verify: Recognize the repeat complaint, retain relevant history, and route it to the right team. Do not promise compensation outside the policy. | Vendor-documented Illustrative scenario, not a test: a customer 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
| Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceHuman handoff Illustrative scenario Please connect me to a person who can approve this exception. What to verify: Transfer to an available team with the conversation and relevant records. Outside working hours, explain the actual follow-up path rather than promise immediate contact. | Vendor-documented Illustrative scenario, not a test: a customer 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 Handoff here is not only a software escalation: the humans on the receiving end can be supplied by Crescendo itself (via the acquired PartnerHero workforce) or by partner BPOs, so a buyer may be purchasing the escalation tier as well as the AI. The independent article's description of the handoff is sourced to partner and vendor executives quoted by the reporter. 2 cited claims for human handoff on CrescendoCrescendo states that when Concierge escalates it "passes along the entire conversation — customer history, issue context, recommended next action" so the specialist "starts at the answer".Vendor-reported
CX Today reported on the Alorica–Crescendo partnership that AI "handles the heavy lifting upfront" and that "when escalation is needed, that full context is passed seamlessly to a human agent", with Alorica's 100,000+ employees across 16 countries available to augment Crescendo deployments.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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| 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. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Workflow evidenceEnterprise Illustrative scenario A multi-brand support organization needs controlled access across regional teams. What to verify: Validate data boundaries, audit records, escalation ownership, and the specific deployment requirements. A vendor's enterprise positioning is not proof of these controls. | Vendor-documented Illustrative buying scenario: a 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
| External report Crescendo's August 2026 platform launch names enterprise and mid-market customers including Grindr, Headspace, Lovepop, Nothing Bundt Cakes, SQUIRE and Good Eggs Grocery. 2 cited claims for enterprise on CrescendoCrescendo's August 2026 platform launch names enterprise and mid-market customers including Grindr, Headspace, Lovepop, Nothing Bundt Cakes, SQUIRE and Good Eggs Grocery.Vendor-reported
CX Today reported a partnership placing Crescendo's AI into "live enterprise service channels" operated by Alorica, a BPO with more than 100,000 employees across 16 countries.Independent report
|
| 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 Crescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented. 1 cited claim for web and in-app chat on CrescendoCrescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented.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 Crescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented. 1 cited claim for email on CrescendoCrescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented.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 Crescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented. 1 cited claim for voice and phone on CrescendoCrescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented.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. | Vendor-documented Crescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented. 1 cited claim for sms on CrescendoCrescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented.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 Crescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented. 1 cited claim for whatsapp on CrescendoCrescendo states its Concierge agent handles "Voice, chat, email, SMS, WhatsApp" from a single AI layer, with a website chat widget, mobile apps and API access also documented.Vendor-reported
| |
| Social messaging | 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 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 Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for zendesk on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.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
| Vendor-documented Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for salesforce on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.Vendor-reported
|
| ServiceNow | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. |
| Freshdesk | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for freshdesk on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.Vendor-reported
|
| Intercom | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for intercom on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.Vendor-reported
|
| HubSpot | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for hubspot on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.Vendor-reported
|
| Kustomer | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for kustomer on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.Vendor-reported
|
| Gorgias | Not established No supporting source is recorded here. Validate it with the vendor; absence of evidence does not establish a missing capability. | Vendor-documented Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for gorgias on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.Vendor-reported
|
| 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. | Vendor-documented Crescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front. 1 cited claim for front on CrescendoCrescendo's documentation lists ticket creation into Zendesk, Freshdesk, Freshservice, Freshchat, Kustomer, Gorgias, Intercom, Salesforce, HubSpot, Slack, email and Front.Vendor-reported
|
| 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
Crescendo: 13 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 · SMSNot established→Vendor-documented
- Channel · WhatsAppNot established→Vendor-documented
- Help desk · ZendeskNot established→Vendor-documented
- Help desk · SalesforceNot established→Vendor-documented
- Help desk · FreshdeskNot established→Vendor-documented
- and 5 more
· 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.
Crescendo: Added to the catalog with 24 claims and 4 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