TAP TAP GO
Compare before combining
Match more than a name. Review the email address, organisation, role and the circumstances in which each record was created. Common names and shared inboxes can create false matches. If the evidence is uncertain, mark the records for review instead of merging automatically. The cost of a mistaken merge can include lost context and a confusing follow-up to the wrong person.
Keep the relationship trail
When a merge is appropriate, preserve the meaningful notes and source history. Distinguish current details from older ones instead of silently overwriting everything. Record who performed the merge and why. Establish a rule for which fields take priority when information conflicts. A clean contact database is not merely a smaller database; it is one where the surviving record remains accurate and useful to the person managing the relationship.
Hypothetical example
A hypothetical team meets the same buyer at two conferences. One record contains a personal introduction and the other a project discussion. After confirming the identity, the team combines them and retains both event notes, giving the next conversation a more complete context.
Make it practical.
Use this checklist as you read. Checks are not stored.Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.
