6 October 2026

Required fields before a stage change

New. Bitrix24 enforces its "required on this stage" fields only in its own form, never when a stage is changed through the API, so closing a lead from the chat could leave fields such as the reason for closing empty. An administrator now defines, in WASync Chat rules → "Before moving to a stage, ask for these fields", which fields must be filled for each pipeline and stage (leads and every deal pipeline). When an operator changes the stage from WASync Chat, a panel asks for those fields, pre-filled from the record; the stage changes only once they are filled, in a single CRM update, and Cancel leaves it as it was. Chat Flows are not affected, and the CRM widget has no stage picker, so Bitrix24's own card applies its rule there.

Templates keep their header image

Improved. WhatsApp Business API templates with an image, video or document header now keep the file uploaded when they were created. Every send — CRM widget, WASync Chat, Chat Flows, Automations and the template robot — uses it by default: the operator sees "Template image" preselected with a preview and can still change it before sending. For templates approved earlier or created in Meta's own interface, "Set default image" in the template list sets it once. Meta keeps the sample only for approval and asks for the file again at every send, which is why this was needed.

Chat visibility after a lead or deal is closed

New. A new administrator option in WASync Chat rules, "Closed leads and deals", removes a conversation from its former responsible employee N days after the lead or deal is closed (0 = immediately). It can optionally ignore the contact's responsible, so only open leads and deals decide who sees a chat. The chat reappears for whoever receives the customer's next lead or deal. Administrators and people who see all chats are not affected.

Under "New chats from unknown numbers" there is also a new option, "Also create a lead when the number is already a contact but has no open lead or deal": the lead is linked to the existing contact and assigned by the same rule (fixed person or round-robin). The "Create lead" button in WASync Chat now appears on conversations linked only to a contact as well. Both options are off by default.

Chat Flows editor: first step of the redesign

Changed. The Start step is now unique and cannot be deleted. It describes in plain sentences when the flow starts — for example "Starts when a customer writes first on +…, with any message" or "Once per customer. Stops when a colleague replies" — with a "Change when it starts" button. Steps are edited in a side panel while the canvas stays visible, instead of a modal.

The Branch step takes conditions as Field · Condition · Value, with a searchable field picker grouped by customer answers, deal or lead, contact, company and ad fields, and list values (stage, source, user, yes/no) chosen by name. Every step that used to ask for an ID now uses pickers with names, and the legacy "Action" step is no longer in the palette. The palette is grouped and searchable, and the top bar has an editable name, a live "N problems" pill that jumps to the step, Undo/Redo and a "Flow settings" panel. The whole editor is available in all 20 languages. Draft and published versions are not part of this step.

"Customer writes first" no longer starts on a reply to your team

Fix. If someone on the team wrote to a customer in the previous 72 hours — from the CRM widget, WASync Chat, the Open Line or the business phone — the customer's answer is now treated as a reply, and the inbound flow does not start. Messages sent by flows, automations or robots do not count, so a flow still starts when the customer truly writes first. This is on by default for every existing flow; the trigger's "Don't start when we wrote first" option turns it off or changes the window (1–168 hours).

Leads created by WASync come with a contact and the form data

Improved. Every lead WASync creates — automatically at the first message, when the operator writes first, or from the "Create lead" button — now gets a linked contact: an existing one found by phone or email, otherwise a new one. When the first message is a Meta lead-form message from a Click-to-WhatsApp ad, its data is mapped: full name to first and last name and the lead title, email to email, a different phone to a secondary phone, and every other question and answer to a comment on the lead's timeline. On existing leads only empty fields are filled; nothing is overwritten.

Every contact of a lead or deal links to that record

Improved. When a lead or deal has several contacts, the WhatsApp conversation of any of them is now linked to that lead or deal, not only the primary contact's. An open deal wins over an open lead, and a closed lead never wins over a contact. This applies to new conversations and to the daily re-check of existing links.

Ad attribution reaches every open deal

Fix. When a customer's first message arrives without Meta's ad data and the referral only comes with a later message, the campaign and ad fields are now written to the contact and to every open deal without attribution opened in the previous 24 hours, not only the first one. An older deal already attributed to a previous ad no longer blocks the new one. An existing attribution is never overwritten.

Pipedrive: subscribing from the WASync panel

Fix. Pipedrive customers can subscribe again from the WASync panel. Pay opens Stripe Checkout in a new tab — WhatsApp QR $19 or WhatsApp Business API $29 per number per month, for 1, 3, 6 or 12 months, the same prices as on Bitrix24 — and the panel updates itself when the payment completes. Account & Plans shows each number's plan and billing state, with "Manage billing" for the card, invoices and cancellation at the end of the period. Paying does not reconnect a number that was disconnected when its trial ended; scan the QR code again.