WhatsApp for teams: how several people write from one number

Example scenario: Picture a furniture shop in Eskişehir. The business number is on the phone by the till. The cashier sees the morning price question, a sales adviser opens the same customer's photo at noon. In the evening the customer asks about delivery, and nobody knows who should read the earlier chat to reply.

The linked-device feature of the WhatsApp Business app allows a limited number of devices. Everyone sees the same chat list; there is no assignment, ownership, or permission split. Two people can answer the same customer at once, or both can assume the other has.

Another route is giving each salesperson a separate business number. Now the customer does not know which number to write to, the company loses its single voice, and when a salesperson leaves, that number's history is on nobody's screen.

A shared inbox gathers the number's messages on a software screen instead of a phone. The team looks at the same list, but each line carries a name. A conversation can be handed from one person to another; the history is not lost, because it lives in the software, not on a phone. What really changes here is that you can see who read and answered what. When a customer says "I wrote to you yesterday", who read it, who replied, and why it was late are visible in the list. Whether the problem is the person, the workload, or the rule is answered from the record, not by guessing.

• Every conversation has an owner.
• Handing over is one action; the history moves to the new owner intact.
• An unanswered conversation stays at the top of the list.
• The conversation is tied to the customer record; the history stays even when the team changes.
• Who can see what is set by role.

Take a sales team in İstanbul covering both sides of the city. When a long-standing client on the Asian side writes, the conversation should go to their salesperson. A price question from a new number goes to the next available person. A return request goes not to sales but to the operations owner. In Corex360 the conversation is assigned to an owner and the unanswered one comes forward; you write the redistribution rule. The decision stays with you. You can read how writing rules for the assistant works on handing the process to the X AI assistant.

A quote request that arrives on Friday evening sits in the middle of the chat list on Monday morning. Weekend messages push it further down. On a shared phone the only safeguard is someone remembering to scroll. There is also a silent kind of unanswered message: the conversation a salesperson reads and leaves to answer later. On a shared phone it shows as read and drops out of sight. In a shared inbox, read does not mean answered; the conversation stays open until a reply goes out.

In a shared inbox, unanswered conversations are sorted by whether they are waiting for a reply, not by time. Which customer is waiting on whom shows in a single list. In Corex360 that list sits where staff and the manager look in the morning.

The only purpose of this visibility is continuity; the record is kept so a salesperson can hand work over to the team with confidence. When a salesperson leaves, the customer's history should stay with the company and the newcomer should continue from where it stopped. Business chats running on personal phones make that impossible.

The manager's question is short: which customer is waiting for a reply today, and from whom? Seeing that list does not require opening every conversation. Only people with permission read the content.

The distinction matters to employees as well. Salespeople know their customer messages sit in the company record and that who may read them follows a rule. When the rule is clear, visibility is taken not as distrust but as a shared way of working. Writing the rule down and sharing it with the team is one of the first jobs in the first week of a shared inbox. A salesperson who knows who can see their customer's conversation has no reason to hold back when filling in the card.

In Corex360 messages are kept on the customer card, on Corex360 Cloud or on your own server. Access is role-based and logged, and personal data is processed under KVKK (Turkey's personal data protection law). Who sees which card is set up to match the team's structure. You can read how this is set up on bringing channels into one inbox with WhatsApp CRM.

The office team opens the inbox in the browser and the rep in the field opens it in the mobile app; both see the same customer card. A salesperson on a client visit sees a message sent to the office on their phone and replies. The reply goes out from the company number, and the conversation stays on the card. A colleague back in the office that evening reads the same conversation from where it stopped. We gathered common questions about mobile use on Corex360 mobile app questions.

In the first week the most common remark is that people used to just pick up the phone and reply. In a shared inbox there is a pause before replying: whose conversation is this, and what does the customer card say? That pause does not slow the reply; it stops the same customer from getting two different prices.

The second habit is handing over. At a home appliance service in Kayseri, the evening shift takes over the repair conversations the day team left open. The customer does not describe the same fault twice, because the earlier conversation is on the card.

The third is to stop writing for the business from personal phones. This is the hardest habit, because customers know the salesperson's personal number. During the move, customers are told the business number, and work arriving on the salesperson's personal line is moved onto the card. In the demo we open a conversation with your own number, hand it to a colleague, and watch together how an unanswered message comes forward in the list.

The Messaging window gathers WhatsApp, Instagram and web chat in one inbox. Above the list sit a search box, a line selector and an Assigned to me filter, and every conversation is assigned an owner. A conversation can be turned into an opportunity and then carries the opportunity number as a badge. A reply can quote a message and mention a colleague by name. The conversation is kept on the customer card, not on a salesperson's phone.