Case Management
Case types, classification, mandatory fields by type, and a defined closure process.
Service Cloud
One case, one view, measurable handling time.
Service Cloud implementation centered around the case journey: intake from every channel, classification, routing, entitlements and milestones, escalation, and measurement — with a knowledge base that serves both agents and self-service.
Capability Map
What's Included and in What Order
This map illustrates the work layers in this service, from infrastructure to user-facing capabilities.
Service Cloud — Capability Map
Case Management
Case types, classification, mandatory fields by type, and a defined closure process.
Omni-Channel Routing
Assignment by skill, workload, and availability instead of manual queue picking.
Entitlements and Milestones
Defining response and resolution targets, tracking deviations, and automatic escalation.
Knowledge Base
Article structure, ownership, update cycle, and usage measurement.
Self-Service
A portal or help center that reduces repeat inquiries.
Measurement
Handling times, first-contact resolution, repeat inquiries, and satisfaction.
The Background
What Truly Matters Here
A service center is measured by time and quality, but both depend on an early decision: how to classify an inquiry. Poor classification leads to poor routing, and from there, all other metrics cannot be corrected.
A single customer view is more important than any automation. An agent forced to switch between three screens to understand what happened will extend the handling time, even if the process is perfect on paper.
A knowledge base is not a side project. It is the prerequisite for effective self-service and the precondition for any future use of Agentforce.
Areas of Work
What we actually do
Omni-Channel Routing
Assignment by skill, workload, and availability instead of manual queue picking.
Entitlements and Milestones
Defining response and resolution targets, tracking deviations, and automatic escalation.
Knowledge Base
Article structure, ownership, update cycle, and usage measurement.
Self-Service
A portal or help center that reduces repeat inquiries.
Measurement
Handling times, first-contact resolution, repeat inquiries, and satisfaction.
Decision Matrix
Decisions that determine the outcome
| Decision | Option A | Option B | What is Decisive |
|---|---|---|---|
| Routing Model | Queue Picking | Omni-Channel by Skill | Inquiry Volume and Expertise Diversity |
| SLA Structure | Uniform Target | Target by Customer Type | Are there binding service agreements? |
| Self-Service | Public Knowledge Articles | Portal with Authentication | Is personal information required in the inquiry? |
| Channels | Email and Phone | Numerous digital channels | Where customers actually turn to |
Routing Model
- Option A
- Queue Picking
- Option B
- Omni-Channel by Skill
- What is Decisive
- Inquiry Volume and Expertise Diversity
SLA Structure
- Option A
- Uniform Target
- Option B
- Target by Customer Type
- What is Decisive
- Are there binding service agreements?
Self-Service
- Option A
- Public Knowledge Articles
- Option B
- Portal with Authentication
- What is Decisive
- Is personal information required in the inquiry?
Channels
- Option A
- Email and Phone
- Option B
- Numerous digital channels
- What is Decisive
- Where customers actually turn to
How We Work
Execution stages
- 01
Mapping the contact journey
Channels, types, volumes, and failure points.
- 02
Data model
Contact, customer, product, entitlement, and history.
- 03
Routing and entitlements
Queues, skills, time targets, and escalations.
- 04
Knowledge and self-service
Structure, ownership, and update process.
- 05
Training
Work scripts for agents and team managers.
- 06
Measurement and improvement
Review of metrics and correction of inaccurate classifications.
Continue from here
Related services and guides
Frequently Asked Questions
Frequently Asked Questions
What is the difference between a queue and Omni-Channel?
A queue requires the agent to pull a contact themselves, so less convenient contacts are left behind. Omni-Channel pushes contacts to the appropriate agent based on skills and capacity, creating a true load distribution and accurate availability measurement.
Is a knowledge base required from the start?
Not a full one, but structure and ownership are. Twenty maintained articles are worth more than two hundred articles that no one updates, and without them, self-service and Agentforce will not work.
How do you measure quality and not just speed?
Combine handling time with first-contact resolution, rate of recurring contacts, and satisfaction. Measuring speed alone encourages early closure and a recurring contact two days later.
When should telephony be integrated?
When call volume is high and the agent is required to manually identify the customer on each call. CTI integration saves significant time on every call, thus justifying itself mainly in high volumes.
The Next Step
Service Cloud Implementation Planning
We will examine channels, volumes, and routing models — and define what is needed to shorten handling without compromising quality.