Instantly
built to land, wired to route.
Instantly is the sending layer of your outbound stack, and we run it like infrastructure: provisioned domains, a warmed mailbox fleet, placement telemetry, and every Unibox reply routed into the CRM with an owner attached. You get a cold-email operation that feeds the pipeline, not a login and a warmup toggle.
Sending Console
Inbox fleet · live
Placement, warmup, and every Unibox reply monitored per mailbox, not discovered when the quarter misses.
Trusted by teams at
Deliverability triage
Cold email dies quietly, then all at once.
Instantly makes it trivial to start sending, and almost nothing to keep the sending healthy. It will happily burn your domains on an aggressive ramp, fire an unsuppressed list into spam traps, drift into Promotions unmonitored, and let replies pile up in the Unibox with no owner. You find out when the pipeline that outbound was meant to feed simply isn't there.
Domains burned by aggressive ramp
New accounts pushed from zero to 150 sends a day inside a week. The warmup pool cannot out-run the ramp: mailboxes get Google-throttled or land on Spamhaus before the first campaign returns a single reply, and the fix is a new domain, not a setting.
Placement collapse you cannot see
Instantly's dashboard reports sends and opens, not where mail lands. Placement drifts into Promotions and Spam for weeks while the send count still looks healthy, and the first real signal is a revenue number that misses target.
Replies trapped in the Unibox
A prospect replies 'interested, send times' and it sits in the master Unibox. No CRM record, no deal, no context for the AE. The highest-intent email of the quarter goes to a shared inbox nobody owns.
Dirty lists poison the whole domain
Instantly sends whatever CSV you upload. With no suppression, you re-email current customers and people who already opted out, and unverified addresses hit spam traps. Push bounce rate past 2% and Google reads the entire sending domain as careless, so one dirty list drags down every mailbox on it, not just the campaign.
Volume is earned, not switched on.
1. Audit & provision
We read the current state first: account fleet, warmup, blocklist and placement status. Then we provision secondary sending domains and mailboxes with SPF, DKIM, DMARC, and a dedicated tracking domain, verified before a single email leaves.
2. Warm & wire
Every mailbox enters the warmup pool on a ramp curve tuned to its provider and age, with a sending schedule that caps daily volume per inbox and lifts it only as reputation supports. Unibox reply detection, suppression, and CRM routing are wired in parallel.
3. Route & hand over
Replies get classified and pushed into your CRM with an owner on each. Placement monitoring, alerting, and the sending-schedule runbook go live, and your team gets the controls and the procedures, not a dependency on us.
What lands in your hands.
Not an Instantly login and good wishes. A running sending operation with the telemetry to keep it alive and the routing to turn replies into pipeline, owned entirely inside your accounts.
A warmed mailbox fleet
Mailboxes across rotating secondary domains, authenticated, warmed through the pool, and ramped, with documented sending capacity per inbox so you know exactly how much volume the fleet supports before placement suffers.
Placement monitoring & alerting
Inbox-versus-spam placement, bounce rate, and reputation tracked per domain with seed-inbox tests, plus alerts that fire when a domain starts slipping, before your reply rate becomes the alarm.
Unibox replies routed to the CRM
Every Unibox reply detected, classified, and landed on the right owner as a CRM record with full thread context. Interested prospects become tasks with deadlines instead of unread lines in a shared inbox.
Suppression & sending-schedule runbook
Customers, open opportunities, and unsubscribes suppressed automatically. Plus the runbook: warmup ramp rules, per-inbox sending caps, the burned-domain swap procedure, and escalation paths your team can execute without us.
Deliverability Monitor
Fleet-wide · daily
Inbox placement
0.6%
Bounce rate
100%
Unibox in CRM
Every reply in the pipeline, not the Unibox.
Scope depends on your target volume, mailbox count, and CRM. We quote after a short call, not from a rate card, and the whole operation runs in your Instantly workspace and your accounts from day one.
The questions we get asked.
What access do you need?
Admin on your Instantly workspace, or we create it in your name. DNS access for the secondary sending domains, or the exact records for your IT to place. And API access to your CRM for Unibox reply routing. We never touch your primary domain's DNS beyond reading it.
How long until we're sending at volume?
Provisioning and authentication take the first week. Warmup through the pool needs two to three weeks minimum, that is physics, not process. First real sequences go out around week three at conservative volume, with full ramp typically by week six to eight. Anyone promising full volume in week one is burning your domains.
Who pays for Instantly licenses and inboxes?
You do, in your own accounts. The Instantly subscription, domain registrations, and mailbox seats all run on your billing, so you own every asset. We size the fleet to your reply targets and advise on the plan and mailbox mix, and the run-rate scales with mailbox count and is fixed before we start.
Instantly already has warmup and a Unibox. Why pay for setup?
Those are raw inputs, not an operation. The warmup pool keeps a mailbox active, it does not enforce a ramp curve or a per-inbox sending cap, which is what actually keeps domains alive. The Unibox collects replies, it does not create CRM records or assign an owner. We build the deliverability discipline and the routing around the features, which is the part that turns sends into pipeline.
Will this put our primary domain at risk?
No, nothing sends from it. All cold volume runs on secondary domains bought for the purpose, and the runbook treats every sending domain as a disposable asset: if one burns, it is rotated out and replaced. Your primary domain only ever receives forwarded replies, so its reputation stays out of the blast radius.
What happens after handover?
Your team owns the placement dashboards, the suppression logic, the CRM routing, and the runbook, including the burned-domain swap procedure. Many clients keep a small monitoring retainer for domain rotation and deliverability reviews, but nothing breaks if you run it alone. That is the point of the runbook.
