Turn repetitive sending into an automated workflow.
Create a send plan, define recipients, control batches and delays, then start it and monitor the workflow.
Recipients
850
- Batch size
- 50 per batch
- Delay between emails
- 30 seconds
- Wait between batches
- 15 minutes
- Sending account
- Gmail
Batch 13 of 17
660 / 850
The workflow
Six steps, then it runs
After the first plan, only the template and the data need choosing.
- 01Step 1
Select a template
The email, and any document to generate with it.
- 02Step 2
Select recipients
A dataset, then all rows or a chosen subset.
- 03Step 3
Configure sending
Batch size, the gap between messages, the wait between batches.
- 04Step 4
Prepare
Every recipient is validated and given its own row.
- 05Step 5
Start the plan
You press send; the campaign claims its first batch.
- 06Step 6
Monitor
Watch each recipient's status as the plan works through.
What you configure
Every setting a plan actually has
These are the real controls, with the ranges the product enforces.
Recipients
Every row in the dataset, or an explicit subset of up to 5,000. Individuals can be skipped from a prepared plan and put back later.
Batch size
From 1 to 10,000 recipients per batch, so the plan works through the list in measured groups.
Delay between emails
A gap of 1 to 300 seconds between individual messages, either fixed or randomised within a range.
Wait between batches
Anything from one second to 24 hours. The plan resumes on its own when the wait is up.
Start and stop
Pause a running plan and continue exactly where it stopped, or cancel it. A message already in flight always finishes.
A plan starts when you send it
There is no calendar scheduler and no recurring plan: you press send, and the campaign then works through its batches and waits on its own. With a wait of up to 24 hours between batches, a single plan can still run for days without anyone watching it.
Watch it as it goes.
A running plan reports progress by batch and a status for every individual recipient, so you can tell the difference between a campaign that is simply still working and one that has a problem worth looking at.
From here you can pause and resume, retry the recipients that failed, or take specific people out of the remaining queue.
About bounces
“Sent” means the receiving server accepted the message. It can still bounce afterwards, and that notice goes to the inbox of the account you connected rather than into this view — OwnSender does not track bounces, so it does not claim a status it cannot fill in.
- SentThe receiving mail server accepted the message.612
- SendingCurrently being handed over.48
- PendingPrepared and waiting for its batch.182
- BlockedNeeds a fix before it can be sent.6
- FailedAttempted, and the provider rejected it.2
Why automate it
What a send plan saves you
- Configure once, reuse the shape
- A plan keeps its template, its pacing and its recipient rules, so the next run starts from a known-good setup.
- Runs unattended
- Once started, the plan works through every batch and every wait on its own — a send spread over hours needs no supervision.
- Interruptible without loss
- Pausing leaves every waiting recipient pending, so resuming continues from exactly where it stopped rather than starting over.
- Failures are isolated
- You can retry only the recipients whose sends failed, without re-sending to anyone who already received their message.
- Nothing sent half-ready
- A recipient missing a value is held back and marked Blocked rather than emailed with a gap in the sentence.
- Visible per recipient
- Every row carries its own status, so six problems never hide behind six hundred successes.
Automate your next send
Build the plan once, press send, and let it work through the list.