Skip to main content
← Back to glossary
Messaging compliance

Number warm-up

Was ist Number warm-up?

Dieser Eintrag liegt derzeit nur auf Englisch vor.

Number warm-up (also called sender registration warm-up or 10DLC warm-up) is the gradual ramp of message or call volume on a newly registered sender — a fresh 10DLC long code, short code, or alphanumeric sender ID — instead of sending at full volume from day one. Carriers have no delivery history to judge a brand-new sender by, so traffic is gated by a daily cap that rises along a growth curve until the number graduates as warmed, earning carrier trust instead of triggering spam-style filtering.

More detail

Warm-up on a messaging or voice sender is distinct from IP warmup (which ramps an email sending IP or domain) and from brand vetting (The Campaign Registry's trust-score screening of the brand behind a 10DLC campaign). The same reputation principle applies to all three, but number warm-up is about the sender's own traffic pattern: a cold number that jumps straight to campaign volume reads as spam-like to carrier filtering even when the brand and campaign are fully registered and approved.

Carriers gate cold senders because a sudden burst with no delivery history is the signature of snowshoe spam and abusive traffic, so messages above what the number's trust tier allows get filtered or dropped before delivery — the platform's daily cap exists so a sender's own pace stays inside what carriers will accept, rather than discovering the ceiling through silent filtering.

On Devotel Orbit, a warming US 10DLC number exposes its state on GET /api/v1/numbers/:id/warming — warming_phase (initial → ramp → steady → verified), the daily_cap, and the live current_day_count — while GET /api/v1/numbers/:id/warming/progression returns the 15-day progression forecast the dashboard warming chart renders. A send that would exceed the day's cap is refused before it reaches the carrier with a 429 WARMING_QUOTA_EXCEEDED response, and the warming phase a number currently holds — a carrier-side trust mechanism, not an Orbit-imposed requirement — still sets what carriers accept from it.

To get through warm-up without stalling a launch: pace each campaign under the day's cap, split early traffic across multiple warming numbers or route overflow through an already-warmed sender, and never retry-loop a refused send inside the same day — the cap resets at midnight UTC, so a retry storm only burns the quota you have left.

Häufige Fragen

How is number warm-up different from IP warmup?
IP warmup ramps an email sending IP address or domain for mailbox providers. Number warm-up ramps a messaging or voice sender — a 10DLC long code, short code, or alphanumeric sender ID — for mobile carriers. Same reputation principle, different asset and different gatekeepers: warm-up on one side does not carry over to the other.
Is number warm-up the same as brand vetting for 10DLC?
No. Brand vetting is The Campaign Registry's screening of the brand behind a 10DLC campaign, and it can raise a number's eventual throughput ceiling. Number warm-up is the ramp of the sender's own traffic pattern as it builds delivery history — a fully vetted brand still warms each new number up before carriers accept full volume from it.
What happens if a campaign exceeds a warming number's daily cap?
On Orbit the over-cap send is refused before it reaches the carrier with a 429 WARMING_QUOTA_EXCEEDED response, so you never pay for messages carriers would filter anyway. Split the day's volume over multiple warming numbers, route overflow through an already-warmed sender, or defer the remainder until the cap resets at midnight UTC — retrying inside the same day does not reopen quota.

Build it on Orbit

Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.