Fast is not always better
If send speed is too high, campaigns can pause or fail. That creates more work than it saves.
A steady campaign that completes cleanly is better than a fast campaign with many errors.
Choose speed based on risk
New lists and first-time campaigns should start slower.
Only increase speed after you see healthy results.
- New list: start conservative.
- Known healthy list: increase in small steps.
- Never jump from low to very high in one go.
Scale with test batches
Use a smaller first batch to check health, then scale.
This reduces the chance of large failures.
- Batch 1: small test send.
- If healthy: increase gradually.
- If errors rise: pause and fix root cause.
Common mistakes
Teams often re-run failed campaigns at the same high speed. That repeats the same problem.
Another common issue is ignoring failure patterns from bad contact data.
What to monitor during send
Watch campaign status while it runs. Do not wait until the end.
- Completion rate
- Failure count
- Pause events
- Follow-up queue size
Simple launch checklist
Run this list before each broadcast.
- List cleaned
- Template tested
- Rate chosen with reason
- Monitor assigned
- Pause/escalation plan ready
Open Help Center
Step-by-step setup and troubleshooting guides.
Review Legal Docs
Privacy policy, terms, DPA, and data request details.