What's new, 31 October 2026: Videos and large files your customers send always reach the Open Channel, a flow message made only of empty CRM fields is skipped instead of stopping the flow, Fill in a field can write only when the field is empty, a flow can save a lead's origin as pending until someone creates the lead, templates with a call-permission request are offered and sent only on numbers with WhatsApp calls on, when a contact changes their WhatsApp number the chat, the CRM record and the old conversation all show it, Open Channel chats can be named automatically from CRM fields, photos, videos and files in the chat open with a fresh link every time and have a Download button, the chat header shows when a contact uses disappearing messages on QR connections, with one lead per number a new chat rule limits an employee's conversations to the number each one is on, numbers brought from another provider show a warning when Meta still routes their conversations to the old partner, customers who write from a WhatsApp username with a hidden number reach your chat and Open Channel as @username, and a new chat rule lets operators move a lead or deal only to the next stage from WASync Chat.
WASync · Developers

17 September 2026

Call permission recorded and shown in the widget, buttons and the call-permission card in the template builder, tapped template buttons reach chat flows, two new flow nodes.

Call permission, end to end

New. When a customer answers the WhatsApp "may we call you?" card, the answer is now recorded on the contact and written to the CRM timeline: allowed permanently, allowed until a date (temporary grants last seven days), declined, or revoked. In the CRM widget and in WASync Chat the phone icon turns green while the permission is active, and a chip next to the customer's name reads "Calls allowed" or "Calls declined". Until now the only way to learn the answer was to place a call and hit Meta's error.

The template picker has a new checkbox, Also ask permission to call after sending: the permission card follows the template automatically. Official WhatsApp Business API connections only — QR numbers have no call permission.

The request sentence itself now goes out in the operator's language, twenty languages, instead of always English, and the call window has an optional field for a custom sentence.

Tapped template buttons reach chat flows

Fix. A quick-reply button tapped on a template, or an interactive button or list choice, used to arrive as an empty message: flows could not branch on it and the inbox showed nothing. The button label is now the message text, and flows branch on it with the usual keyword matching.

Two new chat-flow nodes

New. Ask permission to call sends the permission card from inside a flow. Create Bitrix24 activity adds a to-do on the lead or deal, assigned to the record's responsible person, with a configurable deadline (default 60 minutes) and a notification. A new variable, {{RESPONSIBLE_NAME}}, is available in messages and templates.

Together these enable the re-engagement pattern after the 24-hour window: an approved template with three buttons, one branch per button, a permission request for the customers who want a call, and a to-do for the recruiter when they accept.

Buttons and the call-permission card in templates

New. The template builder adds buttons: up to three quick replies, one link button and one call button, with a preview. A template can also carry Meta's call-permission card as part of the message — tick Include a WhatsApp call-permission request — which is the only way to ask a customer whose 24-hour window has closed. The picker marks such templates and hides the follow-up checkbox for them.

When the follow-up checkbox is used on a closed window, the request is no longer refused: it is parked and sent automatically at the customer's next message, and the header reads Asking… until then. Meta allows one permission request per customer per 24 hours and two per seven days.

Known limit

Call logging in Bitrix24's Call details requires the telephony permission, which ships with app version 3, in Bitrix24 moderation since 17 September. Existing portals will need to update the app from Market once it is approved.

Was this page helpful?

On this page