Review possible duplicate customers before merging
See why two customer records might be the same person, then decide. Nothing merges on a shared name.
Data · Home services · When something happens · Updated
Works with
- Slack
- HubSpot
- Salesforce
- Attio
- Pipedrive
- Airtable
- Microsoft 365
Slack
HubSpot
Salesforce
Attio
Pipedrive
Airtable
Microsoft 365How do you merge duplicate customers safely?
To merge duplicate customers safely, have Maito check after each import. It compares new and existing CRM records, ranks pairs as likely or weak matches by phone, email and address, lists open invoices and job history on each, and posts the evidence in Slack. Your team does the merge.
How it's done today
Someone merges records that look alike by name and the older job history disappears.
What Maito does
- Spot records that may match after an import
- Show the phone, email and address side by side
- Mark which pairs are likely and which are not
- Wait for an authorized person to merge
Example
Loop run: New import into the CRM · 412 customers
The 412-row import created 6 possible duplicate pairs. Likely the same • Dana Whitfield, 18 Birch Ln and D. Whitfield, 18 Birch Lane: same phone (555-0142) and email. 3 jobs on one, 1 on the other. • Acme Dental and Acme Dental Group: same billing email, different suite numbers. Probably different people • Maria Lopez, 77 Oak St and Maria Lopez, 9 Cedar Ct: same name only, different phone, email and address. • 3 pairs where only a first name matches. Catch: the Whitfield pair has an open $1,240 invoice (INV-3318) on the newer record. A merge has to keep that invoice and both job histories. From the CRM and the import file. Nothing is merged.
@Maito I'll merge the Whitfield pair myself. Leave the Lopez records alone and make a note that they're separate people.
Noted. I'll add a note to both Lopez records saying they were checked on Oct 19 and are different customers, so they don't show up as a pair again.
Maito (10:42 AM):
The 412-row import created 6 possible duplicate pairs.
Likely the same
• Dana Whitfield, 18 Birch Ln and D. Whitfield, 18 Birch Lane: same phone (555-0142) and email. 3 jobs on one, 1 on the other.
• Acme Dental and Acme Dental Group: same billing email, different suite numbers.
Probably different people
• Maria Lopez, 77 Oak St and Maria Lopez, 9 Cedar Ct: same name only, different phone, email and address.
• 3 pairs where only a first name matches.
Catch: the Whitfield pair has an open $1,240 invoice (INV-3318) on the newer record. A merge has to keep that invoice and both job histories.
From the CRM and the import file. Nothing is merged.
Nina (10:55 AM):
I'll merge the Whitfield pair myself. Leave the Lopez records alone and make a note that they're separate people.
Maito (10:56 AM):
Noted. I'll add a note to both Lopez records saying they were checked on Oct 19 and are different customers, so they don't show up as a pair again.
How to set it up
- Ask your agent
“Whenever we import customers into the CRM, check for possible duplicates and post them in #office with the evidence. Don't merge anything yourself.”
- Connect CRM
- HubSpot
- Salesforce
- Attio
- Pipedrive
- Connect spreadsheet
- Airtable
- Microsoft 365
Not connected yet? Your agent sends you a link to sign in.
What it won't do
Two records with the same name can still be different people, so a shared name counts as weak evidence. Maito can't see data that isn't in the CRM or the import file.
Questions
No. It only suggests. Someone on your team merges after reading the evidence.
HubSpot, Salesforce, Attio and Pipedrive. It can also read an Airtable or Microsoft 365 spreadsheet of imported rows.
Yes. It can add a note to both records saying they were checked and are different customers, once you tell it to.
