Sent at the speed receivers accept. Never a burst to catch up.
SendTo’s dispatch engine is governed. Every campaign leaves at rates set per receiving provider and per domain, and those rates are never exceeded — including to make up lost time. Receivers see a steady, predictable sender, and steady, predictable senders are the ones they reward.
Receivers score the rate as closely as the content. Most platforms burst anyway.
Every major mailbox provider watches how much mail a domain sends per hour, and how that compares with its history. A sudden spike is one of the strongest signals they use — because a spike is what a compromised account or a spammer with a fresh list looks like. It does not matter that your campaign is legitimate. The spike gets throttled, then deferred, then, if it keeps coming, blocked.
The platforms that do pace usually defeat the purpose. They send at a rate, fall behind, and then burst to hit the schedule. The burst is exactly the spike the pacing was supposed to prevent. The schedule was met. The domain paid for it.
SendTo’s engine has one rule: the governed rate is the rate. If a window is missed — a receiver deferred, a domain was slowed — the platform continues at the governed rate. The campaign takes a little longer. It arrives, and the domain’s standing is intact.
Separate limits for every receiver
Gmail, Microsoft, Yahoo and everyone else have different tolerances and different histories with each domain. The dispatch engine holds a separate rate for each receiver on each domain, adjusted from the responses that receiver is giving right now. A deferral at one provider slows that lane; the others keep flowing.
- Per-receiver, per-domain rate limits
- Adjusted from live receiver responses
- A slow lane never slows the others
● Automated 12.1%
Scanners never count as customers.
| Variation | Subject line | Human opens | Clicks |
|---|---|---|---|
| A · winner | Your six-month check-up is due, {first name} | 33.2% | 7.4% |
| B | Six months already? Let’s keep that smile on track | 29.6% | 6.2% |
No catch-up. Ever.
This is the rule most systems break and the one that matters most. When dispatch falls behind — and it will, because receivers defer — the platform does not burst to recover. It continues at the governed rate until the campaign is done. The trade is a campaign that finishes a little later for a domain that stays trusted. Every serious sender makes that trade.
- Missed windows are continued, never compensated
- Completion time shown honestly
- Reputation never spent to hit a clock
Visible, never a setting to get wrong
See what is queued, what is flowing and at what rate — per receiver, per domain, per campaign. What you cannot do is turn the governor up, because the rates come from the receivers and exceeding them would cost the client the domain. The platform makes the call a deliverability engineer would make, every hour of every day.
- Live queue and rate view per campaign
- Rates derived from receiver behaviour
- No throttle to configure
Steady sending is what receivers reward. Now it is automatic.
Domains that stay trusted
Every campaign adds to a domain’s reputation instead of spending it. Over a year that compounds into the deliverability your clients notice.
Honest timing, no surprises
A campaign shows how long it will take and why. Schedule it early enough and it lands when it should — without a burst.
Nothing to babysit
No throttle to set, no queue to watch. Launch, and the platform sends at the right speed for every receiver.
The first time I saw a platform refuse to catch up, I knew whoever built it had actually run mail at volume.
Questions
How long will a campaign take?
It depends on the size, the client’s domains and how receivers are responding. Progress and rate are shown live. Large campaigns to well-established domains complete quickly; the platform never trades reputation for speed.
Can I make it faster?
Add managed domains. More warmed domains means more lanes at the governed rate. The rate per lane comes from the receivers and is not adjustable.
What happens when a receiver defers?
That lane slows; the others continue. When the receiver accepts again, the lane resumes at the governed rate — never with a burst.
Does pacing affect time-sensitive campaigns?
Schedule so that dispatch starts early enough for the governed rate to complete in time. The expected duration is shown when you schedule.
Is this the same as warmup?
They work together. Warmup sets a domain’s daily ceiling from its history; pacing governs the hourly rate at which each receiver gets mail from it. Both are automatic.
Send at the speed that keeps you trusted.
Governed dispatch is on for every client, every campaign, from the first send.
No contract · Cancel any time · Explore everything before you pay