Ananasi · Campaign services
Campaign Consent Management
A permission workflow should preserve why a contact may receive the intended campaign messages and how that status can change.
Built around your permission and revocation records.
Campaign identity
Use the committee’s campaign identity; keep official government notices separate.
Jurisdiction and scope
Use the actual electoral district, county, city, or retention jurisdiction.
Replies and opt-outs
Assign response coverage and keep suppression records current.
SMS or MMS. The format your campaign needs.
The service conversation
Source, scope, date, disclosure version, and revocation history belong together. Reimporting a contact must not silently erase a previous request to stop.
Review the record model
Confirm the implemented evidence fields, campaign boundary, suppression propagation, access controls, and reauthorization process. Use synthetic cases to test conflicting records and later imports.
- Permission scope
- Evidence fields
- Suppression
- Reauthorization
A later import must respect an earlier stop request
Use a synthetic contact that is opted out, then import a second record for the same number. Inspect whether the final state preserves the suppression and why. A documented reauthorization process is different from a file merge; changing a spreadsheet column should not silently undo a recipient's request.
What to retain from this review
- Evidence model
- Conflict-resolution behavior
- Suppression propagation
- Reviewed reauthorization process
Common questions
What belongs in the first inquiry?
Your committee, office, jurisdiction, target timing, and the permission scope requirement. Keep recipient lists and access credentials out of the inquiry form.
Let’s plan your next campaign message.
Start with your office, location, and campaign timeline.