Practical operating guide
How to stop duplicate customer records from causing duplicate follow-ups
By ByTomorrow · Published
A customer receives the same follow-up twice. The team finds two customer records and assumes merging them will solve the problem.
That may be the right cleanup, but the duplicate message could also come from two workflows using one record. A shared phone number can make two different people look like a duplicate.
Diagnosis
Identify the duplicate before changing the records
The same recipient is not always the same person
Households and businesses may share contact details. A phone match is a candidate for review, not proof that the names and requests belong together.
One record can still send twice
Compare the message history and workflow names. If both messages came from different runs attached to one contact, record cleanup alone will not remove the duplicate sending path.
Merging changes workflow context
HighLevel documents that its Merge Contact action preserves the older contact. It also describes limitations for goals, reply waits and other steps tied to the original contact or message. Check active work before a merge.
Working worksheet
A duplicate-review worksheet
Match evidence
Copy these columns: record A ___; record B ___; matching email ___; matching phone ___; names agree ___; original sources ___; conflicting details ___; reviewer ___. Keep the row restricted to people authorized to handle customer records.
Shared-number example
Illustrative case: two different names use the same office number and ask about different services. Decision: keep separate and ask for a distinguishing contact method. A shared number alone does not authorize combining their histories.
Likely duplicate example
Illustrative case: the same person submitted the same request through two forms with matching email and phone. Decision: confirm identity and request history, then select the surviving record according to the CRM's actual merge behavior.
Active-work check
For each record, list scheduled messages, assigned tasks, open inquiries and waits for a reply. Name which work should remain. Hold redundant sends while an authorized operator reviews them; do not abandon valid customer requests.
Post-cleanup evidence
Record the surviving identifier, reviewed history, retained tasks and intended next message. A successful merge notice is insufficient if both original workflows can still contact the same person.
Use the worksheet
Put it into practice
Trace one duplicate message pair
Compare recipient, inquiry, contact identifier and workflow execution. Decide whether this is a record-identity issue, a repeated event or competing workflows.
Review before merging
Use the worksheet and the CRM's preview or supported export procedure where available. If identity remains uncertain, leave records separate and route the match to a person.
Verify future behavior
Use synthetic contacts to test the cleanup rule. Confirm the intended follow-up happens once and that a second legitimate inquiry is still retained.
Questions
Straight answers.
It is a stricter match than either field alone, but shared or reused details still need review. A matching rule cannot establish identity when the underlying data is ambiguous.
First inspect representative cases and active workflows. Resolve the cause of duplicate creation before applying a broad cleanup. Keep uncertain matches out of automatic merging.
Sources and further reading
- HighLevel Merge Contact workflow action
Supports available identity match criteria, preservation of the older record and documented limitations affecting workflow waits and execution after merges.
Checked .
Bring the two message histories
The contact identifiers and workflow names will show whether the repair belongs in matching, record cleanup or message scheduling.
Discuss your workflow