WhatsApp Team Inbox: Who Should See What

When a business moves from one phone to a shared team inbox, the first instinct is to give everyone access to everything. It feels friendly and it is simple to set up. It is also how a competitor ends up with your customer list when a salesperson leaves.

Three roles cover almost every Indian SMB

• Agent — sees only chats assigned to them, plus the unassigned queue. Can reply, add notes, and mark a chat resolved. Cannot export, cannot see other agents' conversations.
• Manager — sees everything in their team, can reassign, can read transcripts, can run reports. Cannot change billing or delete the account.
• Owner/Admin — everything, including billing, integrations and user removal. Keep this to one or two people.

More roles than this sounds thorough and usually just confuses people. If you cannot explain a role in one sentence, it should not exist.

The permissions that actually matter

Most arguments about access are really about four specific abilities:

1. Export contacts. This is the one that loses you a customer list. Restrict it to owners, and know that an export happened.
2. See customer phone numbers in full. Some teams mask the middle digits for junior agents. It feels paranoid until you have had a leak.
3. Send broadcasts. One careless campaign can damage your quality rating for weeks, so broadcast rights belong with whoever understands the consequences.
4. Delete or edit notes. Notes are your record of what was promised. Editing history should leave a trail.

Assignment: pick one model and stick to it

Round robin spreads load evenly and suits teams where any agent can handle any enquiry. Ownership keeps a customer with the same person forever, which suits high-value or long sales cycles. Skill-based routes by language or product, which is common in Indian teams where one agent handles Marathi and another handles South India.

Whichever you choose, define what happens when nobody picks up. An unassigned chat with no owner is the single biggest source of lost enquiries we see, and it is invisible until you measure it.

Handover without the customer noticing

Customers hate repeating themselves. Three rules make handovers clean:

• The outgoing agent leaves a one-line note before transferring — what the customer wants and what was promised.
• The incoming agent reads the thread before typing. Obvious, routinely skipped.
• Never announce the transfer twice. "I am transferring you" followed by "Hi, I am Rahul, how can I help?" tells the customer nobody read anything.

If a bot is involved, the same applies — the handover rules are in our chatbot examples guide.

When someone leaves the company

Have this ready before you need it:

1. Remove their login the same day, not the same week.
2. Reassign their open chats to a named person, not to "unassigned".
3. Check the export log for the previous 30 days.
4. If they used a personal number for any customers, those customers need a message from the company number introducing their new contact.

What to review every month

• Who has admin rights, and whether they still need them
• How many chats sat unassigned for more than an hour
• Exports performed, by whom
• Agents with no activity — dormant logins are a security hole

Ten minutes a month. It is the cheapest insurance in the whole system.

A permission matrix you can copy

Most teams argue about roles in the abstract and then grant everything. Decide it once, as a table, and apply it. This is the set that works for a team of three to fifteen people in India:

The last row is the one to think hardest about. If your agents are on contract, or churn quickly, masking all but the last four digits of a customer's number costs them nothing — they reply inside the chat anyway — and removes the single easiest way for your customer list to leave with someone.

The four leaks nobody closes

Permissions stop the obvious route out. These four are how customer data actually walks out of an Indian SMB, and none of them is fixed by a role dropdown.

1. Shared logins. One account called "sales" used by four people means no audit trail at all: you can see what was said and never who said it. One login per person is not a licensing detail, it is the whole point of having an inbox.
2. Screenshots. You cannot prevent them. You can make them pointless by masking numbers, and you can make them traceable by keeping a monthly review of who opened which chats.
3. Agents moving the conversation to their personal number. Usually well meant — "customer wanted to reach me directly" — and it takes the relationship off your system entirely. Say explicitly that it is not allowed, and give agents a way to be reachable inside the official number instead.
4. Exports that were only supposed to be used once. A spreadsheet pulled for a campaign in March is still on somebody's laptop in October. Restrict export to the owner, and when an export is needed, agree beforehand what happens to the file afterwards.

Handover, after hours and holidays

A shared inbox fails most visibly at shift boundaries, because a customer who was mid-conversation at 7 pm does not care that the shift changed. Three rules cover it:

• Nothing is left assigned to someone who has gone home. At the end of a shift, open conversations move to the next shift or to a queue, not to an empty chair.
• The twenty-four hour window is the real clock. A customer message opens a window in which you can reply freely; after it closes you need a template. A chat left sitting overnight often means the cheap reply is no longer available in the morning. Make that window visible to supervisors.
• Say when you will be back. An after-hours auto-reply that gives a specific time — "we reply between 10 am and 7 pm, Monday to Saturday" — produces far fewer repeat messages than one that says "we will get back to you soon".

What to log, and how long to keep it

Decide this before you need it, because the day you need it is the day of a dispute. A workable default for a small Indian business:

• Who replied to whom, with timestamps — keep as long as you keep the conversation. This is what answers "who promised the customer a refund?"
• Role and permission changes — keep a year. It answers "when did this person get broadcast access?"
• Exports: who, when, how many rows, why — keep a year. Four lines in a shared sheet is enough if the tool does not do it for you.
• Opt-ins and opt-outs — keep for as long as you hold the contact, plus a buffer. This is a compliance record, not an analytics one.

Then actually read it once a month. An audit log nobody opens is the same as no audit log, and it takes ten minutes: new users, removed users, exports, and any chat opened by someone it was not assigned to.

Frequently Asked Questions

How many roles does a small team need in a WhatsApp inbox?

Three — agent, manager and owner. Agents see only their own chats and the unassigned queue, managers see the whole team and can reassign, owners control billing and user access. More roles than this usually create confusion rather than control.

Should agents be able to export contacts?

No. Export is how customer lists leave a business. Keep it with owners only, and make sure exports are logged so you know when one happened and who ran it.

What should happen to chats when an employee leaves?

Remove their login the same day, reassign their open chats to a named person rather than a queue, and review the export log for the previous month. If they handled customers on a personal number, introduce the replacement from the company number.

Should agents see the customer's full phone number?

Not by default if your agents are on contract or turn over quickly. They reply inside the chat, so the full number adds nothing to their work and is the easiest way for your contact list to leave with someone. Masking all but the last four digits, with the owner still able to see full numbers, keeps service working and closes the gap.

Is one shared login for the sales team acceptable?

No, and it defeats the point of a team inbox. With a shared login you can see what was said but never who said it, so you cannot resolve a dispute, measure anyone, or remove access when one person leaves. Give every person their own login and keep the roles narrow.