Route Your Customer Outreach Conversations in the Legacy Agentforce Builder
Set up Omni-Channel flows to route conversations to the required agent and from the agent to an escalation queue, rep, or other destination you specify.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Field Service and Foundations, or Einstein 1 Field Service Edition or Agentforce 1 Field Service Edition. |
Autonomous Scheduling requires separate agents for Customer-Initiated Scheduling and Customer Outreach. While both agents are based on the Agentforce Service Agent type, they’re set up differently.
The Customer-Initiated Scheduling agent requires the customer to verify their identity and includes a welcome message that’s shown at the beginning of the conversation.
The Customer Outreach agent doesn’t ask the customer to verify their identity and it doesn’t include a welcome message. It’s set up this way because you’re reaching out to a specific customer with a predefined outreach message and therefore you don’t need them to verify their identity.
For a smooth customer experience, it’s best practice to have these agents use the same messaging channel, but you need to make sure that your setup can recognize which agent should be triggered at the start of the messaging session. This way, the customer is only asked to verify their identity when needed and the welcome message is only shown when needed.
| User Permissions Needed | |
|---|---|
| To open, edit, or create a flow in Flow Builder: | Manage Flow |
Set Up the Inbound Omni-Channel Flow
This flow routes incoming conversations to the required agent.
If you’ve already created an inbound Omni-Channel flow for Customer-Initiated Scheduling, open the existing flow and skip to step 5.
- In Setup, find and select Flows.
- Open the Route Conversations to Agentforce Service Agents flow.
- Click Save As New Flow.
- Enter a label. The API name is populated for you.
-
After the Process Customer’s Locale element, add a Get Records element.
-
For Label, enter Get Messaging Session.
The API name is populated for you.
- For Object, find and select Messaging Session.
-
Under Filter Messaging Session Records, enter this condition:
Field: Messaging Session IDOperator: EqualsValue: recordID
-
For Label, enter Get Messaging Session.
-
After the Get Records element, add a Decision element.
-
For Label, enter Is Messaging Session Outbound or Inbound?
The API name is populated for you.
-
Add the details of the first outcome.
Outcome Label: OutboundResource: Find and select Messaging Session from Get Messaging Session and then find and select Origin. When you click on the value, it looks like this {!Get_Messaging_Session.Origin}.Value: Triggered Outbound
- In the second outcome, for the Outcome Label, enter Inbound (Default).
-
For Label, enter Is Messaging Session Outbound or Inbound?
-
Open the Route to Service Agent element.
-
For Route To, select Agentforce Service Agent.
Note If you can’t see this field, remove the selected Service Channel and add it again. - For Agentforce Service Agent, find and select the agent that you created for Customer Outreach.
-
Find and select your Fallback Queue.
Note The fallback queue helps you move around between the agent and the service reps when escalation is required. If you don’t already have a queue, see Create Queues.
-
For Route To, select Agentforce Service Agent.
-
After the Inbound decision outcome, add a Route Work action.
- Copy the previous Route Work element and paste it under the Inbound decision outcome.
-
Change the label to Route to Customer-Initiated Scheduling
Agent.
Update the API name accordingly.
- For Agentforce Service Agent, find and select the agent that you created for Customer-Initiated Scheduling.
- Save and activate the flow.
Set Up the Outbound Omni-Channel Flow for Escalations
This flow routes conversations from the agent to an escalation queue, rep, or other destination you specify.
If you’ve already created an escalation Omni-Channel flow as part of the setup for Customer-Initiated Scheduling, you can skip this entire procedure. The same flow can be used for Customer Outreach as well.
- In Setup, find and select Flows.
- Open the Route Conversations to Agentforce Service Agents flow.
- Click Save As New Flow.
- Enter a label. The API name is populated for you.
- Remove the Process Customer’s Locale element.
- In the Route Work element, change the label, API name, and description to indicate that you’re routing to a queue.
-
For Route To, select Queue.
Note If you can’t see this field, remove the selected Service Channel and add it again. - Find and select your Queue ID.
- Save and activate the flow.
Connect the Omni-Channel Flows to Your Agents
- In Setup, find and select Agentforce Agents.
- Open the agent that you set up for Customer-Initiated Scheduling.
- Click Open in Builder.
- Deactivate the agent so that you can make changes.
- Open the Connections tab.
- Under Inbound Omni-Channel Flows, make sure that you can see the inbound flow that you set up.
- Under Outbound Omni-Channel Flow, select the outbound escalation flow that you created.
- Save your changes.
- Activate the agent.
- Repeat these steps to also connect the Omni-Channel flows to the agent that you set up for Customer Outreach.
Connect the Omni-Channel Flows to Your Messaging Channel
If you’ve already connected the Omni-Channel flows as part of the setup for Customer-Initiated Scheduling, you can skip this entire procedure. The same flow can be used for Customer Outreach as well.
- In Setup, find and select Messaging Settings.
- Open the required messaging channel.
- In Omni-Channel Routing, click Edit.
- For Routing Type, select Omni-Flow.
- For Flow Definition, select the inbound flow that you created.
- For Fallback Queue, select the same queue that you selected when you created your inbound Omni-Channel flows.
- Save your changes.

