Dormant lead alerts: bringing forgotten opportunities back

It is 9:40 on a Tuesday morning. A sales rep opens her lead list; at the top sits a request that came in three days ago. She calls it, sends the quote, moves on. Far down the same list is a name that asked for pricing back in March. That record has not moved in seven weeks: no call, no message, not one note added to it. Nobody lost it and nobody closed it — it simply became invisible. This piece is about the mechanism that turns that invisibility into an event somebody has to answer.

We start by defining when inactivity actually counts as silence. Then we separate a dormant lead from a closed-lost deal, pick thresholds, walk through the first half hour after an alert fires, and build a re-engagement message that gets replies. After that: which records are not worth waking, who the alert should reach, what the setup involves, and the numbers that tell you whether it is working.

When exactly does a lead count as dormant?

A dormant lead is not simply an old lead. The measure is not the creation date but the time elapsed since the last meaningful touch — and a meaningful touch goes both ways: a call that connected, a quote that got a response, a reply to a message, a note written after a conversation. A newsletter open or an automated reminder going out does not qualify. Otherwise hundreds of records you have not spoken to in months look alive on paper.

The first job, then, is to anchor inactivity to one source of truth. Without a working lead tracking setup that keeps every touch on the record in a single stream, dormancy cannot be defined at all, because nothing can answer "when did we last actually talk to this person?" In Rocketly that stream is the Activity Timeline: calls, messages, notes and status changes sit in one sequence, and the inactivity clock runs from the most recent of them.

The second distinction is the record's own rhythm. Three weeks of silence is unremarkable for an enterprise buyer who purchases once a year; the same three weeks on a lead that asked for a demo two days ago is an alarm. One number applied uniformly to the whole list produces noise: alerts fire too often, the team stops opening them, and the system cancels itself within a month.

Is a dormant lead the same as a closed-lost deal?

No, and conflating the two corrupts your reporting. A closed-lost deal is a decision: somebody said it was not happening, wrote down why, and took the record out of the process. A dormant lead is a record where no decision was ever made — technically open, sitting in a pipeline stage, still feeding the forecast, and worked by nobody. One is a closed file; the other is an unattended one.

The practical consequence is an inflated pipeline and a forecast that drifts every quarter. The late-stage version of the same problem is usually discussed as deal rot, where a proposal went out, the stage advanced, and then the process stalled. A dormant lead is the early chapter of that story, and intervening there is cheaper and far more likely to work.

A third category deserves its own name: the record you never reached at all. It is not dormant, it never woke up. Putting it in the same queue produces the wrong action, because the problem is reach rather than memory.

Why do reminders fail where alerts work?

A reminder is something a person sets. By definition, the rep who let a lead go dormant had already forgotten it — so the reminder was never set either. An alert works the other way round: it comes from the state of the record, and when the inactivity window crosses a threshold, the notification fires whether anyone remembered or not.

In the product this maps to a specific behavior. The Dormant Lead Alert notifies the assigned rep automatically for records with no activity at 14, 30 and 60 days, moving "who was supposed to look at this?" out of somebody's memory and onto the record's own timestamp. Score Change Alerts run the mirror image: the team is notified when a score crosses 80, crosses 50, or jumps 15 points at once. One catches silence, the other catches sudden interest.

Reading both signals together is where the value sits. If a long-quiet record suddenly gains points — say the pricing page got visited again — it should not be waiting in the middle of a generic follow-up list. Combine lead scoring with inactivity data and "who do I call first" collapses into one ordered queue.

What do the 14, 30 and 60-day thresholds catch?

Each threshold points at a different failure and asks for a different action. Fourteen days is usually where a follow-up sequence broke: there was a conversation, there was interest, and then something got in the way. Thirty days is where the record fell off the agenda and the context went cold. Sixty days is a decision point in practice: either requalify the record or write down a reason and close it.

Inactivity	What it usually means	Expected action
14 days	The follow-up sequence broke; interest is probably still there	A short check-in on the same channel
30 days	Off the agenda, context has gone cold	A call built on a new reason; review source and campaign
60 days	Still on the list but effectively outside the process	Requalify with discovery questions, or close with a reason
Never answered	First contact never happened; the clock never really started	Separate queue, different channel and different time of day

None of these numbers are sacred. A long sales cycle fits 30-60-90; a team that closes business the same week is better served by 3-7-14. What does not change is the principle: every threshold gets exactly one expected action. An alert with no defined action becomes a notification everyone dismisses within two weeks.

What happens in the first half hour after an alert fires?

The alert is a trigger, not a task; the real work is making a decision quickly. Open the record, read the timeline backwards, and find what was discussed last and who owed whom something. In most dormant records the answer is right there — a document was promised, a price was asked for, the contact went on leave, or a third party never approved.

The second step is asking whether the record still qualifies. What do you actually know about budget, the decision process, the size of the need, and timing? A framework like MEDDIC works as a short checklist here: whichever dimension is missing becomes the purpose of the call. A call whose only purpose is "checking in" tends to end in a second silence.

The third step is choosing a channel. Trying the same channel a third time after two unanswered attempts is wasted effort. The Score Breakdown screen lists each factor's contribution to the score one by one — email, phone, location, budget — so you can see what contact data you genuinely hold, and the Next Best Action suggestion on the same record points at the concrete step: call, send a quote, book a meeting, or hand the lead to a senior rep.

How do you write a re-engagement message that gets answered?

The most common mistake is framing the silence as the buyer's fault. A note that opens with "I have not heard back from you" pushes the conversation into a defensive posture. The structure that works has four parts: restate the context in one sentence, name something concrete that has changed since then, ask exactly one question, and leave a graceful exit.

The thing that changed has to be real: a capability that shipped, a setup you built for a similar company, or a condition that may have shifted on their side. This is the logic behind customer win-back campaigns — you cannot resume an old conversation without producing a new reason for it, and without one the message reads as another follow-up nudge.

The exit matters as much as the question. A line like "if this is off the table for now, just say the word and I will update our list" lifts reply rates, because it hands the other side a cheap way to answer. The same psychology shows up in abandoned cart automation: what recovers the sale is not pressure but an easy way to continue.

Which dormant records are not worth waking?

Not every dormant record is an opportunity, and chasing all of them destroys the credibility of the alert system. Closing is the right call in four situations: the contact details are invalid, the contact is not the decision maker and there is no path to the person who is, the need has clearly disappeared, or the record has already said no twice in plain terms.

Closing is not a loss; it produces data. Reasons like "no budget", "went with another vendor" or "project postponed" tell you which segments are worth revisiting next quarter. In Rocketly a deleted record drops into the Trash and stays restorable with its full activity history for a default of 30 days, so a bad bulk decision is reversible.

Some closed records deserve another look later. A tag such as "revisit at budget season" plus a segment built on it takes a record off the agenda without throwing it away. With the dynamic list switch on in the Segment Dashboard, membership maintains itself: when a record is created or updated the criteria are evaluated again, matches enter and non-matches drop out.

Who receives the alert, and what if nobody acts on it?

The alert goes to the assigned rep, which makes assignment discipline a precondition rather than a detail. A notification raised on an unowned record belongs to nobody and dies quietly. This is where lead assignment rules earn their keep: round-robin distribution, rule priority and a per-person capacity limit establish up front who is answerable for which record.

The second failure mode is a rep who owns the record but has no room for it. If someone carries more open leads than they can work, their dormant count rises in proportion; that is capacity, not attention. The Workload Distribution view shows how many open leads sit with each rep, so you find the source of the pile-up in the distribution rather than in a person.

The third is handover. When a rep leaves and their list is not reassigned, the whole list turns dormant within weeks. Bulk Actions change the owner on hundreds of records in one pass, and a saved view for "unowned and past 14 days" puts that list one click away every week.

What does setting this up involve?

The setup is small enough to finish in a week; the difficulty is in the decisions, not the configuration.

• Write down what a meaningful touch is: which events reset the inactivity clock and which do not.
• Pick thresholds and tie exactly one expected action to each of them.
• Move never-answered records into a separate queue; they are a different problem.
• Make ownership explicit through assignment rules so no alert lands on an unowned record.
• Prepare two or three variants of the re-engagement message and measure which one gets replies.
• Reduce close reasons to a short fixed list instead of free text.
• Put the size of the alert queue on a weekly meeting agenda so it stays visible.

Slowing the growth of that queue is a matter of raising quality at the entrance. A form abandonment recovery flow stops half-finished submissions from flowing straight into the dormant pool, keeping the alert queue reserved for records somebody actually spoke to.

Which numbers show that it works?

Four measures are enough. First, the dormant ratio: what share of open records has crossed a threshold? A ratio that falls over consecutive weeks is the clearest sign the system works. Second, the re-engagement reply rate: of the records you contacted after an alert, how many answered? Third, decision speed: how many days before an alerted record becomes either active again or closed? Fourth, closed revenue traced back to revived records.

Response time belongs in the same picture. The Response Time Dashboard grades time-to-first-response into tiers — instant up to 15 minutes, fast up to an hour, normal up to four hours, slow beyond 24 — and keeps never-answered records in their own group. A rising dormant count usually shows up here first.

These measures pair naturally with the cost side. Revenue recovered per hour spent on re-engagement is one of the most concrete lines available when you calculate CRM ROI, because it requires no additional ad spend; the list is already yours.

Compared with retargeting a visitor who left your site, the difference is plain: there you buy the attention back, here you already hold permission to contact and a full conversation history.

If you want to test the thresholds against your own list, you can start a free account and set them up on the records you already have.

FAQ

How many days should the dormancy threshold be?

It depends on your sales cycle. A practical starting point is a first threshold at roughly one tenth of your average time to close, then two more at double and quadruple that. For many teams 14, 30 and 60 days is a reasonable place to begin.

Do I have to call every record that triggers an alert?

No. An alert asks for a decision, not necessarily a call. One valid decision is closing the record with a reason, and a clean queue depends on making that call consistently.

Could I just send dormant leads a bulk email?

Bulk sending gives you scale but loses context, and reply rates stay low. The best results come from a split: personal outreach for high-scoring records, a campaign for the low-scoring tail.

Should I delete records after a while?

Closing beats deleting almost every time, because a closed record carries reason data that is useful in later segment analysis. If you do delete, a recycle bin that holds records for a period makes wrong deletions reversible.