Solar Outbound Where the Email Opens the Door and the Phone Books the Visit
Here's the uncomfortable truth about commercial solar prospecting: site assessments almost never get scheduled over email. A facility manager will read a well-built savings email, maybe even forward it — but the actual walk-through gets booked in a two-minute phone call, because that's how facilities people coordinate anything that involves someone showing up at their building. Teams that treat cold email as the closer keep wondering why interested prospects go quiet; teams that treat it as the door-opener for a call book assessments.
That division of labor is exactly what Reply.io's multichannel sequences are built for: email, call tasks, and LinkedIn steps live in one flow, so the savings email and the follow-up call are steps two and three of the same sequence instead of two disconnected tools. ColdRelay is the infrastructure underneath — the secondary domains, mailboxes, and dedicated IPs that Reply.io's email steps actually send from. This guide covers how solar teams wire the two together into a call-first assessment machine, with the email doing the warming and the dial doing the booking.
Why Run Reply.io on ColdRelay Infrastructure
Reply.io's core strength for a solar team is that the whole touch pattern lives in one sequence: an email step that lands the facility-specific savings hook, a call task that surfaces in the rep's queue at the right moment, a LinkedIn step aimed at the CFO who actually signs off on the capital spend, and Jason AI plus the unified inbox keeping replies from slipping through. What Reply.io doesn't do is mint the sending infrastructure — its email steps send from whatever mailboxes you connect, and the reputation of those mailboxes is the infrastructure layer's job.
That's where ColdRelay fits. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs — SPF, DKIM, and DMARC pre-configured, ready in about an hour, with no warmup waiting period before sending. Warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup), so the pool you stand up in the morning is feeding call tasks by the afternoon.
The two layers are complementary, not competing: ColdRelay is the infrastructure, Reply.io is the sequencing and multichannel engine on top. The pairing matters more in a call-first motion than in a pure email play, because the economics are chained. A rep only dials prospects the email warmed up — so every savings email that lands in spam is a call that never gets made and an assessment that never gets booked. At 95%+ inbox placement, the top of the funnel actually feeds the phone.
Visit Reply.io →Building the Email-to-Call Pipeline in Reply.io
Provision a call-paced pool on ColdRelay
Size the mailbox pool to your dialing capacity, not to a sends-per-day fantasy — in a call-first motion, every email is supposed to generate phone work, and a rep can only make so many quality dials a day. A team with two reps working the phones is well served by 25-40 mailboxes at 2 outbound sends/day each (4/day total with warmup), on one secondary domain kept separate from the domain you use for proposals and interconnection paperwork. ColdRelay supports 100-150 mailboxes per domain, and everything provisions on isolated Azure tenants with dedicated IPs in about an hour, SPF, DKIM, and DMARC pre-configured.
Connect the mailboxes under Email Accounts in Reply.io
In Reply.io, add each ColdRelay mailbox under Settings → Email Accounts via SMTP/IMAP using the credentials exported from the ColdRelay dashboard. Each mailbox connects as its own sending account, so Reply.io can distribute the email steps of your sequences across the whole pool, and every reply routes back into the unified inbox regardless of which mailbox sent it.
Set per-mailbox sending limits to match the budget
Use Reply.io's per-mailbox sending limits to cap each account at 2 outbound emails per day, mirroring ColdRelay's per-mailbox budget of 4 sends/day total — 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's side as part of that budget, so don't layer additional warmup tooling on these accounts; Reply.io's limit governs outbound only.
Build the multichannel sequence: email, call task, LinkedIn
Create a Reply.io sequence that opens with a facility-specific savings email, then drops a call task into the rep's queue two business days later — the script isn't a pitch, it's "I sent over the rough numbers for your building; takes about 45 minutes on-site to firm them up, does Tuesday or Thursday work?" Add a LinkedIn step targeting the CFO or owner in parallel, because the facility manager hosts the walk-through but the economic buyer approves the project. Load contacts into Reply.io's contact management with the facility manager and CFO tagged as separate roles on the same account.
Turn on Jason AI for reply triage and launch
Enable Jason AI to categorize incoming replies in the unified inbox — interested, not now, referral to someone else, objection — so the reps' time stays on the phone instead of in the inbox. A "call me next week" reply should become a scheduled call task, not an automated follow-up email landing on top of a human conversation. Launch the sequence, and let the call queue fill from the accounts the email steps have warmed.
The Call-First Assessment Playbook for Reply.io
Write the email to be referenced on the phone, not to close on its own
In this motion the savings email has one job: give the call a reason to exist. Keep it to the rough numbers for their building — estimated annual offset, the payback range at their utility's commercial rate — and end with "I'll give you a quick call this week to see if a walk-through makes sense," not a calendar link. That line changes the call from a cold interruption into an expected follow-up, and the email's content becomes the call's opening sentence: "I'm the one who sent the savings estimate for your facility on Tuesday." Recognition is the whole game; a facility manager who connects the voice to the email gives you ninety seconds instead of nine.
Schedule call tasks around facility managers' operational hours
Facility managers live on an operational clock: early-morning building walks, midday vendor and contractor traffic, end-of-day handoffs. The reachable windows are roughly 7:30-9:00am, before the building wakes up, and 2:00-4:00pm, after the lunch-hour crush — and a call that lands mid-morning gets voicemail or a distracted brush-off. Configure your Reply.io sequence so call tasks queue into those windows, and set the email steps to deliver the afternoon before a morning call block, so the savings email is near the top of the inbox when your call references it. The dial-to-conversation rate difference between timed and untimed call blocks is the biggest free win in this playbook.
Run a parallel LinkedIn lane to the CFO — the economic buyer who never hosts the visit
The facility manager schedules the walk-through; the CFO approves the capital expenditure. Treat them as two lanes in one Reply.io sequence: email and call tasks carry the facility manager toward the assessment, while LinkedIn steps — a profile view, then a connection request with a one-line note about the project economics — put you on the CFO's radar before the deal ever reaches their desk. When the facility manager walks the proposal upstairs, the CFO has already seen your name and a payback number instead of opening a cold internal forward. Use Reply.io's contact management to keep both roles tagged on the same account so neither lane fires blind.
Treat the call disposition as the sequence's routing signal
Every dial ends in one of a few outcomes — booked, callback requested, gatekeeper, voicemail, wrong contact — and each should route the account differently in Reply.io rather than letting the sequence march on blindly. Booked assessments exit the sequence immediately so no automated email lands after a human commitment. Callbacks become rescheduled call tasks at the requested time. Voicemails trigger a short same-day email — "just left you a voicemail about the solar estimate for your building" — which doubles the odds the next dial connects. Wrong contacts update the account in contact management and re-aim the next steps. The discipline sounds clerical; it's the difference between a sequence that compounds and one that annoys.
Typical Call-First Solar Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools — and every email that lands is a warmer dial |
| Dial-to-conversation rate after a delivered savings email | 15-25% | Calls placed in the 7:30-9:00am or 2:00-4:00pm facility windows, referencing the email; untimed cold dials with no email run 5-8% |
| Assessments booked per 100 accounts worked | 6-10 | Multichannel sequences (email + call task + LinkedIn) at the high end; email-only follow-up at the low end |
| CFO LinkedIn connection acceptance | 25-40% | Connection requests sent after the facility-manager email lane is active and carrying a one-line economics note |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
What It Costs: Reply.io + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included. Call-first motions run pools sized to dialing capacity rather than blast volume, so the infrastructure line stays lean.
Reply.io is billed separately on its own subscription for multichannel sequences, call tasks, LinkedIn steps, Jason AI, the unified inbox, and contact management — priced per its current plans, typically per user.
Infrastructure cost scales with mailbox count; Reply.io's cost scales with the number of reps working the sequences. They stack cleanly — one bill for sending capacity, one for the multichannel engine. Because the phone does the booking, this motion converts a modest combined spend into assessments at a rate pure-volume email plays rarely match.
| 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; Reply.io handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Does ColdRelay replace Reply.io?
No — they're complementary layers doing different jobs. Reply.io handles the multichannel sequences — email steps, call tasks, LinkedIn steps — plus Jason AI reply triage, the unified inbox, and contact management. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Reply.io's email steps send from. You connect ColdRelay mailboxes under Email Accounts in Reply.io and run both together.
If assessments get booked by phone anyway, why invest in email infrastructure at all?
Because the call only works when the email landed first. A cold dial to a facility manager is an interruption; a dial that follows a delivered savings email is a follow-up to something they've seen — and the dial-to-conversation rate difference is roughly three to one. That makes deliverability the throttle on your entire phone motion: every savings email that hits spam is a dial that reverts to fully cold. ColdRelay mailboxes on isolated Azure tenants with dedicated IPs run at 95%+ inbox placement, which is what keeps the call queue warm.
How many mailboxes does a call-first solar team need?
Match the pool to your dialing capacity, not a volume target. At 2 outbound sends/day per mailbox (4/day total with 2 warmup sends), 30 mailboxes produces 60 emails/day — which generates roughly the call-task volume two reps can work properly inside the morning and afternoon facility windows. ColdRelay supports 100-150 mailboxes per domain, and new mailboxes provision in about an hour with no warmup waiting period, so adding a third rep's worth of capacity is a same-day decision.
Should Jason AI handle replies automatically, or should a rep?
Use Jason AI for triage, humans for anything warm. Let it categorize unified-inbox replies — interested, not now, referrals, objections — and clear the obvious unsubscribes, so reps spend their windows dialing instead of sorting. But a facility manager who replies "call me Thursday afternoon" has just told you exactly how to book the assessment; that becomes a scheduled call task for a rep, never an automated email. In a motion built around the phone, the moment a human engages, a human takes over.