A CRM cadence — Zoho calls it "Cadences," other platforms call it a sales sequence or outreach cadence — is a pre-built series of timed touches, emails, calls, tasks, or WhatsApp messages, that automatically nurtures a lead from first contact through to a reply, a meeting, or a clean exit. Instead of a rep manually remembering to follow up in a week, then two weeks, then a month, the CRM handles the timing, and the human handles the conversations that come back.
We recently built one from the ground up for our own cold outreach. This is what the data says about cadences in general, what we learned building ours, and a few other real examples worth knowing about.
Why It Matters: What the Data Says
A few numbers worth knowing before you design a cadence of your own:
- 58% of replies come from the first email — but the other 42% only show up because someone followed up. A single follow-up alone lifts total replies by roughly 66%.
- The sweet spot is 4–7 touches over about two weeks. A 3-7-7-day spacing pattern captures around 93% of all the replies you were ever going to get.
- Average B2B cold email reply rates sit around 2–3.4%. "Good" is 5–10%, and 10–15%+ is considered excellent — though this varies hugely by industry: legal-services outreach can reach 10% replies, while SaaS/tech and financial-services outreach often sits under 2.5%.
- Personalisation pays for itself: heavily personalised emails see 6–10% response versus 1–2% for fully generic blasts. Advanced personalisation can lift replies as much as 142% over a plain template.
- Multi-channel beats email alone: cadences that mix in calls, SMS, or LinkedIn touches get 2–3x the reply rate of email-only sequences.
Case Study 1: Building Our Own Cold-Outreach Cadence
This is the project we just went through ourselves — setting up our first cold-outreach system on Zoho CRM. A few things stood out as we built it.
Deliverability comes before anything else
Before a single email went out, we had to confirm SPF, DKIM, and DMARC were correctly published for the sending domain. One record looked correct in the DNS panel but simply hadn't been saved — it showed fine on screen but didn't exist on the public internet at all. No cadence, however well written, survives sending from an unauthenticated domain. This is the part that's easy to skip and expensive to skip.
Exit criteria is not optional
A cadence that keeps emailing someone who already replied, unsubscribed, or bounced is the fastest way to damage a relationship or a domain's sending reputation. We set the cadence to automatically un-enroll a lead the moment any one of those three things happens, rather than relying on someone remembering to remove them by hand.
Don't fake personalisation
Our first template drafts included merge fields for a personalised "angle" and "area of interest" for each lead — fields that sounded good in theory but were empty for every real lead we had so far. We stripped them out rather than ship a template with blank spots, and plan to bring them back once that research data actually exists. A guessed personalisation is worse than no personalisation.
A five-step arc, not five copies of the same email
The sequence runs Day 0 (initial outreach), Day 7 and Day 14 (soft follow-ups), Day 30 (a deliberate "should I close this out?" message that lowers pressure rather than repeating the pitch), and Day 180 (a fresh re-engagement email, since five months of silence deserves a new opening, not a continuation of the old thread). Each step has a different job — treating all five as the same email with a different send date wastes the later touches.
The little things that read as "human" or "bulk"
Two small details turned out to matter more than expected: the sender's display name (a real name reads as a person; a bare email address reads as automation) and where the email lands in Gmail's tabs. Landing in the Promotions tab is normal for any CRM-sent bulk email — it is not the same as landing in spam, and isn't a sign anything is broken.
Test on yourself first
Before any real prospect saw the sequence, we enrolled an internal test lead using our own inbox, to confirm the templates rendered correctly, the unsubscribe link worked, and replies were actually being detected — which, on Zoho, requires connecting the sending mailbox back into the CRM via IMAP so incoming replies get matched to the right lead record.
Every Way a Record Can Exit a Cadence
The docx we started from mentioned exit criteria in passing. It deserves a full breakdown, because Zoho gives you more exit paths than most people configure, and leaving one on default is how a cadence quietly keeps annoying someone long after it should have stopped.
Reply detected
The most common and most important exit. Requires the sending mailbox connected via IMAP so replies land back against the correct record — without this, a genuine reply can go unnoticed and the cadence keeps running past it.
Bounce or complaint
A hard bounce or a spam complaint should remove a record immediately, not after the next scheduled step. Left unchecked, repeated sends to a bouncing address are one of the fastest ways to damage sender reputation.
Custom un-enrollment criteria
Zoho lets you define exit conditions based on specific field values or activity signals — a deal stage changing, a specific field being updated, an activity being logged. This is more flexible than the older fixed exit types and worth using deliberately rather than settling for the defaults.
Falling out of the custom view
If a cadence is built on a custom view rather than manual enrollment, a record can be configured to automatically un-enroll the moment it no longer matches that view's criteria — useful when the segment definition itself is the real qualifying condition, not a separate rule layered on top.
Cadence-wide stop date
A specific date after which any record still in the sequence gets un-enrolled regardless of what step it is on. Useful for time-bound campaigns where continuing past a certain point no longer makes sense.
Manual removal or natural completion
Someone removes a record by hand, or it simply finishes every step with no reply — both are legitimate exits, and both are good candidates for a different, longer-cycle re-engagement cadence rather than being left to disappear.
Resume vs. restart, when re-enrolling a record. Zoho lets you re-enroll a previously un-enrolled record either by resuming from wherever it left off, or restarting the full sequence from step one — genuinely useful for a seasonal campaign or a deliberate re-engagement push where the old context no longer applies. Both options are only available for manually enrolled records, not custom-view-based ones, which is worth knowing before you plan a re-engagement flow around it.
Different Follow-Up Types, Not Just Email
A cadence step does not have to be an email. Treating every step as an email by default is a missed opportunity, since Zoho supports several step types natively.
The default and the backbone of most cadences — scalable, trackable, and the easiest to personalise with merge fields.
Task
A reminder for a human to do something — "call this lead," "check their LinkedIn activity" — rather than an automated send. Useful for steps that genuinely need a person's judgement, not automation pretending to be personal.
Call
A logged call step, tracked as part of the sequence rather than happening outside it and never being recorded against the lead.
WhatsApp message
A more recent addition to Cadences — genuinely useful where email open rates are weak but a WhatsApp message is more likely to actually get read, particularly in markets where WhatsApp is a primary business communication channel.
Mixing types deliberately, rather than defaulting to five emails in a row, is exactly what the multi-channel data above points to: a call or a WhatsApp touch mixed into an email-heavy sequence tends to lift replies well past what an email-only cadence achieves on its own.
Workarounds We Actually Used
Fallback text for merge fields, not blank fields
Beyond simply stripping the personalisation fields we didn't have data for yet, we built a fallback default into any merge field that could plausibly be empty — so a template never renders with a literal blank space or an awkward "Hi ," if a field is missing for one specific lead.
A separate subdomain for cold outreach
Rather than sending cold email from the same domain used for regular client correspondence, we used a dedicated subdomain. If something goes wrong with deliverability or a spam complaint during the cadence's early days, it does not put the primary domain's sending reputation at risk.
Checking IMAP sync when replies seem to go undetected
The most common cause of a "missed" reply is not a broken cadence, it's the IMAP connection between the mailbox and the CRM silently losing sync. When a reply doesn't trigger the expected exit, checking the mailbox connection status is the first thing to look at, before assuming the cadence logic itself is wrong.
A spam-score check before going live
Beyond the internal self-test, running the first template through a third-party spam-score checker before enrolling any real lead caught formatting and authentication issues our own inbox test didn't surface, since a self-test to your own address doesn't always reflect how a genuinely cold recipient's mail server will treat it.
Case Study 2: A Growing Sales Team's Zoho CRM Cadence Rollout
A separate, publicly documented Zoho CRM Cadences implementation (via Zoho partner BoostedCRM) reported a similar pattern of results, described qualitatively rather than with precise figures: consistent follow-up replaced ad hoc reminders, automation freed up rep time that used to go into manual chasing, and multi-channel outreach improved engagement and conversion by ensuring better timing and messaging. The framing they used was moving "from chaos to clarity" — the value came from having a repeatable, structured process at all, not from one dramatic metric.
Case Study 3: What 100M+ Cold Emails Reveal About Cadence Design
Cleverly's analysis of over 100 million cold emails is a useful sanity check on cadence length and timing. Their data shows that stopping after one email leaves 42% of potential replies on the table, that a 3-7-7-day cadence captures 93% of replies within ten days, and that going past 4–7 touches produces rapidly diminishing returns. It's a good reminder that "more follow-ups" isn't automatically better — it's a specific, fairly short window where almost all the value sits.
Setting up your first Zoho CRM Cadence, or want an experienced pair of eyes on one that isn't performing?
We implement Zoho CRM Cadences for businesses across India, USA and UAE — deliverability setup, exit criteria, template design and the workarounds that only show up once you're actually running one.
Talk to an Expert → Book a Call Today →Lessons Learned
- Get SPF, DKIM, and DMARC right before anything else — no cadence design fixes a domain that lands in spam.
- Always configure exit criteria (reply, bounce, unsubscribe) before enrolling a single real lead.
- Leave a merge field empty, or give it a sensible fallback, rather than guess — fake personalisation is worse than none.
- Landing in Gmail's Promotions tab is normal for CRM-sent mail; it isn't a spam signal.
- A real sender name, not a bare email address, measurably changes how human an email feels.
- Space touches the way the data suggests: tight in the first two weeks, then a long tail (a month, several months) for the patient re-engagement touch.
- Mix follow-up types deliberately — a task, a call, or a WhatsApp message can outperform another email in the same slot.
- Always test the full sequence on yourself before a real prospect ever sees it, and check IMAP sync first if a reply seems to go undetected.
How to Set Up Your Own Cadence
- Authenticate your sending domain first (SPF, DKIM, DMARC) — and confirm the records are actually live, not just saved in a form.
- Consider a dedicated subdomain for cold outreach to protect your primary domain's sending reputation.
- Map out every step and its timing before writing a single template, and decide deliberately which steps are emails versus tasks, calls, or WhatsApp messages.
- Write the first email to earn a reply, not to sell — keep it short and make the ask small.
- Set every exit condition before you enable anything: reply, bounce, custom criteria, and a cadence-wide stop date if the campaign is time-bound.
- Test the whole sequence on yourself end-to-end, including confirming IMAP reply detection actually works.
- Watch bounce rate and complaint rate, not open rate — those are the numbers that actually threaten your sending reputation.
Frequently Asked Questions
We're a Zoho Authorized Partner and went through this build first-hand for our own outreach — happy to compare notes with anyone setting up their first cadence.
Want a Zoho CRM Cadence built properly the first time, deliverability and exit criteria included?
We implement Zoho CRM Cadences and the wider CRM for businesses across India, USA and UAE — set up correctly from domain authentication through to exit criteria and follow-up mix.
Talk to an Expert → Book a Call Today →