29 September 2026
One conversation per contact across several numbers, made explicit with a sending-number picker; and a fix for new users whose first two hours of messages showed as read.
One thread per contact, whichever number they wrote to
Improved. When a customer has written to two or more of a workspace's WhatsApp numbers, WASync Chat keeps a single conversation with the whole history of that person. It now says which number each message belongs to: a small "via +number" badge on messages that came through a number other than the one selected for replying. The composer always shows the number a reply will go out from and, with two or more numbers, becomes a picker — it defaults to the number the customer wrote to last, and marks a WhatsApp Business number as "templates only" while it is outside the 24-hour window. Every send path follows the chosen number: text, files, templates, voice notes, notes, takeover and the stage or assignee changes written to the CRM.
New users saw their first two hours of messages as read
Fix. An employee opening WASync Chat for the first time had every incoming message of the following two hours counted as already read, in any conversation they had not opened themselves; on workspaces with team-shared read status, the team badge inherited it. The cause was a database session time-zone shift on the moment the inbox was first opened. It is fixed for all workspaces with nothing to configure. The rule is unchanged: whatever existed before a person's first visit is read, and unread accrues from that visit onward.
The same correction applies to the chat export — its date range was two hours off at each end — and to the Bot tab's activity window.
Changelog
New endpoints, improvements and breaking changes to the WhatsApp Platform API — newest first.
25 September 2026
Chat visibility rules per employee (all / department / only their records), enforced on the server, and automatic lead creation with round-robin assignment for chats from new numbers.