Salesforce Service Cloud, architected for the volume you actually run.

Yes — they are the same product under two names. During the 2025–26 Agentforce rebrand, Salesforce began marketing Service Cloud as Agentforce Service, alongside similar renames across its other clouds. Your licences, API names, object names and existing metadata are unaffected, and Salesforce documentation and the product UI still say "Service Cloud" in most places. In practice you will see both names for some time, so it is worth using both when searching for documentation or partners.

A focused implementation covering case management, email-to-case, basic automation, entitlements and reporting typically takes 8–12 weeks. A more comprehensive engagement that adds omni-channel routing, CTI integration, a Knowledge Base build, a customer self-service portal, back-office integrations and AI configuration typically runs 16–24 weeks. The real drivers are the number of channels, integration complexity, data migration volume, and whether you are starting clean or redesigning an existing org. We set a milestone plan before any build begins.

Configuration covers the case data model, record types, queues, assignment and escalation rules, entitlement processes and milestones, Knowledge structure, reports and dashboards, and most automation through Flow — which is the large majority of what a support operation needs. Custom development starts when the agent experience needs an interface Salesforce does not ship (a Lightning Web Component), when logic must run at a volume or complexity Flow cannot handle reliably (Apex), or when an integration needs real error handling and retry rather than a scheduled file. We argue that boundary case by case and put it in writing, because custom code is the most expensive part of a Salesforce org to own over time.

Usually yes, and this is the most common engagement we run. The pattern is consistent: the org is technically live, agents have built informal workarounds beside it, SLA data is not trusted, and leadership cannot pull a report they believe. We run a structured audit of the case model, routing logic, automation, entitlements, integrations and adoption, then rebuild the parts that are failing inside the existing org. The exception is a case data model that cannot support what the business now needs — where that is true we say so and scope the rebuild honestly, rather than automating around a foundation that will not hold.

If you route work through Omni-Channel, yes. Salesforce retired Standard Omni-Channel with the Summer '26 release and orgs that were not migrated lose Omni-Channel work assignment — agents cannot log in to Omni-Channel and are not assigned work. Salesforce upgraded many orgs automatically, but an automatic upgrade is not the same as a validated one: routing configuration, capacity models and supervisor tooling all behave differently enough that they need testing in a sandbox against your own queues. Salesforce documents the retirement and the upgrade path in its Standard Omni-Channel Retirement notice. If you are unsure which version you are on, that is a five-minute check we can do in an audit.

Yes. We integrate Service Cloud with ERP systems such as NetSuite, SAP and Microsoft Dynamics, billing platforms including Stripe, Zuora and Chargebee, telephony and CTI tools including Genesys, Five9, Amazon Connect, Twilio and RingCentral, and product usage or analytics systems — so agents have full customer context without switching applications. We use MuleSoft, Workato, Celigo or native APIs depending on integration complexity, data volume and the middleware you already own. Integration architecture is designed during discovery, not retrofitted after the build.

Zendesk and similar help desks are purpose-built for ticketing and work well for straightforward support workflows — they are often faster to stand up and simpler to run. Service Cloud is native to the Salesforce platform, which means it shares a data model with Sales Cloud and everything else in your org. Where support performance is tied to retention, expansion or account health, that shared record is the deciding factor: the agent sees contract terms, product usage and renewal dates alongside the case. Service Cloud also handles complex entitlement structures, enterprise account hierarchies and multi-tier SLA management that a help desk generally does not. If none of those apply to you, a help desk may genuinely be the better buy.