30 September 2026
Message media now lives in EU object storage and is served through short-lived signed links; deleted WhatsApp messages and edits apply on QR connections; voice notes sent through the WhatsApp Business API arrive as voice notes; a real health check behind every deploy.
Media in EU object storage, served through signed links
Changed. Images, voice notes, videos and documents exchanged over WhatsApp are now stored in an EU-jurisdiction object store (Cloudflare R2) and handed out only through short-lived signed links (15 minutes for the CRM widget and WASync Chat, 30 minutes for a send in progress, 24 hours for a chat export). The same 90-day retention applies, and deletion removes the object store copy too. Nothing changes for what you see in Bitrix24, Pipedrive or WASync Chat; links you copied earlier keep working until they expire.
Deleted and edited WhatsApp messages on QR connections
Fix. When a customer deleted a message for everyone or edited it, the change reached us with a short message id we did not recognise, so the conversation in WASync kept the original. Both now apply within seconds: a deleted message shows as deleted and an edited one shows the new text with an "edited" label.
Health checks that reach the database
Improved. The /api/health endpoint now runs a real database query and
reports the deployed build; a deploy only takes traffic once both agree.
Background jobs run on a single leader, which is what lets a second
application host come next.
Voice notes through the WhatsApp Business API
Fix. A voice note recorded in the CRM widget or WASync Chat and sent through a WhatsApp Business API number reached the customer as a plain audio attachment, without the waveform bubble. It now arrives as a real voice note, the same way it already did on QR-connected numbers.
A number that is already connected cannot be connected twice
Changed. Scanning the QR code with a phone whose number is already connected on the same workspace used to create a second connection that took over the first one, and both imported the conversation history — which showed up as duplicated notes in the CRM. The second scan is now refused with a clear message, in every language of the app, and the existing connection keeps working. If the existing connection shows as disconnected, open it and click Reconnect instead of creating a new one.
6 October 2026
Required fields before a stage change in WASync Chat, templates that keep their header image, chat visibility after a record is closed, the first step of the Chat Flows editor redesign, and leads that always come with a contact.
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.