Send · Deliverability
Warmup is built in, and honest about what it can do
New senders default onto the enforced age ramp. Warmup-enabled senders exchange AI-written, deliberately mundane traffic between your own domains under the same ceiling. Real sends, metered, logged, and never shown in your inbox. What this does not claim: reputation at Gmail and Outlook is built by mail landing in inboxes there, which a self-contained network cannot fake.
62 days old · today’s ceiling comes from the age band
31 days old · today’s ceiling comes from the age band
9 days old · today’s ceiling comes from the age band
2 days old · today’s ceiling comes from the age band
What is actually going on
Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.
The ramp is enforced where the sender is picked
One function lowers your ceilings by an age-banded schedule on any connection with the ramp on. It is the only enforcement point because it is the only path that sends.
Scoring comes from delivery webhooks, not from a guess
Per-sender deliverability is computed from real delivery, bounce and complaint events. A spike re-anchors the ramp automatically and raises an alert that names the numbers and the next action.
A bounce or a complaint suppresses the recipient
And skips their remaining queue rows. Not a flag on a report. An actual stop, at the moment the vendor tells us.
What we will not pretend
Cross-provider inbox-placement warmup needs mailboxes at the providers you want reputation with. Ours is a domain stack, so it cannot fake that. If a peer network is ever wanted, it is a vendor integration and we will say so.
Step by step
How warmup & deliverability runs
- 1
Anchor
Age runs from the attestation date if you set one, otherwise from connection.
- 2
Ramp
The band decides today's ceiling. Weekly is five ramped days.
- 3
Warm
An hourly runner sends mundane traffic between your own warmup-enabled senders, under the same ceiling.
- 4
Score
Delivery events per sender. A spike re-anchors the ramp and raises a worded alert.
The numbers
Facts, not adjectives
Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.
- LinkedIn bands
- 5 / 10 / 20 / your limit at <7, <30, <60, 60+ days
- Domain bands
- 10 / 25 / 50 / your ceiling
- Warmup log
- warmup_messages, never the inbox
- Health cadence
- Every 6 hours
- On complaint
- Suppress recipient, skip remaining steps
Warmup & deliverability, honestly
Does warmup traffic cost credits?
Yes. It is a real send through a real transport, so it is metered like one. Nothing about it is simulated.
Can I skip the ramp on an old account?
Set the attestation date. That is what it is for: the ramp anchors to it instead of to when you connected.
Send
Out through your own accounts, at a safe pace
Keep reading
All featuresWarmup & deliverability is one part of it. The rest runs too.
Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.
Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.