Integrations
Cladiant + Salesforge
Run Salesforge on real mailboxes, not shared IP pools.
Salesforge is an AI-assisted sales sequencing platform in the Forge ecosystem.
Salesforge writes and sends AI-personalized sequences; Cladiant supplies the deliverable mailboxes that make them land. We provision across three real providers, authenticate every domain, and connect the accounts into Salesforge without a CSV in sight.
Where Salesforge's own Mailforge sits on shared IP pools, Cladiant gives you real Microsoft, Google, and dedicated Azure Entra accounts, so you can run Salesforge on infrastructure that is not pooled with thousands of other senders.
The handoff
How Cladiant hands off to Salesforge
Cladiant hands mailboxes to Salesforge with the account username and password, so they drop straight into your Salesforge sequences.
Division of labor
Two layers, zero overlap
Salesforge 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
Salesforge handles
- AI-written personalized sequences
- Multi-mailbox sending and rotation
- Reply management and analytics
- Forge-ecosystem tooling
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 Salesforge
We hand the accounts to Salesforge 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 Salesforge 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
Salesforge + Cladiant, answered
Do I need separate mailboxes for Salesforge?
Yes. Salesforge writes and sends AI-personalized sequences, but the deliverable mailboxes are separate infrastructure. Cladiant provisions real Google Workspace, Microsoft 365, and Azure Entra accounts and connects them into your Salesforge sequences.
How is Cladiant different from Salesforge's own Mailforge?
Mailforge sits on shared IP pools distributed across many businesses. Cladiant gives you real Microsoft, Google, and dedicated Azure Entra accounts, so your Salesforge sending reputation is not pooled with thousands of senders you cannot see.
How do I connect Cladiant mailboxes to Salesforge?
Cladiant hands mailboxes to Salesforge with the account username and password, so they drop straight into your Salesforge sequences without a CSV export or manual per-inbox setup.
How many mailboxes do I need for Salesforge?
Plan for 20 to 40 sends per mailbox per day across a few mailboxes per domain. For 1,000 sends a day that is roughly 30 to 40 mailboxes across a dozen domains, and our free volume calculator sizes it precisely.
Do Salesforge mailboxes still need warmup?
Yes. Regardless of the sequencer, new mailboxes need two to four weeks of warmup at a 2-to-1 ratio. Cladiant mailboxes arrive authenticated and ready to warm before your Salesforge campaigns ramp to full volume.
Ready to run Salesforge on real infrastructure?
One order. One invoice. Mailboxes provisioned across three providers and connected straight into Salesforge.