Duplicate customer records that split the history
Same customer, three records, three different phone numbers. No two agree.
What's the leak?
Same customer, three records, three different phone numbers. No two agree.
What it looks like
'John Smith' called in 2019. 'J. Smith' filled out a form in 2022. 'Johnny Smith' bought a roof last year. All three are the same person. None of the records know about each other. When John calls next week, whoever picks up starts from scratch.
Why it happens
Nothing deduplicates on entry. Every new form, call, or manual entry creates a new record when it should merge into an existing one.
What it costs
Every duplicate record is a rep who insults a repeat customer, a warranty claim you can't verify, and a marketing list that pays to reach the same person twice.
How URBLD closes the leak
The intake surface matches on phone, email, and address before creating a new record. Duplicates surface immediately with a merge action. One customer, one thread, one lifecycle number — forever.
Leak diagnosis
- Observed symptom
- The same person appears more than once, with different history on each copy.
- Inferred root failure
- No match rule at intake and no merge path afterwards, so every channel creates its own copy.
- Lifecycle stage
- Intake
- Financial or capacity consequence
- Lifecycle history splits, so source, follow-up state and balance can all be read wrong at the same time.
Measure it yourself
Count of records sharing a phone number or email, and the share of leads created without a match check.
Practical diagnostic
Group your records by phone number and count the groups with more than one entry.
Recommended operating response
Match on phone and email at creation, merge deliberately with history preserved, and keep one identifier across the lifecycle.
Deeper explanation: Duplicate leads
Related Features
Related Workflows
Other leaks worth checking
See how URBLD closes every leak
One connected workflow from the first lead to the final payment.