Docs/Automation & routing/Omni-Channel Message Routing in Salesforce

Omni-Channel Message Routing in Salesforce

If your use case requires distributing new chats to agents through a queue, Omni-Channel message routing does that: define the rules for each queue and how work is distributed among your agents.

Last updated 28 Nov 2025
Before you start, read the Chat Session documentation, since this guide builds on it.

Enable Omni-Channel message routing

Go to ValueText Setup, open Omni Channel Message Routing, check the box below, and click Update.

ValueText Setup screen showing the Omni channel message routing section, with the Enable omni channel routing for each conversation checkbox checked and an arrow pointing to the Update button.
Fig 01

Configure the sender ID queue

Go to the Sender IDs tab and edit your sender ID.

Sender IDs list view in Salesforce, with the Sender IDs tab and the Edit option in a sender ID's action menu both highlighted.
Fig 02

From here, you can enable a default queue for Omni-Channel, or configure a queue for a specific object, as shown below. Click Edit and configure it to match your requirements, the same way as the example below.

Sender ID queue configuration screen with the Default queue field set to Information Needed (SMS/Email), and Object 1 (Case) and Object 2 (Lead) rows for per-object queue overrides, annotated with a callout explaining the default and object-specific settings.
Fig 03

Turn on Omni-Channel in Salesforce Setup

Go to Omni-Channel Settings in Salesforce Setup, enable the checkbox shown below, and click Save.

Salesforce Setup Omni-Channel Settings page with the Enable Omni-Channel checkbox checked and highlighted.
Fig 04

Create a service channel

Create a Service Channel for the object you want to route, and click New.

Salesforce Setup Service Channels list showing existing channels (Chat, InformationSMSRoute, Phone, Service) with the New button highlighted.
Fig 05

Name the service channel, select the object (Chat Session), and click Save.

New Service Channel edit screen with the Service Channel Name and Developer Name set to InformationSMSRoute and the Salesforce Object field set to Chat Session, both highlighted, above the Save button.
Fig 06

Create a routing configuration

Create a Routing Configuration.

Salesforce Setup Routing Configuration edit screen with the Routing Configuration Name field and the Routing Model field, set to Most Available, both highlighted.
Fig 07

Assign the routing configuration to a queue

Assign the routing configuration to a queue. Remember the name you gave it in the previous step, you will need it here.

Create a new queue, add the Chat Session object to it, and add your users to the queue, as shown below.

Queue Edit screen for the Information Needed (SMS/Email) queue, with the Routing Configuration field pointing to the routing configuration from the previous step and Chat Session added to the Selected Objects list.
Fig 08
Queue Members screen for the same queue, with users moved into the Selected Members column.
Fig 09

Create a presence configuration

Create a Presence Configuration.

Presence Configuration edit screen named Information Needed, with the Allow agents to decline work requests checkbox checked and highlighted.
Fig 10

Create presence statuses

Create a Presence Status. In this example, we created two: "I'm Available" and "I'm Busy".

Salesforce Setup Presence Statuses list view, with the two new statuses, I'm Available and I'm Busy, highlighted in the list.
Fig 11

Assign presence statuses to a profile

Assign the statuses to the profiles that need them. Go to the required profile and refer to the image below.

Salesforce profile detail page for the ADMIN profile, with the Enabled Service Presence Status Access link highlighted.
Fig 12

Add the statuses and click Save.

Enable Service Presence Status Access screen with I'm Available and I'm Busy moved into the Enabled Service Presence Statuses list, above the Save button.
Fig 13

Add Omni-Channel to the user's interface

Add the Omni-Channel widget to the console:

  1. Open the App Manager and edit the required application (Service Console).
  2. Search for Utility Items.
  3. Add a new utility item.
  4. Choose Omni-Channel.
  5. Click Save.
Salesforce Service Console Cases list view with the Omni-Channel widget collapsed at the bottom left, showing Omni-Channel (Offline).
Fig 14

Whenever a new chat session comes in, it is assigned to an available user. When the user accepts the new chat, a Mini Chat Console opens so the agent can communicate with the customer.

Salesforce Service Console with the Omni-Channel panel expanded, status set to IM Online, and one new work request from Oleti Saisravan waiting to be accepted under the New tab.
Fig 15

At the end, your page should look like the image below.

Salesforce Service Console with the Mini Chat Console open on a Chat Session record, showing the message thread, a template selector, and the record's related Details panel.
Fig 16

Notes

  • Routing depends entirely on Omni-Channel: if Omni-Channel is off or misconfigured, chat sessions will not route.
  • If a user does not get the notification, enable the Service Cloud User checkbox on that user's record.
Was this helpful?
← PreviousSchedule Messages via Process Builder in Salesforce Next →Bots for Salesforce: Automate Messaging and Workflows
Docs/Automation & routing/Omni-Channel Message Routing in Salesforce

Omni-Channel Message Routing in Salesforce

If your use case requires distributing new chats to agents through a queue, Omni-Channel message routing does that: define the rules for each queue and how work is distributed among your agents.

Last updated 28 Nov 2025
Before you start, read the Chat Session documentation, since this guide builds on it.

Enable Omni-Channel message routing

Go to ValueText Setup, open Omni Channel Message Routing, check the box below, and click Update.

ValueText Setup screen showing the Omni channel message routing section, with the Enable omni channel routing for each conversation checkbox checked and an arrow pointing to the Update button.
Fig 01

Configure the sender ID queue

Go to the Sender IDs tab and edit your sender ID.

Sender IDs list view in Salesforce, with the Sender IDs tab and the Edit option in a sender ID's action menu both highlighted.
Fig 02

From here, you can enable a default queue for Omni-Channel, or configure a queue for a specific object, as shown below. Click Edit and configure it to match your requirements, the same way as the example below.

Sender ID queue configuration screen with the Default queue field set to Information Needed (SMS/Email), and Object 1 (Case) and Object 2 (Lead) rows for per-object queue overrides, annotated with a callout explaining the default and object-specific settings.
Fig 03

Turn on Omni-Channel in Salesforce Setup

Go to Omni-Channel Settings in Salesforce Setup, enable the checkbox shown below, and click Save.

Salesforce Setup Omni-Channel Settings page with the Enable Omni-Channel checkbox checked and highlighted.
Fig 04

Create a service channel

Create a Service Channel for the object you want to route, and click New.

Salesforce Setup Service Channels list showing existing channels (Chat, InformationSMSRoute, Phone, Service) with the New button highlighted.
Fig 05

Name the service channel, select the object (Chat Session), and click Save.

New Service Channel edit screen with the Service Channel Name and Developer Name set to InformationSMSRoute and the Salesforce Object field set to Chat Session, both highlighted, above the Save button.
Fig 06

Create a routing configuration

Create a Routing Configuration.

Salesforce Setup Routing Configuration edit screen with the Routing Configuration Name field and the Routing Model field, set to Most Available, both highlighted.
Fig 07

Assign the routing configuration to a queue

Assign the routing configuration to a queue. Remember the name you gave it in the previous step, you will need it here.

Create a new queue, add the Chat Session object to it, and add your users to the queue, as shown below.

Queue Edit screen for the Information Needed (SMS/Email) queue, with the Routing Configuration field pointing to the routing configuration from the previous step and Chat Session added to the Selected Objects list.
Fig 08
Queue Members screen for the same queue, with users moved into the Selected Members column.
Fig 09

Create a presence configuration

Create a Presence Configuration.

Presence Configuration edit screen named Information Needed, with the Allow agents to decline work requests checkbox checked and highlighted.
Fig 10

Create presence statuses

Create a Presence Status. In this example, we created two: "I'm Available" and "I'm Busy".

Salesforce Setup Presence Statuses list view, with the two new statuses, I'm Available and I'm Busy, highlighted in the list.
Fig 11

Assign presence statuses to a profile

Assign the statuses to the profiles that need them. Go to the required profile and refer to the image below.

Salesforce profile detail page for the ADMIN profile, with the Enabled Service Presence Status Access link highlighted.
Fig 12

Add the statuses and click Save.

Enable Service Presence Status Access screen with I'm Available and I'm Busy moved into the Enabled Service Presence Statuses list, above the Save button.
Fig 13

Add Omni-Channel to the user's interface

Add the Omni-Channel widget to the console:

  1. Open the App Manager and edit the required application (Service Console).
  2. Search for Utility Items.
  3. Add a new utility item.
  4. Choose Omni-Channel.
  5. Click Save.
Salesforce Service Console Cases list view with the Omni-Channel widget collapsed at the bottom left, showing Omni-Channel (Offline).
Fig 14

Whenever a new chat session comes in, it is assigned to an available user. When the user accepts the new chat, a Mini Chat Console opens so the agent can communicate with the customer.

Salesforce Service Console with the Omni-Channel panel expanded, status set to IM Online, and one new work request from Oleti Saisravan waiting to be accepted under the New tab.
Fig 15

At the end, your page should look like the image below.

Salesforce Service Console with the Mini Chat Console open on a Chat Session record, showing the message thread, a template selector, and the record's related Details panel.
Fig 16

Notes

  • Routing depends entirely on Omni-Channel: if Omni-Channel is off or misconfigured, chat sessions will not route.
  • If a user does not get the notification, enable the Service Cloud User checkbox on that user's record.
Was this helpful?
← PreviousSchedule Messages via Process Builder in Salesforce Next →Bots for Salesforce: Automate Messaging and Workflows
Docs/Automation & routing/Omni-Channel Message Routing in Salesforce

Omni-Channel Message Routing in Salesforce

If your use case requires distributing new chats to agents through a queue, Omni-Channel message routing does that: define the rules for each queue and how work is distributed among your agents.

Last updated 28 Nov 2025
Before you start, read the Chat Session documentation, since this guide builds on it.

Enable Omni-Channel message routing

Go to ValueText Setup, open Omni Channel Message Routing, check the box below, and click Update.

ValueText Setup screen showing the Omni channel message routing section, with the Enable omni channel routing for each conversation checkbox checked and an arrow pointing to the Update button.
Fig 01

Configure the sender ID queue

Go to the Sender IDs tab and edit your sender ID.

Sender IDs list view in Salesforce, with the Sender IDs tab and the Edit option in a sender ID's action menu both highlighted.
Fig 02

From here, you can enable a default queue for Omni-Channel, or configure a queue for a specific object, as shown below. Click Edit and configure it to match your requirements, the same way as the example below.

Sender ID queue configuration screen with the Default queue field set to Information Needed (SMS/Email), and Object 1 (Case) and Object 2 (Lead) rows for per-object queue overrides, annotated with a callout explaining the default and object-specific settings.
Fig 03

Turn on Omni-Channel in Salesforce Setup

Go to Omni-Channel Settings in Salesforce Setup, enable the checkbox shown below, and click Save.

Salesforce Setup Omni-Channel Settings page with the Enable Omni-Channel checkbox checked and highlighted.
Fig 04

Create a service channel

Create a Service Channel for the object you want to route, and click New.

Salesforce Setup Service Channels list showing existing channels (Chat, InformationSMSRoute, Phone, Service) with the New button highlighted.
Fig 05

Name the service channel, select the object (Chat Session), and click Save.

New Service Channel edit screen with the Service Channel Name and Developer Name set to InformationSMSRoute and the Salesforce Object field set to Chat Session, both highlighted, above the Save button.
Fig 06

Create a routing configuration

Create a Routing Configuration.

Salesforce Setup Routing Configuration edit screen with the Routing Configuration Name field and the Routing Model field, set to Most Available, both highlighted.
Fig 07

Assign the routing configuration to a queue

Assign the routing configuration to a queue. Remember the name you gave it in the previous step, you will need it here.

Create a new queue, add the Chat Session object to it, and add your users to the queue, as shown below.

Queue Edit screen for the Information Needed (SMS/Email) queue, with the Routing Configuration field pointing to the routing configuration from the previous step and Chat Session added to the Selected Objects list.
Fig 08
Queue Members screen for the same queue, with users moved into the Selected Members column.
Fig 09

Create a presence configuration

Create a Presence Configuration.

Presence Configuration edit screen named Information Needed, with the Allow agents to decline work requests checkbox checked and highlighted.
Fig 10

Create presence statuses

Create a Presence Status. In this example, we created two: "I'm Available" and "I'm Busy".

Salesforce Setup Presence Statuses list view, with the two new statuses, I'm Available and I'm Busy, highlighted in the list.
Fig 11

Assign presence statuses to a profile

Assign the statuses to the profiles that need them. Go to the required profile and refer to the image below.

Salesforce profile detail page for the ADMIN profile, with the Enabled Service Presence Status Access link highlighted.
Fig 12

Add the statuses and click Save.

Enable Service Presence Status Access screen with I'm Available and I'm Busy moved into the Enabled Service Presence Statuses list, above the Save button.
Fig 13

Add Omni-Channel to the user's interface

Add the Omni-Channel widget to the console:

  1. Open the App Manager and edit the required application (Service Console).
  2. Search for Utility Items.
  3. Add a new utility item.
  4. Choose Omni-Channel.
  5. Click Save.
Salesforce Service Console Cases list view with the Omni-Channel widget collapsed at the bottom left, showing Omni-Channel (Offline).
Fig 14

Whenever a new chat session comes in, it is assigned to an available user. When the user accepts the new chat, a Mini Chat Console opens so the agent can communicate with the customer.

Salesforce Service Console with the Omni-Channel panel expanded, status set to IM Online, and one new work request from Oleti Saisravan waiting to be accepted under the New tab.
Fig 15

At the end, your page should look like the image below.

Salesforce Service Console with the Mini Chat Console open on a Chat Session record, showing the message thread, a template selector, and the record's related Details panel.
Fig 16

Notes

  • Routing depends entirely on Omni-Channel: if Omni-Channel is off or misconfigured, chat sessions will not route.
  • If a user does not get the notification, enable the Service Cloud User checkbox on that user's record.
Was this helpful?
← PreviousSchedule Messages via Process Builder in Salesforce Next →Bots for Salesforce: Automate Messaging and Workflows
Docs/Automation & routing/Omni-Channel Message Routing in Salesforce

Omni-Channel Message Routing in Salesforce

If your use case requires distributing new chats to agents through a queue, Omni-Channel message routing does that: define the rules for each queue and how work is distributed among your agents.

Last updated 28 Nov 2025
Before you start, read the Chat Session documentation, since this guide builds on it.

Enable Omni-Channel message routing

Go to ValueText Setup, open Omni Channel Message Routing, check the box below, and click Update.

ValueText Setup screen showing the Omni channel message routing section, with the Enable omni channel routing for each conversation checkbox checked and an arrow pointing to the Update button.
Fig 01

Configure the sender ID queue

Go to the Sender IDs tab and edit your sender ID.

Sender IDs list view in Salesforce, with the Sender IDs tab and the Edit option in a sender ID's action menu both highlighted.
Fig 02

From here, you can enable a default queue for Omni-Channel, or configure a queue for a specific object, as shown below. Click Edit and configure it to match your requirements, the same way as the example below.

Sender ID queue configuration screen with the Default queue field set to Information Needed (SMS/Email), and Object 1 (Case) and Object 2 (Lead) rows for per-object queue overrides, annotated with a callout explaining the default and object-specific settings.
Fig 03

Turn on Omni-Channel in Salesforce Setup

Go to Omni-Channel Settings in Salesforce Setup, enable the checkbox shown below, and click Save.

Salesforce Setup Omni-Channel Settings page with the Enable Omni-Channel checkbox checked and highlighted.
Fig 04

Create a service channel

Create a Service Channel for the object you want to route, and click New.

Salesforce Setup Service Channels list showing existing channels (Chat, InformationSMSRoute, Phone, Service) with the New button highlighted.
Fig 05

Name the service channel, select the object (Chat Session), and click Save.

New Service Channel edit screen with the Service Channel Name and Developer Name set to InformationSMSRoute and the Salesforce Object field set to Chat Session, both highlighted, above the Save button.
Fig 06

Create a routing configuration

Create a Routing Configuration.

Salesforce Setup Routing Configuration edit screen with the Routing Configuration Name field and the Routing Model field, set to Most Available, both highlighted.
Fig 07

Assign the routing configuration to a queue

Assign the routing configuration to a queue. Remember the name you gave it in the previous step, you will need it here.

Create a new queue, add the Chat Session object to it, and add your users to the queue, as shown below.

Queue Edit screen for the Information Needed (SMS/Email) queue, with the Routing Configuration field pointing to the routing configuration from the previous step and Chat Session added to the Selected Objects list.
Fig 08
Queue Members screen for the same queue, with users moved into the Selected Members column.
Fig 09

Create a presence configuration

Create a Presence Configuration.

Presence Configuration edit screen named Information Needed, with the Allow agents to decline work requests checkbox checked and highlighted.
Fig 10

Create presence statuses

Create a Presence Status. In this example, we created two: "I'm Available" and "I'm Busy".

Salesforce Setup Presence Statuses list view, with the two new statuses, I'm Available and I'm Busy, highlighted in the list.
Fig 11

Assign presence statuses to a profile

Assign the statuses to the profiles that need them. Go to the required profile and refer to the image below.

Salesforce profile detail page for the ADMIN profile, with the Enabled Service Presence Status Access link highlighted.
Fig 12

Add the statuses and click Save.

Enable Service Presence Status Access screen with I'm Available and I'm Busy moved into the Enabled Service Presence Statuses list, above the Save button.
Fig 13

Add Omni-Channel to the user's interface

Add the Omni-Channel widget to the console:

  1. Open the App Manager and edit the required application (Service Console).
  2. Search for Utility Items.
  3. Add a new utility item.
  4. Choose Omni-Channel.
  5. Click Save.
Salesforce Service Console Cases list view with the Omni-Channel widget collapsed at the bottom left, showing Omni-Channel (Offline).
Fig 14

Whenever a new chat session comes in, it is assigned to an available user. When the user accepts the new chat, a Mini Chat Console opens so the agent can communicate with the customer.

Salesforce Service Console with the Omni-Channel panel expanded, status set to IM Online, and one new work request from Oleti Saisravan waiting to be accepted under the New tab.
Fig 15

At the end, your page should look like the image below.

Salesforce Service Console with the Mini Chat Console open on a Chat Session record, showing the message thread, a template selector, and the record's related Details panel.
Fig 16

Notes

  • Routing depends entirely on Omni-Channel: if Omni-Channel is off or misconfigured, chat sessions will not route.
  • If a user does not get the notification, enable the Service Cloud User checkbox on that user's record.
Was this helpful?
← PreviousSchedule Messages via Process Builder in Salesforce Next →Bots for Salesforce: Automate Messaging and Workflows