One WhatsApp Number, Several Admins: Shifts, Handover and Who Owns Each Chat

A customer asks at 11:50 whether an order can be delivered today. The morning admin reads it and goes to lunch, intending to check with the warehouse. The afternoon admin sees the message marked as read and assumes it was handled. At 16:00 the customer writes again, less politely. Nobody was careless. The team shares one WhatsApp number and has no rule for who owns a conversation.

The three failures

Shared numbers fail in three recognisable ways.

• Double replies. Two admins answer the same question, sometimes with different answers.
• No reply. Each admin assumes another has it. A message that has been read looks finished.
• Lost context. The afternoon admin does not know what the morning admin promised, so the customer explains everything again.

All three come from the same gap: the chat has no owner and no status.

Rule 1: every chat has one owner

At any moment, one named person is responsible for each open conversation. Others may read it. Only the owner replies, unless the chat is handed over.

How a chat gets an owner:

• First to open it claims it, visibly, by assigning it to themselves.
• Or by rule: new enquiries to sales, order questions to operations, complaints to a senior person.
• Returning customers go back to their previous owner where possible. People like being recognised.

A team inbox makes this visible with an assignee on each conversation. On a shared phone or WhatsApp Web with no assignment feature, labels with admin names are a workable substitute.

Rule 2: every chat has a status

Four statuses are enough:

• New. Nobody has replied.
• In progress. Owner is working on it and the next step is ours.
• Waiting for customer. We replied and the next step is theirs.
• Done. Nothing more to do.

The status answers the question that "read" cannot: is anything still owed here? At any time, the list of "New" and "In progress" is the list of work.

Rule 3: promises get a note and a time

Any reply that contains a promise, such as "I will check and get back to you", needs two things recorded on the conversation:

• What was promised.
• By when.

"Checking delivery slot with warehouse, reply before 14:00." If the owner leaves, the next person sees exactly what is outstanding. Without the note, a promise lives in one person's memory and leaves with them at the end of the shift.

Rule 4: a handover at every shift change

Five minutes, written, at the end of each shift:

1. Open chats needing action, each with customer, promise and deadline.
2. Reassign them. Each open chat gets a new owner from the incoming shift. Leaving them under someone who has gone home is how messages die.
3. Anything unusual. Out-of-stock items, a courier delay, a price change, a promotion ending.
4. Complaints in progress, and what has been offered.

A template helps:

• Open and urgent:
• Waiting for customer:
• Notes for the next shift:
• Complaints:

Post it where the team already looks, such as the internal group, at the same time every day.

Rule 5: how to take over a chat

Sometimes the owner is unavailable and the customer is waiting. A simple rule prevents collisions:

• If an "In progress" chat has had no reply for longer than the agreed time, for example 30 minutes in business hours, anyone may take it.
• The person taking it reassigns it to themselves first, then replies.
• They read the notes before writing.
• They tell the previous owner.

Reassign, read, reply. In that order.

Rule 6: after hours

Decide and state what happens when nobody is on shift.

• An automatic reply giving the hours and when a reply can be expected.
• Or an AI assistant that answers routine questions and leaves anything else for the morning with a summary.
• A morning routine: the first person in clears everything marked "New" before anything else.

What matters is that the customer is told the truth about when a person will answer.

Consistency across admins

Customers notice when two admins give different answers.

• One price list and one policy page that everyone uses.
• Saved replies for common questions, written once and reviewed.
• A sign-off so customers know who they spoke to.
• A place to ask. When an admin is unsure, they ask in the internal group and wait. A confident wrong answer costs more than a short delay.

Measuring whether it works

Three numbers, weekly:

• Chats unanswered beyond the target time.
• Chats with two different admins replying within a short interval, a sign of collisions.
• Open chats without an owner at shift change. This should be zero.

Tools

These rules can be run with labels and discipline on a shared device, up to a point. Beyond two or three admins, a team inbox that shows the assignee, status and internal notes on each conversation removes most of the manual work. Polynusa's sales inbox works this way, with several team members on one number and notes on each contact. See the pricing page for what each plan includes.

Summary

Give every conversation one owner and one status. Record every promise with a deadline. Hand over in writing at each shift change and reassign open chats. Allow takeovers by a clear rule: reassign, read, then reply. Tell customers honestly what happens after hours. With these rules, three admins on one number look to the customer like one attentive person.

FAQ

How many people can reasonably share one business WhatsApp number?

There is no fixed limit that suits everyone. What matters is whether every chat has one clear owner. Two people without rules cause more double replies than six people with ownership, statuses and handover notes.

What should a shift handover note contain?

Open conversations that need action, with the customer name, what was promised and by when; anything unusual such as a stock problem or a price change; and complaints in progress. It should take five minutes to write and two to read.

Should each admin sign their name on replies?

It helps in most service businesses. A short sign-off or name lets the customer know who they are talking to and makes it easy to trace who said what. Keep it brief and consistent across the team.