20 October 2026

A refused send outside the 24-hour window says why

Fixed. On a WhatsApp Business API number, typing to a contact who had never written (or whose only "incoming" item was a missed call) left the composer open; the send was refused by the 24-hour rule and the message simply disappeared. Now the composer locks for such contacts with the explanation and the Pick a template button, in WASync Chat and in the CRM tab alike, and if a send is still refused the reason stays on screen until the customer replies. Templates on Business API numbers.

A closing message when a run stops for inactivity

New. If no reply has a fourth field, When the run closes, send this message, both in Flow settings and on each question. Write something like "We didn't hear back, so this conversation was closed. Whenever you want to continue, just send us a new message here." and the customer receives it the moment the run closes. Leave it empty to close silently, as before. The preview simulator plays it after the close. Inactivity reminders and closing.

The reminder is the bot's message, not your team's

Fixed. The inactivity reminder was stored like a message typed by a person. For a customer who answered only after the run had closed, that made their reply look like an answer to your team, and Flows do not start on a reply to your team kept the flow from starting again. Reminders and closing messages are now recorded as the flow's own messages: they never count as a colleague taking over, and a late reply starts a new run as the documentation always said.

No second lead when an open lead already holds the number

Fixed. A Customer writes first lead flow found the customer's CRM contact and that contact's open lead or deal, but an open lead that carries the number without any CRM contact on it, typically a lead imported from another tool, stayed invisible, so the flow created a second lead next to it. The flow now also binds to such a lead. Which record a flow creates or binds to.

Edits and deletions in a group stay in the group chat

Fixed. When a member edited or deleted a message inside a WhatsApp group synced to a Bitrix24 group chat, the "message edited" / "message deleted" note was sent to the Open Line as if the group were a person, which opened a one-to-one chat and a lead whose phone number was the group id. The note now goes to the bridged group chat, and a group id is refused as a phone number when sending from a CRM record. Leads created this way can be deleted; they carry a phone of 18 digits starting with 1203.

Videos and documents sent from Bitrix24 no longer fail at 15 seconds

Fixed. On a WhatsApp QR number, a file sent from an Open Channel or from the WASync tab is downloaded and uploaded to WhatsApp in one step, and a large video can take 20 to 30 seconds. Our side gave up after 15 seconds and marked the message as failed in Bitrix24 and in the thread, while the file still reached the customer, so operators sometimes sent it a second time. Media sends now wait up to 90 seconds; short text messages keep their quick timeout.