Intents are the set of reasons that a customer might contact your business and are recognized by the virtual agent when the customer first reaches out. Our ASAPP teams work with you to optimize your intent list on an ongoing basis.

Within intent routing, you can view the full list of intents and the routing behavior after an intent is recognized. Creators have the ability to modify this behavior.

​

Navigate to Intent Routing

You can access Intent Routing in the Virtual Agent navigation panel.

​

Intent Routing List

On the intent routing page, you will find a filterable list of intents along with their routing information. The following information is displayed in the table:

1. Intent name: displays the name of the intent, as well as a brief description on what it is.
2. Code: unique identifier for each intent.
3. Routing: displays the flow routing rules currently configured for an intent, if available. a. If the intent is routed to one or more flows, the column will list such flow(s). b. If the intent is not routed to any flow, the column will display an ‘Add Route…’. These intents will immediately direct customers to an agent queue.

​

Intent Routing Detail Page

Clicking on a specific intent in the list will direct you to a page where routing behavior for the intent can be defined. The intent detail page is broken down as follows:

1. Routing behavior
2. Conditional rules and default flow
3. Intent information
4. Intent toolbar

​

Routing Behavior

Routing behavior for a specific intent is determined by selecting one of the following options:

1. Route to a live agent When the intent is identified, the customer will be immediately directed to an agent queue. This is the default selection for any new intents unless configured otherwise.
2. Route to a flow When the intent is identified, the customer will be directed to a flow in accordance with the conditional rules that you will subsequently define.

​

Conditional Rules and Default Flow

If an intent is configured to be routed to a flow, you have the option to build conditional rules and route to a flow only when the conditions are validated TRUE. If all the conditional rules are invalid, customers will be routed to a default flow of your choosing.

​

Add Conditional Route

To add a new conditional route:

1. Select Add Conditional Route.
2. Define a conditional statement in the Conditional Route editor by: a. Selecting an available attribute as target from the drop-down menu and choose the value to validate against. E.g. authentication equals true. i. Multiple conditions can be added by clicking Add Conditions. Once added, they can be reordered by dragging, or deleted by clicking the trash can icon. b. Selecting the flow to route customers to, if the conditions are validated in the dropdown. c. Click Apply to save your changes.
3. Edit or delete a route by hovering over the route and selecting the respective icons.

​

Multiple Conditional Routes

You can add multiple conditional rules that can route to different flows. You can reorder these conditions by dragging the conditional rule from the icon on the left. Once saved, conditions are evaluated from top to bottom, with the customer being routed to the first flow for which the conditions are validated. If no conditional route is valid, the customer will be routed to the default flow.

​

Default Flow

A default flow must be selected if the routing behavior is defined to route to a flow.

Customers will be routed to the selected default flow if no conditional routes exist, or if none of the conditional routes were valid.

​

Intent Information

The Intent Information panel will display the intent name, code, and description for easy reference as you are viewing or editing intent routes.

The Assigned routes will display any flow(s) that are currently routed from the intent.

​

Intent Toolbar

When you are editing intent routing, the following buttons will display in the toolbar:

• Discard changes: remove all unsaved changes.
• Save: save changes to intent routing.

​

Save Intent Routing

To save any changes to intent routing, click Save from the toolbar. By default, when saving an intent route, it is immediately released to production. There is currently no versioning available when saving intent routes.

​

Test a Different Intent Route in Test Environments

To avoid impacting customer routing and assignments in production you can test a particular intent route in a test environment before releasing it to customers by following the steps below:

• In the Conditional Route editor, add a condition that targets the ‘InTest’ attribute. a. The value assigned to ‘InTest’ should equal ‘TRUE’. b. Select the flow that you want to test the routing for. c. Click Apply.

To fully release the intent route to Production, delete the conditional statement and update the routing to the new flow.

​

Test Intent Routes

Intent routes can be tested in demo environments. To test an intent route:

1. Access your demo environment.
2. Type INTENT_INTENTCODE, where INTENTCODE is the code associated with the intent you want to test. Please note that this is case sensitive.
3. Press Enter to test intent routes for that intent.