Service Cloud setup is a multi-month exercise touching channels, routing, agent UX, Knowledge, SLA tracking, and integration with telephony and messaging systems. Plan an experienced admin or implementation partner; the configuration depth exceeds what a casual Salesforce admin can manage on their own.
- Map the support process and channels
Document how customers contact you (email, web, phone, chat), how requests categorize (technical, billing, returns), how they route (Tier 1, Tier 2, specialized teams), and what SLAs apply. The process map drives every configuration.
- Configure the Case object
Setup > Case > customize fields, picklists, record types, page layouts. Build the support category hierarchy. Configure Case Assignment Rules and Case Auto-Response Rules. Set up Email-to-Case for inbound email routing.
- Build Omni-Channel routing
Setup > Omni-Channel > configure service channels for each work item type (Case, Chat, Messaging). Build routing configurations with capacity and skill requirements. Assign agents to skill profiles.
- Configure the Service Console
Setup > App Manager > pick the Service Console > customize the layout, navigation, related records, and component placement. Add Quick Text, Macros, and Knowledge sidebar for agent productivity.
- Set up Lightning Knowledge
Enable Lightning Knowledge in Setup. Configure article types, categories, and visibility. Author the initial Knowledge library. Surface articles in the Service Console and the customer portal.
- Configure Entitlements and Milestones
Setup > Entitlement Management. Define entitlements with their SLA terms. Define Milestones with target times. Build automation that creates Entitlements per customer and starts Milestone timers on Case creation.
- Set up Live Chat or Messaging if applicable
For real-time channels, configure Live Chat or Messaging settings. Build chat buttons for embedding in websites or messaging app channels. Connect to Omni-Channel for routing.
- Train agents and roll out
Service Cloud adoption depends on agent training. Build sessions on the Console workflow, Quick Text, Macros, Knowledge usage, and SLA awareness. Plan a phased rollout starting with one channel or one team before expanding.
Starter, Pro Suite, Enterprise, Unlimited, Einstein 1 Service. Higher editions include more channels, automation, and AI.
Email-to-Case, Web-to-Case, Live Chat, Messaging, Voice, Social. Pick the channels the support operation needs.
Skill-based or queue-based work assignment. Drives how Cases and other work items reach agents.
- Service Cloud configuration depth exceeds Sales Cloud significantly. The number of moving parts (channels, routing, Knowledge, Entitlements, Console) demands an experienced implementation team.
- Email-to-Case has its own quirks. Bounces, replies that should append, and unrelated emails all need handling rules. Plan email handling carefully during initial setup.
- Omni-Channel routing depends on accurate agent presence and capacity settings. Agents who forget to set themselves available cause work items to pile up. Build training and alerting around presence.
- Lightning Knowledge requires version management. Articles have draft, published, and archived states. Forgetting to publish updates leaves stale information in front of agents and customers.
- Entitlements need automation to attach to new Cases. Without that automation, Cases have no SLA tracking. Build the entitlement-association logic carefully because retrofitting later is painful.