Who this comparison is for
Agent Desk highlights
- Native case lifecycle, customer conversation, queues, skills, presence, capacity, routing, assignment, SLA, entitlements, approvals, and resolution
- Live ContextRefs, resolver providers, source-authorized service actions, linked internal work, problems/incidents, and customer-safe portal operations
- Knowledge, quality, workforce, reports, audit, retention, configuration governance, enterprise identity, and capability-based provider connections
Salesforce Service Cloud highlights
- Salesforce Service Cloud capabilities and operating model vary by product configuration, edition, and connected ecosystem
Capability matrix
| Capability | Agent Desk | Salesforce Service Cloud | Notes |
|---|---|---|---|
| Case intake, lifecycle & customer conversation | Native | varies by product/edition | Staff, portal, trusted-app, API, Bridge, event and provider intake normalize into Agent Desk cases and conversations. |
| Queues, skills, presence, capacity & routing | Native | varies by product/edition | Agent Desk owns queue eligibility, workload, assignment strategies, predictive routing, simulation and governed override. |
| Live business context & source actions | native + capability providers | varies by product/edition | ContextRefs, resolver providers and service-action governance keep source applications authoritative while agents work from one case. |
| Customer-safe portal operations | Native | varies by product/edition | Customer-scoped intake, overview, cases, messages, replies, actions, attachments, timeline, resolution, reopening and CSAT are canonical operations. |
| Problems, knowledge, quality, workforce & reporting | Native | varies by product/edition | Agent Desk includes incident/problem workspaces, knowledge lifecycle, QA, coaching, workforce planning/adherence and operational reports. |
| Integrations, governance & audit | capability-based | varies by product/edition | Handler/RCP, EventBus, Bridge v2, webhooks, provider capabilities, RBAC/resource authorization, retention, legal hold and audit are part of the operating model. |
Total cost of ownership
Agent Desk concentrates service operations in the desk while allowing communication, identity, context, AI, internal work, collaboration, files, automation, notifications, history, analytics, reporting, audit, and enterprise identity to be supplied through configured capability providers.
Assumptions
- The organization wants one governed service-operations system of record with explicit integration boundaries and source-system ownership.
Migration plan
From Salesforce Service Cloud · Inventory → field/lifecycle mapping → provider and queue configuration → pilot → controlled cutover
-
1
Export or map the Salesforce Service Cloud case, requester, conversation, field, queue, user, and service-level data required for the transition.
-
2
Configure Agent Desk case types, lifecycle, queues, roles, routing, SLA, requester identity, context, communication, and required provider capabilities.
-
3
Pilot representative queues and customer-safe workflows while validating authorization, conversation visibility, SLA clocks, routing, reporting, and integrations.
Security
- Core permission enforcement, Agent Desk role and resource authorization, scoped customer ownership, trusted inter-app provenance, secure files, audit, retention, PII policy, and legal hold are built into the service workflow.
Evidence & sources
About Agent Desk
Agent Desk is a complete service-operations workspace for customer and internal support. Requests can enter from staff, customer portals, trusted applications, APIs, governed workspace calls, Bridge v2 connections, events, and configured inbound providers.
Agents work from permission-aware queues with skills, presence, capacity, assignment, priority, SLA, requester identity, live business context, customer conversation, internal notes, attachments, approvals, related work, source-authorized actions, and a complete case timeline.
Supervisors and operations teams manage queues, routing, service levels, problems and incidents, knowledge, quality, workforce, reports, integrations, automations, retention, audit, and enterprise identity from the same application. Connected systems integrate through capability-based provider contracts so each source application can remain authoritative for its own business data while Agent Desk owns service operations.