Salesforce MVP Hall of Fame · Certified Partner since 2010
Service Cloud. Cases, knowledge, and the channel your customer uses.
Service Cloud is the desk for cases, knowledge, and the channel the customer already uses. We implement it around that desk. The first week is in the org, reading what already exists.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
In the org
What this cloud is actually for.
Service Cloud is the desk your support team works from: cases, knowledge, and the channel the customer already used. We implement it so a case reaches the right queue with the history attached, and we will tell you when a knowledge article and a routing rule would fix more than a bot.
Who this is for
The desks that live here.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Architecture
Where this cloud sits in your agent architecture.
The case desk is the record. The channel, the runtime, and the write are separate jobs.
Questions
What we actually say.
- Do you put a bot in front of every case?
- Only when the bot can hand off. A wall is not service. We will say when a knowledge article and a queue are enough.
- Is this the same as Agentforce for service?
- No. Service Cloud is the desk for cases. Agentforce can act on those cases if the agent belongs in Salesforce, including from Slack. Work across other tools or a warehouse is a custom stack.
- Will you publish a deflection percentage?
- Not without a source in this org. We measure whether the case reached the right queue.
The brief
Send the situation.
Name the cloud. Name the week.