> ## Documentation Index
> Fetch the complete documentation index at: https://developers.callaro.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Campaigns

> Understand how campaigns package audience, timing, numbers, and agent behavior into a controlled outbound program.

# Campaigns are the execution unit for outbound calling.

A campaign in Callaro defines who should be called, when they should be called, which agent should conduct the conversation, which numbers should originate those calls, and how execution should be throttled.

<CardGroup cols={2}>
  <Card title="Audience" icon="users">Campaigns can target imported contacts, saved segments, or dynamically prepared lists from your own systems.</Card>
  <Card title="Timing" icon="clock-3">Calling windows, time zones, and concurrency rules prevent campaigns from running outside business policy.</Card>
  <Card title="Agent logic" icon="bot">The campaign selects the active agent and therefore the voice, script, retrieval policy, and permitted actions.</Card>
  <Card title="Number pool" icon="phone">A campaign can use one or more numbers so you can support deliverability, geography, and continuity requirements.</Card>
</CardGroup>

## Launch readiness checklist

<Steps>
  <Step title="Validate contact quality">
    Confirm phone normalization, suppression checks, and segment logic before launch.
  </Step>

  <Step title="Validate script and objective alignment">
    Ensure the selected agent is purpose-built for this campaign objective.
  </Step>

  <Step title="Validate numbers and windows">
    Confirm number pool health, local timezone policies, and concurrency settings.
  </Step>

  <Step title="Validate downstream actions">
    Verify webhook consumer, CRM write paths, and alerting for campaign failures.
  </Step>
</Steps>

<Note>
  Only draft campaigns should be edited structurally. Once execution has started, prefer pause, resume, or clone workflows to preserve auditability.
</Note>