Pay-Per-Meeting Outbound, Run Through Smartlead
Appointment-setting agencies have the most unforgiving unit economics in outbound: you get paid when a meeting happens, not when an email lands. That makes the whole business a capacity equation — meetings booked = sends × reply rate × booking rate × show rate — and every variable in it runs through your infrastructure.
Smartlead is where the campaign side lives: client sub-accounts, sequences, mailbox rotation, and the master inbox where your setters work replies. ColdRelay is the layer underneath — the domains, mailboxes, and dedicated IPs Smartlead actually sends from. This guide covers how setting agencies wire the two together: provisioning isolated per-client mailbox pools on ColdRelay, importing them into Smartlead sub-accounts, and structuring sequences that don't just get replies but get prospects to show up.
Why Setting Agencies Run Smartlead on ColdRelay Infrastructure
When your revenue is priced per booked meeting, your infrastructure cost per meeting is the margin. If a meeting bills at $150-400 and your reply-to-meeting math says you need roughly 1,000 sends per booked meeting, then the cost and reliability of those 1,000 sends is the difference between a profitable client and a charity case. Smartlead doesn't solve that — it sends from whatever mailboxes you connect; the deliverability of the mailboxes themselves is the infrastructure layer's job.
ColdRelay handles that layer: dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, ready in about an hour, with 95%+ inbox placement. Critically for agencies, isolation works per client — each client gets their own domains and mailbox pool, so one client's scraped list or aggressive copy can never burn the pool another client's meetings depend on.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Smartlead is the sender on top. You keep Smartlead's client sub-accounts, sequencing, and master inbox — you just give each client a pool built to land.
Visit Smartlead →Connecting ColdRelay Mailboxes to Smartlead, Per Client
Provision an isolated mailbox pool per client on ColdRelay
Buy fresh secondary domains themed to each client — never their primary domain — and provision a dedicated pool for each. ColdRelay supports 100-150 mailboxes per domain, so a typical per-client pool of 30-100 mailboxes fits on one or two domains. Everything lands on isolated Azure tenants with dedicated IPs, DNS pre-configured, in about an hour — fast enough that a client signed Monday morning is sending Monday afternoon. No warmup period before sending; warmup runs continuously as part of each mailbox's daily budget.
Create a Smartlead sub-account for the client
In Smartlead, use Client Management to create a sub-account per client. This keeps campaigns, analytics, and inboxes walled off — your setters see everything in the agency master view, while each client only ever sees their own numbers. Map exactly one ColdRelay pool to one sub-account so the infrastructure isolation and the reporting isolation line up.
Bulk-import the mailboxes into the sub-account
Export the mailbox list with SMTP/IMAP credentials from the ColdRelay dashboard and bulk-import it in Smartlead under Email Accounts → Add Account. ColdRelay's CSV export matches the column layout Smartlead expects, so a 50-mailbox client pool connects in minutes, not an afternoon of copy-paste.
Set rotation limits to match the 4/day budget
Set each mailbox's daily sending limit in Smartlead to 2 outbound emails per day, mirroring ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. Attach the full pool to the client's campaigns and let Smartlead's mailbox rotation spread sends across it. Leave warmup to ColdRelay rather than double-warming inside Smartlead — stacking warmups wastes budget you're paying for in outbound capacity.
Wire meeting reporting into client dashboards
Use Smartlead's webhooks and API to push positive replies and booked meetings into whatever the client sees — a Slack channel, a CRM, or your own reporting dashboard. When you bill per meeting, the invoice line item should trace back to a webhook event, not a spreadsheet someone updates on Fridays.
The Appointment Setter's Smartlead Playbook
Price campaigns off cost per meeting, not cost per mailbox
Work the funnel backwards before quoting a client: at 2 outbound sends/day per mailbox, a 50-mailbox pool produces ~3,000 sends/month. At a 3% reply rate and a third of positive replies booking, that's roughly 10-15 meetings booked. Now your infrastructure cost divides into a per-meeting number you can put next to your per-meeting price — if the math doesn't clear, fix the pool size or the offer before launch, not after the client churns.
One client, one pool — never share infrastructure
It's tempting to run a small client on spare capacity from a big one. Don't. A bad list from client A tanking deliverability for client B is the single fastest way a setting agency loses both. Per-client domains and mailbox pools on ColdRelay, mapped one-to-one to Smartlead sub-accounts, mean any deliverability problem stays contained to the client that caused it.
Sequence for the show, not just the booking
A booked meeting that no-shows pays nothing. Qualify lightly in-thread before sending the calendar link — one question about team size or current process filters tire-kickers and primes commitment. Then add post-booking steps in Smartlead: a confirmation reply, a day-before reminder, and a morning-of nudge. Agencies that work the post-booking sequence run 70-80% show rates; those that fire a Calendly link at the first 'sure' sit closer to 50-60%.
Staff the master inbox like revenue depends on it — because it does
Smartlead's master inbox is where meetings actually get booked, across every client sub-account in one view. Reply speed is your highest-leverage metric: an interested prospect answered within the hour books at a multiple of one answered the next day. Set SLAs for your setters in the master inbox before you add more sending capacity — replies you don't work are sends you wasted.
Typical Appointment-Setting Benchmarks (Smartlead + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — the variable everything downstream multiplies against |
| Meetings booked per 1,000 sends | 3-7 | At 2-4% reply rates with a qualify-then-book flow; varies by offer and list quality |
| Show rate | 60-80% | Top of range requires in-thread qualification plus reminder steps in Smartlead |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Time from client signed to first send | Same day | ~60 minutes to provision the pool on ColdRelay, plus sequence setup in Smartlead |
What It Costs: Smartlead + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below) — which matters for agencies, since stacking client pools pushes you into better rates. DNS, dedicated IPs, and isolated Azure tenants are included.
Smartlead is billed separately on its own subscription for sequencing, sub-accounts, mailbox rotation, and the master inbox — priced per its current plans.
For a pay-per-meeting agency, the useful view is cost per meeting: total infrastructure plus software cost for a client's pool, divided by meetings booked. Both layers are fixed and predictable per client, so the per-meeting cost is knowable before you quote — and it drops as your total mailbox count across clients climbs the volume tiers.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Smartlead handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Smartlead?
No — they're complementary layers. Smartlead handles sequencing, client sub-accounts, mailbox rotation, and the master inbox where your setters work replies. ColdRelay provides the domains, mailboxes, and dedicated IPs Smartlead sends from. A setting agency uses both: ColdRelay for the infrastructure, Smartlead for the campaigns on top.
How do I keep one client's campaigns from hurting another's deliverability?
Give each client their own domains and mailbox pool on ColdRelay — each pool lives on isolated Azure tenants with dedicated IPs — and map it one-to-one to a Smartlead sub-account. If a client's list turns out to be bad, the damage is contained to their pool; every other client keeps booking meetings on untouched infrastructure.
How many mailboxes do I need per client to hit a meetings target?
Work backwards from the target. Each mailbox sends 2 outbound emails/day (4/day total including 2 warmup), so 50 mailboxes is ~3,000 sends/month. At typical setting-agency rates of 3-7 meetings per 1,000 sends, that's roughly 9-20 booked meetings monthly. Committed to more? Scale the pool — ColdRelay supports 100-150 mailboxes per domain, and new capacity provisions in about an hour.
Do new mailboxes need a warmup period before a client campaign can launch?
No separate waiting period. ColdRelay mailboxes arrive with DNS (SPF, DKIM, DMARC) pre-configured and warmup running continuously as part of the 4/day budget — 2 warmup sends alongside the 2 outbound. You can start a new client's campaign the same day their pool provisions, and you don't need to layer Smartlead's warmup on top.