When a LinkedIn Conversation Goes Stale: An Aging and Recycle Policy

You run comment-led outreach. Your connection requests land warm. Conversations open. Then silence. The thread sits in your unified inbox for weeks, neither closed nor converting, and nobody on your team knows whether to follow up, pause, or write it off.

Without an aging policy, you get duplicate outreach to the same person, inflated pipeline counts, and reply rate metrics that lie. The fix is a conversation lifecycle framework that assigns every LinkedIn DM thread a status, an aging clock, and a restart trigger.

This article walks through the policy Well Met uses internally: four statuses, three aging clocks, suppression checks before any recycle, and the buyer signals that permit a dormant thread to restart.

LinkedIn conversations without aging policies create duplicate outreach and inflated metrics

CRM systems track leads across the entire customer lifecycle, from first contact through closed deal. LinkedIn threads are customer interactions, but most outreach teams treat them as disposable: no status, no owner, no aging rule.

The cost shows up in three places. First, duplicate outreach. Without a suppression check, two people on your team send the same warm connect or opening message to the same buyer. Second, reply rate inflation. If you count a thread as active for 60 days after the last reply, your denominator shrinks and your reported reply rate climbs, but the number is fiction. Third, wasted time. Your team spends hours debating whether to follow up on a thread that should have closed 30 days ago.

What defines an active, nurture, dormant, or closed conversation

Every LinkedIn thread carries one of four statuses. The status determines who owns the thread, what actions are allowed, and when the aging clock starts.

How the aging clocks work

Each status has its own aging clock. The clock starts when the thread enters that status and stops when the buyer replies or the thread moves to a new status.

Active threads age out after 14 days of silence. If you send a message and the buyer does not reply within 14 days, the thread moves to dormant. If the buyer replies on day 13, the clock resets and the thread stays active for another 14 days. The 14-day window is a service target, not a platform rule, and it aligns with the comment-led play: you have been showing up in their feed daily for two weeks, so if they are interested, they reply.

Nurture threads age out after 90 days. These are threads where the buyer said 'not now' but gave a reason: budget cycle, internal review, staffing change. You tag the thread as nurture, add them to a low-touch drip, and the aging clock starts. After 90 days with no buyer-initiated contact, the thread moves to dormant.

Dormant threads do not age out; they wait for a restart trigger. A dormant thread is not closed. It sits in a holding state until a qualifying event permits you to restart. The trigger must be a buyer signal, not your sales calendar.

When a dormant conversation can restart

A dormant thread can restart on exactly three triggers, and all three require buyer activity or verifiable change.

First trigger: the buyer engages with your content. They comment on your LinkedIn post, like your article, or reply to your company newsletter. That is a signal. You can send a direct message referencing the engagement and ask if timing has changed. The restart message must acknowledge the gap and the new signal; do not pretend the old thread never happened.

Second trigger: the buyer changes jobs. If the thread went dormant because of timing or internal process, a job change resets the context. You can send a congratulations message and reintroduce the offer in the new role. Check their new company size, industry, and budget cycle before you restart; if the new role is a bad fit, close the thread instead of recycling it.

Third trigger: your product ships a feature that directly addresses their stated objection. If the buyer said 'we need X and you do not have it,' and you build X, that is a restart trigger. The new message must cite the exact objection from the old thread and show the new capability. Generic feature announcements do not qualify.

Suppression checks before any restart

Before you restart a dormant thread or recycle a lead, run three suppression checks. These checks prevent duplicate outreach and respect explicit declines.

Check one: is the thread marked closed? Closed means explicit decline, bad fit, or bounce. If the status is closed, the buyer is on your suppression list and no restart is permitted unless they initiate contact. This rule is absolute.

Check two: is there another active or nurture thread with the same buyer? If a different rep on your team already has an open conversation with this person, you do not restart the dormant thread. One active conversation per buyer. The CRM or unified inbox should enforce this automatically.

Check three: did the buyer unsubscribe, block, or report your messages? Platform signals override your aging policy. If LinkedIn shows a delivery failure, restriction notice, or spam report tied to this contact, mark the thread closed and add the contact to your suppression list immediately.

How this policy keeps your reply rate honest

Reply rate is the percentage of opened conversations that receive at least one buyer reply. It is one of the proof units buyers care about when they evaluate outreach services, and it is easy to game if your aging policy is loose.

Here is the dishonest version: you count every thread as active for 60 days after you send the last message. Your denominator (opened conversations) stays small because threads that should be closed still show as active. Your numerator (replies) stays the same. The reported reply rate climbs, but the number is fiction.

An honest reply rate requires an honest aging clock. If you define active as 14 days of silence and move threads to dormant after that window, your denominator grows and your reply rate drops to its true level. That number is the one you optimize, and it is the one your clients trust.

Amplemarket's lead recycling research recommends segmenting re-engagement by pain point and timing, not by sales calendar. The aging policy enforces that principle: you cannot restart a dormant thread just because your quota period reset.

Who owns which thread, and when ownership transfers

Thread ownership determines who is responsible for the next action and who gets credit for a booked call. Ownership transfers when the thread status changes.

Active threads are owned by the rep or operated profile that sent the last message. If you send the opening DM after a warm connect, you own the thread until it ages out or the buyer books a call. If the buyer replies and you hand off to an AE, ownership transfers to the AE and the thread stays active.

Nurture threads move to a dedicated queue. Marketing or a nurture-focused agent owns these threads. The original rep no longer monitors them. If a nurture thread converts to a booked call after 60 days, credit goes to the nurture owner, not the original rep. This transfer must be explicit in your CRM so quota assignment is clear.

Dormant threads have no owner until a restart trigger fires. When the trigger fires, the thread moves back to active and the system assigns it to the next available rep or the agent who originally opened it, depending on your routing rules. If the original agent is no longer active, the thread goes to the general queue.

When to close a thread instead of letting it go dormant

Some threads should close immediately, not age into dormant status. Closing a thread marks the contact as ineligible for restart unless the buyer initiates.

Close on explicit decline. If the buyer says 'not interested,' 'wrong time,' or 'we chose a competitor,' close the thread. Tag the reason in your CRM so the next rep knows why it is closed. Do not restart unless the buyer reaches out or changes jobs.

Close on bad fit. If the buyer does not match your ICP (wrong company size, wrong role, wrong industry), close the thread and remove the contact from your target list. Bad fit contacts dilute your pipeline and waste aging clock cycles.

Close on bounce or delivery failure. If LinkedIn shows a message delivery failure, the email associated with the account bounces, or the profile is deleted, close the thread immediately and suppress the contact. Dormant status is for conversations that might restart; closed status is for contacts that cannot.

Close on duplicate. If you discover two active threads with the same buyer (one from your profile, one from a teammate's rented agent), close the newer thread and consolidate all activity into the older one. Mark the closed thread as duplicate so it does not count against your reply rate.

How to log restart attempts and prevent infinite recycling

A dormant thread can restart once per trigger type. If you restart on a job change and the buyer does not reply, the thread moves back to dormant and you cannot restart on the same job change again. You can restart later if a new trigger fires (they engage with your content, or you ship the missing feature), but each trigger is single-use.

Your CRM or unified inbox should log every restart attempt with the trigger type and the date. This log prevents infinite recycling: if a thread has restarted three times and aged out three times, it is a dead lead. Close it.

The policy at Well Met caps restart attempts at two per contact. After two dormant cycles, the thread closes automatically unless the buyer initiates. This cap keeps your pipeline honest and your team focused on real opportunities, not hope.

Example aging policy in action

Day 1: You send an opening DM after two weeks of daily comments. The thread status is active, the aging clock starts, and you own the thread.

Day 3: The buyer replies with a question. The aging clock resets, the thread stays active, and you still own it.

Day 10: You send a follow-up with a case study link. The buyer does not reply. The clock resets and runs for 14 days.

Day 24: No reply. The thread moves to dormant. Ownership clears. The system checks for restart triggers daily.

Day 60: The buyer comments on your LinkedIn post about a feature launch. Restart trigger fires. The thread moves back to active, the system assigns it to you, and you send a message referencing their comment and the old conversation.

Day 63: The buyer replies and books a call. The thread stays active until the call happens, then closes as converted.

Tools that enforce the aging policy automatically

Manual aging policies fail because humans forget to check the clock. The policy must live in your CRM, your unified inbox, or your outreach platform, and it must run automatically.

Salesforce and HubSpot both support custom lifecycle stages and aging workflows. You define the statuses (active, nurture, dormant, closed), set the aging clocks as time-based workflow triggers, and route threads to the right queue when the status changes. IBM's CRM overview confirms that operational CRM systems automate sales cycle tracking and customer interaction workflows, which includes conversation aging.

If you run LinkedIn outreach through a productized service like Well Met, the aging policy is built into the unified inbox. Every thread gets a status on creation, the clock runs server-side, and the system flags restart triggers when they fire. You review flagged threads weekly and approve or skip each restart.

Common mistakes teams make with conversation aging

Mistake one: treating all silence the same. A thread that aged out after one message is different from a thread that aged out after five replies and a demo. The first might restart on any buyer signal; the second needs a strong trigger like a job change or a shipped feature. Tag your threads with engagement depth so your restart logic can differentiate.

Mistake two: restarting on your sales calendar. Month-end, quarter-end, and new-year outreach spikes are sales team problems, not buyer signals. If your aging policy allows restart whenever you need pipeline, you are running cold outreach with a dormant thread label. The policy exists to prevent that.

Mistake three: not logging the decline reason. When a buyer says no, your team marks the thread closed but does not record why. Six months later, a different rep pulls the same contact into a new campaign because the CRM shows no context. Log the reason (wrong timing, chose competitor, bad fit, budget) so the next person knows whether a restart ever makes sense.

Mistake four: skipping suppression checks. You see a job change trigger and restart a dormant thread without checking whether the contact is on your suppression list. The message bounces, or worse, the buyer reports it as spam. Suppression checks run before restart attempts, every time, no exceptions.

How this policy scales across multiple agents and teams

If you run outreach from one profile, aging policy enforcement is straightforward. If you run five rented agents across two teams, the policy must prevent cross-agent duplication and enforce ownership transfers cleanly.

Your CRM must deduplicate contacts at the person level, not the thread level. If agent A has a dormant thread with a buyer and agent B pulls the same buyer into a new campaign, the system blocks the second thread and flags the conflict. One buyer, one active or nurture thread, across all agents.

When a thread transfers from active to nurture, the handoff must be explicit. The original agent stops monitoring, the nurture queue takes over, and the CRM updates ownership. If the nurture thread converts to a call, your quota rules must specify who gets credit. Ambiguity here breaks trust between reps and kills adoption of the aging policy.

Implementation summary

A conversation aging policy assigns every LinkedIn thread a status (active, nurture, dormant, closed), an aging clock, and clear restart triggers so your team knows when a thread is dead and when it can recycle.

Active threads age out after 14 days of silence; nurture threads after 90 days; dormant threads restart only on buyer signal (content engagement, job change, shipped feature that addresses their objection).

Run suppression checks before every restart: confirm the thread is not closed, no duplicate active thread exists, and the contact has not blocked or reported your messages.

Log every restart attempt with the trigger type and cap total restarts at two per contact to prevent infinite recycling of dead leads.

The policy must run automatically in your CRM or unified inbox; manual aging policies fail because humans forget to check the clock.