Campaign Settings Reference

Plain-English map of Create Campaign and Edit campaign in the wizard (New Campaign, including opens from a template, clone, or existing draft). The behavior described here matches the live product.

Slot media brief

Use these briefs when adding final captures to the asset registry:

Kind	Brief
Static	Full wizard or Review summary table for “where does this field live?”.
GIF	Stepping 1–6; highlight Schedule → Outcomes → Review.
Video	Operator narrative: which step owns telephony vs schedule vs goals.

Jump to the right step

What blocks Next (by step)

Step	Blockers
1 Basics	Non-empty Campaign Name; Agent selected.
2 Telephony	At least one number in Number Pool (and related telephony state).
3 Audience	On create: CSV file, or at least one Contact ID, or a Segment selected. On edit, audience validation is relaxed so you can move steps while loading an existing campaign.
4 Schedule	If Scheduled: Schedule Date & Time must be set. (The client does not require “at least one call window” to advance.)
5 Outcomes	Invalid goal targets (when a target is non-empty); A/B on with variant configuration errors.
6 Review	(none) — Create / Save is on this step.

Steps 1–3 (short)

Template (optional) — pre-fills fields when you pick a saved template.
Campaign Name / Agent — Basics.
Primary From Phone Number / Number Pool / Call Recording / Prefer country-matched numbers for each contact — Telephony. Pool capacity uses the in-app capacity preview for the numbers you selected.
Contact Source — CSV, Contact IDs, or Segment; CSV column or segment field mapping and optional Call Variables — Audience. Exact labels and options match the wizard.

Step 4: Schedule (field reference)

UI / concept	What the app does
Trigger Mode	Immediate or scheduled start; scheduled campaigns store a start date and time.
Schedule Date & Time	Shown when you choose a scheduled start; required to continue.
Timezone	Stored on the campaign; options are the fixed list in the Timezone control.
Call Windows	Per weekday: on or off, start and end time (24-hour style in the control); Copy to all copies times only. Defaults: Mon–Fri 09:00–18:00 on, weekend off.
Testing Mode / dry run	Shown only in non-production builds. Production users do not see this; new campaigns are live-capable by default.
Parallel calls	Full pool capacity vs a custom concurrency limit; custom is capped at the pool ceiling when the preview supplies it.
Priority	1–10, validated as you type.
Call window timezone mode	New campaigns from this wizard use contact-local evaluation; there is no separate Schedule dropdown for it.

Step 5: Outcomes (field reference)

UI / concept	What the app does
Retry on voicemail	On or off.
Max retries	1, 2, or 3 only.
Max voicemail attempts	Optional; disabled when retry-on-voicemail is off; empty means no separate limit.
A/B testing	When valid: enabled test with weighted variants, distinct agents per variant, weights totaling 100%, variant A matches the Basics agent (read-only in the UI).
Follow-ups / Contact memory	Shown on eligible plans. Includes missed-call follow-up, contact memory, and follow-up rules attached after the campaign is created.
Campaign Goals	Up to three goal types from the wizard list; optional; validated when you enter a target.

Step 6: Review (what appears in the summary)

The Review list is a partial mirror of the wizard. It includes the rows documented in Wizard Step 6: Review (name, pool, source, trigger, mode or dry-run, retries, concurrency, priority, timezone, windows, A/B, recording, goals, optional call variables). It does not duplicate every Telephony, Audience, or plan-specific Outcomes line.

Submit

Create — saves a new campaign (with CSV upload, contact IDs, or segment, depending on what you chose).
Edit — updates an existing campaign (with or without re-upload flows depending on source).
On failure, the banner shows Failed to create campaign or Failed to save campaign with Retry.

Inbound returns and smart routing

When a contact in this campaign calls you back, Callaro's smart inbound routing attributes the call to the campaign and routes it to the right agent automatically. Specifically:

An inbound from a contact with an active or retry_pending task in this campaign closes that task as contacted_inbound and bridges the call to the campaign's agent.
An inbound that matches an active follow-up created from this campaign is attributed to the campaign and the follow-up is closed.
The Campaign detail page now includes an Inbound returns card with a count by routing reason and a link to filtered call logs.

You can disable smart routing per tenant or tweak look-back windows in Tenant settings → Inbound routing. See Inbound Routing for the full layer-by-layer behavior, kill switch, and contact memory scope.