Skip to main content

Understanding operators, teams and chat assignment in Wati

Summary

Wati provides several ways to organize your team and manage customer conversations. By using operator roles, teams, automation rules, and chat visibility settings, you can control who can access conversations, how chats are assigned, and how customer inquiries are routed to the right people.

This guide explains how operator seats work, the difference between roles and teams, how chat assignment works, and how to configure chat visibility for different business structures such as support teams, sales teams, and multiple branches.

Instructions

Operator seats and subscriptions

Every Wati subscription plan includes a set number of operator seats, which determine how many operators can access the Wati workspace.

Wati’s Growth plan includes 3 operators by default. Pro and Business plans include 5 operators by default.

Additional operator seats can be purchased depending on your subscription plan.

The number of additional seats available and their pricing vary by plan.

Operator roles and teams

Wati helps you organize your staff using roles and teams.

Operator roles

Each operator is assigned a role that determines what actions they can perform within Wati.

Examples of roles include:

  • Admin

  • Operator

Roles control permissions such as managing settings, viewing conversations, and accessing features.

Teams

Teams help you group operators based on their responsibilities.

For example:

  • Customer Support Team

  • Marketing Team

  • Sales Team

An operator can belong to one or more teams.

Default Team

Every Wati workspace automatically includes a Default Team.

New incoming conversations are assigned to the Default Team unless additional routing rules are configured.

How chat assignment works

Incoming conversations can be handled by:

  • Chatbots

  • AI agents

  • Individual operators

  • Teams

What happens when a new chat is received?

When a customer sends a message:

  • The conversation is assigned to the configured automation, such as a chatbot, if one exists.

  • The conversation is also assigned to the Default Team.

  • Operators who belong to the Default Team, as well as admins, can view the conversation.

  • Any authorized operator can reply to the customer.

Last assignee routing

When an operator replies to a conversation, that operator becomes the last assignee for the chat.

For example:

  • A customer starts a conversation.

  • Operator 1 replies to the customer.

  • Operator 1 becomes the last assignee for that conversation.

When the same customer contacts your business again, the conversation can automatically be routed back to Operator 1.

To use this behavior, you must configure a Last Assignee automation rule.

Google, Meta or CTWA Ads

You can use automation rules to route leads from Click to WhatsApp Ads (CTWA) to the appropriate team, operator, or chatbot.

For example:

  • Create a Click to WhatsApp Ad on Meta, Google, or TikTok.

  • Set the default message in the ad to "service a".

  • In Wati, go to Automations > Rules and create a rule with the keyword "service a".

  • Configure the action you want the rule to perform, such as assigning the conversation to a specific team, operator, or chatbot.

When a customer clicks the ad and sends the default message "service a":

  • The conversation appears in the Wati Team Inbox.

  • The automation rule is triggered automatically.

  • The conversation is routed based on the action configured in the rule.

Chat visibility controls

Chat visibility settings allow you to control which conversations operators can access.

This feature is available on the Wati Business plan.

Example

Consider the following setup:

  • Operator 1 has the Operator role.

  • Operator 1 belongs to Team A.

  • Team A also includes Operator 2 and Operator 3.

If chat visibility restrictions are enabled for Operator 1:

  • Operator 1 can only view conversations assigned directly to them.

  • Operator 1 cannot view conversations assigned to other operators.

  • Operator 1 cannot view all conversations assigned to Team A.

This helps businesses restrict access to conversations and ensure operators only see the chats assigned to them.

Example: Managing multiple branches with teams and chat visibility

This example shows how to structure teams, operators, and automation rules when managing multiple branches or stores.

How incoming conversations are handled

  • Admins can view all conversations across the workspace.

  • All new incoming conversations are initially assigned to the Default Team.

  • If a chatbot is configured, the conversation is also handled by the chatbot before being routed further.

  • Automation rules can then route conversations to the appropriate manager or team.

Example setup

  • Team structure

Operator

Role

Team

User 1 (Boss)

Admin

Default Team

User 2 (Manager A)

Operator

Team A

User 3 (Support Agent A1)

Operator

Team A

User 4 (Support Agent A2)

Operator

Team A

User 5 (Manager B)

Operator

Team B

User 6 (Support Agent B1)

Operator

Team B

User 7 (Support Agent B2)

Operator

Team B

  • Automation rules

Create automation rules to route conversations to the correct branch manager.

Rule 1

  • Trigger: New incoming message

  • Condition: Message contains the keyword "branch A"

  • Action: Assign conversation to Manager A

Rule 2

  • Trigger: New incoming message

  • Condition: Message contains the keyword "branch B"

  • Action: Assign conversation to Manager B

Example workflow

  • A customer sends a message containing the keyword "branch A".

  • The conversation is assigned to Manager A.

  • Manager A reviews the conversation and assigns it to Support Agent A1.

  • Support Agent A1 handles the customer conversation.

  • Manager A can still view the conversation because they belong to Team A.

  • Manager A can reassign the conversation to another team member, such as Support Agent A2, if needed.

Recommended chat visibility configuration

Admin (User 1)

  • Role: Admin

  • Member of Default Team

  • Can view all conversations

Managers (Users 2 and 5)

  • Role: Operator

  • Assigned to their respective teams

  • Chat visibility: Disabled

With chat visibility disabled, managers can view conversations assigned within their team and continue supervising team activity.

Support agents (Users 3, 4, 6, and 7)

  • Role: Operator

  • Assigned to their respective teams

  • Chat visibility: Enabled

With chat visibility enabled, support agents can only view conversations assigned directly to them.

Best practice when using Chat Visibility feature

Enable chat visibility restrictions only for support agents who should handle their own assigned conversations.

Managers typically do not require chat visibility restrictions because they need visibility into conversations handled by their team members.

Frequently Asked Questions (FAQs)

Subscription and operator management

1. How many operators are included in a Wati subscription?

The number of operators included depends on the subscription plan. Wati's Growth plan includes 3 operators by default, while Pro and Business plans include 5 operators by default. Additional operator seats can be purchased depending on the subscription plan.

2. What is the difference between roles and teams in Wati?

Roles determine what actions an operator can perform in Wati, such as managing settings, viewing conversations, and accessing features. Teams are used to group operators based on their responsibilities, such as customer support, marketing, or sales.

3. What is the Default Team in Wati?

Every Wati workspace includes a Default Team automatically. New incoming conversations are assigned to the Default Team unless additional routing rules have been configured.

Chat assignment and automation

4. What happens when a new customer message is received?

When a customer sends a message, the conversation is assigned to any configured automation, such as a chatbot, if one exists. The conversation is also assigned to the Default Team. Operators who belong to the Default Team, as well as admins, can view the conversation, and any authorized operator can reply.

5. What is Last Assignee routing?

Last Assignee routing automatically routes future conversations from the same customer back to the operator who most recently handled the conversation. To use this behavior, a Last Assignee automation rule must be configured.

6. How can I route leads from Click to WhatsApp Ads (CTWA) to specific operators or teams?

Create a Click to WhatsApp Ad with a predefined message, such as "service a". In Wati, create an automation rule using the same keyword and configure an action such as assigning the conversation to a specific operator, team, or chatbot. When a customer sends the predefined message, the automation rule is triggered and routes the conversation accordingly.

Chat visibility and team management

7. What does the Chat Visibility feature do?

Chat Visibility controls which conversations an operator can access. When chat visibility restrictions are enabled, an operator can only view conversations assigned directly to them and cannot view conversations assigned to other operators or the rest of their team. This feature is available on the Wati Business plan.

8. How should Chat Visibility be configured for managers and support agents?

Managers should typically have Chat Visibility disabled so they can view and supervise conversations handled by their team. Support agents should typically have Chat Visibility enabled so they can only view conversations assigned directly to them.

9. How can Wati be configured for multiple branches or teams?

Create separate teams for each branch or department and use automation rules to route conversations based on keywords. For example, messages containing "branch A" can be assigned to Manager A and Team A, while messages containing "branch B" can be assigned to Manager B and Team B. Managers can then assign conversations to support agents within their team while maintaining visibility of those conversations.

Did this answer your question?