You are here:
Set Up Multiple Agent Record Assignment
Create an autolaunched flow that routes your Service Assistant agents to specific case types, business units, or other criteria.
Required Editions
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To set up multiple Service Assistant agents: | Customize Application OR System Admin AND Service Planner Builder permission set |
- Create Your Flow
- Create Input and Output Variables
- Add a Get Records Element
- Configure Your Agent Routing Logic
- Test Your Flow
- Assign Your Flow to Service Assistant
This article guides you through creating an autolaunched flow that routes Service Assistant agents to specific record types, business units, or other criteria, and then connecting the flow to Service Assistant in Setup. Your flow must be autolaunched and include a text input variable that receives the record ID and a text output variable that returns the API name of the agent to assign.
Because every customer’s business requirements are different, these steps provide guidance for creating the required variables and adding your flow to the Setup page. We only provide general guidance for configuring Get Records, Decision, and Assignment elements that must be configured to your business needs.
If you have an existing record routing flow, you can use it for Service Assistant as long as it’s autolaunched and includes the required input and output variables. Go directly to Assign Your Flow to Service Assistant and complete all procedures from there.
Before you begin, make sure:
- Your eligibility flow is configured and assigned in the Setup page.
- At least two Service Assistant agents are created and are active.
- Gather the API names of each of your agents from the Agent Details Setup page.
Create Your Flow
Create an autolaunched flow to assign your agents to specific cases. Autolaunched is the only supported flow type.
- From Setup, go to the Flows Setup page and click New Flow.
- Select Autolaunched Flow (No Trigger).
- Click Create.
Create Input and Output Variables
Create input and output variables for your flow that receive the case data to evaluate and return the agent to assign. The input variable passes the Case Record ID into the flow, and the output variable passes the selected agent’s API name back to Service Assistant to assign the agent to the case.
-
From the Toolbox panel, click New Resource and set these variable
settings for the caseId .
- Resource Type: Variable
- API Name: caseId
- Data Type: Text
- Enable Available for Input.
- Click Done.
-
Click New Resource and set these settings for the output variable
that holds the API Name of the agent to invoke.
- API Name: BotDefinitionDeveloperName. This is a suggested name.
- Resource Type: Variable
- Data Type: Text
- Enable Available for Output.
- Click Done.
Add a Get Records Element
Add a Get Records element to retrieve the case record using the input variable.
- On the Flow Builder canvas, click + and select Get Records.
-
From the configuration panel, set these settings.
- Enter a name for the element in the Label field, such as Get Case.
- From Data source, select Salesforce Object and then select Case.
- Set Field to Case Id.
- Set the Operator field to Equals.
- Set the Value field to caseId.
- Optional: To access fields from related records in your routing logic, select Also get related records and choose the relationships you need, like Account or Contact. This makes related record fields available as conditions in your Decision element.
- Click Done.
Configure Your Agent Routing Logic
Add Decision and Assignment elements to define how cases are routed to your Service Assistant agents. The Decision element evaluates your conditions to determine which outcome path to follow. Each outcome path leads to an Assignment element that sets the output variable to the API name of the target agent. The steps outline the general setup for you to make your specific business requirements.
-
Add a Decision Element.
- From the Flow Builder canvas, under the Get Records Element, click + and select Decision.
- Enter a label that describes the criteria you’re evaluating, like “Check Case Type”.
- Create an outcome for each routing scenario. For each outcome, define a condition using case fields, related record fields, or other flow variables. Set an operator and a value that matches your criteria.
- Click Done.
-
Add an Assignment Element.
- Under each outcome branch, click + and select Assignment. Set the variable to your output variable, the operator to Equals, and the value to the API name of the agent for that scenario.
- Click Done.
- Repeat for each remaining outcome.
- Save your flow and click Activate.
Test Your Flow
Save, activate, and test your flow to verify that cases route to the correct agent.
- From the Flow Builder menu, click Debug.
- Enter the record ID of a record for a specific record that you expect a specific agent to be assigned.
- Click Run.
- Verify it routes to the correct agent.
Assign Your Flow to Service Assistant
Connect your flow to Service Assistant in the Setup page and assign a default agent.
If you have an active Service Assistant implementation before the general availability of the multiple agent feature on June 30, 2026, your existing agent is automatically set as your default agent. Update your default agent based on your multi-agent setup. If you activate and set up Service Assistant after the release date, you must manually set a default agent.
- Go to the Service Assistant Setup page.
- From the Case tab, go to the Setup Your Agent Assignment section.
- From Set the Default Agent section, select a default agent.
-
From the Define Your Agent Assignment Criteria section, complete these
configurations.
- Set your multi-agent flow in the Flow label field.
- Set your flow’s input variables in the Input Variables Section.
- Set your flow’s output variables in the Output Variables Section.
- Click Save.
After assigning your flow, manually test your setup by drafting service plans for records that match different outcome paths in your flow.
Create a new record that matches each routing condition in your flow. Generate a plan summary and review the subagent name shown in the summary text. For example, if you see “Service Plan Available: Order Refund,” the assigned agent uses the “Order Refund” subagent.
If the subagent shown isn’t what you expect, the wrong agent was assigned. Review your Decision element conditions and Assignment element values to confirm they match your routing criteria.

