Wizard Step 4: Schedule
Schedule is your campaign’s safety rail. It controls when calls are allowed, which timezone rules apply, and how fast the system can dial without harming quality.
At a glance
- Choose Immediate vs Scheduled start.
- Set a campaign timezone (the UI uses contact-local call window behavior by default).
- Define call windows by day and time.
- Decide parallelism: full pool capacity vs custom concurrency.
- Optionally set a budget cap and priority.
Before you start
- Decide the “acceptable calling hours” for your audience.
- Know whether you want a supervised launch window.
- Know if this campaign must share capacity with other campaigns.
If a call would annoy you at that hour, it will annoy your customers too. Tight windows beat wide windows for early learning.
Trigger Mode
Immediate
Calls can begin as soon as the campaign is launched (subject to call windows and capacity).
Scheduled
Recommended Use scheduled mode when you want a clean launch event and live monitoring.
Set a Schedule Date & Time so the system has a clear start moment.
Timezone
Set timezone thoughtfully:
- If your audience spans multiple regions, prioritize contact-local behavior and consistent windows.
- Avoid choosing “ops timezone” unless your audience is also in that timezone.
Call Windows (the real safety rail)
For each day:
- Enable the day.
- Set start/end times.
- Use Copy to all to replicate times once, then adjust exceptions.
If all days are disabled, or your windows are too narrow for your scheduled start, the campaign can appear “stuck.” If you see no progress, check windows first.
Parallel calls (pacing)
Use full pool capacity
Recommended Start here for most pilots.
This uses the maximum safe concurrency based on:
- the sum of per-connection limits across your selected number pool, and
- any tenant-level concurrency cap.
Custom concurrency limit
Advanced Use this when you want to:
- slow-ramp a new campaign,
- leave headroom for other campaigns,
- keep one telephony connection from getting saturated.
The UI clamps your custom value to the pool ceiling (so you can’t accidentally exceed safe capacity).
Priority
Advanced Priority matters when multiple campaigns compete for dispatch capacity.
If a lower-priority campaign is “not getting airtime,” priority can be a factor — but windows and capacity are more common blockers.
Budget cap
Advanced Use budget caps for governance:
- pilots (limit spend while learning),
- shared tenants (avoid surprise costs),
- operational containment.
Testing mode (development only)
In some environments you may see a Testing Mode / Dry run toggle.
- Dry run processes tasks without placing real calls.
- This is for testing configuration safely in development.
If you don’t see it, that’s expected in production.
Validation rules (what blocks Next)
- If Trigger Mode is Scheduled, a schedule date/time must be provided.
Common mistakes (and quick fixes)
- Campaign appears stuck. Fix: verify enabled call windows and timezone.
- Quality drops at higher speed. Fix: reduce concurrency and narrow windows; review number health.
- Team can’t monitor launch. Fix: schedule a supervised window and coordinate owners.
Final checklist
- Trigger mode matches how you want to launch.
- Timezone and call windows match the audience, not internal convenience.
- Concurrency is intentionally chosen (full pool vs custom).
- If using budget caps, the cap matches pilot intent.