Update inbound router
Turn an agent’s inbound router on or off and change its default task, AI thresholds, and clarifying questions. Requires confirm: true.
"confirm": true. Settings you leave out keep their value. Any other key returns 400 invalid_router_settings_field, with the unknown keys in fields.
Turn the router on
- Without a default task, Nexor prefers the Agent’s arrival task. Otherwise, it prioritizes active, unpaused tasks and then creation order.
candidate_workflow_idslimits the candidates when set. - The default task must be one of the agent’s tasks. A paused task is allowed.
- When
candidate_workflow_idsis set, the default task must be in that list. - Turning the router on does not enable incoming calls. Set the Agent’s incoming-call mode separately with
set_agent_inbound_callsin the MCP orPUT /master-workflows/{id}/inbound-callsin the API.
Decide when the agent asks first
Turn the router off
call_reception_stop_failed.Authorizations
Path Parameters
Body
Send only the settings to change. Any other key returns 400 invalid_router_settings_field.
Below confidence_threshold but at or above this value, the agent asks the lead a clarifying question instead of guessing (WhatsApp and web chat). Below it, the conversation goes to the default task. Must not be greater than confidence_threshold. null restores the default (0.55).
0 <= x <= 1What the AI receptionist says word for word to every new caller while it routes calls (AI routing on, or a keyword rule that applies to calls), instead of any task's inbound greeting. Up to 160 characters after trimming; whitespace is collapsed. Variables in double curly braces are not allowed. null uses the generated greeting, returned as reception_greeting_default by GET. Calls use a new value within a minute or two.
1 - 160