4 November 2026
With one lead per number, a message sent from an open lead or deal moves the conversation off a closed record, so the customer's reply no longer opens a new lead (on request).
Sending from an open record moves the chat off a closed one
Fixed. With one lead per number turned on, a conversation whose record on that number was already won or lost stayed on it, even when an advisor sent a message from the customer's open deal. The reply then opened a new lead for the unknown-numbers rule. Now a message sent from an open lead, deal or Smart Process item moves the conversation to that record, and a reply to a closed record first looks for the contact's open deal or lead before creating one. Off by default: write to support to turn it on for your portal. When the number's record is closed.
Mexican numbers typed with +52 stay in one conversation
Fixed. WhatsApp files a Mexican mobile as 521 followed by the 10-digit
number, while people usually type +52 and the 10 digits. A message sent to a
number typed the second way reached the customer but opened a second, empty
conversation, and the customer's reply arrived in the first one. Both
spellings now open the same conversation; duplicates created before the fix
will be merged on our side.
Default country.
Lead flows can create the lead without a new contact
New. A lead flow that creates the lead when the customer writes first can now skip creating a CRM contact. Tick Create only the lead (no new contact) on the Start card: the lead is created on its own, and linked to a contact only when one with the customer's phone already exists. Create only the lead, without a new contact.
One CRM timeline comment per day per record
New. A busy conversation no longer fills a deal's timeline with one comment per WhatsApp message. Turn on One comment per day per record under CRM Timeline Log in Settings: each record then gets one comment per day, and every message is added to it as a line with the time, the direction and the operator's name. One comment per day per record.