Home/Changelog/One contact, one lead per enquiry

Release

One contact, one lead per enquiry

A lead added with a mobile number now finds or creates its contact, a double entry is caught, and a second enquiry from the same customer can be added on purpose.

Updated 26 Oct 2026 · 1 min read

Two leads for the same mobile number used to be two unrelated cards with no shared history. A lead now belongs to the contact for its number, so every enquiry from one person sits in one place.

What changed

  • A lead added with a phone number links to the contact for that number, and creates the contact when there is none. It works on every plan.
  • One live lead per contact, unless you mean otherwise. Add the same number again, with or without spaces or a country code, and you are shown the lead that already exists. If it is a different enquiry from the same customer, add it as another lead and give it an enquiry name (a trip, a package): each lead keeps its own stage, reminders and notes, on one contact.
  • The API and Zapier follow the same rule. Creating a lead for a number that already has one returns the existing lead with a duplicate flag, unless the call sets allow_additional, which adds a second lead on the same contact. Leads carry an optional title for the enquiry.
  • Meta lead ads link each lead to the contact for that number, so the history stays together. Every ad submission still gets its own card, because a new submission is a new request.
  • The API now reads a number typed without a country code in your workspace's own country, not India's.

A website form with the same email still updates the existing lead, as before.

Run your WhatsApp on VGraple CRM

Free forever plan, official Meta WhatsApp Business API, set up in 15 minutes. No card needed.