Give Remote Teams a Clear Approval Route for CRM Record Merges
Give a remote CRM team a defined way to propose a record merge before granting authority to perform one. The decision needs more than a similar name. Identify the exact records, explain the matching evidence and show which values and relationships should remain in the surviving record.
This matters to the colleague who opens the record next. They need to know which customer history they are reading, who owns the relationship and whether an apparently tidy profile has combined information that belonged to different people. A merge can remove visible duplication while creating a harder problem underneath.
Make a proposed merge a specific decision
Use the system's stable record identifiers alongside names and links. Record why the pair was flagged and what still needs checking. Two records sharing a company name could describe different branches, while two contacts with similar names could be different people. The team's job is to gather the evidence required by the business's matching policy.
HubSpot's merge-record documentation explains that a merge combines records and that they cannot subsequently be unmerged. It also specifies merge permissions and notes that behaviour varies by object type. Those product facts make the decision worth reviewing before the final action, rather than relying on a cleanup label to imply permission.
Define whether the remote role may only identify candidates, prepare the comparison or execute an expressly approved merge. Access to a button does not establish the business authority to use it.
A changed employer creates a relationship decision
Imagine two contact records for a customer who has changed employers. One contains the current email address and a recent enquiry. The other contains an older address, a previous company association and useful correspondence. This is a fictional case, not a reported client example.
The assistant proposes a surviving record but does not simply copy every old property into it. The CRM owner needs to decide how the current company relationship should appear and whether the older association remains relevant history. A current email address also does not determine every communication permission or preference associated with the customer.
The comparison should therefore show the evidence for identity, the proposed surviving values and the unresolved relationship questions. If identity cannot be established under the agreed process, keep the records separate and escalate the gap. The assistant can continue reviewing unrelated records within their authorised scope.
Review what the combined record will mean
| Part of the record | Question for the reviewer |
|---|---|
| Identity | What evidence establishes that these records describe the same entity? |
| Surviving values | Which value should remain where the records disagree? |
| Associations | Which company, deal or ticket relationships should carry forward? |
| Ownership | Who will own the combined relationship and any open work? |
| Downstream use | Which reports, integrations or configured automations need review? |
This table is an illustrative planning aid. Check the actual platform behaviour and configuration rather than assuming that all CRMs resolve conflicts in the same way. For example, if the business has configured an automation around a record property, its owner should explain whether the proposed surviving value changes what that automation will do.
Keep sensitive fields out of an unnecessarily broad comparison export. The reviewer needs enough information to decide, using the approved system and access route.
Record approval against the exact proposal
An approval should identify the two record IDs, the intended survivor and the agreed handling of material differences. If the proposal changes after approval, return the changed point to the decision owner. A general request to remove duplicates is not approval for every subsequent merge.
Agree who can act if the usual owner is unavailable. Naming a colleague as a backup only helps when that person actually holds the necessary authority and can review the evidence. DCV's guide to delegated decisions develops that boundary for a remote team.
Verify the result before closing the item
After an authorised merge, read back the surviving record and compare it with the approved proposal. Check the retained values, relevant associations, open tasks and ownership. Save the resulting record ID and the action evidence in the agreed work record so the next person can trace what happened.
If the result is unclear, investigate that same record before repeating an action. A delay in the interface is not evidence that no change occurred. Keep the merge item open until the outcome can be reconciled or handed to the CRM owner.
Where the maintenance work begins with an import, use the separate DCV guide to reconciling imported records. Import acceptance checks the incoming batch; merge approval decides how specific existing records should become one. Keeping those decisions clear gives a remote specialist useful responsibility without asking them to invent the business's identity rules.