One Outreach Program, Two Kinds of Persistence
Most ecommerce brands chase two very different partners with the same follow-up cadence — and lose both. A retail buyer who opened your pitch twice but never clicked needs a different next email than a creator who clicked your collab link and went quiet. The buyer is quietly evaluating and needs the line sheet and terms put in front of them; the creator is interested but stuck on specifics and needs content examples and the exact commission math. Send them the same generic 'just bumping this' follow-up and you've answered neither.
Woodpecker is built around exactly this problem: its condition-based follow-up paths branch a sequence on what each prospect actually did — opened, clicked, replied — so one campaign can carry buyer-shaped persistence and creator-shaped persistence at the same time. ColdRelay is the layer underneath: the secondary domains, mailboxes, and dedicated IPs that Woodpecker actually sends from, kept entirely separate from the store domain your customer email depends on. This guide covers how ecommerce teams wire the two together and run one partner program that follows up differently depending on who's on the other end.
Why Run Woodpecker on ColdRelay Infrastructure
Woodpecker's whole value in this motion is behavioral signal — its if-opened and if-clicked conditions decide which follow-up path each prospect travels. But those signals only exist if the email lands in the inbox in the first place. A pitch that goes to spam registers as 'never opened,' your branching logic routes the prospect down the cold path, and the campaign quietly degrades for reasons no amount of copy testing will reveal. Woodpecker monitors deliverability per campaign and paces sends at human-like intervals, but it sends from whatever mailboxes you connect to it — it doesn't provision domains or own the reputation underneath them. That's the infrastructure layer's job.
ColdRelay fills that slot. You provision outreach mailboxes on isolated Azure tenants with dedicated IPs, with SPF, DKIM, and DMARC pre-configured, ready in about an hour. There's no warmup waiting period before your first campaign — warmup runs continuously as part of each mailbox's 4 sends/day budget (2 outbound + 2 warmup) — and with 95%+ inbox placement, the open and click data feeding your condition paths reflects real prospect behavior instead of filter behavior. ColdRelay supports 100-150 mailboxes per domain, so a dual-track partner program rarely needs more than one or two domains.
The pairing is additive, not competitive: ColdRelay is the infrastructure, Woodpecker is the sequencing layer on top. You keep Woodpecker's condition paths, timezone-aware delivery, and A/B testing — you just feed them open and click signals you can actually trust.
Visit Woodpecker →Connecting ColdRelay Mailboxes to Woodpecker
Provision a partner-outreach mailbox pool on ColdRelay
Register secondary domains that read like the partnerships arm of the brand — brand-partners.com or workwithbrand.com — never your storefront domain. A dual-track buyer-and-creator program is a finite-list motion, so most brands start with 20-50 mailboxes on a single domain (ColdRelay fits 100-150 per domain). Everything provisions on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured.
Add the mailboxes in Woodpecker and cap them at the ColdRelay budget
In Woodpecker, add each ColdRelay mailbox as a sending account via the SMTP/IMAP credentials from your ColdRelay dashboard export, then set each account's daily sending limit to 2 outbound emails. That mirrors ColdRelay's per-mailbox budget — 4 sends/day total, split 2 outbound + 2 warmup. Warmup runs continuously on ColdRelay's side, so there's no waiting period before launch; let Woodpecker's human-like sending intervals handle the pacing within that cap.
Build the buyer track with condition-based follow-up paths
Create the buyer campaign and put Woodpecker's if-opened and if-clicked conditions to work. Prospect opened twice but never clicked? Branch to a follow-up that attaches nothing and asks one question: 'Worth sending the line sheet?' Prospect clicked your catalog link? Branch straight to terms — wholesale pricing, MOQs, lead times — because a buyer who clicked is pricing you against their current assortment. Prospects who never open just get a clean resend with a new subject line. Each branch answers what the behavior was actually asking.
Build the creator track with its own branch logic
Clone the structure, not the branches. In the creator campaign, an if-clicked condition on your collab page link routes to commission specifics — rates, cookie window, payment schedule — because a creator who clicked is doing the math. The if-opened-but-not-clicked path routes to proof instead: two or three examples of content from creators already in the program, with real numbers attached. Same Woodpecker mechanic as the buyer track, completely different persistence — which is the entire point of running both tracks as condition-path campaigns.
Turn on timezone delivery and A/B test inside each branch
Set Woodpecker to deliver in each prospect's timezone — buyers read email in their working morning, and creator lists are scattered across continents, so a fixed send window quietly wastes half the list. Then use Woodpecker's A/B testing within branches rather than across whole campaigns: test two versions of the post-click terms email against each other, not buyer copy against creator copy. Watch Woodpecker's per-campaign deliverability monitoring as you scale; if one track's metrics dip, you can pause and diagnose it without touching the other.
The Ecommerce Woodpecker Playbook
Let the click decide what the next email contains
A click is the most honest thing a partner prospect ever tells you. A buyer who clicked your catalog wants commercial terms, not more brand story; a creator who clicked your collab page wants the commission math, not another compliment about their feed. Build every Woodpecker if-clicked branch to deliver the document the click was implicitly requesting — line sheet and MOQs on the buyer track, rates and payment schedule on the creator track — and you'll stop sending interested prospects back to the top of the funnel.
Calibrate persistence to how each partner type actually decides
Buyers and creators don't just need different content — they need different clocks. A category buyer works on review cycles and routinely replies on touch five or six, so the buyer track should run long with patient, spaced steps. Creator interest decays in days; past the third touch you're recruiting someone who already said yes to another brand. Set the buyer track to 5-6 steps over six weeks and the creator track to 3-4 steps over ten days, and let Woodpecker run both cadences from the same mailbox pool simultaneously.
Use opened-but-not-clicked as your objection detector
The prospect who opens every email and clicks nothing is telling you the offer has a snag they won't volunteer. On the buyer track, that branch should name the likely objection outright — 'If the concern is minimums, we do opening orders from 50 units.' On the creator track, it should drop the barrier — a no-strings product sample, no contract attached. Woodpecker's condition paths let you aim that objection-handling email at exactly the prospects whose behavior says they have one, instead of leading with concessions to the whole list.
Read per-campaign deliverability per track, not blended
Buyer and creator lists fail differently: buyer lists rot as retail contacts churn roles, creator lists carry more throwaway and secondary addresses. Keep the two tracks as separate Woodpecker campaigns and watch its deliverability monitoring per campaign, so a bounce spike on one track triggers a list-cleaning pass on that list alone. Both tracks send from the same ColdRelay pool, so list hygiene is the variable you manage — the domains, dedicated IPs, and isolated tenants underneath stay constant.
Typical Dual-Track Partner Outreach Benchmarks (Woodpecker + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — and the open/click signals feeding condition paths stay trustworthy |
| Reply rate — buyer track with condition-based follow-ups | 3-6% | Branched follow-ups outperform linear bumps; most buyer replies arrive on touches 3-6 |
| Reply rate — creator track with post-click commission detail | 5-10% | Creators who clicked and then received exact terms reply at the high end; speed matters |
| Click-to-reply conversion on if-clicked branches | 15-25% | The branch email answers what the click asked for — terms for buyers, rates for creators |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup; both tracks share the pool |
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 both partner tracks share one mailbox pool, a dual-track program doesn't cost more infrastructure than a single-track one.
Woodpecker is billed separately on its own subscription for sequences, condition-based follow-up paths, timezone delivery, A/B testing, and deliverability monitoring — priced per its current plans.
Infrastructure cost scales with mailbox count; Woodpecker's cost scales with its plan and prospect volume. The two stack cleanly — one bill for sending capacity, one for the sequencing logic — and neither touches your Klaviyo or transactional email spend.
| 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, used together. Woodpecker handles sequencing, condition-based follow-up paths, timezone-aware delivery, A/B testing, and per-campaign deliverability monitoring. ColdRelay provides the underlying secondary domains, mailboxes, and dedicated IPs that Woodpecker sends from. Woodpecker decides which email each prospect gets next; ColdRelay makes sure every one of those emails lands where the prospect can act on it.
Do buyer and creator outreach really need separate follow-up logic?
Yes — they fail in opposite ways with shared logic. Buyers decide slowly against review calendars and reward long, patient sequences with concrete commercial detail; creators decide fast and go cold if the third touch still hasn't shown them the commission math. Woodpecker's condition paths let you encode both kinds of persistence as two campaigns with different branch rules, while the sending capacity underneath — one ColdRelay mailbox pool at 4 sends/day per mailbox (2 outbound + 2 warmup) — stays shared.
Will condition-path campaigns work if our emails land in spam?
No — and that's the quiet failure mode of behavioral sequencing. An email that hits spam reads as 'never opened,' so your if-opened branches route a potentially interested prospect down the cold-resend path and the logic eats itself. ColdRelay's isolated Azure tenants with dedicated IPs and pre-configured SPF, DKIM, and DMARC hold placement at 95%+, which keeps Woodpecker's open and click data describing prospect behavior rather than filter behavior.
How many mailboxes does a dual-track partner program need?
Usually fewer than expected, because both tracks draw from one pool. Each ColdRelay mailbox sends 4 emails/day total — 2 outbound + 2 warmup — so 30 mailboxes gives 60 outbound sends a day to split between the buyer and creator campaigns however Woodpecker's queues demand. That covers most brands' curated partner lists with multi-step branched sequences; scale toward 50-100 mailboxes when you add regions or categories, and remember ColdRelay fits 100-150 mailboxes on a single domain.