When one team WhatsApp stops keeping up

A shared WhatsApp inbox lets several people answer the company's single number without stepping on each other: every chat lands in a common queue, someone takes it, and the conversation is filed with the client it belongs to. You need one when the office phone, or the group chat where screenshots get forwarded, no longer tells you who replied to what. In AgentticCRM that queue is part of the inbox and WhatsApp feature, next to email and forms.

Picture a ten-person agency with one WhatsApp Business number. At first the receptionist handles it from her phone. Then WhatsApp Web goes onto two more computers, and someone starts an internal group to pass client messages to whoever should handle them. Six months later a client writes on Monday asking about a quote, two people answer with different prices, and nobody replies to the client who wrote on Friday afternoon.

Signs the shared number has overflowed

The trouble is rarely the number of messages. It shows up when the team can no longer answer simple questions about its own chats:

• You cannot tell which conversations are still unanswered, because "read" on the phone does not mean "handled".
• Two people reply to the same client, or nobody does, because each assumed the other would.
• What the client asked for on WhatsApp is missing when someone opens their record, so you have to search the phone of whoever took it.
• When someone goes on vacation or leaves the company, their conversations leave with their phone.
• Screenshots travel from one internal group to another and nobody knows which version was sent.

If two or three of these sound familiar, the channel has no owner, and that is where the next client will slip away.

What changes with a shared WhatsApp inbox

In a shared inbox, new messages arrive in a list called Unassigned. Whoever is going to answer clicks Claim and the conversation moves to their name, where everyone can see it; it can also be handed to someone else. That settles the question of who replies.

Each person sees their own conversations, and whoever has the permission sees the number's full queue, which is what a coordinator needs to know what is still pending. Pinning a chat, marking it as priority or archiving it changes only your list and leaves your colleagues' lists alone.

For every message you send you can see whether it was sent, delivered or read. And in the same thread you can paste a screenshot before replying, without going through the internal group.

The chat stays in the client's record

The difference you notice most after three months is where the conversation ends up. On WhatsApp you confirm which client each chat belongs to, and from then on the conversation lives in that client's record. Whoever opens the client later sees what was said without asking anyone for their phone.

From the thread itself you can save the person as a contact, link them to their company and create an opportunity with an owner and a follow-up task, without typing the details again. If what comes in is a problem that needs formal follow-up, the chat can become a ticket with a priority and a history. And if someone leaves the team, their conversations stay with the organization, with the full history, for whoever takes over.

The 24-hour rule and templates

WhatsApp Business has a rule the whole team should know. For 24 hours after the client's last message you can reply with free text. After that, you can only write to them with approved templates. In AgentticCRM the editor switches to your templates on its own when the window closes, asks you for the details they are missing and shows you the exact message before you send it.

In practice this rewards answering on time. A queue where unassigned chats are in plain view helps the Friday client get an answer before their window closes.

What the inbox leaves to your team

The inbox does not auto-reply to your clients; every message is sent by a person on the team. If your organization has AI configured, the Assistant, or the ChatGPT or Claude you connect, can leave you a draft with the context of the conversation. You edit it, accept it or discard it, and sending is up to you.

Connecting the number is also a person's job: an administrator connects the organization's official WhatsApp Business account, picks the number by its name and runs a test. Until the test passes, the account shows as pending.

A shared inbox will not fix a number nobody checks, either. Agree on who watches Unassigned at each time of day and what they do when a chat asks for something outside their area. If you are weighing up the tool, also compare what it costs with what it takes to set up, as we cover in license or implementation. And if you want to see how the conversation fits into the rest of the client work, client context belongs in the CRM goes into more detail.

Frequently asked questions

Can several people answer the same WhatsApp number?

Yes. They all work from the same queue for the organization's number. Each conversation has a visible owner and whoever has the permission sees the full queue.

What do I need to connect the number?

Your organization's official WhatsApp Business account. An administrator connects it from the inbox settings, picks the number and runs the test; once it passes, the first incoming message shows up in Unassigned.

Does the inbox reply on its own after hours?

No. Messages arrive in the queue and the team answers them. AI, if configured, only prepares drafts that a person reviews before sending.

What happens to the chats of someone who leaves the company?

They stay with the organization and in each client's record, with their full history, and can be assigned to someone else.