With find_next_folder enabled the agent transfers calls to the account's menu and transfer routes assigned to it. Assignments are changed submitting a routes list with the update request:
| field | description |
|---|---|
route_id | the route to assign or release |
deleted | false assigns the route to this agent, true releases it |
aiTags | optional tags the agent selects the route on, for example sales or support. Tags are stored # prefixed, submitting the # is optional. Omit or leave empty to keep the route's existing tags |
Unlike the settings above, route assignments are merged: routes left out of the routes list keep their current assignment.
A route can be assigned or released without submitting new tags. Omitting aiTags, submitting an empty array ([]), or submitting only blank entries preserves the route's existing tags while updating the assignment. This also works when the route has no stored tags. A non-empty list replaces the stored tags; an empty list does not clear them.
For example, {"route_id": "298788", "deleted": false, "aiTags": []} assigns the route using its existing tags. Omitting aiTags has the same effect, and deleted: true releases the route while keeping its tags. Include these entries in the routes list alongside the current tools and fine_tuning settings, as described in the update request below.
Route ids the selected account does not own are ignored, and a route of a type that cannot be updated fails the request with route_id: unsupported route type.
route_id is the id of one of the account's menu or transfer routes, listed by List Transfer Routes: the routes it reports with assignable set to false are the ones that fail with route_id: unsupported route type. The routes currently assigned to the agent are returned by the Get request, as transfer_call.children.find_next_folder.assigned_route_ids.