Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

CRM & Marketing Automation › Troubleshooting

Leads Stalling in a Nurture Sequence

Why leads enter a nurture sequence and never progress: no observable goal, content that fills slots, exits that never fire and no feedback from sales.
Troubleshootingintermediate18 min readUpdated

First, check the sequence has a goal event, exits and a holdout to read it against

Before anything else, say what progressing means for this sequence. The nurture sequences guide asks every sequence for one goal, stated as a change in the lead's state that the system can observe: a pricing page viewed, a comparison downloaded, a demo requested, a reply to a named person. If the sequence you are reading has no such event, there is no progression figure to read, only a count of sends and whatever engagement the platform shows, and a stall cannot be diagnosed from that. Write the goal down now, even if only on paper, because every check below compares what the leads did against it. Kaushik's Digital Marketing and Measurement Model, as the measurement plan framework states it, sets out objectives, goals, KPIs and targets, and a sequence judged on opens has neither an objective nor a target behind the number.

Then find the exits. The guide names three that should fire before the series runs out: the goal event itself, a disqualifying event such as an unsubscribe, a bounce, a reply asking to stop or a deal closed lost, and a higher-priority workflow taking the lead. Open the workflow and list which of those are wired. A sequence with no exits ends on a timer, so a lead who reached the goal at the second step still receives the rest, and a lead who was never going to progress receives all of them too. Both appear in the same report as leads who did not progress, which is why the exits have to be known before the figure can be trusted.

Finally, ask whether anyone was held out. The guide measures a sequence by the share of entrants who reach the goal within a window, compared with a small random share of eligible leads kept out of it. Without the holdout the sequence takes credit for leads who would have moved on their own and blame for leads who were never going to, and a stall can be an honest report of a quiet quarter rather than a fault in the design. Once the goal is known, the See-Think-Do-Care framework gives the test for each step: which cluster is this lead in, what would that person thank you for, and does this message answer it? A step that answers a different cluster's question is filling a slot, and the table below finds the ones that do.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
Entrants receive every step; the report shows sends and clicks but no progression figureWhether the workflow names a goal event and exits on itThe sequence has no observable goal event, so it finishes on a timer whether or not the lead movedWrite one observable goal, exit on it and read entrants against a holdout
Clicks fall step by step, and the steps that earn clicks are not the ones before goal eventsEach step's content against the question of the lead's stageContent chosen by publication date rather than the question the lead has at that stageReplace each slot-filler with the asset the stage goal calls for
Leads view pricing or ask for information and still receive the next stepsThe hand-off threshold and decay rule against where leads sales accepted sat before hand-offThe hand-off threshold set so high, or decay so slow, that leads sit in nurture after showing intentRecalibrate the line with sales from what closed; route declared actions at once
The enrolled list holds current clients and contacts with open dealsEntrants' lifecycle stage and open-opportunity field, at entry and nowCustomers, open opportunities and closed deals still inside the sequence, diluting the progression figureGate entry and every send on customer and opportunity status; exit a deal's contacts when it is won
Unsubscribes and replies asking to stop cluster in the weeks the newsletter or an event invitation also wentEverything the lead received from every workflow in the same weekThe sequence competing with the newsletter and events for the same inbox, with no priority or capSet a global frequency cap and a priority order, and make nurture yield
The same leads enter again after sales returned them, with no reason on the recordThe disqualification reason on recycled records and the sequence they re-enteredLeads sales rejected recycled into the same sequence with no reason recordedRequire a reason on every return; recycle by reason into a sequence built for it, or close the record

Fix, verify and prevent each cause

The sequence has no observable goal event

The nurture guide's first design question is the goal, and its first common mistake is a sequence without one: the series finishes on a timer whether or not the lead moved. A sequence built that way cannot stall, strictly speaking, because it never said what moving would look like; it can only be finished or unfinished. The symptom you are reading is the gap between what the sequence sends and what it was meant to produce, and it will not close until the goal is an event the workflow can see.

Fix: write one observable goal for the sequence, chosen from the stage it serves, since the guide's table pairs each stage with the question the lead has and the event that shows it was answered; add that event as the first exit; and open the nurture sequence plan template so the goal, the exits and the holdout have a written home beside the workflow.

Verify: take a seed lead through the sequence, raise the goal event part-way, and confirm the lead leaves at once; then read the next period's entrants as a share reaching the goal, beside a held-out share, rather than as a count of sends.

Prevent: make the plan a condition of building. A sequence whose plan cannot name its goal event and its exits is not ready for the canvas, as the template says, and a plan written first is the cheapest check the sequence will ever get.

Content chosen by date rather than by the lead's question

A sequence fills up. The product team asks for the release note to go in, the events team adds its invitation, and whatever was published last month takes the slot that was free. The content goals and KPIs guide describes the drift in general terms: goals set as output and measured by whatever the tool shows first, until the calendar is the plan and the plan is the goal. Inside a sequence the result is a step that announces rather than answers, and the nurture guide's test catches it: if the lead reads this and nothing else, are they closer to the goal event? The See-Think-Do-Care clusters make the test concrete. A problem-aware lead wants to know whether the problem is worth solving; a solution-aware lead wants to know which kind of solution fits; an evaluating lead wants price, effort and proof. A release note answers none of those questions.

Fix: map each step to the lead's stage and question, replace the steps that fail the test with the asset the content goals guide plans for that stage, and move anything that is an announcement to the newsletter where it belongs.

Verify: compare the steps that earn clicks with the steps that precede goal events; after the change the two lists should start to coincide, and unsubscribes per step should stop clustering on the announcements.

Prevent: give each step a job in the sequence plan, and refuse any new step that cannot state the question it answers for the lead at that stage.

A hand-off threshold so high that intent waits in nurture

A nurture is meant to end when the lead shows they are ready, and the lead scoring guide decides when that is. Thresholds mean something only when they are tied to the stage definitions sales and marketing agreed, set from where the leads that later closed sat the week before they were accepted, and recalibrated against outcomes with sales in the room. A line set from instinct, or never revisited, sits above the behaviour of real buyers, and the lead who viewed pricing twice stays in nurture receiving the explainer written for someone much earlier in the funnel. Decay works the same way: intent that fades too slowly keeps old readers near the line while recent buyers wait behind them. The guide also names the one case that should never wait for a score: a declared action such as a demo or quote request is routed at once, whatever the fit fields say.

Fix: run the scoring guide's calibration, find where accepted and won leads sat on the score before hand-off, and move the line with sales to where most of them would have crossed; add the automatic hand-off on declared actions; and set decay so that recent intent outweighs old reading. Where the two teams cannot agree how far to move the line, the lead scoring threshold test randomises leads in the band just below it between sales and nurture and reads pipeline per lead.

Verify: leads who show the agreed intent signals leave the sequence for sales within the service window, and the share of entrants reaching the goal rises without the share sales accepts falling.

Prevent: keep the quarterly calibration the scoring guide asks for, tied to the pipeline review so that stage definitions and the threshold move together, and log every change to the line with its reason and date.

Customers and open deals inside the sequence

A progression figure counts entrants who reached the goal over entrants who could have. Customers cannot request a first demo, contacts with an open opportunity already have one, and both sit in the denominator making the sequence look worse than it is while receiving messages written for strangers. The closed-won workflow tutorial owns the moment a deal is won: the customer stage is set, the deal's contacts leave every prospect sequence, and the customer stage becomes a suppression condition at entry and before each send so that a later form fill cannot enrol them again. The automation governance guide adds the open-opportunity and not-a-fit conditions beside it, as rails every workflow carries. When the people inside the sequence are the complaint rather than the figure, the diagnosis for customers receiving prospect messages traces which gate, status, record or import let them in.

Fix: add customer, open-opportunity and closed-deal conditions at entry and before every send, exit anyone already in the sequence who meets them, and build or repair the closed-won workflow so the exit happens the moment a deal is won rather than when someone notices.

Verify: the enrolled list contains nobody with the customer stage or an open deal; a test deal marked won removes its contacts from the sequence at once; and the goal share, recomputed on prospects only, is the figure you now read.

Prevent: keep a seeded customer contact and a seeded open-deal contact that must stay out of every prospect sequence, and check them after each change to the sync, the closed-won workflow or the entry conditions.

The sequence competing for the inbox with no priority or cap

From inside the canvas a sequence looks reasonable: one message at a time, each with a purpose. The lead's inbox also holds the newsletter, the webinar invitation, the product announcement and whatever sales sends by hand. The nurture guide is explicit that frequency is governed across workflows, not within one, and the governance guide owns the two controls that see the whole picture: a channel-level frequency cap checked before every send, and a priority order that decides which workflow goes and which waits when several compete. Without them the lead's response is to leave, and a reply asking to stop is a disqualifying exit the sequence must honour at once. The ICO's direct marketing guidance, as the site's guides state it, expects an objection to marketing to be honoured in every tool, not noted in one.

Fix: set the global cap and the priority order at the governance level, make the nurture yield to a demo request, a service message and any workflow that outranks it, and route replies to a named person who can act on them and exit the lead from the automated steps.

Verify: the send logs for a sample of enrolled leads show no week in which the cap was exceeded across all workflows, and unsubscribes and stop replies stop clustering in the weeks the newsletter went.

Prevent: judge frequency on the inbox rather than the sequence, and use the governance guide's monthly spot check of suppression and consent conditions with seed contacts to find a cap or a priority rule that has quietly stopped being applied.

Leads sales rejected, recycled with no reason

A lead sales returns is not a lead to send round again. The lead stages and pipeline guide separates the two kinds: fit and junk reasons close the record, and timing, budget and need reasons recycle it into a nurture sequence designed for that reason, with a re-entry rule that lets it cross the marketing-qualified line again when behaviour changes. The reason is what decides, and it has to be recorded from a short picklist both teams agreed. When it is not recorded, every returned lead goes back into the sequence that produced it, reads the same steps, crosses the same line and is returned again, which is the stall at its purest: a loop with no learning in it. The nurture guide asks for the same feedback from the sales side, with rejected leads coming back carrying a reason that feeds the scoring model.

Fix: make the reason a required field on every return and every lost opportunity, route recycled leads by reason into a sequence built for a stalled or lost lead rather than the original one, close the records whose reason was fit, and feed the reasons into the next scoring calibration.

Verify: recycled and disqualified records appear separately in the report, no record enters the sequence it was returned from, and the sales-accepted share of recycled leads who re-qualify can be read by reason.

Prevent: report recycled and disqualified records separately from new ones, as the pipeline guide asks, and read the re-qualification share by reason at the quarterly calibration, so that a reason that never re-qualifies is retired and a reason that does gets a sequence of its own.

Prevention: a sequence plan with one goal, written exits and a quarterly calibration with sales

Every cause above is a design decision that nobody wrote down. The goal lived in the head of whoever built the sequence; the exits were whatever the platform defaulted to; the threshold was set once and defended; the customer gate was assumed; the frequency was judged one workflow at a time; the recycling rule did not exist. The nurture sequence plan template gives each of those decisions a field, and the habit that prevents the stall is simply that the plan is written before the build and revised whenever the sequence changes. Stage and goal, entry trigger and gates, exits, re-entry rule, each message's job, consent and frequency, score and hand-off, what sales sees and does, the measure and its holdout, and the owner and review date: a sequence whose plan has a blank in any of those rows is a sequence that will one day stall for exactly that reason.

The second habit is to read progression on a fixed rhythm, against the holdout, and to review it beside the scoring calibration so both halves of the loop change together. The nurture guide names the three figures: the share of entrants reaching the goal within the window, which is the sequence's own conversion rate; the time to goal; and the downstream rate of progressed leads that sales accepted and that became opportunities, which tells you whether the goal event was the right proxy for readiness. The governance guide's quarterly audit already asks for nurture conversion rates to be reviewed against their holdouts and for scoring weights and thresholds to be calibrated with sales, so the review has a home; the work is to put the sequence plan on the table at the same session, with the step-level clicks and unsubscribes beside it, and to record the decision taken as well as the numbers. What happens to leads after the hand-off belongs to a different review: when leads cross the line and sales returns them, the diagnosis for marketing-qualified leads that never become sales-qualified starts from the rejection reasons rather than from the sequence.

The third habit is to keep the rails and the seeds. Lead nurturing depends on conditions it cannot see from inside the canvas: the customer stage set by the closed-won workflow, the open-opportunity flag, the suppression list, the frequency cap, the priority order. Each of those is owned by a guide linked above, and each is tested the same way, with permanent seed contacts that should enter, should be gated out as a customer, should be pulled out by a demo request and should be held back by the cap. Run the seeds after any change to the sequence, the sync, the scoring model or the entry conditions, and read the enrolment history rather than the workflow's settings. The workflows hub describes that check for any launch, and the lead scoring guide's weekly look at who crossed the line and who was returned is where a threshold that has drifted shows first.

Two neighbouring symptoms are worth telling apart from this one before the routine starts. A sequence that enrols nobody at all, or stops acting on the leads it enrols, is a workflow fault rather than a design fault, and the diagnosis for a CRM workflow that is not running reads one run as trigger, condition, action and exit. Clicks that never become orders, in a campaign rather than a sequence, are the subject of the email clicks but no sales diagnosis, which starts from tagging and the path to checkout. The glossary entry for lead nurturing gives the short definition this page assumes, and the marketing automation troubleshooting hub lists the other symptoms a stalled sequence can arrive with, such as customers receiving prospect messages or values reverting after a sync, so the right page is read first.

A payroll bureau rebuilds a sequence that never ended (illustrative)

Illustrative example — not a real result

Sylvokarr Payroll Bureau

Sylvokarr Payroll Bureau, an invented payroll bureau for small employers, runs a 9-step sequence for people who downloaded its year-end checklist. The sequence was built to produce demo requests. Over two quarters 1,460 leads entered and 23 requested a demo while enrolled, and the marketing lead is asked why a sequence with a 38% average click rate produces so little.

Reading the sequence against the nurture guide finds four faults at once. There is no exit on a demo booked through another route, so 41 leads who booked by phone or from the pricing page received the remaining steps, and 6 of them replied asking to stop. Four of the 9 steps are product announcements the product team added over the year, and they account for 52 of the quarter's 71 unsubscribes while preceding 2 goal events between them. The hand-off threshold was set at launch from a guess and never revisited: 112 leads who viewed the pricing page at least twice stayed in nurture, and when the operations lead checks where the 19 won deals from the period sat on the score the week before sales accepted them, 14 would have crossed a line roughly a third lower. And 87 of the entrants were existing clients, enrolled because the checklist form had no customer condition.

The bureau writes a plan for the sequence with one goal, a demo request or a pricing visit followed by a reply, and exits on the goal, on any demo booked by any route and on a stop reply. It removes the four announcements and replaces two of them with a comparison of in-house and outsourced year-end processing and a short note from a named account manager. It lowers the threshold with sales to the line the calibration found and adds an immediate hand-off on any demo request. The closed-won workflow is extended to set the customer stage and to suppress the sequence at entry and before every send, which removes the 87 clients, and a seeded client contact is kept to check it. A random 10% of eligible leads is held out. The following quarter 690 prospects enter, 61 reach the goal within 45 days against 2 of the 77 held out, sales accepts 49 of the 61, and unsubscribes fall to 14.

Common mistakes

  • Reading opens and clicks as progression. They show which steps earn attention; only the goal event shows whether anyone moved.
  • Adding or removing steps before adding a goal and exits. Length is rarely the fault, and without the goal the change cannot be read.
  • Letting the sequence end on a timer. A lead who reached the goal at the second step still receives the rest, and the report cannot tell them from a lead who never moved.
  • Treating the hand-off line as fixed. A threshold set from instinct and never calibrated keeps ready leads in nurture and sends the blame to the sequence.
  • Counting customers and open deals as entrants. They cannot progress, and they make the figure look worse than the sequence deserves.
  • Judging frequency one workflow at a time. The sequence is restrained; the inbox, with the newsletter and events added, is not.
  • Recycling a returned lead into the sequence that produced it. With no reason recorded, the loop learns nothing and the lead is returned again.
  • Skipping the holdout. The sequence takes credit for leads who would have progressed anyway, and a stall cannot be told from a quiet quarter.

Frequently asked questions

The platform reports healthy opens and clicks for the sequence. Why does that not count as progressing?

Because opens and clicks measure attention to the emails, and a nurture sequence is judged by movement of the lead. The question is whether people who entered the sequence reached the event it was built to produce, such as viewing pricing or requesting a demo, and whether they did so at a higher rate than similar leads who were held out of it. A sequence can earn good engagement from readers who were never going to buy, and poor engagement from a step that nonetheless precedes most goal events. Read click-through per step to decide which steps to edit; read progression against a holdout to decide whether the sequence works.

Should I shorten the sequence, or add more steps, when leads stall?

Neither, until the sequence has a goal event, exits that fire on it and a holdout to read it against. Length is rarely the fault. A sequence with no goal finishes on a timer however long it is; a sequence whose hand-off line sits too high keeps ready leads however few steps it has; a sequence full of customers and open deals looks like it stalls whatever you send. Fix the design, read one period of entrants against the holdout, and only then decide whether the steps that remain are too many or too few for the question the lead has at that stage.

Sales says the leads we hand over are not ready, and we say they sit in nurture too long. Who is right?

Possibly both, because they are describing two different thresholds. Leads sitting in nurture after they have viewed pricing or asked for information point at a hand-off line set too high or decaying too slowly; leads sales returns as not ready point at a score that rewards reading rather than buying, or a line that was lowered to hit a volume target. The way to settle it is the calibration the scoring guide describes: find where the leads that later closed sat on the score the week before sales accepted them, and move the line there together, with the rejection reasons from sales feeding the next review. A test that sends a band of leads just below the line to sales on purpose answers the question with evidence rather than opinion.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Digital Marketing and Measurement Model — Avinash Kaushik
  2. Direct marketing guidance — Information Commissioner's Office (UK)

Related