sf-service-omnichannel-routing

Design Omni-Channel routing plans mapping queues to agent skills and presence.

15|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-omnichannel-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-service-omnichannel-routing
Source: https://github.com/sfdc-brendan/Demo-Lab/tree/main/Service%20Cloud/skills/sf-service-omnichannel-routing
Command: npx skills add https://github.com/sfdc-brendan/Demo-Lab --skill sf-service-omnichannel-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Omni-Channel routing design consolidates queues, presence, and capacity planning to optimize workload distribution across Service Cloud channels, helping teams meet SLAs and improve agent utilization.

Core Features & Use Cases

  • Queue-to-skill mapping: Align queues with agent skills and presence to route work to the right teams.
  • Presence & capacity modeling: Define agent statuses and capacity units to manage concurrency and load.
  • Fallback & overflow rules: Specify escalation paths for peak periods or unavailable skills.
  • Deliverables: Routing plan, skills matrix, presence model, and a monitoring dashboard spec.

Quick Start

Configure an initial Omni-Channel routing plan by mapping queues to skills, setting presence-based thresholds, and validating with a sample workload.

Frequently Asked Questions about sf-service-omnichannel-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up omni-channel routing in Service Cloud based on agent skills and presence?

Omni-channel routing in Service Cloud aligns work items with agent skills, presence, and capacity. You configure queues mapped to skills, set presence-based thresholds, and define capacity models to manage concurrency across chat, voice, and messaging.

What is skills-based routing and when do I need it for multi-channel support?

Skills-based routing distributes work items to agents with matching competencies. You need it for multi-channel support to optimize workload distribution, meet SLAs, and ensure chat, voice, messaging, and case work reaches the right teams.

How do I design overflow and fallback routing rules for peak periods?

Design overflow and fallback routing rules by specifying escalation paths for peak periods or unavailable skills. This involves defining alternate queues and routing logic to handle workload when primary skilled agents are unavailable.

Can I use omni-channel capacity planning to manage agent concurrency across chat and voice?

Yes, omni-channel capacity planning uses capacity units to manage agent concurrency and load. By defining agent statuses and capacity models, you control how many chat, voice, or messaging work items an agent handles simultaneously.

What deliverables do I need to configure a complete Service Cloud routing plan?

A complete Service Cloud routing plan requires a routing plan, skills matrix, presence model, and a monitoring dashboard spec. These deliverables define queues, skills, presence statuses, and capacity thresholds for workload distribution.

What's the best way to model agent presence and capacity for omni-channel queues?

The best way to model agent presence and capacity is defining agent statuses and capacity units to manage concurrency. This aligns queues with skills and presence to route work efficiently and prevent agent overload.