19 October 2026

WhatsApp from CRM Marketing and automation rules

New. WASync registers itself as a Bitrix24 message provider, WASync WhatsApp. Choose it in a CRM Marketing campaign under Send using, in the Send message automation rule, or in the message button of a lead, deal, contact or company (Bitrix24 labels that button SMS). The customer receives a WhatsApp message from your WASync number, and it lands on the record's timeline. How it chooses the number and what happens on a Business API number outside the 24-hour window: WhatsApp from CRM Marketing and automation rules.

Existing portals get the provider when the app is next updated from the Market, or on request.

Campaign and ad set on conversations from ads

New. Give WASync a Meta Ads token (System User, ads_read) in Settings and every conversation from a Click-to-WhatsApp ad carries the campaign id in UTM Campaign, the ad set id in UTM Term and the ad id in UTM Content, with their names on the timeline note. Without a token nothing changes. Campaign and ad set on conversations from ads.

Flows and "Each number creates its own lead"

Fixed. With the option on, a flow that starts for a known customer reused any open lead or deal of the contact, including one from another channel. It now reuses only the record that belongs to the number the customer wrote to, otherwise it creates the number's own lead. Which record a flow creates or binds to.

Reliability

• Fixed. On portals with many advisors online at once, the WASync Chat list asked Bitrix24 for the responsible person of every conversation on every refresh and hit Bitrix24's request limit at the start of the day, which also refused sign-ins and new leads for a few minutes. The list now reads from its cache.
• Fixed. Automation rules (Send WhatsApp Message, Send WhatsApp Template) stopped working on portals where the portal's first user had been deactivated. They now run under the user who installed WASync.