How to Assign WhatsApp Messages to Team Members

Once a WhatsApp number is shared across a team, the question stops being “how do we all see the messages” and becomes “how does everyone know which messages are theirs.” Assignment is the mechanism that answers that: it turns a pile of incoming conversations into a set of owned, trackable pieces of work.

This guide is a configuration walkthrough. It covers exactly how to set up each of the four assignment methods available in a WhatsApp team inbox: manual assignment, auto-routing rules, workload balancing, and department-based team inboxes, plus the unassigned queue that catches anything the others miss. If you’re looking for the broader day-to-day workflow (claiming etiquette, handoffs, avoiding double replies) rather than the setup steps, see our guide on managing WhatsApp messages with multiple agents.

Why assignment has to be configured, not assumed

The standard WhatsApp Business app has no concept of ownership. Every conversation sits in one shared thread, and whoever opens it first replies, or doesn’t. That’s fine for a single operator. With two or more agents on the same number, it fails fast:

• Two agents open the same conversation at the same time and both start typing a reply
• A message is marked “seen” by the customer but nobody actually answers it, because everyone assumes someone else has it
• A manager has no way to see who is meant to be handling what until a customer complains that nobody replied

A team inbox platform like Resolvenyx fixes this by giving every conversation a named owner, either a person or a team, at all times. Getting there takes about fifteen minutes of setup. Here’s exactly how.

Setting up manual assignment

Manual assignment is on by default in every Resolvenyx inbox, no configuration required, but it’s worth knowing exactly how agents use it day to day, since it stays the fallback method even after you layer on automation.

1. Open any conversation in the shared inbox. In the right-hand panel you’ll see an Assignee field, empty for new or unassigned conversations.
2. Click the Assignee field and either select Assign to me to claim it instantly, or pick a specific teammate from the dropdown to hand it to them.
3. The conversation moves out of the unassigned queue and into that agent’s personal “My conversations” view, so it’s clear to the whole team who owns it.
4. To reassign later, for a shift handover, escalation, or because the wrong agent claimed it, open the same field and pick a new owner. Add an internal note first so the next agent has context and the customer never has to repeat themselves.
5. If you run a small team, appoint one person each morning to triage the unassigned queue and manually hand out overnight messages before the day starts.

Manual assignment works well up to roughly four or five agents, where people can naturally self-select which conversations to take. Past that, it starts to eat into actual response time, which is where auto-routing rules take over.

Configuring auto-routing rules

Auto-routing rules assign incoming conversations the instant they arrive, before any agent has to look at them. Here’s how to build one:

1. Go to Settings → Automations → Routing Rules and click “New rule.”
2. Give the rule a name (e.g. “Route refunds to Billing”) and choose the trigger: New message received.
3. Set the condition. This is where you choose what the rule matches on: a keyword or phrase in the message body (“refund,” “cancel order,” “where is my delivery”), a contact tag (route anyone labelled “VIP” to a senior agent), or a time-of-day window (route anything outside 9am–6pm to an on-call agent or a next-morning queue).
4. Set the action: assign to a specific agent, or assign to a team inbox (covered below) so any available agent on that team can pick it up.
5. Set the rule’s priority relative to your other rules. Rules run top to bottom and stop at the first match, so put your most specific conditions (a named product issue) above your broadest ones (a general time-of-day catch-all).
6. Toggle the rule to Active and send a test message that matches the condition to confirm it routes correctly before relying on it live.

A few rules worth setting up in the first week: one keyword rule for your top two or three request types (billing, returns, technical support), one VIP tag rule if you have a priority customer segment, and one time-of-day rule so after-hours messages don’t sit untouched until morning. You can chain routing with tagging and internal notifications using automation workflows so the assigned agent gets flagged the moment a rule fires.

Turning on workload balancing

Keyword and tag rules are precise, but precision has a downside: if half your incoming messages happen to mention the same product, every one of them routes to the same agent while others sit idle. Workload balancing fixes this by distributing new conversations based on how busy each agent currently is.

1. Go to Settings → Automations → Workload Balancing and switch it on for the inbox (or for a specific team inbox).
2. Set a maximum active conversations per agent if you want a hard cap, useful for keeping quality high rather than just maximising throughput.
3. Choose which conversations the balancer applies to: all unassigned messages, or only those routed to it by a specific auto-routing rule (so keyword and tag rules still take priority, with balancing handling anything left over).
4. Open the Team workload panel from the inbox sidebar at any time to see each agent’s current active conversation count in real time, useful for spotting when someone needs help before it becomes a backlog.
5. Adjust the cap or the pool of eligible agents as your team grows; the balancer recalculates on every new incoming message, so changes take effect immediately.

Most teams turn this on once they pass four or five agents sharing an inbox: it keeps response times even across the whole team instead of one or two agents becoming the bottleneck while others wait for work.

Setting up team inboxes for department routing

Team inboxes group agents by department, Sales, Support, Billing, or whatever structure matches your organisation, so routing rules can target a whole team rather than one named individual. This is the structure to reach for once a single flat list of agents no longer reflects how your business is actually organised.

1. Go to Settings → Teams and click “New team.” Name it after the department it represents (e.g. “Billing”).
2. Add the agents who belong to that team. An agent can belong to more than one team if their role spans departments.
3. In your auto-routing rules, set the assignment action to Assign to team instead of a named agent, then pick the team. Any conversation matching that rule becomes visible to the whole team.
4. Within the team, agents can either claim conversations manually from the team’s shared view, or you can layer workload balancing on top so the platform distributes them evenly among team members automatically.
5. Optionally set a team-level escalation: if a conversation assigned to the team sits unclaimed past a set time, automatically notify the team lead or reassign it to a specific fallback agent.

For a full walkthrough of building out team structure, permissions, and department-specific inboxes, see our guide on creating a WhatsApp team inbox.

The unassigned queue: your safety net

Whichever combination of the above you use, one view matters more than the rest: the unassigned queue. It lists every conversation that hasn’t been claimed or routed yet, whether that’s a brand-new contact with no tags for a rule to match on, a message that doesn’t contain any of your configured keywords, or simply a conversation that arrived before your rules were set up.

1. Pin the unassigned queue as a saved view or filter in the inbox sidebar so it’s one click away at all times.
2. Set an internal alert, either a scheduled team notification or an SLA-style timer, if any conversation sits in the unassigned queue for longer than a set number of minutes.
3. Assign one rotating “queue owner” per shift whose job is specifically to sweep the unassigned queue and either claim or route anything the automated rules missed.

Treat the unassigned queue as your control panel, not a dumping ground: if it’s consistently non-empty, that’s a signal to add another routing rule rather than to hire another triager.

Ownership notifications keep everyone in the loop

Every assignment method above ends the same way: the agent who now owns the conversation gets notified instantly, whether they claimed it manually, a keyword rule routed it to them, or workload balancing picked them as the least-busy option. Notifications appear in-app and, depending on your settings, as a push or email alert, so agents don’t need to keep refreshing the inbox to find out what has landed on their plate.

This closes the loop that makes assignment actually work: it’s not enough for the system to know who owns a conversation, the agent has to know it too, immediately, without hunting for it.

A worked example: routing a billing message end to end

It helps to see the four methods working together rather than in isolation. Here’s what happens, in order, when a customer messages “I need a refund for my last order” on a WhatsApp number set up the way this guide describes:

1. The message arrives and, before any agent sees it, the keyword rule matching “refund” fires and routes it to the Billing team inbox rather than the general queue.
2. Inside the Billing team, workload balancing checks each Billing agent’s active conversation count and assigns the message to whoever currently has the fewest open conversations.
3. That agent receives an ownership notification the instant the assignment happens, so they see it within seconds rather than stumbling on it during a routine inbox check.
4. If the agent has to step away mid-conversation, they use manual assignment to hand it to a colleague, with an internal note explaining where things stand, so the customer never has to repeat the request.
5. Had the message not matched any keyword, for instance if the customer wrote “my order never showed up” instead, it would have landed in the unassigned queue, where the shift’s queue owner would pick it up manually and either claim it or route it themselves.

That’s the whole system in miniature: rules catch what they can predict, balancing spreads what rules send their way, notifications make ownership visible immediately, manual assignment covers handoffs and exceptions, and the unassigned queue makes sure nothing that falls outside all of the above goes unnoticed.

Which combination should you start with?

• Under 5 agents: manual assignment plus one or two keyword rules for your most common request types. Skip workload balancing and team inboxes for now.
• 5–15 agents: turn on workload balancing so volume spreads evenly, and start grouping agents into team inboxes once you have two or more distinct departments handling WhatsApp.
• 15+ agents or multiple departments: team inboxes as the primary structure, auto-routing rules directing traffic to the correct team, and workload balancing distributing the load within each team. Keep manual assignment available throughout as the fallback for edge cases.

None of these four methods are mutually exclusive. Most mature teams end up running all four at once: rules handle the obvious cases, balancing spreads what’s left, team inboxes keep departments organised, and manual assignment stays available for the exceptions that don’t fit a rule. Explore the rest of what a shared WhatsApp inbox can do on our features page.