Throttling
Throttling is the deliberate limiting of send volume — emails per hour, calls per day, API requests per minute — to stay within deliverability, rate-limit, or compliance boundaries.
What is Throttling?
Throttling protects reputation, compliance, and system stability. In email, throttling caps sends per hour to avoid triggering ISP-level rate limits and reputation damage. In API integrations, throttling caps requests per minute to stay within vendor rate limits. In voice, throttling caps calls per hour to comply with TCPA-like regulations. Modern throttling is dynamic — it tightens automatically when negative signals fire (deliverability drop, API error spike) and loosens when conditions are healthy.
Why it matters
- Protects against reputation damage from sending spikes.
- Keeps systems within vendor rate limits to avoid hard failures.
- Modern throttling is dynamic — tightens automatically when signals fire.
Use cases
- Email send throttling. Caps per-mailbox send rate to protect deliverability.
- API request throttling. Caps integration request rate to stay within vendor limits.
- Voice throttling. Caps calls per hour for TCPA and similar compliance.
How turgo helps
turgo throttles dynamically based on mailbox health, reputation signals, and per-vendor rate limits — protecting deliverability without unnecessarily restricting send volume.
See turgo in action →
