Ananasi · Campaign services
Self-Service Campaign Messaging
Self-service sending should be evaluated against the actual product controls and access available to the campaign.
Built around your self-service workflow questions.
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
Drafting, approval, scheduling, import, pause, and export permissions are different capabilities. A demonstration should show which roles can perform each action.
Review access before purchase
Ask for an implemented workflow demonstration with synthetic records. Verify audit history, suppression visibility, campaign separation, and what support is available when an operator makes an error.
- Implemented controls
- Role access
- Audit history
- Support path
Demonstrate the permission boundary
Use a synthetic operator account to show which actions it can perform and which require another role. An operator who can draft should not be assumed to have approval or export access. Ask the demonstration to include a changed draft, a suppressed contact, and an attempt to revise a scheduled send.
What to retain from this review
- Role demonstration
- Approval and revision behavior
- Suppression visibility
- Support arrangement
Common questions
What belongs in the first inquiry?
Your committee, office, jurisdiction, target timing, and the implemented controls 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.