Skip to main content
Endpoint · POST /conversation/actions
ai_assistance runs the AI employee you choose on the conversation without assigning it. It’s a one-off run: the employee runs transiently and produces its assistance (context/suggestion) on the conversation, but it does not become the assigned employee — the conversation stays with whoever handles it (another AI employee or a human), and the assignment doesn’t change. How it differs from the other AI actions:
  • run_ai runs the assigned employee —the one handling it— and takes the turn.
  • assign_ai_employee changes which employee handles the conversation.
  • ai_assistance runs another employee without assigning it — its output doesn’t change who handles the conversation.
Fields
  • ai_employee{ name } of the AI employee to consult (required).
  • instructions — optional text with the query or focus for the employee (for example, “Does this customer qualify for the enterprise plan?”).
It consumes tokens from the consulted employee’s model and counts as an AI-triggering action (maximum 3 per group). In a list, this object goes in the actions array of a POST /conversation/actions — see Assembling an action list.

Executable example

An ai_assistance on a conversation identified by phone and channel: it runs the chosen AI employee as a one-off, without changing the conversation’s assignment.

Request

Response

202 Accepted — the group was accepted and runs in the background. The per-action result does not travel in the response (query it later — see How it runs).
string
Always processing: confirms the group was accepted and is running.
integer
How many actions in the array were admitted for execution — not how many succeeded.