Case management
Case types, classification, mandatory fields by type and a defined closure process.
Service Cloud
One case, one view, a handle time you can measure.
Service Cloud implemented around the case journey: intake from every channel, classification, routing, entitlements and milestones, escalation and measurement — with a knowledge base that serves agents and self-service alike.
Capability map
What's included, and in what order
Service Cloud — Capability Map
Case management
Case types, classification, mandatory fields by type and a defined closure process.
Omni-Channel routing
Assignment by skill, load and availability instead of manual pulls from a queue.
Entitlements & milestones
Response and resolution targets, breach tracking and automatic escalation.
Knowledge base
Article structure, ownership, review cycle and usage measurement.
Self-service
A portal or help center that reduces repeat contacts.
Measurement
Handle time, first-contact resolution, repeat contacts and satisfaction.
Background
What actually determines the outcome
A service desk is judged on speed and quality, but both depend on an early decision: how a case gets classified. Bad classification produces bad routing, and every metric downstream becomes unrecoverable.
A single customer view matters more than any automation. An agent forced to jump between three screens to understand what happened will extend handle time even if the process is flawless on paper.
A knowledge base isn't a side project. It's the precondition for effective self-service, and also the precondition for any future use of Agentforce.
What we do
Areas of work
Omni-Channel routing
Assignment by skill, load and availability instead of manual pulls from a queue.
Entitlements & milestones
Response and resolution targets, breach tracking and automatic escalation.
Knowledge base
Article structure, ownership, review cycle and usage measurement.
Self-service
A portal or help center that reduces repeat contacts.
Measurement
Handle time, first-contact resolution, repeat contacts and satisfaction.
Decision matrix
The decisions that determine the outcome
| Decision | Option A | Option B | What decides it |
|---|---|---|---|
| Routing model | Manual queue pulls | Skill-based Omni-Channel | Case volume and diversity of specialties |
| SLA structure | One uniform target | Targets per customer tier | Whether binding service agreements exist |
| Self-service | Public knowledge articles | Authenticated portal | Whether personal data is needed in a case |
| Channels | Email and phone | Multiple digital channels | Where customers actually reach out |
Routing model
- Option A
- Manual queue pulls
- Option B
- Skill-based Omni-Channel
- What decides it
- Case volume and diversity of specialties
SLA structure
- Option A
- One uniform target
- Option B
- Targets per customer tier
- What decides it
- Whether binding service agreements exist
Self-service
- Option A
- Public knowledge articles
- Option B
- Authenticated portal
- What decides it
- Whether personal data is needed in a case
Channels
- Option A
- Email and phone
- Option B
- Multiple digital channels
- What decides it
- Where customers actually reach out
How we work
Delivery steps
- 01
Map the case journey
Channels, types, volumes and failure points.
- 02
Data model
Case, customer, product, entitlement and history.
- 03
Routing & entitlements
Queues, skills, time targets and escalations.
- 04
Knowledge & self-service
Structure, ownership and update process.
- 05
Training
Playbooks for agents and team leads.
- 06
Measure & improve
Metric review and correcting inaccurate classification.
Keep exploring
Related services and guides
FAQ
Service Cloud — questions we hear often
What's the difference between a queue and Omni-Channel?
A queue requires the agent to pull a case manually, so less convenient cases get left behind. Omni-Channel pushes a case to the right agent based on skill and capacity, giving you real load balancing and accurate visibility into availability.
Do we need a full knowledge base from day one?
Not a large one, but you do need structure and ownership. Twenty well-maintained articles beat two hundred nobody updates, and without them self-service and Agentforce simply won't work.
How do we measure quality, not just speed?
Combine handle time with first-contact resolution, repeat contact rate and satisfaction. Measuring speed alone encourages premature closure and a repeat contact two days later.
When should we connect telephony?
When call volume is high and agents have to identify the customer manually on every call. CTI integration saves meaningful time per call, so it pays off mainly at high volumes.
Next step
Plan a Service Cloud rollout
We'll review your channels, volumes and routing model, and define what's needed to cut handle time without hurting quality.
Next step
Plan a Service Cloud rollout
We'll review your channels, volumes and routing model, and define what's needed to cut handle time without hurting quality.