Start with the contact point
Phone and email records each carry their own provenance, consent, suppression, and usability state. A blocked channel stays blocked on its own record.
Keep policy decisions deterministic
Feature approval, shop and channel flags, consent, suppression, workflow rules, provider readiness, and incident controls run as application checks on every send.
Keep manual work and provider delivery distinct
Manual call notes, drafted content, internal tests, provider acceptance, delivery, failure, and opt-out record as separate events.
Read the evidence on the record
The Compliance workspace shows the operational evidence behind every eligibility result, so the team sees exactly why a send went out or stayed blocked.
Worked example: checking one contact point
A customer has both a phone number and an email on file. Each carries its own provenance, consent, suppression, and usability state.
The email is consented but the phone is suppressed, so the phone stays blocked while the email remains available.
The team records the send decision and its evidence on the record, so a later reviewer can see why.
Checklist: contact-compliance review
Review at the level where eligibility is decided.
- Check the contact point, not just the customer
- Treat consent, suppression, and usability as separate states
- Keep manual call notes distinct from provider delivery
- Read the evidence behind an eligibility result before acting
Common questions
On the contact point. A phone number and an email address each carry their own consent, suppression, and usability state, so one can be blocked while another is available.
More guides
Other safety guides
Send every message consent-checked
How drafts, eligibility, provider acceptance, and delivery stay separate, with consent and suppression checked on every contact point before a send.