Follow-Up That Branches on Behavior, Run Through Woodpecker
Most agency follow-up sequences make one decision for everyone: wait three days, send the bump. But the prospect who opened your email twice and said nothing is in a completely different conversation than the one who clicked through to your pricing page — and both are worlds away from the one who never opened at all. Sending all three the same 'just floating this to the top of your inbox' wastes the only data a cold campaign generates for free: what each prospect actually did.
Woodpecker is built around that data. Its condition-based follow-up paths — if-opened and if-clicked branching inside the campaign — let one campaign split into several self-adjusting pursuit tracks, each matched to a behavior. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs those branched campaigns actually send from. This guide covers how an agency wires the two together so that follow-up stops being a schedule and starts being a response.
Why Engagement-Branched Campaigns Need Their Own Infrastructure Layer
Branching logic is only as good as the signals feeding it — and the signals are only as good as the deliverability underneath. An if-opened condition can't fire on an email that went to spam, and a click can't happen on a message nobody received. When campaigns land inconsistently, Woodpecker's branches don't just underperform; they misread the audience, routing genuinely interested prospects down the 'cold' track because the email never reached them. Woodpecker monitors deliverability per campaign and paces sends at human-like intervals, but it sends from whatever mailboxes you connect — domains, DNS, and IP reputation are the infrastructure layer's job.
That's where ColdRelay fits. You provision secondary domains and mailboxes on isolated Azure tenants with dedicated IPs — SPF, DKIM, and DMARC pre-configured, ready in about an hour, sustaining 95%+ inbox placement. There's no warmup waiting period before the first branched campaign goes live: warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup). And because the branching motion runs entirely on secondary domains, your agency's primary domain — the one carrying proposals and client threads — never touches the experiment.
The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Woodpecker is the sequencing and branching layer on top. Woodpecker decides which message each prospect gets next; ColdRelay makes sure every message lands well enough for that decision to be based on real behavior.
Visit Woodpecker →Wiring ColdRelay Mailboxes Into Woodpecker's Branching Campaigns
Provision the sending pool on ColdRelay
Order secondary domains adjacent to your agency's name — never the primary domain your clients email. ColdRelay supports 100-150 mailboxes per domain, so a typical branched-campaign pool of 20-50 mailboxes fits on a single domain. Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC pre-configured.
Connect the mailboxes in Woodpecker via SMTP/IMAP
Export the mailbox credentials from the ColdRelay dashboard, then add each account in Woodpecker's email account settings over SMTP/IMAP. If you manage campaigns for multiple clients, Woodpecker's agency panel lets you keep each client's campaigns and connected mailboxes in their own workspace — pair that with a separate ColdRelay pool per client so reputations never mingle.
Set daily limits to 2 and let Woodpecker's intervals pace them
Cap each mailbox's daily sending limit in Woodpecker at 2 outbound emails, mirroring ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup, with warmup running continuously on ColdRelay's side. Woodpecker's human-like sending intervals will space those sends naturally through the day; don't add a second warmup system on top of the budget that's already allocated.
Build the branch map with if-opened and if-clicked conditions
In the Woodpecker campaign editor, write step one, then add condition-based follow-up paths instead of a flat bump chain. If-opened but no reply after three days: the case study email — proof, not pressure. If-clicked on the pricing or portfolio link: the direct ask — a specific call slot, because that click already said 'evaluating.' No open after five days: a new subject line and a different angle entirely, treating it as a fresh first impression. Any reply exits the automation and goes to a human.
Turn on timezone-aware delivery and launch per-prospect
Enable Woodpecker's timezone detection so each prospect's branch fires in their morning, not your server's — a pricing-click follow-up that arrives at 9am local reads as attentive; the same email at 3am reads as a machine. Launch with the full ColdRelay pool in rotation and watch Woodpecker's per-campaign deliverability stats alongside the branch-level reply data.
The Engagement-Branching Playbook for Agencies on Woodpecker
Write four follow-ups for four audiences, not one bump for everyone
The branch map is really a message map. Opened-but-silent prospects have seen your offer and weren't moved — they need new evidence, so the if-opened path carries your strongest case study with a number in it. Pricing-clickers have privately advanced the conversation — the if-clicked path skips persuasion and proposes a time. Never-opened prospects haven't rejected anything; they've rejected a subject line — their path gets a different hook, not a louder repeat. One campaign, four scripts, each written for what the reader actually did.
Treat the pricing-page click as a raised hand with a short half-life
A prospect who clicks through to pricing or your portfolio is doing silent evaluation — the highest-intent behavior a cold campaign can observe short of a reply. Set the if-clicked branch to fire within a day, while the visit is still fresh in their memory, and make the ask concrete: a 20-minute scoping call, two proposed slots. Agencies that fold clickers back into the generic follow-up cadence routinely lose them to whoever else was in the inbox that week — the click was the moment, and the branch exists to catch it.
Give the no-open branch a genuinely new angle, not a louder echo
When a prospect hasn't opened by step three, the failure is at the subject line, and 'RE: my last email' isn't a fix. Use the no-open branch to change the variable that failed: a different hook (a question about their vertical instead of your service), a different proof point, even a different service line if your agency has more than one. Pair it with Woodpecker's A/B testing on the new subject line so the resurrection attempt generates data too — over a quarter, the no-open branch becomes your subject-line laboratory, funded by prospects you'd otherwise have written off.
Review branch-level numbers weekly, and rebalance the scripts
Flat sequences produce one reply rate; branched campaigns produce a distribution that tells you where the motion leaks. If the opened-no-reply pool is large but the case study branch converts poorly, the proof isn't landing — swap the case study, not the offer. If clicks are plentiful but the direct ask stalls, the friction is in the CTA. And if the never-opened pool dominates despite ColdRelay's 95%+ placement, the list or the opening subject line is the problem, not deliverability. Run this read weekly per campaign — and per client, if you're managing several through the agency panel — and the branches keep tuning themselves.
Typical Engagement-Branching Benchmarks (Woodpecker + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants outperform shared Google/Microsoft pools — and clean placement is what keeps if-opened conditions honest |
| Reply rate on branched vs. flat follow-up | 4-8% vs. 2-3% | Behavior-matched follow-ups outperform the uniform 'bumping this up' chain on the same list |
| Reply rate on the if-clicked branch | 12-20% | Pricing- and portfolio-clickers answered a direct ask within 24 hours of the click; speed of the branch matters more than its copy |
| Recovered opens from the no-open branch | 10-15% of cold pool | A genuinely new subject line and angle re-opens prospects the flat sequence would have abandoned |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup, warmup running continuously |
What It Costs: Woodpecker + 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 branching raises reply yield per send rather than raw volume, agencies often find a modest pool goes further here than in a flat-sequence motion.
Woodpecker is billed separately on its own subscription, covering condition-based follow-up paths, timezone-aware delivery, per-campaign deliverability monitoring, A/B testing, and the agency panel — priced per its current plans.
The combined spend buys two different kinds of leverage: ColdRelay's per-mailbox pricing buys the placement that makes engagement signals trustworthy, and Woodpecker's subscription buys the logic that acts on them. Since the branching motion wins by converting more of the same sends, the stack pays for itself in reply yield rather than volume.
| 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
Does ColdRelay replace Woodpecker?
No — they're complementary layers, not competitors. Woodpecker is the sequencing and branching layer: condition-based follow-up paths, timezone-aware delivery, A/B testing, per-campaign deliverability monitoring, and the agency panel. ColdRelay is the infrastructure layer underneath: the secondary domains, mailboxes, and dedicated IPs those branched campaigns send from. An agency running engagement-based follow-up uses both — Woodpecker to decide what each prospect gets next, ColdRelay to make sure it lands.
Do open and click conditions still work reliably enough to branch on?
They're noisier than they used to be — privacy features can inflate opens, and security scanners can trigger phantom clicks — but they remain directionally useful, especially in combination. That's also why the infrastructure layer matters: emails landing in spam produce no signal at all, so poor placement silently miscategorizes interested prospects as cold. With ColdRelay sustaining 95%+ inbox placement, the signals Woodpecker branches on reflect real behavior. Treat clicks as the stronger signal, repeated opens as the medium one, and let a reply — the only perfect signal — always exit the automation to a human.
How many mailboxes does a branched campaign need?
About the same as a flat one — branching changes which follow-up each prospect receives, not how many emails go out. Each ColdRelay mailbox contributes 2 outbound sends/day of its 4/day total (the other 2 are warmup), so a 30-mailbox pool delivers 60 sends/day across all branches combined. Because behavior-matched follow-ups convert better per send, agencies often hit their meeting targets at lower volume than a flat sequence would need — scale the pool when reply handling, not capacity, becomes the constraint.
Do new mailboxes need a warmup period before we launch the branching campaign?
No waiting period. ColdRelay mailboxes provision in about an hour with SPF, DKIM, and DMARC pre-configured, and warmup runs continuously as part of the standard budget — 4 sends/day per mailbox, split 2 outbound + 2 warmup — rather than as an upfront quarantine. Set Woodpecker's per-mailbox daily limit to the 2 outbound sends, let its human-like sending intervals pace them through the day, and the campaign you build this morning can start branching on real engagement by the afternoon.