# Round-robin routing in Kustomer

> Kustomer has no built-in round-robin assignment. A workflow can approximate even distribution.

Source: https://help.kustomer.com/en_us/round-robin-routing-in-kustomer-H1yXYs4RMg

Last updated: 2026-11-20T19:12:45.964Z

**Who it is for:** Admins.

## Voice calls: route to the agent who least recently took a voice call

By default, Kustomer ranks eligible agents for each voice call by skill match (when the call requires skills), then by the percentage of capacity each agent has remaining, then by how long ago each agent was last assigned any work. Agents who carry a large backlog of chat or email can therefore receive fewer voice calls.

To rank agents by voice-call history instead, go to **Settings > Routing > General** and turn on **Route by longest time without a voice call**. This setting is available with Kustomer Voice and is off by default.

When the setting is on:

*   Among eligible agents, the agent whose last accepted voice call was longest ago receives the call. An agent who goes from offline to available has no voice-call time recorded, so that agent goes first. Remaining capacity is no longer used to rank agents.
*   Agents must still be eligible. They must be available, belong to the queue, have no pending offer, and not be on a voice call. They must also have capacity, unless over-capacity routing applies (see below).
*   Required skills still apply. Only agents who hold every required skill are eligible. Skill proficiency and optional skills no longer affect which agent is chosen for a voice call.
*   The time of an agent's last voice call updates when they accept a call. A call that is declined or times out does not move the agent to the back of the line.
*   The setting applies to the whole org and only to Kustomer Voice calls. It does not affect chat, email, or other channels.

For active Kustomer Voice calls, the team routing setting **Route when over capacity** lets agents who are over capacity receive calls. If that setting is off, agents with no remaining capacity are not eligible, even when the round-robin setting is on.

## Other channels: even distribution

Kustomer does not support native round-robin assignment for conversations in other channels. There is no built-in setting that automatically distributes new conversations evenly across available agents.

You can use workflows to build a custom assignment rule. The most common approach is a Conversation: Assign action step in a workflow triggered on Conversation Created, combined with conditions that evaluate current agent workload. This requires workflow configuration and does not replicate true round-robin behavior dynamically.

For examples of workflow-based routing, see the "Requeue snoozed conversations workflow" article.

## Related

*   [Configure general queue settings](https://help.kustomer.com/configure-general-queue-settings-Skqfto4Rzl)
