Scheduler
One place to see and cancel future MailReach and VoiceReach launches.
Scheduler shows every campaign queued for a future launch time. It combines scheduled MailReach campaigns and scheduled VoiceReach campaigns into one chronological view.
The backend checks due campaigns once per minute. When a scheduled time arrives, the normal launch pipeline runs, so delivery, call history, alerts, and dashboard metrics behave the same as a manual launch.
End-to-end operator flow
- 1Start: open this feature from the dashboard sidebar and confirm your prerequisites are connected in Settings.
- 2Configure: complete the required fields and selections for your target audience and objective.
- 3Launch: run the action immediately or schedule it for later based on your workflow.
- 4Monitor: watch status, history, and dashboard metrics to confirm progress and outcomes.
- 5Troubleshoot: if results stall, verify credentials, audience data quality, and feature-specific validation messages.
What appears here
MailReach campaigns
Campaigns with status SCHEDULED and a scheduledAt timestamp.
VoiceReach campaigns
Campaigns with status SCHEDULED and a scheduledAt timestamp.
Scheduling flow
- 1Open MailReach or VoiceReach and configure the campaign.
- 2Choose Schedule instead of launching immediately.
- 3Pick a future date and time.
- 4Open Scheduler to verify the campaign is queued.
- 5Cancel from Scheduler if the campaign should return to draft/immediate mode.
Backend behavior
The Campaign Scheduler runs every minute in the NestJS backend. It queries MongoDB for due scheduled email and calling campaigns, then launches each campaign through the same service method used by manual launch.
If the backend is offline at the scheduled time, the campaign launches after the backend comes back and the cron sees the campaign as due.
Tips
- Scheduling stores launch intent on the campaign document; there is no separate queue service.
- Make sure provider credentials and contacts are ready before the scheduled time.