Write a campaign charter before a script
A useful charter fits on one page. It states why the business is calling, who should receive the call, what evidence makes each destination eligible, what the assistant may ask, and what counts as completion. Appointment reminders, service updates and a permissioned follow-up can look similar in a dashboard while carrying very different expectations for the recipient.
Keep one primary purpose per campaign. If the conversation begins as an operational reminder and turns into a promotion, your permission model and caller expectation may change. Split purposes when the approval, audience or desired action differs. That also makes results easier to interpret and scenarios easier to review.
Make recipient eligibility inspectable
Do not upload a contact list and treat its existence as permission. For each destination, preserve the approved purpose, the source and timing of relevant evidence, suppression state, jurisdictional review and any expiry or withdrawal rule your advisers require. The campaign owner should be able to explain why a given record was eligible at launch.
Design for subtraction. A do-not-call update, withdrawn permission, invalid destination or changed customer state should remove a record before an attempt. Reconcile your source system with campaign membership instead of allowing copies to diverge silently. When evidence is incomplete, quarantine the record for review rather than guessing.
- Approved purpose and audience definition
- Evidence source and accountable owner
- Suppression and do-not-call checks
- Destination and market eligibility
- Audit note for exceptions and removals
Design timing, attempts and exits as one policy
Calling windows should be evaluated in the recipient's local time, not the campaign manager's clock. Add business-specific quiet periods as well as any requirements your legal review identifies. A technically permitted hour can still be a poor customer experience for the purpose of the call.
Set an attempt policy before launch: when a retry is allowed, which outcomes stop further attempts, and how a person can suppress future contact. Avoid optimizing for maximum dials. The better operating metric is whether the intended audience received an appropriate, explainable interaction without unnecessary repetition.
Version the conversation and its structured result
A conversation scenario should define the opening disclosure, identity checks appropriate to the use case, permitted questions, prohibited claims, fallback language and completion states. Store each approved scenario as a fixed version. If the wording or decision logic changes, create a new version and preserve which campaign run used the earlier one.
Plan the result before the call. A booking request, preference, declined contact, wrong destination or request for a person should become a structured outcome that downstream operators can understand. Free-form summaries can add context, but they should not be the only source for workflow-critical decisions.
Voxora starts with a required introduction as a Voxora assistant for your business, in the configured language. This sentence does not explicitly say 'AI'; review any additional notices for your market.
Run a controlled rehearsal
Use internal or specifically approved destinations to rehearse the entire path. Test time-zone boundaries, suppression changes, unanswered calls, mid-call opt-out language, ambiguous answers and the action that follows each disposition. Review the caller identity and the experience when the recipient calls back.
Have someone outside the campaign team challenge the run. Their job is to find assumptions: an unclear purpose, a data field with no owner, an exit that does not suppress future attempts or a result that cannot be reconciled. Record the evidence required to move from rehearsal to the agreed activation gate.
Operate the campaign as a controlled change
Name the person who can start, pause and stop the campaign. Define a small first audience, review delivery history and dispositions, and set escalation conditions before expanding. A compliance control is useful only when someone understands what it blocked and can investigate why.
Voxora supports saved campaign plans, fixed scenario versions and checks around consent purpose, do-not-call state, local calling windows and destination eligibility. Availability remains subject to the activated jurisdiction and account. These controls support your process; they do not choose the lawful basis, approve the message or replace counsel.