Set the campaign once. Pingovo sends it on time.
Schedule a campaign for a date and time, or set it to repeat on a cron schedule. Everything runs in your own time zone and stays armed through a restart.
Campaign schedule
Your zone
schedules run in your own time zone
5-field
standard cron for recurring sends
10 min
auto-resume after a daily-limit pause
Restart
safe — schedules reload on boot
What the scheduler actually guarantees
Runs in your time zone, not UTC
Pingovo picks up the time zone you are working in and interprets the schedule there. 9 AM means your 9 AM, with no offset arithmetic and no UTC conversion to get wrong.
Recurring sends on a cron schedule
Weekly, monthly, or a specific set of dates — any standard five-field cron expression. It is validated when you save, so an invalid expression is refused up front instead of silently never firing.
Survives restarts and pauses
Every armed schedule is reloaded when the server starts, so a deploy cannot quietly drop a send. Campaigns paused by a daily limit are picked back up automatically once the window resets.
Scheduling a campaign, step by step
- 1
Build the campaign and add recipients
Scheduling is refused until the campaign has recipients, so a schedule can never be armed against an empty list.
- 2
Pick one-time or recurring
Choose a single date and time, or a cron expression for a send that repeats. Recurring schedules calculate their next run after every execution.
- 3
Confirm the time zone
Pingovo fills in the time zone you are working in. The schedule is interpreted there, so the hour you typed is the hour it fires.
- 4
Watch it run, or cancel it
The campaign moves to scheduled, then sending when its moment arrives. Cancel a schedule any time before it fires, and monitor delivery live once it does.
Everything the scheduler includes
Part of campaign sending — not a separate add-on.
Frequently asked questions
Yes. Pick a date and time and Pingovo arms the campaign to send at that moment, or set a cron expression for a campaign that repeats. The campaign sits in a scheduled state until it fires, and you can cancel it at any point before then.
The time zone you are working in. Pingovo fills it in from your browser when you set the schedule and stores it on the campaign, then runs the schedule in that zone — so a 9 AM send fires at 9 AM where you are, not 9 AM UTC.
No. A scheduled campaign is a single send: everyone on the list receives it at the same moment, and that moment is fixed by the schedule you set in your own time zone. If your list spans several regions, pick the hour that suits most of your audience — or segment the list by region and schedule one campaign for each.
A recurring schedule takes a standard five-field cron expression — minute, hour, day of month, month, day of week. Pingovo validates it when you save and refuses an expression it cannot parse, rather than accepting one that would never fire. After each run it calculates and stores the next run time.
Nothing is lost. Every scheduled and recurring campaign is reloaded from the database when the server starts, so a deploy or a restart re-arms the schedules that were pending rather than dropping them.
It pauses rather than failing, and resumes on its own. A background job checks every ten minutes for paused campaigns whose daily window has reset, clears the counter and continues the send. Soft-bounced recipients are separately retried, so a temporary rejection does not cost you the contact.
Start for free
Build a campaign, set a schedule, and let Pingovo run it.