Increase seasonal volume safely
Plan pre-season ramp so peak events look like natural growth, not a cold spike.
Objective
Scale sending safely
Increase sending volume on an already warm identity without triggering filters.
Starting state
Known peak season target above current baseline
Prerequisites
- Historical season metrics
- Capacity plan
Estimated time
2–4 hours
Difficulty
advanced
Required access
- ESP
- campaign calendar
Inputs
- Peak target
- Lead time in days
- Segment priority
Step-by-step instructions
- Back-plan the rampWork backward from peak day to define required daily steps.
- Pre-warm cohortsRaise volume on engaged segments before the peak event.
- Execute peakHit peak with monitoring and a prepared rollback threshold.
Verification
- Pre-peak days complete without metric breaches
Common mistakes
- Peak-day spike after skipping pre-warm days
- Split peak across IPs or subdomains if step size is still too large?
Rollback / recovery
- Defer non-critical sends and protect engaged core traffic
Expected outcome
Seasonal peak delivered with preserved reputation.
When to escalate
- Provider throttling on peak day