Integrations
Cladiant + Instantly
One order of authenticated mailboxes, dropped straight into your Instantly workspace.
Instantly is a cold email outreach and deliverability platform popular with agencies and founders.
Instantly runs your sequences and unibox; Cladiant supplies the mailboxes that feed it. We provision across Google Workspace, Microsoft 365, and Azure Entra in one order, authenticate every domain, and connect the accounts directly into your Instantly workspace.
No grey-market SMTP relays and no shared Azure pools: each Azure domain gets its own dedicated tenant, so a reputation problem on one inbox never spreads across your Instantly campaigns.
The handoff
How Cladiant hands off to Instantly
Cladiant hands mailboxes to Instantly using the account username, password, API key, and workspace, so they appear in the right Instantly workspace ready to sequence.
Division of labor
Two layers, zero overlap
Instantly runs the campaign. Cladiant runs the infrastructure it sends from. Neither does the other's job, which is exactly why they fit together.
Cladiant handles
- Google Workspace, Microsoft 365, and Azure Entra mailboxes
- Domain purchase plus SPF, DKIM, and DMARC on every domain
- A dedicated Azure Entra tenant per domain
- Deliverability monitoring that pulls a bad inbox to warmup
- Month-to-month billing on one invoice
Instantly handles
- Sequences and the unified inbox
- Built-in warmup
- Lead Finder database and reply detection
- Campaign analytics and workflow automation
Setup
From order to sending
- 01
Tell us your volume
Say how many emails a day you need to send. We size the mailboxes and domains so no single inbox or domain is overloaded.
- 02
We provision and authenticate
Real Google Workspace, Microsoft 365, and Azure Entra mailboxes, with SPF, DKIM, and DMARC written and verified on every domain before anything sends.
- 03
Connect to Instantly
We hand the accounts to Instantly using the credentials it expects, including a Microsoft OAuth link for Azure inboxes, so they land in your workspace ready to send.
- 04
Set safe limits and launch
Cap daily volume per mailbox, keep warmup running, and keep bounces low. Your campaigns run; we keep the infrastructure healthy underneath.
Sizing it
How many mailboxes you need
A safe cold-email cadence is 20 to 40 sends per mailbox per day across a few mailboxes per domain, with new mailboxes warmed up over two to four weeks and bounce rate kept low. A target of 1,000 sends a day works out to roughly 30 to 40 mailboxes across a dozen or so domains, and Instantly rotates across them for you.
What you get
Infrastructure built for the inbox
01
Three real providers
Google Workspace, Microsoft 365, and Azure Entra in one order, not a single-source SMTP relay.
02
Authenticated before sending
SPF, DKIM, and DMARC written and verified on every domain before a mailbox goes live.
03
Dedicated Azure tenants
Every Azure domain in its own tenant, so your reputation is never pooled with other senders.
Troubleshooting
When something goes wrong, who fixes it
Most cold-email problems are either a sequencer problem or an infrastructure problem. Here is how to tell them apart, and which layer owns the fix.
| Symptom | Likely cause | How it gets fixed |
|---|---|---|
| Emails landing in spam on seed tests | A DNS or authentication gap, or a blacklisted domain | Cladiant re-checks SPF, DKIM, DMARC and reputation, then remediates or replaces the domain |
| Reply rate declining over several weeks | Domain or inbox reputation wearing down | Cladiant rotates sending to rested mailboxes and warms the affected ones back up |
| Bounce rate climbing above 2 to 3 percent | List quality, not infrastructure | Pause and re-verify the list before sending more; suppress hard bounces in the sequencer |
| Good deliverability but low replies | Copy or targeting, not infrastructure | A/B test messaging in your sequencer; if a plain-text version also lands in spam, it points back to infrastructure |
| A sudden drop across many inboxes at once | A shared-reputation or tenant-level problem | Isolated Azure tenants contain the blast radius, so Cladiant investigates only the affected tenant |
FAQ
Instantly + Cladiant, answered
Does Instantly provide the mailboxes?
No. Instantly runs your sequences, unibox, and warmup, but you supply the sending mailboxes. Cladiant provisions real Google Workspace, Microsoft 365, and Azure Entra accounts and connects them straight into your Instantly workspace, so the sequencer and the infrastructure come from one order.
Can I add Google Workspace and Outlook mailboxes to Instantly?
Yes. Instantly supports Google and Microsoft accounts plus SMTP. Cladiant connects mailboxes using the account username, password, API key, and workspace, with a Microsoft OAuth link for Azure Entra inboxes, so every provider appears in the right Instantly workspace ready to sequence.
How do I add Cladiant mailboxes to an Instantly workspace?
Order the mailboxes and Cladiant provisions, authenticates, and connects them to your Instantly workspace automatically. You skip the manual per-inbox setup, and you can drop the new inboxes into existing campaigns while keeping your sequences, leads, and analytics.
How many inboxes do I need for Instantly?
A safe cadence is 20 to 40 sends per mailbox per day across a few mailboxes per domain. For 1,000 sends a day plan on roughly 30 to 40 mailboxes across a dozen domains. Use our free volume calculator to size it for your campaign.
Do I need warmup if Instantly has it built in?
Instantly includes warmup, and new mailboxes still need two to four weeks of ramp before full-volume cold sending. Cladiant mailboxes arrive authenticated and ready to warm, so you can turn Instantly warmup on immediately and keep a 2-to-1 warmup ratio.
Why not just use grey-market SMTP inboxes with Instantly?
Shared SMTP pools mean your sender reputation is tied to strangers you cannot see. Cladiant gives each Azure domain its own dedicated tenant on real Google and Microsoft accounts, so a reputation problem on one inbox never spreads across your Instantly campaigns.
Ready to run Instantly on real infrastructure?
One order. One invoice. Mailboxes provisioned across three providers and connected straight into Instantly.