Contacts and duplicates

People rarely write once. They send a form and then an email, reply with the date, or come back months later for another event. Leadveyor recognises the same person and keeps their story together: repeat messages build one lead, and all leads of a person meet on one contact.

Day 0 → Lead A
Enquiry: wedding, 120 guests
Day 4 → Lead A
Reply: “date is 14 May”
Day 19 → Lead A
Form again, adds a phone number
Day 52 → Lead B
New enquiry: birthday party
30-day window · both leads belong to contact sarah@example.com
Messages from the same email or phone within 30 days build one lead; later ones start a new lead on the same contact.

In the example, Sarah writes on day 0, replies on day 4 with the date, and fills the form again on day 19 with her phone number: all three messages are merged into lead A. On day 52, outside the 30-day window, she asks about a birthday party: that becomes a new lead B. Both leads belong to the same contact.

How a person is recognised

By email and phone only:

  • Emails are compared ignoring case.
  • Phones are compared by their last nine digits, so "+61 412 345 678", "0412 345 678" and "0412345678" are the same number, whatever the formatting.
  • Names are never used — two people can share a name, and one person writes it in many ways.

A message with neither an email nor a phone can't be matched and always starts a new lead.

Repeat messages: one lead

When a new message comes from someone who has an active lead from the last 30 days, it is merged into that lead instead of creating a new one:

  • Contact details are combined: a new phone or a second email is added.
  • Missing values are filled in: a date given in the reply completes the lead.
  • Nothing is overwritten: what the customer said first stays.
  • The summaries of both messages are kept.
  • Answers to criteria are combined: a definite new answer replaces the old one, but "unknown" never erases a known answer.

The lead is then scored again with everything known, using the same profile version — without another model call for the old message. The lead's history shows every message it was built from, and a webhook reports the change.

Contacts: every lead of a person

A contact collects all leads of one person, without a time limit — so you see that the birthday enquiry comes from last year's wedding client. Each contact counts its leads and how many were won and lost.

Contacts can be flagged VIP (an important customer) or blocked (never a customer). The flags travel with the contact's data through the API and webhooks, for your CRM and automations to act on; to give regular customers a higher score, use an exceptional criterion.

Separate worlds

Matching never crosses boundaries: leads and contacts of one workspace are never matched with another's, and test messages never merge with live leads.

Was this page helpful?