Agentic Email Cadence Template
The cadence Wyse runs by default on cold pipeline. Five touches over fourteen days, each one informed by the reply (or silence) on the last.
Why this matters
- 1Cold email open rates have collapsed: average is now 18 to 22 percent across SaaS. Cadence does the work that subject lines used to.
- 2Most teams stop at touch three. The fourth and fifth touch convert at roughly 1.7x the first because the inbox-noise floor is high but the persistence floor is low.
- 3An AI agent can read what's on a prospect's LinkedIn this week and personalize touches two through five without a human ever opening the prospect's profile.
- 4Graceful breakup emails recover roughly 8 percent of dead pipeline. Most cadences skip them.
The template, step by step
- 01
Score the lead before you draft anything
Personality read first: are they an LP-style decision-maker (skim a one-pager, want numbers) or an analyst-style (will read the whole sequence, want the proof)? Wyse infers this from their LinkedIn, recent posts, and the title family. The cadence shape stays the same. The voice shifts.
- 02
Touch 1, day 0: the value, not the ask
Subject line is six words or fewer, no question mark, no caps. Body is three sentences: relevant observation, one specific value drop (case study, number, framework), one soft CTA (a yes-or-no question they can answer in five words). No calendar link on touch one.
- 03
Touch 2, day 3: the deeper proof
Reference the first email by name ("sent you a note about X on Monday"). Add the next layer: a customer quote, a screenshot from your dashboard, a one-sentence case study with a number. Same CTA shape as touch 1.
- 04
Touch 3, day 7: the pivot
Change the angle. If touches 1-2 led with the buyer's role pain, lead with the team pain. If you led with revenue, lead with operations. This is the touch that earns the meeting from the second-tier prospects who are interested but were waiting for the angle that mattered to them.
- 05
Touch 4, day 11: the time-bound
Introduce a real constraint. Could be a new feature shipping, a pricing change, a webinar slot, or an honest "we have three slots left this quarter for hands-on rollout." If the constraint isn't real, skip the touch entirely. Fake urgency reads as fake.
- 06
Touch 5, day 14: the graceful exit
Subject: "Closing the loop on [Company]." Body: one sentence acknowledging the silence, one sentence with the door left open, one sentence with a no-strings asset (a free playbook, your changelog, your latest blog post). This is the touch that brings 8 percent back from the dead.
TOUCH 1 — Day 0 (Tuesday or Thursday) Subject: [6-word value framing, no question] Body: - Sentence 1: Specific observation about [Company] - Sentence 2: One numerical value drop (case study, framework) - Sentence 3: Yes/no question they can answer in five words TOUCH 2 — Day 3 Subject: Re: [touch 1 subject] Body: - Sentence 1: Reference touch 1 by topic - Sentence 2: Next proof layer (quote, screenshot, mini case) - Sentence 3: Same shape CTA as touch 1 TOUCH 3 — Day 7 Subject: [New 6-word angle, fresh] Body: - Pivot the value: role pain → team pain (or revenue → ops) - One sentence why this angle matters for [their role] - Soft CTA, optional calendar link TOUCH 4 — Day 11 Subject: [Time-bound trigger] Body: - Mention the real constraint (feature, pricing, slot) - One sentence on what they lose by waiting - Clear CTA with deadline TOUCH 5 — Day 14 Subject: Closing the loop on [Company] Body: - Acknowledge silence in one line - Leave door open in one line - Attach a free asset (playbook, changelog, blog post) — no ask
Common mistakes
- Sending touch 1 on a Monday or Friday. Both have ~30 percent worse open rates than Tuesday/Thursday.
- Reusing the touch 1 subject line on touches 3 and 4. Inbox dedup hides it.
- Putting a calendar link in touch 1. Conversion-killer when there's no relationship yet.
- Sending touches 4 and 5 if the prospect replied to any earlier touch, even with "not now." Move them to nurture, not the next cold step.
- Treating touch 5 as another ask. It's a goodbye. The asset matters, the question doesn't.
Let OpsWyse run this template on autopilot.
Wyse drafts every input, every personalization, every follow-up in your brand voice. You approve before anything goes live.
Questions
Why five touches and not seven?
Touches six and seven add diminishing returns and burn deliverability. The data we have across roughly 12,000 cadences run through Wyse shows touches 6-7 add about 1.4 percent reply rate at a 2x increase in spam-folder risk. Five touches is the conversion peak before quality starts to decay.
What if they reply mid-cadence?
Pause the cadence immediately. Wyse moves them to a 'Talking' segment and assigns a human follow-up within four business hours. The cadence is for silence. Once there's a reply, you are not running a cadence anymore, you are running a conversation.
Does Wyse personalize each touch or use templates?
Both. The cadence shape is templated. The opening line of each touch is personalized using the prospect's LinkedIn, recent company news, and any prior conversation context. The closing CTA stays templated to avoid voice drift across the cadence.
What's a good reply rate for this cadence?
On warm-ish lists (existing waitlist, MQLs, demo no-shows) we see 18 to 24 percent reply rates across the full cadence. On cold lists, 6 to 9 percent is realistic. If you're below 4 percent on cold, the list is the problem, not the cadence.
Can I run this cadence without Wyse?
Yes. The template is platform-agnostic. The point of Wyse is that the personalization, the personality read, and the reply handling all run automatically and stay in your brand voice. Without Wyse you'll do the personalization manually or skip it. With Wyse, the personalization is the default.
Cold Outreach Sequence Template
Multi-channel cold outreach: email, LinkedIn DM, voicemail. Eight touches across three channels in eighteen days.
ICP Research Brief Template
Ideal customer profile worksheet: nine sections, sixty questions, the brief you'd hand a researcher to define who you actually sell to.