The GC Courtship, Run as One Sequence
Ask any rainmaker how they landed their first general counsel relationship and you'll hear the same arc: the GC had seen their name somewhere first, the written introduction was measured and specific, and the phone call came only after the GC had signaled some interest — never before. That arc is etiquette, not accident. In-house counsel are professionally allergic to pursuit; they respond to lawyers who show up the way other lawyers do — visible, restrained, and willing to wait for an opening.
Reply.io is one of the few platforms that can run that entire arc as a single sequence: its multichannel flows combine email steps, LinkedIn steps, and call tasks in one timeline, with conditions that decide when each fires. The call task doesn't go on anyone's calendar until the prospect has engaged — which is exactly the rule a senior partner would set anyway. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs that Reply.io's email steps send from, kept entirely separate from the domain that carries the firm's privileged correspondence. This guide covers how to wire the two together so the sequence behaves the way lawyers actually network — and how to write one bar-compliant copy standard that every channel in the flow respects.
Why Run Reply.io on ColdRelay Infrastructure
Reply.io is a sequencing and engagement platform — it orchestrates the email, LinkedIn, and call steps, manages contacts, and consolidates every response into a unified inbox, with Jason AI assisting on reply handling. But its email steps send from whatever mailboxes you connect; provisioning the domains, the mailboxes, and the sending reputation behind them is the infrastructure layer's job.
That's where ColdRelay fits. You order dedicated mailboxes on isolated Azure tenants with dedicated IPs, fully DNS-configured (SPF, DKIM, DMARC) and ready in about an hour — never on the primary domain your clients and the courts use to reach you. Connect them in Reply.io and the firm can be sending the same day, because warmup runs continuously as part of each mailbox's send budget rather than as a multi-week waiting period.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Reply.io is the sequencing and engagement layer on top. And for an engagement-gated sequence, deliverability isn't just hygiene — it's the trigger mechanism. The call task only fires when the prospect engages, and the prospect can only engage with an email that reached the inbox. With 95%+ inbox placement underneath, the sequence's conditions are reading real prospect behavior, not the silence of a spam folder.
Visit Reply.io →Connecting ColdRelay Mailboxes to Reply.io
Provision mailboxes on ColdRelay
Pick secondary domains adjacent to the firm's name — never the primary domain that carries client correspondence and court filings. ColdRelay supports 100-150 mailboxes per domain, but an engagement-gated program starts small by design: 10-20 mailboxes is typical, because every sequence is anchored to a named attorney who must be available for the calls it generates. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Connect the mailboxes as Reply.io email accounts
In Reply.io, go to Settings → Email Accounts and connect each ColdRelay mailbox via SMTP/IMAP using the credentials from the ColdRelay dashboard. Name each sending identity after the real attorney who owns that sequence — the from-name must match the LinkedIn profile the prospect will check and the voice on the eventual call, or the arc breaks at its first seam.
Set per-mailbox sending limits to the ColdRelay 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 — 4 sends/day total, split 2 outbound + 2 warmup. ColdRelay's network runs the warmup half continuously, so Reply.io only ever schedules the outbound 2. Skip any additional warmup layer; the budget already includes it.
Build the multichannel sequence — presence, then email, then an earned call
In Reply.io's sequence builder, order the steps the way a GC relationship actually forms: a LinkedIn step early (profile view and connection request from the attorney's real account), two or three conservative email steps spaced about a week apart, and a call task that is conditioned on engagement — a reply, a repeated open, or an accepted connection. Reply.io executes the LinkedIn touches and emails on schedule, but the call task only lands on the attorney's task list once the prospect has given a reason for the phone to ring.
Stand up the unified inbox and Jason AI triage
Route every response into Reply.io's unified inbox and let Jason AI categorize them — interested, referral, not-now, opt-out — so nothing waits on a manual sweep. Interested replies create a same-day call task for the owning attorney; not-now replies get a respectful long-interval follow-up; opt-outs are honored immediately and logged. Jason AI drafts responses if you want the head start, but in a law firm every outbound word still goes through attorney review before it sends.
The Law Firm Reply.io Playbook
Gate the call on engagement — a GC's phone is invitation-only
A cold call to a general counsel is an interruption from a stranger; the same call placed two days after that GC replied to an email, or accepted the attorney's connection request, is a follow-up between professionals. The difference is the entire phone channel for legal BD. Use Reply.io's conditional steps so the call task simply cannot fire on an unengaged prospect — no engagement, no dial, the sequence just continues its patient email cadence. Partners are far more willing to make BD calls when every number on the task list comes pre-warmed by a signal.
Treat LinkedIn as the credential check it actually is
Before a GC replies to an unknown lawyer, they look the sender up — usually on LinkedIn, usually within a day of the first email. The LinkedIn step in your Reply.io sequence isn't really outreach; it's making sure that when the inevitable lookup happens, the profile passes inspection: current role, real practice-area substance, recognizable matters, a photo that matches a lawyer they'd retain. A profile view and a plain connection request from the attorney's account are enough activity — the profile's job is to survive scrutiny, not to perform. An out-of-date or threadbare profile silently kills sequences whose emails were perfectly good.
Keep Jason AI inside the attorney-review fence
Reply.io's Jason AI is genuinely useful to a small BD operation — it categorizes inbound replies, flags the interested ones, and drafts responses in seconds. Use all of that for triage. But outreach from a law firm is professional speech, and bar advertising rules attach to the lawyer regardless of who — or what — drafted the words. The working rule: Jason AI reads everything, drafts anything, sends nothing. Every AI-drafted reply gets attorney review before it leaves the building, and the approved versions become templates so review gets faster every month rather than being re-litigated per message.
Write one compliance standard and make all three channels inherit it
A multichannel sequence multiplies compliance surface: in many jurisdictions, attorney advertising and solicitation rules reach written communications broadly — which can cover the LinkedIn connection note as much as the email — and a phone call to a prospective client has its own etiquette and, in some places, its own rules. Don't write three policies. Write one conservative copy standard — factual statements of experience and credentials, specific and verifiable observations about the prospect, no outcome promises, no urgency, required labeling where your jurisdiction demands it — and apply it to the email templates, the connection note, and the call talk track alike. Store the talk track with the templates so the whole sequence, spoken steps included, is one reviewable artifact. Nothing on this page is legal advice about your own compliance obligations.
Typical Engagement-Gated Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — the call trigger can only read engagement on emails that actually landed |
| Email reply rate within the multichannel flow | 3-6% | A visible attorney profile behind a conservative email outperforms the 2-5% email-only norm for legal BD |
| Call connect rate on engagement-gated dials | 25-40% | Calls placed within two business days of a reply or accepted connection; cold dials to GCs sit in low single digits |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Engagement-to-call window | 1-2 business days | Jason AI triage plus same-day call tasks keep the follow-up inside the window while the firm's name is still fresh |
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 — and because an engagement-gated program is throttled by attorney call capacity rather than send volume, the 10-20 mailbox footprint most firms need keeps this a small line item.
Reply.io is billed separately on its own subscription for the multichannel sequences, call tasks, Jason AI, unified inbox, and contact management — priced per its current plans, typically per seat.
Infrastructure cost scales with mailbox count; Reply.io's cost scales with seats. The two stack cleanly — one bill for sending capacity, one for the sequencing and engagement software — and the combination costs less per year than a single associate-hour spent weekly on manual follow-up tracking.
| 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, LinkedIn steps, engagement-conditioned call tasks — plus Jason AI reply handling and the unified inbox. ColdRelay provides the underlying domains, mailboxes, and dedicated IPs that Reply.io's email steps send from. ColdRelay is the infrastructure layer; Reply.io is the sequencing and engagement layer on top — an engagement-gated program uses both together.
Why not just have attorneys cold-call general counsel and skip the email steps?
Because the call's effectiveness comes from what precedes it. A cold dial to an in-house legal team connects in the low single digits and can read as exactly the pursuit GCs are trained to deflect; the same call placed after a reply or an accepted connection request connects several times more often and arrives as a follow-up, not an ambush. The email and LinkedIn steps exist to earn the call — and Reply.io's conditional call tasks enforce that order automatically, so no attorney ever dials a number the sequence hasn't warmed.
Is it appropriate for a law firm to let Jason AI handle replies?
For triage, yes — categorizing responses, flagging interested prospects, and creating call tasks is operational work that AI does well and fast. For outbound words, keep a hard fence: bar advertising rules treat outreach as the attorney's professional speech regardless of who drafted it, so AI-drafted replies should always pass attorney review before sending. Used that way, Jason AI shortens response times without ever putting unreviewed language in front of a prospective client.
Does the 2-outbound-per-day mailbox budget limit a multichannel sequence?
Less than you'd think, because only the email steps draw on it. Each ColdRelay mailbox sends 4 emails/day total — 2 outbound + 2 warmup — while LinkedIn steps run from the attorney's own profile and call tasks run on the phone, consuming no email budget at all. A 15-mailbox pool moves 30 outbound emails a day, which for an engagement-gated program is usually more than the attorneys' call capacity can absorb anyway. If email throughput ever becomes the constraint, add mailboxes — ColdRelay supports 100-150 per domain — rather than pushing any single mailbox harder.