---
title: "A practical IP warming schedule you can hand to a new customer"
canonical: https://pulsepigeon.com/blog/ip-warming-schedule-practical-guide
last_updated: 2026-10-20
---

# A practical IP warming schedule you can hand to a new customer

A practical guide to PulsePigeon's staged dedicated-IP volume caps, reputation thresholds, minimum dwell, and safe pauses when a gate is not met.

Status: dedicated IPs are an operator-gated beta for eligible Scale and Enterprise tenants, available by request, not generally available and not self-serve. This post describes the warm-up automation built for them.

PulsePigeon's built-in schedule uses five daily recipient caps: 100 at starter, 250 at ramp_250, 500 at ramp_500, 1,000 at ramp_1000, and 5,000 at mature. These are platform safety caps, not a promise that every mailbox provider will accept the same traffic pattern.

Before a stage can advance, it must meet its delivered-volume floor: 50, 150, 350, and 750 messages for the four non-mature stages. The default automated schedule also requires seven days in each non-mature stage.

Advancement pauses when the current stage window exceeds any implemented ceiling: a bounce rate above 5%, a complaint rate above 0.1%, or a deferred rate above 20%. Insufficient delivered volume and incomplete dwell time are also explicit blockers.

Treat a blocker as a diagnostic signal, not a reason to force the stage forward. Correct list quality, authentication, routing, or destination-specific deferrals, then let new delivery events establish a clean evaluation window. The [DNS checker](/tools/dns-checker) and [transactional email guide](/transactional-email) provide starting points for authentication and application-mail context.

Keep critical transactional traffic on a proven route while a new dedicated IP earns reputation. PulsePigeon's operator-controlled routing policies and warm-up-only provider gate support a bounded canary instead of an all-at-once cutover.