Group chat
A question in another thread. Both phones still show the customer as unread.
One customer, one reply
How to stop agents replying to the same WhatsApp customer
The failure is ordinary: two people open the same unread chat and both send a slightly different yes. A staff group that asks “is anyone on this?” is not a lock. Assignment names an owner. Collision detection shows that someone is already viewing.
Keep WhatsApp Business. This page is the double-reply job, not the shared inbox hub.
The double send
Two slightly different answers, one customer
Two agents open the same unread WhatsApp. Both draft a confirmation. Both send. The customer now has two times, two prices, or two “yes we have it” notes, and no idea which one stands. That is collision. It is not a missing broadcast tool.
The Business app on one phone hides this because only one person can type. The moment a second person can see the same chat — a companion device, a forwarded screenshot, a shared PIN — the unread badge becomes a race. Hoping people “just check the group” is how the race stays on.
The WhatsApp shared inbox is the product encyclopedia. This page stays on the collision: what the viewing signal means, what assignment does that a group chat cannot, and what we will not claim. How you put a name on the thread is how to assign WhatsApp chats— a different job.
The signal
What “someone is viewing” actually means
In InboxBay, collision detection is live. When a teammate already has the conversation open, you can see that they are viewing or typing. It is a workspace signal, not a WhatsApp tick the customer sees. It does not send a reply for you. It does not lock the composer. It makes the second person visible before they become a second reply.
That is narrower than “the system prevents double replies.” Two people can still send if both ignore the signal. The job of the inbox is to stop the usual case: two quiet tabs, two drafts, two sends, no one knew. A staff WhatsApp group that asks “taking this?” still leaves both phones with the same unread customer thread. The question and the reply race in parallel.
Collision detection ships on Growth (AED 999 per workspace / month) and Business. Starter has assignment, notes, labels, and saved replies without that viewing signal. We will not pretend Starter includes it. List prices and the 7-day trial are on pricing.
Why the group fails
A staff chat is not a lock on the customer thread
The pattern is familiar. Someone pastes a screenshot into the team group. Two people type “I got it.” One of them is already on a call. The other sends. The first person also sends when the call ends. The group now has a post-mortem. The customer has two messages.
A group chat is a side channel. It does not share the composer, the draft, or the open tab. It does not mark the customer thread as owned. It adds a second place to look while the unread badge still shouts on every companion device. Meta’s own multi-agent benefit can assign chats inside the Business app — that is still WhatsApp’s app, with device caps, not a workspace history. The short distinction is on WhatsApp multi-agent.
Assignment
A named owner on the same thread the customer wrote. Visible before you type.
Viewing signal
A teammate is already in the conversation. You can wait or take it over on purpose.
Two tools, one failure
Assignment names the owner. Collision shows the other tab.
Assignment answers “whose job is the next reply?” Collision answers “is someone already in this thread right now?” You want both. Assignment without a viewing signal still lets two people open an unassigned chat at the same second. Collision without assignment still lets a resolved-looking thread sit with no owner after both people back away.
InboxBay has both, on the plans above. Notes and mentions sit on the same conversation so a specialist can look without becoming a third public reply. Saved replies reduce the time two people spend drafting the same “yes, we have that color.” None of that is AI answering. Suggested replies and autonomous answering are coming soon. A person still sends.
After the fact — who actually sent the message the customer is quoting — is how to see which employee replied. That page is attribution, not collision. We do not claim Chatwoot Enterprise audit logs we have not rebuilt.
What we will not say
A shared inbox does not make two replies impossible
We will not write “never again” or invent a percentage of collisions saved. The workspace makes the second person visible. The team still decides not to send. InboxBay connects to WhatsApp Business; it does not replace it and is not a BSP. The inbox core is Chatwoot MIT plus an InboxBay overlay. Demo: demo.inboxbay.work.
If your actual job is five people covering one number — Friday, after-hours, who holds the phone — that is how five employees use one WhatsApp number. If you are buying a process for open / pending / resolved, start at WhatsApp customer support for a team. Fit versus campaign suites: vs WATI, vs respond.io. No invented competitor prices.
Meta bills WhatsApp per delivered template or marketing message. InboxBay does not collect or mark those fees up. Collision detection does not change Meta’s 24-hour customer-care window.
FAQ
Straight answers
How do I stop two agents replying to the same WhatsApp customer?
Make ownership visible before anyone hits send. Assignment puts a name on the thread. Collision detection shows that a teammate is already viewing or typing. A staff group chat that says “is anyone on this?” is a hope, not a lock.
What does “someone is viewing” mean?
In InboxBay, collision detection is a live signal that another agent already has that conversation open — viewing or typing. It does not send a message for you. It makes the second person visible so they can stop.
Does assignment alone stop a double reply?
It makes the usual failure obvious: if the chat is already owned, opening it as a second reply is a choice. It does not physically block send. Collision detection is the extra warning when two people still land on the same unread.
Why does a WhatsApp group or staff chat fail at this?
Because the customer is not in that group, and the unread badge is still on every phone. Two people can both decide they are “taking it” while the group is still scrolling. The workspace shows the same thread once, with an owner and a viewing signal.
Is this the same as assigning chats?
No. Assignment is the workflow — unassigned queue, named owner, round-robin on Growth. This page is the failure mode: two replies, one customer. The assignment lander is a different URL.
Does InboxBay replace WhatsApp Business for this?
No. InboxBay connects to WhatsApp Business. Collision and assignment live in the workspace. The customer still writes the same number. InboxBay is not a BSP.
Who pays Meta’s WhatsApp message fees?
Meta bills WhatsApp per delivered template or marketing message. Conversation-based pricing was deprecated as of 1 July 2025. InboxBay does not collect or mark up Meta’s fees. You keep the WhatsApp Business number.
Keep reading
Related pages
See the other
person first.
Open the demo and look at a thread with an assignee. Collision detection is live on Growth — we do not sell it as magic that makes a second send impossible.
demo.inboxbay.work · Login and Start free go to the same workspace