Industries
Same problem, different sources
Every industry duplicates its customers for its own reasons — portals, branches, service bays, intake seasons. Here is where the records come from in each, what goes wrong, and what we fix first.
01 of 07
Real estate brokerages and developers
Every portal enquiry, roadshow sign-up and agent's personal list lands as a new contact. The same investor ends up owned by three agents, with three phone formats and two nationalities on file.
Where the records come from
- Property portal leads
- Roadshow and event sign-ups
- Agents' own spreadsheets
- WhatsApp enquiries
- Developer launch lists
up to 5 entries
What goes wrong
- One buyer, several agents
Duplicate ownership means two agents call the same investor about the same unit.
- Portal noise
Repeat enquiries from the same person create a new lead each time instead of updating one.
- Mixed-script names
Arabic and Latin spellings of one buyer sit side by side and never match.
What we fix first
- 1Merge buyer clusters across agents, with an ownership rule you choose
- 2Normalise every number to E.164 so portal and WhatsApp leads match
- 3Keep transliterated names as aliases so the next portal import matches first time
Usual engagement: Cleanup, then ongoing hygiene on portal imports
02 of 07
Automotive dealers and aftersales
A customer who bought a car, booked three services and entered a showroom competition can exist four times — once per system — with the vehicle linked to only one of them.
Where the records come from
- Dealer management system exports
- Service booking records
- Showroom and test-drive forms
- Campaign and event lists
up to 4 entries
What goes wrong
- Service and sales don't agree
The customer the service team knows isn't the one sales is chasing for a trade-in.
- Company-car contacts
Fleet drivers and the companies that own the vehicles are mixed together.
- Stale numbers
Phones change between purchase and the next service, and nobody updates the old record.
What we fix first
- 1Match customers across sales and service exports on phone, email and name
- 2Separate fleet companies from individual drivers
- 3Flag numbers that no longer validate before the next service campaign
Usual engagement: Audit, cleanup and a migration when the DMS or CRM changes
03 of 07
Trading and B2B distribution
Trading databases grow by trade show, by rep and by branch. The same account appears as an abbreviation, a full legal name and an Arabic name, each with its own contacts and its own history.
Where the records come from
- Trade show scans
- Branch and rep spreadsheets
- ERP customer master
- Quotation and invoice contacts
up to 4 entries
What goes wrong
- Account sprawl
Northgate, Northgate Trdg and NORTHGATE TRADING LLC are one customer with three credit histories.
- People who moved on
Buyers change employers; the old record keeps getting quotations.
- ERP and CRM drift
The finance system and the sales system disagree about who the customer is.
What we fix first
- 1Collapse account-name variants into one company with aliases
- 2Re-link contacts to the right company and retire the ones who left
- 3Align CRM accounts with the ERP customer master where both exist
Usual engagement: Cleanup, and migration when moving off spreadsheets or between platforms
04 of 07
Clinics and healthcare groups
Booking apps, call centres and branch front desks each register the same person. Family members share a phone number, so naive matching merges people who should stay separate.
We work on the CRM and marketing database you're entitled to share — not clinical records. Scope is agreed in writing and covered by our DPA before any data moves.
Where the records come from
- Online booking platforms
- Call-centre logs
- Branch front-desk lists
- Campaign sign-ups
up to 4 entries
What goes wrong
- Shared family numbers
One phone, four family members — phone-only matching would wrongly merge them.
- Branch silos
A patient known to two branches receives two of every message.
- Consent in several places
An opt-out given at one branch isn't respected by the others.
What we fix first
- 1Match on several fields together so shared numbers never cause a merge on their own
- 2Reconcile consent so the strictest opt-out wins everywhere
- 3Send low-confidence clusters to review instead of merging them
Usual engagement: Audit and cleanup of the CRM and marketing database
05 of 07
Training and education providers
A course enquiry can come from the learner, a parent or an employer sponsor. Each becomes a contact, and the relationship between them is lost — so follow-ups go to the wrong person.
Where the records come from
- Website and ad enquiry forms
- Open-day and fair registrations
- Corporate sponsor lists
- Past-student records
up to 4 entries
What goes wrong
- Who is the customer?
Parent, learner and sponsor are stored as unrelated contacts.
- Re-enquiries
Returning students and repeat enquiries arrive as brand-new leads.
- Intake-season decay
Each intake adds thousands of records that nobody maintains afterwards.
What we fix first
- 1Merge repeat enquiries into one learner record
- 2Link parents and sponsors to the learner instead of duplicating them
- 3Add entry validation before the next intake season
Usual engagement: Cleanup before intake, then ongoing hygiene
06 of 07
Logistics and freight
Freight databases hold customers, their consignees, overseas agents and carriers in the same tables. Without a clear type on each record, campaigns reach agents and quotations reach consignees.
Where the records come from
- Quotation and booking systems
- Agent network lists
- Customs and documentation contacts
- Sales rep spreadsheets
up to 4 entries
What goes wrong
- No record type
Shipper, consignee and agent are indistinguishable in the CRM.
- International number formats
Contacts across dozens of countries stored without country codes.
- Shared mailboxes
ops@ and docs@ addresses stand in for named people.
What we fix first
- 1Classify records by role so each team sees its own list
- 2Infer country codes and normalise every number to E.164
- 3Separate shared mailboxes from named contacts
Usual engagement: Cleanup and platform migration
07 of 07
Retail and e-commerce
An online order, an in-store loyalty sign-up and a WhatsApp enquiry from the same shopper create three customers. Segments built on that data overcount and under-target.
Where the records come from
- E-commerce platform customers
- Point-of-sale and loyalty sign-ups
- WhatsApp and social enquiries
- Marketplace orders
up to 4 entries
What goes wrong
- Online and offline split
Store and web shoppers are counted twice, so lifetime value is understated.
- Disposable and typo emails
Checkout typos and throwaway addresses quietly sink deliverability.
- Opt-outs that don't travel
An unsubscribe in the email tool doesn't reach SMS or WhatsApp lists.
What we fix first
- 1Join web and store customers on phone and email
- 2Suppress disposable and bounced addresses before the next campaign
- 3Carry suppression across every channel's export
Usual engagement: Cleanup and ongoing hygiene
Your industry isn't here?
The audit works on any database with an export
Tell us what the business does and which systems feed the CRM. The $99 audit shows where your duplicates come from before you commit to anything.
Agencies serving several of these industries: see partner access.
Get your data health score — $99, one working day
Read-only export or a scoped key. Nothing in your CRM is changed.