Attribution
How to see which employee replied on WhatsApp
The Business app shows a number. The manager who asks “who promised Tuesday?” needs a named assignee and a thread they can search. InboxBay has that in the conversation. It does not have Chatwoot Enterprise audit logs rebuilt.
Assignee + history in the thread. Not Chatwoot EE audit logs. Shared inbox hub.
“Who told them Tuesday?” is an attribution question
WhatsApp Business shows the customer a business number. It does not give the manager a named agent history they can search like a mailbox sent folder. When the customer says “you already confirmed,” someone has to open a thread and see which employee was on it.
Companion devices and Meta’s multi-agent benefit still live inside WhatsApp’s app. Customers do not see which device sent a message. That is Meta’s design, not an InboxBay setting. A workspace puts an assignee on the conversation and keeps the messages that land after you connect. That is the log we have.
This is not collision — two people typing now. That is stop agents replying to the same customer. It is not the assignment how-to. That is how to assign WhatsApp chats. This page is after the fact: can you name the person.
A number, a device list, not a searchable agent file
The public identity is the WhatsApp Business number. With multi-agent, Meta lets you name a linked device and assign chats inside that app. The customer still does not see the agent. The manager still does not get a helpdesk-style sent history they can filter by employee the way they filter a shared mailbox. Device caps and the 14-day primary-phone rule are on the multiple-agents guide. We do not reprint them here.
If the only record is the phone that sent the tick, the record leaves with the phone. That is the attribution failure: the closer resigns, the handset is wiped, and “who promised Tuesday” becomes a guess in a staff group.
Assignee on the conversation, history in the thread
Once the Business account is connected, new chats land in the workspace. Each conversation can show a team and/or an individual assignee. Messages that arrive after the connect stay on that thread, with notes and labels. You can search the workspace for the customer and read what was sent. That is the named history we will stand behind.
Do not plan on a full WhatsApp archive import the day you connect. Ask before you assume last year’s chat moves. We do not invent a reporting suite, an agent scorecard, or a productivity dashboard. Conversation status and search are what we have.
Assignee
A named owner on the thread. Visible to the team, not to the customer.
Thread history
Messages that landed in the workspace, in order, with the note beside them.
Search
Find the customer and the promise. Not a BI export.
Not EE audit logs
No rebuilt Chatwoot Enterprise trail of logins, views, or exports.
We have not rebuilt Chatwoot Enterprise audit logs
InboxBay is a Chatwoot MIT core plus an InboxBay overlay. Chatwoot’s Enterprise edition has audit features we have not rebuilt and do not sell. If you need login history, permission-change trails, or “who viewed this conversation” as a compliance export, stay on a product that ships that — including Chatwoot itself if you self-host the edition that has it. Our Chatwoot alternative page is a fit note, not a claim that we beat Chatwoot.
What you can do today: open the thread, see the assignee, read the messages and the private notes, mention the person who should look next. That answers most “who replied” questions for a small shop. It does not answer an auditor who wants an enterprise log.
InboxBay connects to WhatsApp Business. It does not replace it and is not a BSP. Plans are Starter AED 499, Growth AED 999, Business AED 1,999 per workspace / month, 7-day trial on Ziina. Demo: demo.inboxbay.work. AI suggested replies are coming soon. A person still sends every message you will later want to attribute.
Meta bills WhatsApp per delivered template or marketing message. InboxBay does not collect or mark those fees up. Attribution in the workspace does not change what the customer sees on WhatsApp.
Straight answers
Can I see which employee replied on WhatsApp?
On the WhatsApp Business app the customer sees your business number, not a named agent the manager can search later. In InboxBay the conversation has an assignee and a message history in the thread. That is what you can look up. We do not have Chatwoot Enterprise audit logs rebuilt.
Does the customer see the agent’s name?
They write the WhatsApp Business number they already saved. They do not see workspace assignment, notes, or which employee owns the thread. Replies come from that number.
Is this an enterprise audit log?
No. We have not rebuilt Chatwoot EE audit logs — login history, export trails, “who viewed this.” What we do have is the assignee on the conversation and the messages in the thread. Do not buy InboxBay for a compliance audit suite we do not ship.
Can I search who handled a customer last month?
You can search the workspace for the thread, read the history that landed after you connected, and see the current assignee. Do not plan on a full WhatsApp archive import the day you connect. We do not invent a report builder.
How is this different from collision detection?
Collision is two people typing now. Attribution is who sent the message the customer is quoting later. Different jobs, different pages.
Does this replace WhatsApp Business?
No. InboxBay connects to WhatsApp Business. It is not a BSP. Meta still operates the channel.
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.
Related pages
A name on the
thread you can open.
Open the demo and look at assignee plus history on a conversation. Do not expect an enterprise audit export we have not shipped.
demo.inboxbay.work · Login and Start free go to the same workspace