When an agent sends a message from the linked WhatsApp mobile or desktop app, WAHA receives it as fromMe: true.
Right now the Chatwoot integration mirrors those messages as private notes:
const private_ = message.private ?? payload.fromMe;
That prevents a send loop, which makes sense, but it also means Chatwoot does not treat the message as a normal agent reply.
As a result, things like waiting_since, reply reporting and conversation status can stay incorrect even though the agent actually replied from WhatsApp.
This matters for teams using companion/linked devices, where agents often reply from the native WhatsApp app while supervisors use Chatwoot to see the full conversation history.
Would it be possible to add an optional mode for native fromMe messages, for example:
conversations.nativeAppOutgoing = private-note | public-echo
with private-note remaining the default for backward compatibility?
In public-echo mode, a message with:
could be created in Chatwoot as a normal public outgoing message with:
and a WAHA-specific marker so the Chatwoot webhook handler knows not to send it back to WhatsApp again.
That would keep the current loop protection while allowing native WhatsApp replies to behave like real outgoing replies inside Chatwoot.
Checked on WAHA 2026.8.2.
When an agent sends a message from the linked WhatsApp mobile or desktop app, WAHA receives it as
fromMe: true.Right now the Chatwoot integration mirrors those messages as private notes:
That prevents a send loop, which makes sense, but it also means Chatwoot does not treat the message as a normal agent reply.
As a result, things like
waiting_since, reply reporting and conversation status can stay incorrect even though the agent actually replied from WhatsApp.This matters for teams using companion/linked devices, where agents often reply from the native WhatsApp app while supervisors use Chatwoot to see the full conversation history.
Would it be possible to add an optional mode for native
fromMemessages, for example:with
private-noteremaining the default for backward compatibility?In
public-echomode, a message with:could be created in Chatwoot as a normal public outgoing message with:
and a WAHA-specific marker so the Chatwoot webhook handler knows not to send it back to WhatsApp again.
That would keep the current loop protection while allowing native WhatsApp replies to behave like real outgoing replies inside Chatwoot.
Checked on WAHA
2026.8.2.