Summary
Wati's chat assignment features help distribute incoming chats among team members so conversations are handled efficiently and workloads are balanced.
You can use:
Round Robin to assign chats sequentially to eligible team members.
Load-Based Routing to assign chats to the eligible online team member with the lightest workload.
Auto Reassign with No Response to automatically reassign a Round Robin chat when the assigned team member does not respond within the configured time.
You can configure Round Robin in three ways:
Default Actions
Chatbot Flows
Rules
Note: Round Robin and Load-Based Routing are available on Business and Enterprise plans.
Instructions
What is Round Robin chat assignment?
Round Robin chat assignment distributes incoming chats among eligible team members in a sequential order.
When a new chat is assigned to a team with Round Robin enabled, Wati assigns it to the next eligible team member in the rotation. This helps distribute conversations evenly across the team.
Key features
Automatically assigns chats to eligible team members.
Distributes chats sequentially using Round Robin logic.
Allows admins to be included in the Round Robin assignment pool.
Can be configured through Default Actions, Chatbot Flows, or Rules.
Supports Auto Reassign with No Response to reassign unanswered chats.
What is Load-Based Routing?
Load-Based Routing assigns an incoming chat to the eligible online team member with the lightest workload instead of following a fixed sequence.
How Load-Based Routing works
When a new chat arrives in a Team Inbox with Load-Based Routing enabled:
Wati checks the current number of open tickets for the eligible online team members in the assigned team.
The chat is assigned to the team member with the lowest number of open tickets.
If all eligible operators are at maximum capacity, the chat is assigned to the bot.
This approach helps distribute chats based on each team member's current workload.
What is Auto Reassign with No Response?
Auto Reassign with No Response automatically reassigns a chat when the assigned team member does not respond within a configured time window.
This helps prevent chats from being missed or left unanswered when an assigned team member does not respond.
How Auto Reassign with No Response works
When a chat is assigned to a team member through Round Robin:
The configured response timer starts.
Wati waits for the assigned team member to send a reply.
If the team member does not reply within the configured time, the chat is automatically reassigned to the next eligible team member in the queue.
How to configure Round Robin chat assignment
You can configure Round Robin chat assignment in three ways:
Default Actions (legacy)
Chatbot Flows (recommended)
Rules (recommended)
Choose the method based on how you want chats to be routed and when you want the assignment to occur.
1. Via Default Actions (Legacy)
Go to Automations > Default Actions.
Find the chat assignment settings.
Enable the Round Robin option.
Configure the available assignment settings.
Click Save Settings.
Important: Round Robin chat assignment configured through Default Actions works when your incoming contact messages are assigned to the Default Team. It does not apply to contacts assigned to custom teams unless the chat is routed to that team through a supported automation flow.
How Round Robin works with Default Actions
When a new chat starts:
The chat is assigned to the Default Team.
If Round Robin is enabled, the chat is assigned to the next eligible team member instead of remaining with the bot.
Each subsequent chat is assigned according to the Round Robin sequence.
If a Keyword Action routes a chat to a specific team, Round Robin can assign the chat to an eligible member within that team.
How chat assignment works with other Default Actions
Default Action | Behavior when chat assignment is enabled |
Out-of-office reply | The message is sent according to the working-hours configuration. |
No agent online reply | The configured message can be sent instead of assigning the chat when no eligible agent is available. |
Welcome message | The welcome message can be sent before the chat is assigned, depending on the configuration. |
Delayed response | Assignment behavior depends on when the chat is considered open and when the automation runs. |
Fallback message | If a chatbot is triggered, its routing logic can determine the assignment. |
24-hour inactivity response | Works independently according to its configured behavior. |
Keep last assignee for expired/closed chats | Can keep the previous assignee instead of applying a new Round Robin assignment. |
Automations and Default Actions
When chats are assigned directly to a team member through Default Actions, some automations may not run as expected if they require the chat to first be assigned to the bot.
If you need automations or chatbot logic to run before assigning the chat to a team member, use the Chatbot Flow method.
2. Via Chatbot Flows
You can use a Chatbot Flow when you need to run chatbot logic or other actions before assigning the chat.
Go to Automations > Chatbots.
Open an existing chatbot or create a new one by clicking Add Chatbot.
Add an Assign Team node.
Select Round Robin and choose the team.
Click Save.
Note: Round Robin configured through Chatbot Flows supports incoming chats from WhatsApp, Instagram, and Facebook Messenger.
How assignment works in Chatbot Flows
When the chatbot assigns a chat to a team:
Round Robin assigns the chat to an eligible team member according to the Round Robin sequence.
If Skip users that are offline during assignment is disabled, chats may be assigned to offline users.
If the assignment type is set to Direct, the chat is assigned only to the team and not to an individual team member.
You can enable Direct lead to the contact owner when using HubSpot integration to assign leads directly to contact owners.
Chatbot Flow assignment settings work independently of Default Actions.
You can use Default Actions and Chatbot Flow settings together or separately.
3. Via Rules
You can use Rules to route specific incoming chats to a team based on a trigger and optional filters. Round Robin can then distribute the routed chat among eligible team members in that team.
For example, you can create a rule that triggers when a customer sends an incoming WhatsApp or Instagram message and use filters to narrow down which chats should be routed.
To configure Round Robin assignment through Rules:
Go to Automations > Rules.
Click + Create Rules to create a new rule.
Under Trigger, select the event that should start the rule, such as Incoming WhatsApp Message or Incoming Instagram Message.
Add Filters to narrow down which chats should be routed, if required.
Under Actions, select Route chat as the action type.
Under Routing, select To Team.
Under Choose Team, select the team to which you want to route the chat.
Enable the option Assign to users of the team in round-robin.
Save the rule.
Configure assignment settings
When configuring chat assignment through a Chatbot Flow or Rule, you can customize the assignment method and control which team members are eligible to receive chats.
Assignment options
You can configure the following assignment options:
Load-Based Routing — Assign chats to the eligible team member with the lowest number of open tickets instead of using sequential Round Robin assignment.
Auto Assign on Agent No Response — Automatically reassign a chat when the assigned team member does not respond within the configured time.
Direct Lead to Contact Owner — Assign the chat directly to the contact owner.
Operator availability
You can also control which team members can receive chats:
Assign chats to admins — Include admins in the assignment pool.
Assign chats outside working hours — Allow chats to be assigned even outside configured working hours.
Skip users that are offline during assignment — Exclude offline team members from the assignment pool.
These settings are the same whether you configure the assignment through a Chatbot Flow or a Rule.
Once the chat is routed to the selected team, the configured Round Robin assignment logic can distribute the chat among eligible team members in that team.
Important: Rules use Route chat to send the conversation to a team. You do not select Round Robin as the Rule action itself. Round Robin determines how the chat is assigned within the selected team.
Round Robin vs Load-Based Routing
Both options distribute chats among team members, but they use different assignment logic.
Assignment method | How chats are assigned |
Round Robin | Assigns chats sequentially to the next eligible team member in the rotation. |
Load-Based Routing | Assigns chats to the eligible online team member with the lowest number of open tickets. |
Load-Based Routing at maximum capacity | If all eligible operators are at maximum capacity, the chat is assigned to the bot. |
Use Round Robin when you want a predictable, sequential distribution. Use Load-Based Routing when you want assignments to reflect the team's current workload.
How Auto Reassign with No Response works with Round Robin
Auto Reassign with No Response works with chats assigned through Round Robin.
For example:
A new chat is assigned to Agent A through Round Robin.
The response timer starts.
Agent A does not reply within the configured time.
Wati automatically reassigns the chat to the next eligible team member.
This helps ensure that an unanswered chat does not remain with an unavailable or unresponsive team member.
Important considerations and limitations
Keep the following points in mind when configuring chat assignment.
Chats must be assigned to a single team
Round Robin and Load-Based Routing apply when a chat is assigned to a single team.
Chats assigned to multiple teams are not distributed through these routing methods.
Admins can be included in Round Robin
Admins can be included in the Round Robin assignment pool by enabling the option to include admins.
If the option is disabled, admins are not included in the Round Robin assignment pool.
Online and offline users
The Skip users that are offline during assignment setting controls whether offline users can be included in the assignment.
When enabled, offline users are skipped during assignment.
Working hours
When configured through Default Actions, assignment behavior can be affected by working hours and related settings.
If you need assignment logic to run outside standard working hours or during Holiday Mode, use a Chatbot Flow to control the assignment.
Automations and chatbots can affect assignment
If a chatbot or automation is triggered before the assignment takes place, its routing or assignment action can determine what happens to the chat.
Consider the order of your automation logic when configuring chat assignment.
Manual assignments
Chats that are manually assigned to a team member are not redistributed by Round Robin simply because Round Robin is enabled.
Reopened chats
The behavior of reopened chats depends on how the chat was previously assigned and the settings controlling expired or closed chats.
If Expired or Closed chat will not be assigned to Bot is enabled, the previous assignee can remain unchanged instead of applying a new Round Robin assignment.
Which assignment method should you use?
Use Round Robin when:
You want chats distributed sequentially.
You want a predictable assignment rotation.
You want to use Auto Reassign with No Response for unanswered assigned chats.
Use Load-Based Routing when:
Team members have different numbers of open tickets.
You want new chats assigned based on current workload.
You want to avoid assigning new chats to team members who already have a heavier workload.
Use Rules when:
You want to route only specific types of incoming chats.
You need to use triggers and filters to determine which chats should be routed.
You want to route chats to different teams based on specific conditions.
Conclusion
Wati provides multiple ways to distribute incoming chats across your team.
Round Robin assigns chats sequentially, while Load-Based Routing assigns chats based on the current workload of eligible online team members. You can configure Round Robin through Default Actions, Chatbot Flows, or Rules, depending on how you want to route conversations.
Auto Reassign with No Response adds another layer of protection by automatically moving a Round Robin chat to the next eligible team member when the original assignee does not respond within the configured time.
Together, these options help teams distribute conversations effectively and reduce the risk of chats being left unanswered.
Frequently Asked Questions (FAQs)
Round Robin and Load-Based Routing
1. What is Round Robin chat assignment?
Round Robin chat assignment distributes incoming chats among eligible team members in a sequential order. Each new chat is assigned to the next eligible team member in the rotation.
2. What is the difference between Round Robin and Load-Based Routing?
Round Robin assigns chats sequentially to the next eligible team member in the rotation. Load-Based Routing assigns chats to the eligible online team member with the lowest number of open tickets.
3. What happens if all eligible operators are at maximum capacity with Load-Based Routing?
If all eligible operators are at maximum capacity, the chat is assigned to the bot.
Auto Reassign with No Response
4. What is Auto Reassign with No Response?
Auto Reassign with No Response automatically reassigns a chat when the assigned team member does not respond within the configured time window. For Round Robin assignments, the chat is reassigned to the next eligible team member in the queue.
Assignment Rules and Eligibility
5. Can admins and offline users receive Round Robin assignments?
Admins can be included in the Round Robin assignment pool by enabling the option to assign chats to admins. The Skip users that are offline during assignment setting controls whether offline team members can receive assignments. When this setting is enabled, offline users are skipped.
6. Can automations or manual assignments affect Round Robin chat assignment?
Yes. A chatbot or automation triggered before assignment can determine how the chat is routed or assigned. Manually assigned chats are not redistributed by Round Robin simply because Round Robin is enabled.









