Campaign Settings Reference
Use this page as the plain-English reference for every important field in the Campaign Wizard.
It’s designed for operators who want to answer these questions fast:
- What does this field control?
- When should I change it?
- What breaks if I get it wrong?
Before you start
- Open the campaign draft you are reviewing.
- Know the campaign's audience, objective, and follow-up path.
- Have the script owner and campaign owner available if you expect to make changes.
Great campaigns are internally consistent: the agent matches the audience, the numbers match the geography, the schedule matches the experience, and outcomes match the follow-up workflow.
Quick decision map (where problems usually live)
- Pickup rate is poor: start with Telephony (numbers + pool + country match) and then Schedule (pacing).
- Outcomes are confusing: start with Agent (Basics) and Outcomes (retries/follow-ups/goals).
- “Nothing is dialing”: start with Audience and Schedule (windows/timezone/trigger).
Field-by-field reference (what it means + how to decide)
Campaign name
Recommended Name it so a teammate understands it without opening settings.
If the name is unclear, reporting and ownership drift later.
Agent
Recommended The agent controls the call behavior (script + tools + voice).
Change the agent when:
- the audience changes, or
- the intended “successful call” changes.
Template (optional)
Use templates as baselines when you want a standard default. Prefer cloning for “known-good in the wild” configs.
Primary From Phone Number
Recommended Required. Also becomes part of your number pool.
Number pool
Use a pool to protect deliverability and scale. The pool uses performance-weighted rotation and keeps contacts sticky to the first successful number.
Prefer country match
Recommended Keep ON when you have multi-country audiences and matching numbers.
Call recording
Keep ON for QA, transcripts, and coaching.
Audience source
- CSV: best control and mapping flexibility
- Segment: best reusability if your segments are owned and clean
- Contact IDs: best for advanced workflows
Field mapping (CSV + Segment)
Mapping decides whether the agent has the context it expects. Treat duplicate mapping warnings as blockers.
Call variables
Campaign-wide constants applied to every call. Use them for offer labels, rep names, internal campaign tags.
Trigger mode
- Immediate: begin when launched (within windows)
- Scheduled: begin at a specific time (best for supervised starts)
Schedule date/time (Scheduled trigger only)
Required if Scheduled is selected.
Timezone
Set to match the audience experience. Avoid “ops timezone” unless the audience is also there.
Call windows
Per-day allowed dial times. If all days are disabled, the campaign can appear stuck.
Parallel calls (concurrency)
- Full pool capacity: uses the safe ceiling computed from the number pool
- Custom limit: use to slow-ramp or leave headroom
Priority
Advanced setting when campaigns compete for dispatch capacity.
Budget cap
Governance lever for pilots and spend containment.
Retries
Sets total attempts per contact and voicemail behavior. Bad retries amplify bad lists.
A/B testing
2–3 variants with weights totaling 100. Variant A is always the Basics agent.
Goals
Targets for answer rate, conversion rate, and call score. Invalid goals block Next.
What good looks like
- The campaign tells one consistent story end-to-end.
- The pilot is sized and scheduled for learning.
- Telephony capacity is understood, not guessed.
- Outcomes match follow-up reality.
Final checklist
- Name and agent match the intended outcome.
- Numbers and schedule match the audience experience.
- Audience source and mapping are correct.
- Concurrency is intentionally paced.
- Outcomes match real follow-up capacity.