9 October 2026

A chat flow per Meta ad

New. The Start step of an inbound flow gains "From a specific ad": list the Meta ad ids the flow should answer (for a campaign, list all of its ad ids; an empty list means any ad). A number can now have several inbound flows, and the one that starts is chosen by how specific it is: the matching ad first, then keywords, then "any message". A flow bound to the number beats a workspace-wide one, and within the same level the older flow wins. A message from an unlisted ad, or from no ad, falls back to the keyword or any-message flow. A human reply stops every inbound flow set to stop on it. The editor does not yet warn when the same ad id is listed in two active flows, and the simulator cannot yet pretend a message came from an ad.

Insert a step on a connection line

New. In the Chat Flows editor, hovering a line between two steps shows a "+" next to the "×". It opens the same step picker as the "+" on a step and inserts the new step in between, keeping the branch or answer option the line carried. The new step lands halfway along the line with its panel open.

Flows no longer advance on a re-delivered message

Fix. WhatsApp can deliver the same incoming message twice, for example after a session re-sync or a retry. The copy was treated as a new answer from the customer, so a flow could move on by itself. Copies are now ignored by flows, lead creation and automations; the conversation already showed the message once.

Choose who is rung first for incoming calls

New. Settings → "Incoming calls" (administrators) sets who is rung first when a known customer calls: "The contact's responsible person" (the default, as before), "The responsible person of the most recent open deal or lead" (falling back to the contact's responsible when there is none), or "Both at once". The rest is unchanged: only people online in Bitrix24 who handle the number are rung, and after 8 seconds without an answer everyone online who handles the number is rung too.