Duplicate Detection
The same person landing on your list twice is what this stops. Before a lead is written it is checked on the email, and failing that the phone, both cleaned up first. Exact, with no similarity score for anybody to argue about.
An incoming row that already exists
matched on email- Job titlereplacedOperations ManagerHead of Logistics
- Cityleft aloneOaklandempty
- Lead scorereplaced6274
- Assigned tonever touchedS. BhattM. Ortiz
- Tagsnever touchedenterprisewebinar
- Custom fieldsadded toterritoryfleet_size
Product figures from the platform’s own defaults - not customer averages
How it works.
Email first, because it identifies
An email match is taken over a phone match whenever both are available, on the grounds that two people genuinely share a switchboard number far more often than they share a mailbox. Names are never compared at all.
Cleaning it up first is what makes it exact
Addresses are trimmed and lowercased. Numbers are reduced to their digits and rebuilt behind a plus, and a leading double zero is read as the international prefix it is, so a number wrapped in brackets and dashes lands on the same key.
Checked per chunk, not per row
During an import the comparison runs once for a whole batch of five hundred rather than once per row. Within a run the row identifiers are fixed, so a crash and a retry pick up without doubling anything; a second upload of the same file is a fresh run and leans on the keys alone.
The original wins, not the newest
Where several records hold the key, the earliest created one is the match. An incoming row therefore joins the record that has been accumulating history, rather than the copy somebody made last week.
Two moments in every record.
Every record passes through the same seven. Duplicate Detection is the lit ones, and everything either side of it is a different page in this category.
- 01Capture
how it arrives, and from where
- 02Shape
the fields and stages it carries
- 03Find
getting back to the right ones
- 04Work
what happens against it day to day
- 05Advance
moving it toward a decision
- 06Protect
who may see it, and staying clean
- 07Report
what the floor is judged on
The specifics.
8 facts- Keys
- Normalized email, then normalized phone. Names and addresses are never read
- Email rule
- Trimmed and lowercased. Dots and plus-addressing are not folded together
- Phone rule
- Primary then mobile, reduced to digits behind a plus. Home and other ignored
- Method
- Exact once normalized. No similarity scoring and no confidence value
- Tie break
- The earliest created record is chosen when several carry the key
- Runs on
- Import, and any lead a call creates. Not scheduled, and not on demand
- Two runs at once
- The call path holds a transaction lock. Concurrent imports are best effort
- Normalized both ways
- The stored key and the incoming one are built by the identical routine, so a match cannot depend on which side was typed first
What else writes to this record.
A record is worked by more than one part of the system at once. These are the ones that put something on it, or read it back.
More in Leads & Sales CRM
12 capabilitiesThe system of record the phone writes to directly - nothing to sync.
Each stage carries its own odds, so where a deal sits is already most of a forecast. Unlimited pipelines, seven seeded, every stage change written down.
Name the stages your floor actually argues about, color them and rate them hot, warm or cold. Six fixed categories keep last quarter comparable with this one.
The same source can never arrive spelled three ways. Ten come seeded and sealed, yours sit beside them, and renaming one carries every lead holding it.
The thing your business tracks that no CRM ships with. Eleven types on leads, deals, products and vendors, no migration to schedule and nobody to wait on.
Some of what you collect is not for everyone on the floor. Close a whole section once per profile instead of opening and shutting a hundred fields one by one.
Hand a list to a CRM role rather than a person and the question outlives whoever first asked it. A new hire opens the board instead of rebuilding it daily.
Ask the same question tomorrow and the list narrows the same way, because the server settles it. Eighteen operators, fitted to the kind of field they sit on.
Nobody writes this up. A field change keeps both readings, before and after, beside the notes, mail and tasks, so it still means something in six months.
Every exchange with this lead on one line: calls, voicemails, mail and text. A call lands on the right record by the number it reached, linked by nobody.
A thing owed, by a named person, by a date. At the hour you set it leaves the product to find them, rather than sitting in a list waiting to be spotted.
The rep two desks over cannot open the book you are working, and one BPO client never sees the next. Sixteen permissions, sharing rules across branches.
A number, a window, and somebody standing against it. Attainment is worked out from won deals and logged work as you open it, so nothing sits going stale.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Leads & Sales CRM
See duplicate detection on your own floor.
Thirty minutes, your numbers and your data. We will set duplicate detection up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included