Investigate duplicate campaign emails using message evidence

Define the decision

Possible explanations include two active campaigns, an internal test, different follow-up steps, a provider display issue or a repeated transport attempt. The investigation needs evidence that distinguishes them. Preserve headers and timestamps through an authorized support channel, with unnecessary personal content removed.

Work through the procedure

1. Ask for the two messages' sender, recipient, received timestamps and Message-ID values. Record whether the content is identical or only similar.
2. Map each message to a campaign, enrollment and step where possible. Check overlapping lists and manually sent replies or tests.
3. Compare provider acceptance evidence with application attempt records. Treat a timeout after transport as an uncertain outcome rather than proof of failure.
4. Contain the affected scope while investigating. Resume only after identifying whether a duplicate path remains and how existing contacts should be handled.

Worked example

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

Evidence comparison
Message A: recipient Lee, campaign Operations, step 1
Message B: recipient Lee, campaign Procurement, step 1
Different message identifiers; overlapping enrollment
Finding: audience coordination failure, not yet evidence of a worker retry bug
Fix: review cross-campaign exclusions

Read the result

The example points to enrollment overlap because the messages belong to different campaigns. Another case with one enrollment and conflicting attempt records would require a different investigation. Avoid declaring a root cause from the symptom alone; the remedy should explain the evidence you actually found.

Check before moving on

1. Keep provider and application times in a common timezone.
2. Preserve the original evidence before deleting test records or changing enrollment state.
3. After the repair, inspect the affected path with a controlled address rather than sending another diagnostic message to the prospect.

Limits and next action

Do not recreate a contact or replay the campaign while the first outcome is uncertain. Zintara tracks send attempts and pauses ambiguous cases to reduce duplicate risk, but a support review still needs concrete identifiers and provider evidence. A screenshot without message details may be insufficient.

Source: Zintara sequence product context