If you have shopped for SMTP infrastructure, you know the price brackets. Budget resellers charge $50-200/month for shared pools. Mid-tier platforms charge $200-800. Enterprise dedicated IPs start at $5,000. So when agencies see ColdSend pricing — $79 to $199 per month — the reflexive assumption is that we must be bundling cheap SMTP and marking it up.
We are not.
Our infrastructure is Azure Communication Services (ACS). It is not SMTP. It is not a relay. It is not a shared pool we manage. It is Microsoft's transactional email API, and it works differently from every SMTP provider you have evaluated.
Why People Think We Are an SMTP Provider
The confusion is understandable. Most cold email infrastructure falls into one of three categories:
- SMTP resellers — Rent access to an IP pool and give you credentials to plug into Instantly or Smartlead.
- Mailbox providers — Sell Google Workspace, Outlook, or warmed Gmail accounts that happen to use SMTP.
- IP warming services — Charge you to gradually introduce a new IP to Gmail by sending fake emails.
ACS looks like category 1 if you squint. You get inboxes. You send emails. The price is low. But the mechanism underneath is entirely different.
What ACS Actually Is
Azure Communication Services is a set of REST APIs for transactional messaging — email, SMS, and chat. Microsoft built it for applications that send password resets, shipping notifications, and appointment reminders. The infrastructure underneath is the same IP pool that Outlook.com uses for its own traffic.
When you send through ACS:
- You do not get an SMTP server address natively. You get an API endpoint.
- You do not get a static IP. Microsoft allocates dynamically from a large, pre-warmed pool.
- You do not manage IP reputation. Microsoft monitors the pool and retires underperforming IPs automatically.
That said, if you want to use ColdSend-provisioned inboxes inside Smartlead, Instantly, or any other external sequencer, we do generate SMTP/IMAP credentials for export. The inboxes are still ACS underneath — the SMTP wrapper is just a protocol adapter. We have step-by-step export guides in our help center. The nature of the infrastructure does not change because the protocol does.
ACS is not "SMTP with a fancy wrapper." It is a different protocol layer entirely. SMTP is a 1980s push protocol that hands your email to a server and hopes for the best. ACS is an API call that returns a message ID, tracks delivery programmatically, and integrates with Azure's compliance and monitoring stack.
The pre-warmed IP part is real, but it is a side effect of Microsoft's scale, not something we or any vendor manufactured.
SMTP vs. REST API: The Technical Difference
This is why we built a sequencer on top of ACS instead of treating it as a dumb pipe. ACS is send-only by design. We added reply handling, campaign scheduling, and bounce guardrails because ACS does not provide them out of the box.
If we were an SMTP provider, we would just hand you credentials and let you plug them into Smartlead. We do the opposite: we absorb the infrastructure layer so you do not need a separate sequencer at all.
We Are Infra-Agnostic
ACS is what we offer natively, but it is not a walled garden.
You can connect any SMTP inbox to ColdSend — Google Workspace, Outlook, custom Postfix, AWS SES, SendGrid, whatever you already pay for. We import them via SMTP/IMAP or OAuth, just like Instantly or Smartlead would. The difference is that those platforms only import. They do not also provision.
ColdSend does both:
- ACS track: Create inboxes natively on Microsoft's pool. No warmup. No per-inbox cost. ~100K emails per slot. Use them inside ColdSend's sequencer, or export via SMTP/IMAP to any external tool.
- Import track: Bring your own Gmail, Outlook, or SMTP inboxes. Use our warmup tool if they are fresh. Use our sequencer regardless.
Agencies often start on ACS to skip warmup, then migrate warmed domains to cheaper SMTP infrastructure once reputation is established. That rotation strategy is the entire point. We are not locking you into Azure. We are giving you a faster on-ramp.
The Warmup Misconception
Because ACS does not require IP warmup, some users assume it is "bulletproof SMTP" — a pool that ignores spam complaints. It is not.
ACS enforces bounce rate limits. Cross 4% hard bounces and Microsoft restricts your resource. Cross it repeatedly and they suspend it. The pool is managed aggressively because it is also used for Microsoft's own transactional traffic. One bad sender can affect Outlook's password reset deliverability, so Microsoft does not tolerate abuse.
We added campaign auto-pause at 4% bounce rate specifically to keep users inside ACS guardrails. This is not a feature we invented to be cautious. It is a survival mechanism. If you treat ACS like bulletproof SMTP, you will lose the account.
For a deeper walkthrough of how warmup works and why it matters — even when you are skipping IP warmup — watch this:
Bottom Line
ColdSend is not an SMTP provider. We are a sequencer wrapped around Azure Communication Services — an API-driven transactional email platform — with the option to import your own SMTP infrastructure if you prefer.
If you came here looking for a platform that provisions enterprise-grade inboxes, handles sequencing, and lets you migrate to your own infrastructure later, you are in the right one. And if you want to export those inboxes via SMTP to another sequencer, we support that too — the infrastructure underneath is still ACS.
The $79 price is not a trick. It is what happens when you automate provisioning instead of charging $2,000 for manual setup.
Related:
