#Outbound Campaigns

Outbound Campaigns is a partner operational surface for creating, validating, launching, pausing, resuming, cancelling, and reporting on AiDial outbound campaigns.

#Who Can Use It

Role	Access
`partner_admin`	Create campaigns, import contacts, attach DNCR/registry wash evidence, run validation, control campaign state, and view reports.
`partner_user`	View assigned-client campaign status, contacts, validation, and reports in read-only mode.

Customer roles do not manage outbound campaigns in the current portal.

#Campaign Workflow

Create a campaign for an assigned client project.
Import contacts by CSV.
Attach DNCR/registry wash evidence when required.
Run validation and resolve blockers.
Launch the campaign when validation is ready.
Pause, resume, or cancel the campaign as operational needs change.
Review reporting for contact outcomes, retry state, registry results, and linked call summaries.

There is no hard delete action. Cancelling preserves campaign, audit, and reporting history.

#CSV Import Rules

CSV imports require a to_number column. Optional columns include contact reference, recipient timezone, registry status/evidence, consent evidence, exemption information, call type, priority, max attempts, and campaign-approved personalization keys.

The portal sends CSV content through its server-side upload path to the AiDial API. The API validates rows, accepts valid rows, returns row-level errors for invalid rows, and encrypts phone numbers and personalisation before persistence. Portal responses display masked phone placeholders and safe metadata only.

#Launch Validation

Telemarketing and research campaigns cannot launch until validation confirms:

imported contacts exist
DNCR/registry wash evidence is present and current where required
contacts are not on the registry and have required registry status
consent or exemption evidence is valid where required
calling-window, public-holiday, recipient-timezone, and project outbound compliance controls are ready
outbound capacity is configured
required CLI disclosure fields are present

Run and resume controls recompute validation before changing campaign state.

#Data Safety

The portal and API do not expose raw phone numbers, imported CSV payloads, ciphertext, raw configuration files, provider secrets, secret-management references, bearer tokens, API keys, or transcripts. Partner users receive read-only operational summaries only.