Round-robin conversation distribution: how to hand inquiries out among employees
A new conversation with no owner sits in the "Unassigned" tab until somebody notices it. The "round-robin" mode hands it to the next employee who is on the line right now. Here is how to turn it on, who counts as "on the line", where to see the queue, and what happens at night, on holidays and when an AI employee answers first.
What you need to know
- The mode hands out only conversations that have no employee yet. A conversation already handled by a person is left alone.
- The conversation goes to the marked employee who is on the line and has gone the longest without a new one. This evens out the load of new inquiries.
- Settings are changed by the admin and the manager. Other employees only see the "Waiting for an operator" label in the chat.
- Turning the mode on is part of the Business plan; see the plan contents and terms on the pricing page. You can view the settings and the queue on any plan, and you can always turn the mode off.
- The mode exists only in the business cabinet. It is not available in the children's cabinet (AISAR Kids).
Step 1. Turn on the "round-robin" mode
Open Settings → Chat and go to the "Distribution" tab. The "Auto-assignment of New Conversations" block has three options:
| Option | What it does |
|---|---|
| Off | Conversations wait in the "Unassigned" tab, employees take them on their own. |
| A single employee or team | Every new conversation goes to the same employee or team. This is the earlier auto-assignment and it works as before. |
| In turn among employees | The conversation goes to the next employee on the line, in a circle. |
Choose the third option and press the page's common save button. If the mode will not turn on and there is a lock next to it, it is not part of your plan.
Additional mode settings
- "Who gets them": everyone who takes conversations, or one team only. If a conversation was handed to a team, it is distributed inside that team.
- "If an AI employee works on the channel, it answers first": see the AI employee section below.
- "Outside working hours": wait for the start of the working day or distribute around the clock to those on the line. Details below.
Step 2. Mark who takes conversations
Below on the same tab is the "Who takes conversations" list. It contains every company employee who can handle conversations. For each you see the teams, the number of open conversations, the status and the "Takes" switch. Mark the employees you need, with the "Mark all" button or a team filter. The list is saved by the same common button as the other settings. If saving the list failed, the other settings are saved anyway, try again.
An employee without access to the conversation channel will not get it even if marked. Access to channels and teams is set up as usual, see Users and roles. You can mark only someone who sees the company conversations under their permissions.
Who counts as "on the line"
An employee gets conversations only if both conditions hold: their status is "Online" and the cabinet is open in the browser. The cabinet reports to the server every two minutes that the employee is at the desk; they count as present for another 5 minutes after the last signal. Each employee changes their own status in the profile menu.
| In the list | What it means |
|---|---|
| Online | Status "Online" and the cabinet is open. Gets new conversations. |
| Away | New conversations do not arrive. Already assigned ones stay with the employee. |
| Offline | New conversations do not arrive. |
| Cabinet closed | The status is "Online" but there has been no signal from the cabinet for more than 5 minutes. New conversations do not arrive, already taken ones stay with the employee. |
| Does not take conversations | The employee is not marked in the list. |
The statuses in the list update on their own. How statuses affect conversations is described below in the "Breaks and leaving the line" section.
Breaks and leaving the line
An employee picks their status in the profile menu, the availability item ("Set availability"): "Online", "Away" or "Offline". The status affects new conversations only: the ones you have taken stay with you.
| Status | What happens to conversations |
|---|---|
| Online | New conversations arrive in turn. |
| Away | A break: new ones do not arrive, your conversations stay with you. |
| Offline | New conversations do not arrive. All conversations you have taken stay with you and are not handed to colleagues. |
Going offline needs no confirmation and does not hand conversations over: you simply stop receiving new ones. A taken conversation stays assigned to you until another employee takes it over or you leave the conversation yourself, after which it goes in turn to the next employee on the line. Conversations of clients pinned to you as the responsible manager behave the same way.
The status applies in every company where the employee takes conversations in turn: everywhere they stop receiving new conversations, and the ones taken stay with them.
When a conversation leaves an employee
- Another employee took the conversation over: a colleague assigns the conversation to themselves, and it moves to them.
- The employee left the conversation themselves: it goes in turn to the next employee on the line, and if nobody is there it joins the queue.
- The employee is no longer in the company (dismissed or removed): all their conversations are taken off and go in turn.
What the employee and colleagues see
- When an employee leaves the conversation or is no longer in the company, a service entry appears in the feed. If the conversation immediately goes to another employee, an "Assigned in turn: Name" entry follows.
- A conversation with nobody to assign to joins the queue with the "Waiting for an operator" label, see the queue section.
Round-robin and the responsible manager
The queue: why a conversation waits
If there is nobody to give a conversation to, it joins the queue. The "Queue" block on the tab shows the number of waiting conversations, how long the oldest has waited and why they wait:
| Reason | What to do |
|---|---|
| Nobody is marked or nobody has access to the channel | Mark employees in the list and check that they have access to the conversation channel. |
| All marked employees are away or offline | Nothing: the conversation goes to the first one back on the line. Distribution starts within a minute. |
| Waiting for the start of the working day | Nothing: the queue starts being handed out in the first minute of the working day. |
In the chat such a conversation carries a yellow label "Waiting for an operator 12 min" or a grey "Waiting for the start of the working day", and the conversation header shows the same label next to the assignees. The minutes count up on their own, and the label disappears once an employee gets the conversation. You can still take it by hand by adding yourself as a participant.
If you removed an employee from a conversation by hand, the system will not hand that conversation out again for a minute, so you have time to assign the right person. Closed conversations are not distributed; auto-close is set on the "Rules" tab, see Automatic conversation close.
Order of distribution and response times
The conversation that has waited longest leaves the queue first. If the company has response times (SLA) turned on, the order differs: conversations with a higher priority and the nearest deadline are handed out first.
Night, weekends and holidays
The "Outside working hours" setting decides what happens when the company is closed under its working hours:
- "Wait for the start of the working day": conversations pile up in the queue and go to employees in the first minute after opening.
- "Distribute around the clock to those on the line": the schedule is ignored, those who are "Online" get conversations. If there is nobody, they wait in the queue.
Under the switch it shows whether the company is open now and when it opens. Holidays and your own days off count as closed days just like weekends, and an own working date opens the day. How to set them: Holidays and days off. An empty schedule means "always open".
If an AI employee works on the channel
With "If an AI employee works on the channel, it answers first" turned on, a conversation is not handed to people while the AI employee handles it. An employee gets the conversation when the AI hands it over to a human. Turn the setting off if people should get the conversation right away, alongside the AI. The switch is always available, even if you have no AI employees now: they can be connected later. Where an AI employee works is set in the "AI employees" section.
Limitations
- Distribution goes in turn, by the time of the last assignment. The current load (how many conversations an employee has open) is not taken into account when choosing; the number of open conversations in the list is informational.
- Conversations the employee has already answered, and those of clients where they were manually set as the responsible manager, are not redistributed even if they went "Offline", closed the cabinet or were removed from the list. Conversations are taken off only on dismissal, see the "Breaks and leaving the line" section.
- Group chats and hidden conversations are not distributed.
- The mobile app does not report presence, see above.
Common issues
| Symptom | Cause and what to do |
|---|---|
| Conversations are not handed out and the queue grows | Open the "Queue" block and look at the reason. Most often nobody is marked, or every marked employee is not "Online" or has the cabinet closed. |
| An employee is "Online" but gets no conversations | Check that they are marked in the list, have the cabinet open in the browser (not just the app) and have access to the channel. |
| The mode will not turn on | The mode is part of the Business plan; on other plans turning it on is locked. Only the admin and the manager can save changes. |
| Conversations are not handed out at night | That is how "Wait for the start of the working day" works. Choose "Distribute around the clock" if somebody is on duty at night. |
| A conversation on an AI channel is not handed to people | The "If an AI employee works on the channel, it answers first" setting is on: the conversation goes to a person when the AI hands it over. |