Bulk sending without losing control.
Send personalized emails to multiple recipients while controlling batches, delays and recipient selection.
Recipients
1,000
- Batch size
- 50 per batch
- Delay between emails
- 30 seconds
- Wait between batches
- 10 minutes
20 batches of 50, a 30-second gap between messages and 10 minutes between batches.
Controlled sending
Four controls, and you set all of them
Every value here is enforced by the product, not a suggestion.
Recipients
Send to every row in your dataset, or pick an explicit subset. You can also take individual recipients out of a prepared campaign and put them back later.
Batch size
Break the campaign into chunks, from 1 up to 10,000 recipients each, so it goes out in measured groups instead of all at once.
Delay between emails
Leave a gap between individual messages — up to five minutes, either fixed or randomised within a range you set.
Wait between batches
Pause between chunks for anything from one second to 24 hours. The campaign resumes on its own.
Decide exactly who is included.
A campaign is built from a dataset, and you choose how much of it to use.
- All recipients
- The default. Every row in the connected dataset is included.
- Selected recipients
- Choose an explicit set of rows to send to, up to 5,000 at a time.
- Skip individuals
- Remove specific recipients from a prepared campaign without touching anyone else, and unskip them later.
- SentAccepted by the mail server1,187
- SendingCurrently in progress24
- PendingPrepared, awaiting its batch31
- BlockedNeeds a fix before sending6
- FailedRejected by the provider2
“Sent” means the receiving mail server accepted the message. Open and click tracking are not part of this view.
Why it helps
What controlled sending is actually for
- Manage the sending pace
- A large campaign leaves your account gradually rather than in one burst, which keeps the volume predictable.
- Control the workload
- Generation and sending are spread over time instead of competing for resources at once.
- Work through batches unattended
- Once a campaign is running it continues through its chunks on its own, including the waits between them.
- Avoid sudden spikes
- Pacing smooths a send out, so a thousand messages do not all hit your provider in the same minute.
What pacing does not do
Pacing controls how quickly OwnSender asks your provider to send. It cannot promise that a message reaches an inbox rather than a spam folder — that decision belongs to the receiving mail server, and no sending tool can guarantee it.
Messages go out through your own connected account, so the practical ceiling on volume is whatever Gmail, Microsoft or your SMTP provider allows. Those limits are between you and them.
Set it up once, then let it run.
A campaign keeps its recipients, its batch size and its waits, so once it starts it works through the whole list on its own — including the pauses between batches.
You can pause a running campaign and continue later from exactly where it stopped, retry only the recipients that failed, or cancel it outright. A message already in flight always finishes, so a send never stops mid-message.
- Create the campaign01
Template, dataset, recipients
- Set the batch size02
1 to 10,000 per chunk
- Set the delays03
Between messages, and between batches
- Send04
Starts when you press send
- Monitor05
Per-recipient status as it works through
The sequence
What running a campaign looks like
- 01Step 1
Prepare
Recipients are validated and one row is created per person.
- 02Step 2
Configure
Batch size, message gap, and the wait between batches.
- 03Step 3
Send
The campaign starts and claims its first chunk.
- 04Step 4
Monitor
Watch statuses update as each batch completes.
Create a sending plan
Pick your recipients, set the pace, and let the campaign work through it.