ChatGPTClaudePerplexityGoogle
View as Markdown

TL;DR

  • The first merge is the moment a client decides whether to trust your cleanup.
  • Doing it live on a call lets them see exactly what happens to their records.
  • Recap the rules, review a sample together, merge one set, check it in the CRM, then merge a small batch.
  • End with a clear plan for the rest, and what the client should watch for.
  • In Dedupely, previews show the result before each merge, and Merge History records what changed.

A client can approve your merge rules on paper and still be nervous about the first merge. They don't know what it will look like in their CRM, and they're the one who will hear about it if something goes wrong.

Running the first merge live, on a call with the client, turns that nervousness into confidence. They see the records before, the merge and the result in their own CRM. This post gives a format for that session.

Who should be there

  • The client's CRM owner or admin. They know the data and approve the result.
  • A sales or support lead, if their team uses the records most.
  • You, sharing your screen.

Keep it to three or four people. More than that and the session turns into a debate on merge rules.

A 45-minute format

Time What happens
5 min Recap: what counts as a duplicate, which record survives, which values win
10 min Review a sample of 10 to 20 sets from the safest search together
5 min Merge one set, then open the merged record in the CRM
10 min Check the result: values, activities, linked deals, owner
10 min Merge a small batch from the same search
5 min Agree on the next steps and what to watch for

Start with the search the client is least likely to argue with, usually contacts with an exact email match. The aim of the session is a clean first result, not the biggest number.

Leave the harder cases, like companies with branches or deals, for a later session once the client has seen a merge work.

Check the result in the CRM

Don't just show the merge in the tool. Open the merged record in the client's CRM, the screen their team uses every day, and check:

  • The name, email and phone are the ones they expect.
  • The activities and notes from both records are there.
  • Linked deals and companies moved to the merged record.
  • The owner is right.

End with a plan

Before the call ends, agree on:

  • The next search to merge, and when.
  • Who checks a few merged records the next day.
  • How the team reports a problem, and who they tell.

How Dedupely helps in a live session

In Dedupely, previews show which record survives and which values win before you merge, with winning values in bold. You can reject a set during the call and it stays out of future searches for that object, and you can add filters on any synced field to leave out cases like shared inboxes. Merge a single set, or select a batch and merge it in one step. Merge History shows every merge with each original record's values, and most merges can be undone for 30 days, though every merge should be treated as permanent. If the client wants to follow along afterwards, you can invite them to their own company with a role that fits, like Read-only User.

Run your next client cleanup

Let the client see it happen

A live first merge shows the client exactly what a merge does, on their own records, with them in the room. Start with the safest search, check the result in their CRM, merge a small batch and end with a plan for the rest.

Frequently asked questions

Should I merge duplicates with the client on a call?

For the first merge, yes. It shows them what happens to their records and builds trust for the rest of the cleanup.

How long should the session take?

About 45 minutes: a recap, a sample review, one merge, a check in the CRM and a small batch.

Which duplicates should I merge first?

The safest ones, usually contacts with an exact email match. Leave harder cases for later sessions.

What if the client spots a set that shouldn't merge?

Reject it on the call and, if it's a pattern, add a filter. It shows them their input changes the rules.

Who should attend?

The client's CRM owner or admin, a lead from the team that uses the records most, and you.