Customer Intake & CRM
Duplicate customer prevention
Catch likely duplicate customers before they split your service history, billing, and equipment records.
Overview
When the same customer gets entered twice, their job history, invoices, and equipment records get split across two profiles, and your team loses the full picture. Thorbis is building duplicate detection that flags likely matches as records are created. You'll catch and merge duplicates up front, so each customer keeps one clean history and your billing stays straight.
What we're building
When the same customer gets entered twice, their job history, invoices, and equipment records get split across two profiles, and your team loses the full picture right when they need it.
Thorbis is building duplicate detection that flags likely matches as records are created, comparing name, address, phone, and email. You'll catch and merge duplicates up front, so each customer keeps one clean history and your billing stays straight.
It's for intake and office staff who create customer records all day and need confidence that one customer means one profile.
What you'll be able to do
- Flag likely duplicate customers at creation
- Match on name, address, phone, and email
- Merge duplicate records into one history
- Keep billing and equipment tied to one profile
- Protect the integrity of customer history
- Catch duplicates up front before they split records
- Keep one clean service history per customer
Rollout plan
- 01
Duplicate detection at creation
In progressFlag likely matches as new customer records are created.
- 02
Multi-field matching
In progressCompare name, address, phone, and email to catch near-duplicates.
- 03
Merge into one history
In progressCombine duplicates so billing and equipment stay on one profile.
Milestones
- Not started:
Match rules defined
Decide which fields and thresholds signal a likely duplicate.
- Not started:
Creation-time flagging
Warn when a new record looks like an existing one.
- Not started:
Merge workflow
Let staff combine duplicate records into one history.
More in Customer Intake & CRM
How to send useful feedback
Name the blocked role
Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.
Explain the workaround
Describe what your team does today and where the process fails under real work.
Define success
Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.