Prevent duplicate campaign enrollment across overlapping lists

Define the decision

There are at least two distinct collisions: the same address in multiple sequences and different people at one company receiving incompatible messages. Address-level deduplication solves only the first. Decide whether the campaign targets independent contacts or a coordinated account conversation before merging lists.

Work through the procedure

1. Create a staging worksheet with normalized email, company, source list, current campaign and intended owner. Preserve the original address alongside the comparison key.
2. Flag exact address collisions across active and proposed campaigns. Choose one relevant sequence or a deliberate human handoff.
3. Review company-level overlap separately. Different addresses should not be merged automatically, but their messages may need coordination.
4. Apply exclusions before enrollment and retain a reason for each omitted record. Recheck overlaps when another list is added later.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Collision worksheet
[email protected] — list A — operations sequence
[email protected] — list B — procurement sequence
[email protected] — list B — same company, different role
Decision: one sequence for Lee; coordinate Kim's message with the account owner
Do not merge Lee and Kim into one person

Read the result

Exact email overlap is strong evidence of duplicate targeting; a shared company is evidence for review, not automatic deletion. The chosen sequence should match the recipient's role and the actual offer. Keeping the exclusion reason prevents a later import from quietly reintroducing the collision.

Check before moving on

1. Check existing customers, ongoing conversations and suppression before treating a duplicate as merely a data-cleaning issue.
2. Verify whether the source has changed an address rather than assuming two addresses are the same person.
3. Reconcile the final unique enrollment count against the approved staging worksheet.

Limits and next action

Do not assume every product-level duplicate guard handles cross-campaign business context. This is an operator procedure that supplements application behavior. Avoid deleting records to fix a collision when retaining history and excluding them from a new campaign is the more informative action.

Source: Zintara sequence product context