Assignment nodes: hand off to an agent, assign AI agent, and respond with AI

Three nodes to decide who handles each conversation: Hand off to an agent (human), Assign AI agent, and Respond with AI inside your workflows.

Jun 26, 2026

Watch this step in the video · Transferring to a person or a team

When an automation has to decide who keeps handling a conversation, the assignment nodes step in. Omnifox offers three, all in the Actions section of the workflow editor (Workflows menu):

  • Hand off to an agent (handoff): passes the conversation to a human.
  • Assign AI agent: puts an AI agent in charge and makes it reply right away.
  • Respond with AI: generates a one-off reply without changing who owns the conversation.

Hand off to an agent (handoff)

Use it to escalate to a person. Besides assigning, this node stops the other workflows running on that conversation, so the AI or an automated cadence doesn't step on the human's reply.

  1. Drag the Hand off to an agent node and connect it.
  2. Under Assign to, pick: a specific user, a team, a user within a team (with round-robin, least-load, or manual logic), or unassigned.
  3. Optionally, write a notify message (notify_text) that gets posted as a system note in the conversation.
  4. Save and publish.

Assign AI agent

Handy for putting a specific AI agent on the conversation (for example, routing to your "Tech support" bot based on the topic).

  1. Drag Assign AI agent and connect it.
  2. Choose the AI agent (it must be active and belong to the same workspace).
  3. By default, the node stops other workflows and triggers an immediate reply to the customer's latest unanswered message. You can turn either option off.
  4. Save and publish.

Respond with AI

Unlike the previous one, this doesn't change assignment: it just asks an AI agent to draft a reply on the spot.

  1. Drag Respond with AI and connect it.
  2. Pick the AI agent and the mode:
    • Auto: uses the agent's persona and chat history, as if a customer message had just arrived.
    • Prompt: you write a one-off instruction (e.g. "Apologize for the delay and ask for the order number"); the AI follows it using the history as context.
  3. Decide whether to send to the channel or store it in a variable ($ai.response) to use in another node.
  4. Save and publish.

Plan: the Respond with AI node is available on the Escala and Exclusivo plans. If your plan doesn't include it, the node is skipped without spending tokens.

Verifying it works

Use Test and check the execution timeline: you'll see who the conversation got assigned to and the text the AI generated. In the Inbox, confirm the new owner in the chat header.

If it doesn't work

  • "AI agent ... is not active": activate the AI agent in its editor before using it in the flow.
  • "does not belong to this workspace": the chosen agent is from another workspace; pick one from the conversation's workspace.
  • The AI doesn't reply after Assign AI agent: confirm there's an unanswered inbound message; if there isn't, it will reply to the customer's next message.
  • Respond with AI gets skipped: your plan likely doesn't include the node; check Plans & billing.

Tips

  • Combine them: use an AI classifier to route by intent, then Assign AI agent or Hand off to an agent depending on the case.
  • Add a clear notify_text to the handoff so the human agent gets the context when they receive the conversation.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp