Assign To (human)

Hand the conversation to one teammate, or let the step pick round robin or fewest open contacts, with an optional timeout message if nobody answers.

Quick start

  1. Go to Automate → Workflows and open a workflow. Click + and pick Assign To (human).
  2. Under Action, pick Assign to a specific user, then pick the teammate under Assign To.
  3. Or pick Assign to a user in the workspace, then round robin or fewest open conversations under Assignment Logic.
  4. Optional: switch on Add Timeout Branch and type a message for the customer if nobody answers.
  5. Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.

Watch out

  • The teammate is not told. Nothing is pushed when this step runs, so add Escalate after it when somebody must know.
The Add Steps menu open on the canvas, with Assign To (human) highlighted.
The step panel with Action set to Assign to a specific user, and Assign To under it.
Assignment Logic's two choices, with Advanced Settings open below them.
Details

Getting here

Automate → Workflows, open a workflow, click + on the canvas, then pick Assign To (human) under Add Steps.

Before you start

  • An owner, admin or agent can add this step and save the workflow. Only an owner or admin can publish it, and publishing is what makes it run on live conversations.
  • Building and running workflows depends on your plan; see pricing.
  • Somebody for the step to pick. It can pick any member of your workspace, including you, so if you are the only member every conversation comes back to you.
  • Nothing outside Inchat has to be connected. The step only writes to the conversation.

Set up

  1. Open the workflow and click + where the assignment belongs — usually at the end of the path that needs a person.
  2. Pick Assign To (human).
  3. In Action, choose Assign to a specific user to name someone, or Assign to a user in the workspace to let the step pick.
  4. Naming someone: choose them under Assign To. Letting the step pick: choose Assign to users round robin or Assign to the user with least open contacts under Assignment Logic.
  5. Optional, under Advanced Settings: cap how many open contacts a teammate may already be holding. You can also switch on Add Timeout Branch and type the message to send if the assignee has not answered in time.
  6. Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.

Fields

Action
What the step does: name one teammate, hand to an AI agent, hand to a team, let the step pick from the workspace, or clear the assignee.
Default: Assign to a specific user
Limits: The AI-agent and team choices save a different step. Each has its own page.
Assign To
The teammate who gets the conversation.
Limits: Shown only for Assign to a specific user.
Assignment Logic
Assign to users round robin takes the next teammate after the current assignee. It takes the first when there is no current assignee, or when a cap left them out. Assign to the user with least open contacts takes whoever holds fewest.
Limits: Shown for the workspace and team choices, not when you name a person.
Only assign to online users
Round robin and fewest open contacts skip any teammate who is not online. Not online means Busy, Offline, no Inchat tab or app open, or idle for an hour.
Default: off
Limits: Shown only with an Assignment Logic; a teammate you name is never skipped. If nobody is online, nobody is assigned — see When it fails.
Only assign to users with fewer than … open contacts assigned to them
Skips any teammate who already has that many open conversations or more, counted across every channel in your workspace.
Limits: Offered and saved only together with an Assignment Logic. Ignored when you name a person.
Add Timeout Branch
Queues a message to the customer if the assignee has not answered them by the time the timeout passes.
Default: off; 10 minutes when switched on
Limits: Queues nothing if the message box is left empty. What the panel builds here is one message — see Limits.

How it works

  • The conversation shows that teammate as its owner, and it appears when you filter the Inbox by Assignee.
  • Before that, it checks the teammate is still a member of this workspace. A workflow naming somebody who has left fails, rather than handing the thread to a person who can no longer open it.
  • Assign to a specific user takes the person you named and nobody else. If they are not on the workspace member list, the step picks no one.
  • Assign to users round robin keeps the teammates it may pick in one fixed order and takes the one after whoever holds the conversation now, starting again at the first after the last.
  • With no assignee yet it takes the first. It also takes the first when the current assignee is not in the pool, because a cap or a departure left them out.
  • Assign to the user with least open contacts counts how many open conversations each teammate holds in this workspace and takes the lowest. If two teammates hold the same number, the same one is always chosen.
  • That count covers every channel in your workspace together, and every team in it.
  • Unassign clears the assignee and changes nothing else. Status, tags and the thread itself stay as they were.
  • The conversation does drop out of the old assignee's own list, because it goes back to unassigned. That is the point of the action.
  • A Timeout Branch does not make the workflow wait. The timeout message is saved for later and the workflow goes straight on to the next step.
  • About every minute, Inchat checks whether the assignee has sent the customer anything since getting the conversation. If they have, the timeout message is dropped and nothing is sent.
  • An internal note does not count as answering. Only a message the customer receives stops the timeout message going out.

When it fails

  • Nobody online: with Only assign to online users on and every teammate away, the step fails and the conversation keeps the owner it had — or stays unassigned. The run log reads no teammate online to assign — the conversation keeps its current assignee.
  • Nobody available: with an Assignment Logic set and every teammate already at your open-conversation limit, the step fails and the conversation keeps the owner it had. The step's line in the run log reads no teammate available to assign.
  • The named teammate has left the workspace: the step fails with that assignee is no longer a member of this workspace. Again the conversation keeps its previous assignee rather than gaining an unreachable one.
  • A failed assignment does not stop the workflow. This one step is recorded as failed and the workflow keeps going, so a message, a tag or a close placed after it still happens, even though nobody new got the conversation.
  • So a conversation that had no owner still has none, and one round robin was moving off a teammate stays with that teammate.
  • You read the reason in the workflow's Activity tab: pick the run under Execution log, and the failed step carries its own line of text.
  • Saving is refused before any of that if neither a teammate nor an Assignment Logic is set — Pick a teammate or a distribution rule for Assign To.

Limits

  • Only assign to online users counts a teammate as online when Inchat cannot read their status, or when they have never opened Inchat at all. It never skips somebody just because their status is unknown.
  • The step does not check channel access. Unlike automatic assignment, it can hand a conversation to a teammate whose channel list does not include that channel, and they will not be able to open it.
  • It does not notify the assignee. Nothing is pushed when the step runs, and there is no assigned-to-you notification anywhere in the product.
  • Whether a later message reaches the assignee depends on the conversation — on whether it is left waiting for a person, and then on their notification setting, their availability and whether they muted it. When somebody has to be told, use Escalate: it stops the AI answering and alerts a person.
  • It sends the customer nothing. Unless a later step or the timeout message speaks, the customer sees no change at all.
  • It does not pause the AI agent. A thread assigned by a workflow is still a thread the AI may answer on. Escalate or Pause AI / Unassign is what stops that.
  • In the Configure step panel, the timeout branch can only send one message. The box builds a single Send a Message, and with the switch on and the box empty nothing is queued at all.
  • A workflow written by Build with AI can put other steps in the timeout branch — an assignment, a tag — and they do run. But the panel only ever shows the text of the branch's first step, and typing in that box replaces the whole branch with one message. Edit such a step somewhere else, or expect to lose the rest of it.
  • Round robin remembers only who holds the conversation now. It does not keep a shared turn list for the workspace, so two new unassigned conversations both go to the same first teammate.

Best practices

  • Put the assignment after the tag or the internal note that says why somebody has it. A thread that lands in a queue with no context is a thread that gets read twice.
  • On the path where the AI did not answer, assign first and put Escalate after it. The AI Reply step already alerts whoever holds the conversation when it refuses to answer; what Escalate adds is the AI pause. Placed after the assignment, both it and the alert are addressed to the person you just gave the conversation to.
  • Escalate and this step answer different questions — *look at this now* against *this is yours*. Most paths that need a person want both, the assignment first, so the escalation has somebody to address.
  • Use fewest open contacts rather than round robin when most new conversations have no owner yet: round robin hands every one of them to the same person.
  • Set the timeout message to something the customer benefits from reading. An apology for the wait beats a nudge aimed at your own team, because the customer is who receives it.

Use cases

  • A customer asks for a person after the AI has answered: assign to the workspace by fewest open contacts, with a two-minute timeout message. Then Escalate, so the AI stops and the alert is addressed to whoever now has it.
  • A payment slip arrives: move the deal to its next stage, then assign the thread to the one teammate who checks transfers.
  • Out of business hours, Date & Time sends the flow to a template; inside them, it assigns round robin to the next teammate on the list.
  • A high-value deal stage is reached: assign the named account owner rather than the rota.

FAQ and troubleshooting

Does the contact leave the workflow once it is assigned to a person?
No. Assigning records who owns the conversation, and the run carries on to the next step — a wait, a question or a message placed after it still happens. Put an End step after the assignment if the flow should stop there.
The step says it failed. Where did the conversation go?
Nowhere. It keeps the assignee it had before, and the rest of the run still executed. Open the workflow's Activity tab, pick the run under Execution log, and the failed step's line gives the reason.
Why does round robin keep choosing the same teammate?
Round robin steps off whoever holds the conversation now, and a new conversation has nobody. So every unassigned conversation starts at the same first teammate. Assign to the user with least open contacts spreads a new queue evenly.
I switched on Only assign to online users and it still assigns to people who are away.
The step skips a teammate whose status is Busy or Offline, who has no Inchat tab or app open, or who has not touched Inchat for an hour. Someone who left a tab open and is still active counts as online. A teammate you name with Assign to a specific user is never skipped.
Does the teammate get a notification when a workflow assigns them a conversation?
Not for the assignment itself. Nothing is pushed at that moment, and there is no assigned-to-you notification anywhere in the product. The conversation does appear under their Assignee filter in the Inbox. Whether a later message pushes to them is a property of the conversation. When the AI replies on its own, no alert is meant to be sent, and their notification setting, availability and mute all still apply. Do not rely on it — when somebody has to be told, put Escalate after the assignment, so the alert has an assignee to address.
Can the timeout branch pass the conversation to somebody else?
Not from the panel: the box there sends the one message you typed, and only if the assignee has not already answered the customer. A workflow written by Build with AI can put an assignment in the timeout branch and it does run. Do not add a second Assign step after this one hoping it runs on timeout: the workflow does not wait, so it would run a few seconds later.

Reading this with an AI assistant? Plain Markdown version.