Two Motions, Two Branch Trees
Most recruiting outreach fails at the follow-up, not the opener. A hiring manager who opened your email twice and clicked the comp data deserves a different second touch than one who never opened at all — and a candidate who clicked the role profile link is a fundamentally different conversation than one who ignored it. Flat sequences send both prospects the same 'just bumping this' email, which is why recruiter follow-ups have a reputation for being noise.
Woodpecker's condition-based follow-up paths fix exactly this: if-opened and if-clicked conditions split each sequence into branches, so the prospect's own behavior chooses the next email. ColdRelay is the layer underneath — the secondary domains, mailboxes, and dedicated IPs Woodpecker sends from. This guide covers how recruiters build two separate branch trees: a client BD tree that branches on engagement with hiring signals, and a candidate tree that branches on profile-link clicks, each with its own persistence rules.
Why Run Woodpecker on ColdRelay Infrastructure
Woodpecker's strength for a recruiting desk is behavioral routing. Condition-based paths mean the BD prospect who clicked your hiring-signal link gets a meeting ask while the non-opener gets a re-framed subject line; timezone-aware delivery means the candidate email lands when the candidate is actually awake; per-campaign deliverability monitoring tells you which of your two trees is drifting before replies dry up. What Woodpecker doesn't do is provision the mailboxes those trees send from — it connects to whatever accounts you give it, and the deliverability of those accounts is the infrastructure layer's job.
ColdRelay is that layer. You provision dedicated mailboxes on isolated Azure tenants with dedicated IPs, DNS (SPF, DKIM, DMARC) pre-configured, live in about an hour. There's no warmup waiting period — warmup runs continuously as part of each mailbox's send budget of 4 emails/day, split 2 outbound + 2 warmup — so both branch trees can launch the same day.
The two products are complementary layers, not rivals: ColdRelay supplies the domains, mailboxes, and IPs; Woodpecker runs the branching logic on top. And branching logic is only worth tuning if the emails it routes actually reach the inbox.
Visit Woodpecker →Building Both Branch Trees in Woodpecker
Provision the mailbox pool on ColdRelay
Branch-driven outreach is targeted, not blasted — most desks running both motions start at 20-50 mailboxes on one or two secondary domains adjacent to the agency brand, well under the 100-150 mailboxes a single domain supports. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Connect the mailboxes and set human-like intervals
Add each ColdRelay mailbox in Woodpecker via SMTP/IMAP and cap it at 2 outbound emails/day — mirroring ColdRelay's per-mailbox budget of 4 sends/day total, split 2 outbound + 2 warmup. Leave Woodpecker's human-like sending intervals on so the few sends each mailbox makes are naturally spaced, and skip any additional warmup tooling: ColdRelay's warmup already runs continuously inside the budget.
Build the client BD tree with if-opened and if-clicked paths
Create the BD campaign with a hiring-signal opener — a link to something concrete about the prospect's open roles. Then add condition-based follow-up paths: if-clicked routes to a direct meeting ask ('worth 15 minutes on that search?'), if-opened-but-not-clicked routes to a shorter resend of the evidence, and the no-open branch gets a new subject line and angle rather than a bump. The hiring manager's engagement chooses the email — you never send 'just following up' to someone who already showed intent.
Build the candidate tree branching on profile-link clicks
The candidate campaign hinges on one behavior: did they click the role profile link? Set an if-clicked condition path that routes clickers to a scheduling ask within a day — a clicked profile is a candidate deciding whether to raise their hand — while non-clickers get one re-framed touch on the role's strongest hook, then stop. Enable Woodpecker's timezone-aware delivery so each candidate's email arrives in their local morning, not 3 a.m. wherever they live.
A/B test the branches and watch per-campaign deliverability
Use Woodpecker's A/B testing inside each branch — two versions of the if-clicked meeting ask, two versions of the no-open re-frame — so you learn which follow-up converts each behavior, not just which opener gets opened. Check Woodpecker's per-campaign deliverability monitoring weekly: because the BD and candidate trees are separate campaigns, a dip shows you exactly which motion is drifting while the other reads clean.
The Branch-Tree Recruiting Playbook for Woodpecker
Let the click choose the next email
A candidate who clicked the profile link has already told you they're curious — the next touch should be a time, not more persuasion. A hiring manager who clicked your signal evidence is mid-evaluation — ask for the meeting. Woodpecker's if-clicked paths exist so intent gets answered with a close, and silence gets answered with a new angle.
Give each motion its own persistence rules
Hiring managers tolerate persistence — a search that's costing them money justifies five or six touches over three weeks. Passive candidates don't — two ignored touches means not now, and a third reads as spam from a recruiter they'll remember badly. Because each tree is its own Woodpecker campaign, you set the follow-up count and stop conditions per motion instead of compromising on one cadence for both.
Deliver on the prospect's clock, not yours
Candidates read personal email in their local morning and evening; hiring managers read work email in business hours. Woodpecker's timezone-aware delivery per prospect means a desk recruiting nationally — or placing remote roles across regions — isn't silently sending half its sequence at hours nobody reads, which quietly suppresses the very opens and clicks the branches key on.
Treat branch stats as a diagnosis, not a scoreboard
When the candidate tree's click rate holds but clicked-branch replies fall, your follow-up ask is the problem. When clicks themselves fall across both trees, check Woodpecker's per-campaign deliverability monitoring first — engagement decay is often placement decay in disguise, and on dedicated ColdRelay infrastructure you can isolate whether it's the copy or the campaign drifting.
Typical Branch-Tree Recruiting Benchmarks (Woodpecker + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared provider pools |
| Candidate profile-link click rate | 12-20% | A specific role link beats a generic 'open to opportunities?' ask |
| Reply rate on the clicked-profile branch | 8-14% | Routing clickers to a same-day scheduling ask converts intent while it's warm |
| BD reply rate, engagement-branched follow-ups | 4-6% | Condition paths out-pull flat 'bumping this' sequences on the same list |
| Time to first campaign | Same day | ~60 minutes to provision, plus building both branch trees in Woodpecker |
What It Costs: Woodpecker + ColdRelay
Billed per mailbox per month, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — a two-tree desk's 20-50 mailbox starting pool keeps the infrastructure bill modest.
Woodpecker is a separate subscription covering condition-based follow-up paths, timezone-aware delivery, A/B testing, deliverability monitoring, and the agency panel — priced per its current plans.
Infrastructure scales with mailbox count; Woodpecker scales with prospects and features. Adding reach to either motion means adding mailboxes to the shared ColdRelay pool — the branch logic itself costs nothing more to run.
| 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; Woodpecker handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Is ColdRelay an alternative to Woodpecker?
No — they're complementary layers of one stack. Woodpecker is the sending and sequencing software: condition-based follow-up paths, timezone-aware delivery, A/B testing, per-campaign deliverability monitoring. ColdRelay is the infrastructure underneath: the secondary domains, mailboxes, and dedicated IPs Woodpecker sends from. Recruiters use both together.
Do condition-based branches multiply my send volume?
No. Each prospect travels exactly one path through the tree, so a three-branch follow-up consumes the same sends as a flat sequence — the branching changes which email goes out, not how many. Capacity math stays simple: at 2 outbound sends/day per mailbox (4/day total including 2 warmup sends), 25 mailboxes is 50 outbound emails a day shared across both trees.
How many follow-ups should each tree allow?
Different rules per motion — which is the point of running them as separate Woodpecker campaigns. Client BD can carry five or six touches over about three weeks; an open search is an active pain and persistence reads as professionalism. Candidate trees should stop sooner: route clickers to a scheduling ask, give non-clickers one re-framed touch, then end the sequence. A candidate who ignored two emails remembers the recruiter who sent a sixth.
Can a recruiting agency run client-branded campaigns this way?
Yes. Woodpecker's agency panel keeps each client's campaigns, prospects, and stats separated under one login, and ColdRelay supplies the sending layer per engagement — provision a mailbox group (or a separate secondary domain, with 100-150 mailboxes supported per domain) for each client so one account's deliverability never touches another's. Each client engagement provisions in about an hour.