Client and work management
Several branches, one shared inbox for every message
How to handle email, WhatsApp and form messages from several offices without leaving a conversation without an owner.
To centralize conversations from several branches, bring the email, WhatsApp Business and forms of every office into one shared inbox, and give each conversation a visible owner. Anyone with permission then sees which messages are still unanswered, whichever office they came into. The conversation is stored with the client who wrote it and no longer depends on one office's mailbox.
Picture a maintenance company with an office in the capital and another in a city a few hours away. Each office has its own email address, someone answers WhatsApp on the reception phone, and the website forms land in the manager's mailbox. A corporate client with facilities in both cities writes to both offices about the same fault. Two technicians give two different answers, and nobody notices until the client calls, annoyed, asking which answer to believe.
Why each office ends up with its own version of the client
When each branch handles its own channels, each keeps one piece of the story. The capital's email knows what was quoted, the regional WhatsApp knows the technician already visited the site, and the form the client filled in sits in one person's mailbox. Nobody is hiding anything, yet nobody has the whole picture.
The problem grows with every new office. Management can no longer tell what is pending without asking each office, and when someone goes on vacation their conversations sit still in a mailbox nobody else opens. Losing control as you add locations rarely comes from the number of messages. It comes from having no single place where all of them appear with their owner.
Email, WhatsApp and forms in the same list
In AgentticCRM's Inbox and WhatsApp you connect your organization's email account with its address, server and password, and a test button checks that it can receive and send before you save it. What you do there happens in your real mailbox: reply to, archive or delete an email and it looks the same in the mail program you already used.
Your organization's WhatsApp Business number works as a shared queue, with the state of each message: sent, delivered, read. Forms come in as one more conversation, and each form reaches the people you choose. That lets the service request form on one city's page reach that office's team, for example, without creating a separate inbox.
Every conversation hooks onto the client it belongs to. For email, the inbox tries to recognize the sender by their address; on WhatsApp you confirm it yourself. From then on the conversation lives in the client's record, and whichever office answers next reads what was already said.
Unassigned and Claim: who answers each message
New messages land in Unassigned. Whoever is going to handle one clicks Claim and the conversation moves to their name; if it turns out to belong to someone else, it can be handed over. That removes the case of a client getting two answers from two offices, because everyone sees the conversation already has an owner.
It helps to agree on a simple rule between branches. For example: every morning someone from each office checks Unassigned and claims what belongs to their area, and anything without a clear area goes to one named person. The rule can change over time, as long as it is written down and everyone knows it.
What each person sees and what management sees
Each person sees their own conversations, and whoever has the permission sees every conversation in the organization. For a manager who oversees several branches, that permission is the overall view: what came in, who has it and what is still unanswered. Pinning, prioritizing or archiving a conversation changes the list of the person who does it and nobody else's, so each office can sort its own work without disturbing the other.
Sometimes the office that receives the message is not the one that knows the case. With the Discuss with the team button, the client's email or WhatsApp is sent to an internal channel in Team chat. The other branch comments there, and you then reply to the client once from the inbox. The client does not see that internal conversation.
Moving from one mailbox per office to a shared inbox
- List the channels each branch uses today: email addresses, WhatsApp numbers and website forms.
- Connect the organization's email and run the test button before saving.
- An administrator connects the official WhatsApp Business account from the inbox settings. If the account has several numbers, you pick by the visible name and number. Until the test passes, the account shows as pending.
- Decide who each form reaches, based on which office handles each kind of request.
- Agree on the Unassigned rule and review it with both offices at the end of the first week.
If a client writes on WhatsApp and more than 24 hours have passed since their last message, the editor switches to your approved templates and shows you the exact message before it goes out. Have those templates ready before you move every branch over.
If each client's history is still scattered across mailboxes, the article on why client context belongs in the CRM explains how to bring it into one record. And if, once the inbox is in order, you are thinking about adding artificial intelligence, read the five tests for an AI CRM in a small business first.
Frequently asked questions
What happens to the conversations if someone at a branch leaves the company?
They stay. The conversation belongs to the organization and remains in the client's record, with its full history, for whoever takes over.
Does the artificial intelligence answer for the branches after hours?
No. The AI prepares a draft from the conversation, and you edit, accept or discard it. Sending is always decided by a person on the team.
Can I create a client from a WhatsApp chat?
Yes. From the thread you save the person, link them to a company and create the opportunity with its owner and its follow-up task, without retyping anything.