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 the time zone you choose and stays armed through a restart.
Campaign schedule
Any zone
schedules run in the time zone you choose
Calendar or cron
pick exact dates, or use a cron expression
Auto
resumes once the daily limit resets
Restart
safe — schedules reload on boot
What the scheduler actually guarantees
Runs in any time zone you choose
Pingovo fills in the time zone you are working in, and you can switch to any other. 9 AM means 9 AM in that zone, 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, and you can pick any other. 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.
Spreading a large send across days
Scheduling answers when a campaign starts. A daily send limit answers how fast it goes once it has. Set one on the campaign and Pingovo sends up to that many a day and no more — the progress bar shows today's count against the cap, and the campaign tells you how many days are left at the current rate rather than making you work it out.
When the cap is reached the campaign pauses itself with the reason recorded, and a background job running every ten minutes picks it back up the moment the window resets. You do not restart it, and you do not lose your place — the recipients already sent stay sent, and the queue resumes where it stopped. That is what turns a 60,000-address list into a paced send instead of one burst that a receiving server reads as a spike.
What the campaign shows while it paces itself
What each campaign status means
A campaign is only ever in one of seven states, and the one people ask about most is paused — because a pause is usually Pingovo protecting the send rather than something going wrong.
- Draft
- Being built. Nothing is armed and nothing will send.
- Scheduled
- A date or a cron expression is armed and waiting for its moment.
- Sending
- Working through the recipient queue in batches right now.
- Paused
- Stopped for a recorded reason — the daily cap, a bounce rate climbing too fast, credits running out — and resumed automatically where the reason allows it.
- Completed
- Every recipient has a final outcome. The report is final.
- Cancelled
- Stopped deliberately before finishing. It will not restart.
- Failed
- The send could not proceed at all — a sender configuration problem.
A recurring campaign keeps every run separately
A weekly newsletter that overwrites its own numbers each Tuesday is worse than useless — you can never tell whether last week was better than this one. A recurring schedule in Pingovo does not accumulate into a single set of totals: each firing becomes its own run, with its own recipients, its own opens and clicks, and its own report.
The schedule itself stays in one place. Edit the content or the cron expression on the parent and every future run picks it up, while the runs already sent keep the numbers they earned.
- One parent schedule, one report per firing
- Next run recalculated and stored after each one completes
- Runs stay linked to the parent, so week-on-week is a comparison rather than an archaeology exercise
0 9 * * 2 · Asia/Kolkata
Runs
Tue 18 Feb
4,210 sent
41.8%
opens
Tue 11 Feb
4,186 sent
38.2%
opens
Tue 4 Feb
4,151 sent
44.1%
opens
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.
No. Scheduling and recurring sends are on paid plans. On the free plan you can still build a campaign and send it straight away.
Any time zone you choose. Pingovo fills in the one from your browser when you set the schedule, and you can switch to any other. It is stored on the campaign and the schedule runs in that zone — so a 9 AM send fires at 9 AM there, 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 the time zone you chose. 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.
Yes — set a daily send limit on the campaign. Pingovo sends up to that number each day, pauses itself when the cap is reached, and resumes when the window resets, until the list is finished. The campaign shows today's count against the cap and estimates how many days are left at the current rate, so a 60,000-address send paces itself rather than going out in one burst.
Pingovo pauses a send rather than pushing through a problem, and records the reason. The daily cap being reached is the common one and clears itself. Others include the bounce rate climbing past a safe threshold mid-send, credits running out, or the sending capacity available to you being exhausted for the day. The ones that resolve on their own are resumed automatically; the rest wait for you.
Start for free — 200 credits/day included
Build your first campaign for free, then upgrade to schedule it.