Assign To (team)
Route the conversation into a team's queue, and optionally hand it to a teammate on that team by round robin or fewest open contacts.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Assign To (team).
- Under Team, choose the team the conversation should route into.
- Under Assignment Logic, pick Leave it in the team's queue or one of the two options that pick a person.
- Under Advanced Settings (person picked): cap open conversations, or turn on Add Timeout Branch with a customer message.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- Round robin and fewest open contacts pick only team members who can open this conversation's channel. If nobody qualifies, it stays in the team's queue.
- This step does not notify the person or stop the AI. With nobody online, Only assign to online users leaves it in the team's queue.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Assign To (team) under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Publishing it is an owner or admin action.
- Building and running workflows depends on your plan; see pricing.
- At least one team must already exist in the workspace for this step to route into.
- For a person to be picked, the team needs members who are owners, admins or agents and can open the conversation's channel.
- Nothing outside Inchat has to be connected. The step only writes to the conversation.
Set up
- Open the workflow and click + where the assignment belongs.
- Pick Assign To (team).
- Under Team, choose the team the conversation should route into.
- Under Assignment Logic, choose Leave it in the team's queue to route only, or Assign to users round robin / Assign to the user with least open contacts to also hand it to a teammate.
- Optional, under Advanced Settings: cap how many open contacts a teammate may already be holding, and switch on Add Timeout Branch with a message to send if nobody has answered in time.
- 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
- Team
- The team the conversation is routed into. Always written, whichever Assignment Logic is picked.
- Assignment Logic
- Leave it in the team's queue files the conversation into the team without naming a person. Assign to users round robin and Assign to the user with least open contacts also pick one person from that team's members who can open the conversation's channel.
- Default: Leave it in the team's queue
- 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. Only the team's members are checked: if none of them is online, the conversation stays in the team's queue.
- Only assign to users with fewer than … open contacts assigned to them
- Skips any teammate already holding that many open conversations or more, counted across the whole workspace. Round robin passes over them; they get a turn when the order comes round to them again and they are under the limit.
- Limits: Offered and saved only together with an Assignment Logic other than the team's queue.
- Add Timeout Branch
- Queues a message to the customer if the teammate the step picked, or the assignee round robin kept, has not answered them by the time the timeout passes.
- Default: off; 10 minutes when switched on
- Limits: Not when the conversation was only left in the team's queue, or when the step found nobody to give it to.
How it works
- The step always writes the conversation's team, whatever Assignment Logic is chosen — this is what puts it in that team's queue.
- If Leave it in the team's queue is chosen, the step does no more than that, and the assignee is left exactly as it was — untouched if it had one, still unassigned if not.
- Both picks choose only from the team's members who are owners, admins or agents and can open the conversation's channel. Someone off the team, a viewer, or a teammate without that channel is never picked.
- Assign to users round robin gives the conversation to the next of those teammates in turn. The order is fixed, and each team keeps its own turn on each channel, so the next conversation goes to the next teammate.
- Round robin passes over teammates who set themselves Busy or Offline. They stay in the order and get a turn when it comes round to them again and they are available.
- A conversation that already has an assignee keeps them under round robin, and the turn does not move.
- Round robin writes the person only if the conversation still has no assignee and is still with this team.
- When the AI agent hands a conversation with no assignee to a team, it picks the same way: the next teammate in the same turn order, among those who can open the conversation's channel.
- A hand-off to a team that Inchat finishes after an interruption also picks the next teammate from the same turn order, when nobody has been assigned in the meantime.
- Assign to the user with least open contacts takes, from the same teammates, the one holding the fewest open conversations across the whole workspace. A tie goes to the same teammate every time.
- Fewest open contacts replaces an existing assignee with whoever holds the fewest, after checking they are still a member of this workspace.
- A Timeout Branch works exactly as it does on Assign To (human): it queues a message for later and the run continues to the next step immediately, without pausing.
When it fails
- The chosen team no longer exists in this workspace: the step fails with no team with id … in this workspace — it may have been deleted, and the conversation's team is left as it was.
- If no teammate can open the channel, or all are at the open-conversation limit, the step fails with no teammate available to assign.
- Round robin fails with that same line when everyone on the team set themselves Busy or Offline, whether or not Only assign to online users is on.
- Otherwise, with Only assign to online users on and nobody on the team online, the step fails with no teammate online to assign — the conversation stays in the team's queue.
- Round robin: if a person assigns the conversation or moves it to another team while the step picks, it fails with the conversation changed while a teammate was being picked.
- Round robin fails with could not pick a teammate — the conversation stays in the team's queue when it cannot finish its pick.
- That happens when something it needs, such as the team's members, cannot be read or saved, or when other hand-offs to the team keep taking the turn first.
- Fewest open contacts fails with a line that starts could not read the team's members when it cannot read who is on the team.
- The conversation's team has already been written and is not rolled back.
- So, unless someone changed it meanwhile, it is left in that team's queue with its assignee exactly as it was before the step ran — still whoever it was, or still nobody.
- A failed assignment does not end the run, exactly as on Assign To (human) — the flow moves to the next step regardless.
- 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 if no team is chosen — Pick a team for the “Assign to team” action.
Limits
- Round robin never moves a conversation that already has an assignee. Fewest open contacts does, to whoever on the team holds the fewest.
- Fewest open contacts does not skip a teammate who set themselves Busy or Offline unless Only assign to online users is on.
- Only assign to online users checks only the team's members. Under fewest open contacts, a teammate who has never opened Inchat counts as online.
- A teammate who is on the team but cannot open a channel never gets a turn for conversations on that channel.
- When everyone on the team set themselves Busy or Offline, the AI agent's hand-off assigns nobody: the conversation waits in the team's queue and owners and admins are notified.
- It does not notify the assignee, and it sends the customer nothing beyond a Timeout Branch message if one is configured and reached.
- It does not pause the AI agent — a thread assigned this way is still a thread the AI may answer on.
Best practices
- Use Leave it in the team's queue when the point is that the right group should see it and pick it up themselves, rather than have the step guess who.
- Use round robin to spread new conversations across a team in turn. The AI agent's hand-offs to that team on the same channel take turns from the same order.
- Before relying on either pick, check that every teammate who should take these conversations can open the channel. One who cannot is never picked there.
Use cases
- A billing question routes into the billing team's queue for a person to claim, with no automatic pick.
- A general enquiry routes into the support team's queue and goes to the support teammate with the fewest open contacts, with a timeout message if they do not answer.
- New leads route round robin to the sales team, one teammate after another, skipping anyone who set themselves Busy.
FAQ and troubleshooting
- Does Assign to a user in a specific team only pick from that team?
- Yes. Round robin and fewest open contacts pick only from that team's members who are owners, admins or agents and can open the conversation's channel. Someone off the team, a viewer, or a teammate without access to that channel is never picked.
- Does the AI agent's hand-off to a team use the same turns?
- Yes. When the AI agent hands a conversation with no assignee to a team, it goes to the next teammate in the same turn order, among those who can open the conversation's channel. A team-only hand-off that Inchat finishes after an interruption does the same.
- What happens if I pick a team but leave the Assignment Logic as the team's queue?
- The conversation is filed under that team and its assignee is left exactly as it was, no more. If it had none, a person still has to claim it; if it already had one, they keep it.
Reading this with an AI assistant? Plain Markdown version.