Preventing duplicate sends
A campaign should define uniqueness for a specific send: committee, audience record or normalized number, approved content version, and send operation.
Putting the guide into practice
Deduplicate within the intended audience, create a stable send reference, and test how retries or staff resubmissions are recognized. Retain suppression across later imports.
- Audience uniqueness
- Campaign boundary
- Send reference
- Retry behavior
Limits and review decisions
Do not merge unrelated committees merely because they share a phone number. Campaign boundaries and permission records must remain explicit.