Service Channel
A Service Channel is a Salesforce object that defines a category of routable work inside Omni-Channel.
Definition
A Service Channel is a Salesforce object that defines a category of routable work inside Omni-Channel. Each Service Channel ties a specific sObject (Case, LiveChatTranscript, MessagingSession, custom object) to a Routing Configuration that decides how the work is matched to agents. The Service Channel is what makes Omni-Channel work-type-aware: a Cases channel and a Chats channel can use different routing rules, different capacity weights, and different presence categories, all running in parallel.
Salesforce ships standard Service Channels for the platform's built-in work types: Cases, Chats, Leads, Live Messages, Voice Calls. Custom Service Channels can be created for any custom object, which turns Omni-Channel into a generic routing engine for whatever Salesforce-tracked work the team handles. A Service Channel is the lowest-level routing primitive; without one, work of a given type cannot be routed through Omni-Channel. Configuring Service Channels correctly is the first step in any Omni-Channel rollout.
How Service Channels structure work routing in Omni-Channel
What a Service Channel ties together
A Service Channel record links three things. The Salesforce Object Type identifies the kind of work to route (Case, LiveChatTranscript, MessagingSession, Order__c). The Routing Configuration links to the routing model and Push Time Out (defined separately as a Routing Configuration record). The Push and Pull Routing Type defaults the behavior for newly created Service Channel members. Together, the three references make a Service Channel a thin coupling object: it does not itself carry routing rules, but it is the entry point for Omni-Channel to find them.
Standard vs Custom Service Channels
Salesforce includes standard Service Channels for the platform's built-in work types. Cases ships with the org. Live Chat ships with Live Agent. Messaging ships with Messaging. Voice ships with Service Cloud Voice. Each can be enabled or disabled and tied to the routing configuration that fits the team. Custom Service Channels are created in Setup, Service Channels, New. The Object Type dropdown lets you pick any custom object. Custom channels enable routing patterns Salesforce did not anticipate: routing approval requests, routing internal support tickets, routing manual review tasks.
Push Time Out and the agent acceptance window
Each Service Channel inherits its Push Time Out from the Routing Configuration. The Push Time Out is how long an agent has to accept incoming work before Omni-Channel re-routes. Typical values are 30 to 60 seconds. Below 20 seconds the rejection rate climbs sharply. Above 90 seconds the queue dwell time inflates. The right value depends on the channel: chat needs short Push Time Out (the customer is waiting live), case can tolerate longer (the customer is asynchronous). Tuning Push Time Out per channel is one of the first knobs to adjust after the initial Omni-Channel rollout.
Capacity Weights tied to Service Channels
Inside a Presence Configuration, each Service Channel gets a Capacity Weight. The weight is what the channel costs against the agent's total capacity. A Chat Service Channel weighted 1 means a single chat occupies one unit of capacity. A Case Service Channel weighted 2 means a case costs two units. If the agent has Capacity 10, they can hold 10 chats simultaneously, or 5 cases, or 4 cases and 2 chats. Weights are how Omni-Channel models the cognitive load different work types impose. Wrong weights overload or under-utilize agents.
Pull routing through Service Channels
Service Channels support both Push routing (system assigns, agent accepts) and Pull routing (work sits in queue, agents claim). Pull routing is configured on the Service Channel record and used for older queue-cherry-pick models or for low-priority backlog. Most modern Service Cloud deployments use Push exclusively, but Pull remains useful for after-hours overflow queues or training queues where the right agent might not be obvious. The choice is per Service Channel, so one channel can be Push and another Pull in the same org.
Skills-Based Routing on Service Channels
Skills-Based Routing layers on top of Service Channels. The channel decides "this is a Case" or "this is a Chat". Skills-Based Routing decides "this Case requires Spanish, Refund Knowledge, Tier 2". The two interact through Required Skills set on the work item at creation, typically via Flow. The Service Channel handles the basic routing, and Skills-Based Routing narrows the candidate agent pool. Skill-only matching without a Service Channel does not work; the channel is what tells Omni-Channel which Routing Configuration to consult.
External Routing through a Service Channel
Service Channels can be configured for External Routing, which hands the work off to an external system (Genesys, NICE, Five9) instead of routing internally. The external system returns the chosen agent's ID, and Omni-Channel completes the assignment. This is the integration model for hybrid contact centers that use Salesforce for case data and an external platform for voice and skill-based routing. The Service Channel is the routing endpoint; the Connected App and partner adapter handle the bidirectional API calls.
Creating a Service Channel for Omni-Channel routing
Creating a Service Channel is a quick Setup workflow. Pick the sObject, choose the Routing Configuration, set the routing type. The work happens once per channel.
- Enable Omni-Channel first
Setup, Omni-Channel Settings, Enable. Service Channels cannot be created until Omni-Channel itself is enabled at the org level.
- Open Service Channels in Setup
Setup, Quick Find Service Channels, click the link. The page shows existing channels (Cases, Chats, etc.). Click New.
- Pick the Salesforce Object Type
Dropdown lists every sObject available for routing: Case, LiveChatTranscript, MessagingSession, custom objects. Pick the object whose records should be routed.
- Set the Routing Type
Choose Most Available (matches by capacity), Least Active (matches by current item count), or External Routing (hands off to a third-party system).
- Link the Routing Configuration
Pick a Routing Configuration that defines Push Time Out and Auto-Accept. The configuration was created earlier in the Omni-Channel rollout.
- Save and confirm in Presence Configuration
Save the Service Channel. Open the relevant Presence Configurations and add the new channel to the Service Channel section with the appropriate Capacity Weight.
Display name shown in routing dashboards and agent UI. Should describe the work type plainly (Cases, Customer Chats, Refund Approvals).
API name used in SOQL and Apex references. Defaults from the Service Channel Name but cannot contain spaces or special characters.
The sObject whose records get routed. Standard objects (Case, LiveChatTranscript) or custom objects (Custom_Request__c) are supported.
Most Available, Least Active, or External Routing. Determines the algorithm used to pick the matching agent.
Reference to a Routing Configuration record that holds Push Time Out, Auto-Accept, and reroute behavior.
- A Service Channel can only reference one Routing Configuration. To route the same object type with different rules, create multiple Service Channels.
- Custom Service Channels require the custom object to support routing. Some custom objects lack the necessary lifecycle hooks. Test the routing in a sandbox before enabling in production.
- Service Channels for Chat and Messaging require the related products (Live Agent or Messaging) to be licensed and enabled before the standard channel records appear.
- External Routing requires a Connected App with the right OAuth scopes and a partner adapter. The Service Channel is just the entry point; the heavy lifting is the integration.
- Disabling a Service Channel in production stops all routing for that work type immediately. Plan the change carefully; agents will see no new work until re-enabled.
Trust & references
Straight from the source - Salesforce's reference material on Service Channel.
- Service ChannelsSalesforce Help
- Omni-Channel OverviewSalesforce Help
- ServiceChannel Object ReferenceSalesforce Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Service Channel?
Q2. What does capacity weight control?
Q3. How should weights be calibrated?
Discussion
Loading discussion…