Looking for guides on service design so we can optimize using Service Cloud and self service.
I am familiar with many of the features in Service Cloud. From one perspective, it looks like our cases often require a discussion with the customer to solve their issue or provide the content, reporting, technical investigation, etc. that is needed. Looking for best practices on how to identify different types of cases and then design tiers or services. We have a compressed tiered approach, with 6 global employees serving as a "front line/Tier 1" and two of us handling more technically advanced issues (like failed email sends). Our range of skills and content needed to handle cases crosses 5 major software systems, about 50 different policy and business initiatives. Many of these require customer to complete stages of submitting materials and acknowledging completion.
Is there information available on how Service Cloud and service design can help with different types of inquiries and complexity of cases? Then, how can I match these to features?
I’d approach this by classifying cases based on complexity, required skills, and the customer actions needed, rather than simply assigning everything to Tier 1 or Tier 2.
For example, you could define categories such as:
Tier 1: Common questions, known solutions, standard requests, and cases covered by knowledge articles.
Tier 2: Issues requiring investigation across Salesforce or another connected system.
Specialist/Workflow cases: Requests where the customer needs to submit documents, complete steps, provide approvals, or acknowledge completion.
In Service Cloud, this classification can then drive Case Assignment Rules, Omni-Channel routing, Entitlements, Milestones, Flows, Knowledge, Case Status values, and escalation rules. I’d also use Case fields to capture the system involved, issue type, complexity, and customer action required. That gives you much better routing and reporting than relying on free-text case descriptions.
Since you mentioned five different systems and a large number of policies, I’d also map the customer journey first, then decide which Salesforce feature supports each step. That prevents the implementation from becoming a collection of isolated automations.
Girikon has a useful overview of Salesforce CTI and customer experience design that touches on how telephony and service workflows can fit into a broader Service Cloud setup: Salesforce CTI customer experience
The bigger goal is to make Tier 1 responsible for resolution where possible, while Salesforce automatically identifies and routes cases that genuinely need specialist attention.
