What is the best time to reach out to a ghost member — before or after they've been silent for 30 days?

Before. The Early ghost window — 7 to 30 days of silence — is the highest-ROI intervention window in the ghost tier framework because the causal failure is most recent, the billing relationship is newest, and the reactivation response rate (35–50%) is substantially higher than in any later tier. The operative threshold is Day 7, not Day 30. By Day 7, a new member has either activated — posted at least once in a non-introduction channel, made at least one peer connection — or they haven't. Members who have not activated by Day 7 have a dramatically lower probability of spontaneous activation in the days that follow. The slope is steep in the first week and flattens to near-zero by Day 30. Waiting until Day 30 to reach out means the response rate has already begun its decline from the Early-tier peak. The single most effective timing for a reactivation message to an Early ghost is Day 8 or Day 9 — immediately after the Day 7 scorecard would have identified them as non-activated, and while the reason they haven't engaged is almost certainly an onboarding gap rather than a genuine disengagement decision. At this point the member is likely a passive member who hasn't yet had the right prompt, not a member who has decided the community isn't for them. The message at Day 8 is not a reactivation message in the traditional sense — it doesn't need to re-sell the community's value. It needs to provide the one specific action the Day 0 DM and Day 3 nudge failed to provide clearly enough. For the Established ghost tier (31–90 days), the timing of first outreach matters less than the content: a message at Day 35 and a message at Day 80 should look different because the probable root cause has shifted from onboarding failure toward goal drift or life circumstances. The Established ghost requires a personal reference and a peer connection offer, not a reminder of what to do in the community. For Terminal ghosts (90+ days), the reactivation message is not the operative tool at any timing. The hold offer is.

Should I mention that I noticed they've been quiet, or pretend I don't know?

Do not mention the absence. This is one of the most consistent findings in reactivation message testing across paid community operators, and it runs against operators' instinct to be transparent. The reasoning for mentioning the absence is sound: it signals that the operator is paying attention and cares about the member's experience. The problem is that the signal the ghost member receives is different. A message that opens with 'I noticed you've been quiet lately' or 'I haven't seen you in the community recently' frames the interaction as an accountability check. The ghost member is already carrying some level of guilt or embarrassment about not engaging with a community they're paying for. The absence-mention leads with that guilt rather than with an offer of value, which makes the member more likely to feel called out and less likely to respond with re-engagement. The reactivation message formula in the reference card — and the one that produces the 35–50% response rate in the Early ghost tier — does not mention absence. It references a specific piece of recent community activity or conversation that is directly relevant to the member's stated joining reason, asks one direct question, and offers one peer connection. The message is written as if the operator is reaching out to share something interesting, not as if they are checking up on a truant member. The effect is that the member receives a message that gives them something of value — a specific content reference, a potential connection — rather than a mirror showing them their own non-participation. The practical test: read your reactivation message draft and ask whether a member reading it would feel welcomed back or would feel called out. If the answer is called out, remove the reference to their absence, replace it with a specific content reference, and the message will perform better.

What's a hold offer and should I offer it to every ghost who doesn't respond?

A hold offer is a 30-day billing pause offered at no cost to the member, with an explicit invitation to return when they're ready. It is not a discount and it is not a cancellation. It is a suspension of billing for one period, during which the member retains community access. The hold offer is appropriate for Established ghosts (31–90 days) who did not respond to two direct messages, and for Terminal ghosts (90+ days) who are approaching their renewal date. It is not appropriate for Early ghosts (7–30 days) who have not yet had a chance to respond to a first outreach message — offering a hold to an Early ghost treats them as a churn risk before they have demonstrated that the direct-message intervention has failed. The hold offer does two things that a reactivation message cannot. First, it removes the billing pressure that may be triggering the ghost member's cancellation review. A member who is passively paying for a community they're not using is likely to notice their billing statement at some point and initiate a cancellation review; the hold offer meets them before that review with a friction-reducing alternative to cancelling. Second, it separates life-circumstance ghosts from price-inertia subscribers. A member who accepts a hold because they are temporarily overwhelmed will often return as an active member during or after the pause — the pause acceptance rate among Established ghosts who return to active membership within 60 days is approximately 45–55%. A member who accepts a hold but cancels at the end of the pause is almost certainly a price-inertia subscriber: they were staying passive because cancelling was more friction than continuing to pay, and the hold gave them the moment to complete the decision. This is useful information that a reactivation message cannot produce on its own. You should not offer it to every ghost who doesn't respond. Offer it selectively: to Established ghosts after two failed direct messages, to Terminal ghosts approaching renewal, and never to Early ghosts before the reactivation message has had a chance to work.

How do I know when to stop trying to reactivate a ghost member?

The graduation criteria differ by ghost tier, and they are based on the number of interventions attempted, not on the duration of the ghost period alone. For Early ghosts (7–30 days): one initial reactivation message, one follow-up 14 days later if no response. If the follow-up receives no response, the Early ghost has by this point aged into the Established tier and should be moved to the Established ghost reactivation track. For Established ghosts (31–90 days): two direct messages (the personal reference + peer connection format) with a 14-day gap between them, then one hold offer presented by message. If the hold offer is declined or receives no response, move to passive monitoring. For Terminal ghosts (90+ days): one hold offer presented at or near renewal. If declined or no response, no further active outreach. The Terminal ghost who has not responded to a hold offer is approaching cancellation at next renewal with high probability; continuing to send messages at this point costs operator time and increases the probability that the member cancels specifically to stop receiving them. Passive monitoring means the member remains on your roster, receives community-wide communications (if they're opted in), and is welcomed back if they choose to re-engage — but receives no direct individual outreach. The passive monitoring state is not a write-off. Ghost members in passive monitoring occasionally reactivate without prompting, typically because a community event is directly relevant to something they're working on, or because another member mentions them in a thread and pulls them back in. When a passive-monitored ghost reactivates, treat the reactivation as a new start: welcome them back, apply the onboarding sequence you'd give a new member, and do not reference the ghost period. The member who returns deserves the same clean-slate experience as someone joining for the first time.

Member Retention & Reactivation

Published 15 August 2026 · 22 min read

Paid community member reactivation: the ghost member problem most operators mistake for retention — and why the Early ghost window (7–30 days) is your only high-ROI intervention

A community operator asked me to look at their ghost-member dashboard last quarter. Fourteen percent of their paying members had not posted a single message — not in any channel, not in any thread — in the prior 60 days. Another 11% had posted exactly once, in their introduction channel, on the day they joined. Combined, 25% of their paying members were functionally absent. The operator’s first instinct was to move these members into a low-priority segment and focus energy on the actively participating 75%. That instinct costs paid community operators more in LTV than almost any other retention error. A ghost member who is still paying is not a retained member. They are a pre-churner. The question is not whether they will cancel — it is when, and whether you reach them before the decision is made.

Ghost, churned, at-risk: why conflating these three categories produces the wrong interventions for all of them

Paid community operators monitor engagement as a proxy for retention. When engagement falls, the operator intervenes. The problem is that “engagement falls” describes three categorically different states, each requiring a different intervention, and treating all three with the same engagement tactic — more content, a personal note, a community event — produces diluted results across the board.

A churned member has cancelled. Their billing relationship is over; their workspace access has been revoked or is pending revocation. The intervention for a churned member is re-acquisition: a different message, a different offer, a different budget. Reactivation messaging does not apply to churned members. Sending a “we miss you” email to someone who cancelled three months ago is not reactivation — it is a re-acquisition attempt using reactivation language, and it performs substantially worse than messaging designed explicitly for re-acquisition.

An at-risk member is an active member showing declining engagement signals: decreasing post frequency, decreasing reply rate, decreasing attendance at events or calls. The critical distinction is that they are declining from a participating baseline. They had a relationship with the community that is weakening; the intervention is anything that reinforces the relationship they already had. Content that resonates, a peer who reaches out directly, an event that lands on a topic they care about. The at-risk intervention is lighter-touch because the member’s relationship with the community is still warm — it is cooling, but it has not gone cold.

A ghost member is still paying and has stopped participating. The billing relationship is intact. The psychological relationship has ended — or, more accurately, it never fully formed. Most ghost members in the 7–30 day window are not members who had a relationship with the community and then lost it. They are members who never fully entered the community in the first place. They joined, did not complete the onboarding actions that would have built a relationship, and settled into passive payment as the path of least resistance. The billing auto-renews. The workspace icon sits in their Slack sidebar. They open it occasionally, see that they don’t know what’s happening, and close it without posting.

The intervention for a ghost member is not the same as the intervention for an at-risk member, and it is entirely different from re-acquisition. The ghost member still has skin in the game: the billing relationship means they have made a financial commitment, and that commitment creates a psychological stake that churned members don’t have. Ghost members respond to reactivation in ways churned members don’t because they are still, technically, members — with the workspace access, the member directory listing, and the monthly charge that creates a small but real pressure to justify the spend. The reactivation message works on a ghost member because there is something to reactivate. There is nothing to reactivate in a churned member; you are starting from zero.

The operator error — the one that costs the most in preventable LTV loss — is treating ghost members like churned members and trying to re-sell the value of the community. The operative question for a ghost member is not “why should you be here?” The answer to that question is whatever their stated joining reason was; they already know why they joined. The operative question is “what is the one specific thing that would bring you back to the community today?” And the answer to that question is almost always either a specific first action they haven’t taken yet, a peer connection they haven’t made, or a reduction in the friction of staying a member while life circumstances are in the way.

The three ghost tiers: Early, Established, and Terminal — and why the Early window changes everything

The paid community member reactivation reference card classifies ghost members into three tiers based on duration of inactivity. The classification matters because the probable root cause, the reactivation response rate, and the correct intervention are different at each tier. Using the same intervention across all three tiers is the second most common reactivation error, after the ghost-vs.-churned conflation described above.

Early ghosts are members who have been silent for 7 to 30 days. This is the highest-ROI ghost tier by a significant margin. The reactivation response rate for a well-constructed personal message to an Early ghost is 35–50% — meaning that 35 to 50 out of every 100 Early ghost members who receive a direct, specific, personal message will respond. Of those who respond, approximately 60% will post in the community within the following seven days. This is not a marginal lift; it is a structural feature of the Early ghost tier that makes personal reactivation outreach one of the highest-ROI retention activities a paid community operator can do.

The reason the Early tier response rate is elevated is that the causal failure is still fresh. In the 7–30 day window, the overwhelming majority of ghost members became ghosts for one reason: an onboarding gap. They joined and did not receive a specific enough first action — or did not receive one at the right moment, or did not take the one they were given — and the community settled into the background before a relationship could form. This is a recoverable state. The member joined recently, their payment is recent, their stated joining reason is still current, and the failure point (the onboarding gap) is one that a single well-timed message can close. The Early ghost is not a member who has decided the community isn’t worth it. They are a member who hasn’t had the opportunity to find out whether it is.

Established ghosts are members who have been silent for 31 to 90 days. The response rate drops to 18–28%: still meaningful enough to justify the effort, but substantially lower than the Early tier. The probable root cause has also shifted. An Established ghost has been through at least one or two billing cycles. The initial joining energy has long since dissipated. The root cause is less likely to be a pure onboarding gap and more likely to involve goal drift (the member’s reason for joining has changed), a programming void (the community’s content calendar doesn’t serve their goal), or life circumstances that have made community participation a low priority. The intervention for an Established ghost is different: a personal reference to something specific in the community, a direct question about their current focus, and a peer connection offer. The Established ghost needs a reason to re-enter that is specific to them, not a reminder of what the community is.

Terminal ghosts are members who have been silent for 90 or more days. The response rate to a direct reactivation message drops to 8–14%. This is below the threshold at which personal outreach is an efficient use of operator time for most community sizes. The member has been absent for three months or more; their relationship with the community — to the extent one formed — has been inactive long enough that re-engagement requires a significant triggering event, not a well-worded message. The operative tool for Terminal ghosts is the hold offer, not a reactivation message. The hold offer (a 30-day billing pause) is a low-friction alternative to cancellation that preserves the billing relationship and extends the decision window. The reactivation comes later, or it doesn’t come — but the hold offer keeps the door open without requiring the operator to run a high-effort outreach campaign against a population with a sub-15% response rate.

The threshold structure matters for prioritization. Most paid community operators who track ghost members at all apply roughly equal effort across the ghost population: a batch message to all ghosts, or a monthly check-in cadence applied uniformly. The tier framework replaces uniform effort with prioritized effort. Early ghosts get high-touch personal outreach because the response rate justifies it. Established ghosts get medium-touch personal outreach with the hold offer available as a follow-up. Terminal ghosts get the hold offer. This allocation produces a better reactivation outcome per hour of operator time than any uniform approach.

The five root causes of ghosting — and which ones the operator can actually fix

Not all ghost members became ghosts for the same reason, and not all root causes are operator-fixable. The reactivation message that works for an onboarding-failure ghost will not work for a goal-drift ghost, and the hold offer that is appropriate for a life-circumstances ghost is actively wrong for a price-inertia subscriber. Diagnosing the probable root cause before choosing an intervention is the third determinant of reactivation success, after tier classification and timing.

The first root cause is onboarding failure. The member joined, did not receive a clear enough first action, and drifted into passivity before making their first post or peer connection. This is the dominant root cause in the Early ghost tier, accounting for approximately 50–60% of 7–30 day ghosts in communities that do not have a automated conditional Day 3 nudge. Onboarding failure is fully operator-fixable: the fix is a specific reactivation message that names the first action the onboarding sequence failed to deliver, paired with an offer to facilitate it. The response rate to a well-constructed onboarding-failure message for an Early ghost is the highest of any ghost type: 40–55%. The paid community onboarding metrics reference card documents the relationship between Day 3 nudge conditionality and Early ghost formation rates in detail; communities with an automated conditional Day 3 nudge for non-posting members produce 30–40% fewer Early ghosts per cohort.

The second root cause is a programming void. The member joined with a specific goal — connection with peers at a similar stage, access to a specific type of expertise, learning frameworks for a specific problem — and the community’s content calendar, events, and discussion patterns do not serve that goal. The member may have activated initially — posted an introduction, attended one call — and then gone quiet when the subsequent programming failed to match their reason for joining. Programming void is the most common root cause in Established ghosts who had some initial activation: they tried the community, didn’t find what they were looking for, and drifted out. This is operator-fixable at a community level (restructuring programming toward underserved goal tracks) and partially fixable at an individual level: a reactivation message that references programming that is directly relevant to the member’s stated goal, or that offers to connect them with the members who are working on the same problem, can recover programming-void ghosts at an Established-tier response rate of 20–28%. The paid community engagement benchmarks reference card covers the relationship between goal-track distribution and ghost formation rates by programming type.

The third root cause is goal drift. The member joined for a reason that is no longer current. They achieved the goal (closed the funding round, hired the team, launched the product), or the goal became irrelevant (the business pivoted, the role changed, the priority shifted). Goal drift is not operator-fixable in the traditional sense: you cannot change the fact that the member’s original joining reason no longer applies. The operator-available intervention is to identify whether the community offers something else of value to the member at their current stage, and to re-anchor the member’s relationship with the community around that new value. This requires a diagnostic conversation, not a reactivation message: a direct question about what the member is working on now, followed by a community offer that is genuinely relevant to the current answer. Response rates for goal-drift ghosts are lower (15–22%) because the intervention requires the member to re-evaluate their relationship with the community rather than simply take a first action they hadn’t taken yet.

The fourth root cause is life circumstances. The member joined during a period of relative availability and then encountered a change that reduced their bandwidth for community participation: a job change, a new child, a health event, a business crisis. Life circumstances are not operator-fixable. The member’s non-participation is not a statement about the community’s value; it is a statement about the member’s current capacity. The correct intervention is the hold offer, not a reactivation message: a 30-day billing pause that acknowledges the member’s circumstances without requiring them to defend their non-participation, and that reduces the friction of staying a member until their capacity returns. Life-circumstance ghosts who receive a hold offer and accept it have a 40–50% probability of returning to active membership within 60 days of the pause ending — substantially higher than the reactivation rate for the same tier without a hold.

The fifth root cause is the price-inertia subscriber. The member joined, never engaged meaningfully, and has continued paying because the monthly cost is below the threshold of attention and cancellation is marginally more friction than continuing to pay. This is the most common root cause in Terminal ghosts (90+ days of silence), and it is the least recoverable. Price-inertia subscribers are not a community-engagement problem; they are a billing-friction artifact. The reactivation message produces a low response rate (sub-10%) because the member has already made an implicit decision not to engage; they simply haven’t formalized it as a cancellation. The hold offer is useful here as a diagnostic tool: a price-inertia subscriber who receives a hold offer will typically accept the pause and cancel at its conclusion. This is the correct outcome — the hold offer converts an implicit decision into an explicit one, clears the ghost from the roster, and produces clean churn data. An operator who offers a hold to their Terminal ghost population will find that 30–40% of Terminal ghost hold-accepters cancel at the end of the pause; these are almost certainly price-inertia subscribers whose implicit decision became explicit when given a low-friction path.

The reactivation message formula: no mention of absence, one content reference, one question, one peer connection offer

The reactivation message is a single Slack DM or email, depending on how active the member is in the workspace. For Early and Established ghosts, a Slack DM is preferred if the operator has reason to believe the member opens the workspace occasionally; email is appropriate if the member has not opened the workspace in the past two weeks. The message follows four structural rules.

The first rule is no mention of absence. The most common reactivation message mistake is opening with a reference to the member’s non-participation: “I noticed you’ve been quiet lately,” “I haven’t seen you around in the community,” or “just wanted to check in since you haven’t posted in a while.” The intuition behind these openers is sound: the operator wants to signal that they notice the member’s absence and care about their experience. The problem is the signal the ghost member receives. A paying member who has not engaged with a community they’re paying for is already carrying some level of ambient guilt or embarrassment about the gap between what they’re paying and what they’re getting. A message that leads with the absence holds a mirror up to that guilt rather than offering an alternative to it. The ghost member who receives an absence-mention message is more likely to feel called out than welcomed back. The response rate to absence-mention reactivation messages is 12–18% — compared to 35–50% for messages that do not mention absence. The entire first-rule difference is in how the ghost member receives the opening frame.

The second rule is one specific content reference. The message should reference something specific that happened in the community recently — a conversation, a call, a piece of member content — that is directly relevant to the member’s stated joining reason or to the goal they mentioned in their Day 0 DM response. The specific reference does two things: it signals that the operator knows who the member is and what they joined for (not a batch message), and it provides the ghost member with an immediate reason to re-enter the community that is anchored in specific community content rather than an abstract promise of value. “We had a conversation in #ask-the-community last week about [specific topic] that I thought about when I saw your name on the roster” is specific and personal. “We’ve had a lot of great conversations in the community lately” is generic and produces a generic response rate. The specific content reference takes 5–10 minutes of research per message; it is the highest-leverage minute of the reactivation process.

The third rule is one direct question. The message should close with a single, direct, narrow question that requires minimal effort to answer. Not “is there anything I can do to help?” — which requires the ghost member to generate options — but a specific yes/no or short-answer question: “Are you still focused on [their stated goal], or has your direction shifted since you joined?” or “Have you had a chance to check out [specific resource or channel] yet?” The narrow question reduces the activation energy required to respond. A ghost member who has not been in the community for 30 days faces a re-entry cost: they have to remember why they joined, assess what’s changed, decide whether re-engagement is worth the attention. A message that asks one narrow question reduces the re-entry cost to the minimum: they only need to answer one thing. The response opens the conversation; the conversation handles the rest.

The fourth rule is one peer connection offer. For Established ghosts especially, the peer connection offer is the highest-leverage element of the message — more effective than the content reference alone, and substantially more effective than any content push. The offer is simple: “I’d like to connect you with [specific member name] who is working on [the same thing the ghost member joined for] — would you be open to a 20-minute intro?” The peer connection offer converts the community from an abstract membership to a specific relationship. Members cancel memberships. They do not cancel relationships. A ghost member who has a peer connection pending — a real introduction to a real person who shares their specific situation — has a concrete reason to re-enter the community that no amount of content or nudge can replicate. The reactivation rate for Established ghosts who receive a peer connection offer and accept is 55–65%, compared to 18–28% for the standard message without a peer offer. The bottleneck is identifying the right peer: this requires knowing which active members are working on topics similar to the ghost member’s joining reason. Communities using member segmentation data for routing, as described in the paid community member health score reference card, can operationalize the peer connection offer at scale; smaller communities do this manually using the operator’s knowledge of the active member roster.

The no-ghosting protocol for the reactivation sequence is: send the initial message, wait 14 days. If no response, send one follow-up with a different specific content reference and the peer connection offer repeated. If the follow-up receives no response, move to the hold offer for Established and Terminal ghosts, or reclassify the Early ghost as Established and move them to the Established track. Beyond two messages plus a hold offer, additional direct outreach has a diminishing return that crosses into counterproductive: a ghost member receiving a fourth or fifth message from an operator is more likely to cancel specifically to end the outreach than to re-engage with the community.

The hold offer: what it is, when it applies, and what it actually buys you

A hold offer is a 30-day billing pause offered at no cost to the member. The member retains community access during the pause period. At the end of the pause, billing resumes automatically unless the member cancels. The hold offer is not a discount, not a downgrade, and not a cancellation. It is a friction-reduction tool that extends the decision window for a ghost member who is approaching the point at which the implicit decision to leave becomes an explicit cancellation.

The hold offer is appropriate for two ghost populations. The first is Established ghosts (31–90 days of silence) who have not responded to two direct messages. These members have demonstrated that the direct-message reactivation track has not worked; they either have not seen the messages, or have seen them and chosen not to respond. The hold offer gives them a path to stay that does not require re-engagement as a precondition. The second population is Terminal ghosts (90+ days) who are approaching their renewal date. For Terminal ghosts, the hold offer timing is critical: it is most effective when presented 10–14 days before the renewal charge, giving the member time to consider the option before the billing event triggers a cancellation review. A Terminal ghost who receives a hold offer immediately before billing is more likely to cancel the billing and not take the pause; a Terminal ghost who receives the offer 10 days before has time to evaluate it as an alternative.

The hold offer does two things that the reactivation message cannot. The first is cancellation deferral. An Established ghost who accepts a hold offer has a 40–50% probability of returning to active membership within 60 days of the pause. A Terminal ghost who accepts a hold offer has a 15–25% probability of return within 60 days. Both rates are higher than the direct-reactivation rates for the same tiers, which suggests the hold offer itself is producing reactivation work by removing the billing pressure that may have been accelerating the member toward a cancellation decision. A member who is not being billed is not being reminded each month that they are paying for something they are not using. The absence of that reminder extends the window in which circumstances might change and the member might re-engage.

The second thing the hold offer does is classification. A price-inertia subscriber — a member who is passive because cancellation friction exceeds the monthly cost, not because of life circumstances or a recoverable engagement gap — will typically accept a hold offer and cancel at the end of the pause. This is not a reactivation failure; it is a diagnostic outcome. The hold offer converts the price-inertia subscriber’s implicit exit decision into an explicit cancellation, which produces clean churn data and clears the ghost from the active member roster. An operator who has been carrying a price-inertia subscriber as an “engaged” (billing) member for six months without actual engagement is not retaining that member; they are deferring a cancellation that was inevitable. The hold offer accelerates the resolution and gives the operator correct data about the community’s actual retention rate.

The expected acceptance rate for the hold offer is 45–60% for Established ghosts and 55–65% for Terminal ghosts offered the hold at or near renewal. The higher acceptance rate for Terminal ghosts reflects the proximity of the renewal event: a member who is about to be charged for another month of a community they’re not using will find the pause option more compelling than a member who has just been charged. The hold offer should be presented as an offer, not a diagnostic: “I know life gets busy — I wanted to make sure you have the option to pause your membership for 30 days if you need it, no questions asked. You can come back whenever you’re ready. Want me to set that up?” The framing acknowledges that the member’s non-participation may have a cause that is unrelated to the community’s value, and that the operator is not treating non-participation as a failure that requires explanation. This framing is what separates the hold offer from a cancellation path: it presents staying as the easier option, with a temporary reduction in cost.

The win-back email sequence for members who cancel despite the hold offer is a separate track, documented in the paid community win-back email sequence reference card. Win-back is re-acquisition, not reactivation; it applies after a cancellation, not before. The distinction between the two tracks — hold offer before cancellation, win-back after — is the boundary between retention and re-acquisition, and maintaining it as a real operational boundary prevents the operator from spending re-acquisition budget on members who are still paying and retaining budget on members who have already left.

Prevention versus reactivation ROI: why fixing the onboarding is cheaper than running the reactivation cadence

The prevention and reactivation decisions are not mutually exclusive — both are necessary in a functioning paid community — but they have very different cost structures, and operators who run only a reactivation cadence without addressing the upstream prevention failures are running a higher-cost retention program than they need to.

The prevention cost is one-time infrastructure investment. Upgrading a Day 0 DM to include specific channel direction (naming two channels for the member’s goal track rather than directing them to “explore”) takes 20–30 minutes of operator writing time, once, for a template that applies to every future member. Adding a conditional Day 3 nudge for non-posting members — a message that fires only if the member has not posted in any non-introduction channel by Day 3 — takes 30–45 minutes of setup time, once, for automation that runs on every cohort without additional operator time. Adding a Day 7 health scorecard review takes 2–3 hours of initial setup plus 15–20 minutes per week for a community of 200 members. Total prevention investment: approximately 4–5 hours one-time, plus 15–20 minutes per week for the ongoing review. The paid community churn prevention reference card documents the specific impact of the three-touch sequence on Early ghost formation: communities with a conditional Day 3 nudge produce 30–40% fewer Early ghosts per cohort than communities with a fixed Day 0 DM and no conditional follow-up.

The reactivation cost is recurring manual work. One personal reactivation message, researched and written for a specific member with a specific content reference, takes 10–15 minutes. Two messages per ghost member (per the no-ghosting protocol) is 20–30 minutes per ghost. A hold offer message takes 5–8 minutes. For a community with 40 ghost members across all tiers (20% of 200 members, which is a representative ghost rate for a community without strong Early intervention), a complete reactivation cycle across all active tiers takes 12–18 hours per month. This is recurring: next month, the new-joining cohort will produce its share of Early ghosts, and the previous month’s Early ghosts who did not respond will age into the Established tier. The reactivation cadence does not end; it runs alongside the community indefinitely.

The correct frame is not “prevention OR reactivation” — it is “prevention reduces the volume of the reactivation work.” Prevention specifically reduces onboarding-failure ghosts (the dominant cause in the Early tier) and, to a lesser extent, programming-void ghosts among members whose goal track the operator’s content calendar was not serving. Goal-drift, life-circumstance, and price-inertia ghosts will be produced by any community regardless of onboarding quality; they require the reactivation and hold-offer tracks. But a community that converts 40% fewer Early ghosts per cohort through upstream prevention is running a reactivation cadence against a population that is 40% smaller than it would otherwise be — which translates directly into 40% less recurring reactivation work for the same community size and the same LTV protection.

The sequence priority is: fix prevention first (it is cheaper, it compounds, and it produces a permanent reduction in the ghost formation rate for every future cohort), then run the reactivation cadence for the ghosts that prevention cannot reach. An operator who runs the reactivation cadence without addressing prevention is doing the right work in the wrong order: they are cleaning up a production problem rather than fixing the line. The paid community offboarding reference card covers the terminal end of this continuum — what to do when a member has decided to leave regardless of reactivation or hold intervention — and the framework for using exit data to identify which prevention investments would have the highest impact on the next cohort.

When to stop: graduation criteria by tier and what passive monitoring means in practice

The reactivation cadence has a stopping point for each tier, and knowing when to stop is as important as knowing when to start. Continuing to send reactivation messages past the graduation threshold wastes operator time, produces diminishing returns below any meaningful level, and — at the extreme — triggers cancellations from members who are staying passive specifically to avoid dealing with the outreach.

For Early ghosts (7–30 days): the graduation threshold is two messages. One initial reactivation message (following the formula: no absence mention, specific content reference, one question, one peer offer), one follow-up 14 days later if no response. If the follow-up receives no response, the Early ghost has by this point aged past the Early tier boundary. They should be reclassified as Established and moved to the Established track, which begins with a different message style: more personal, more direct, with the peer connection offer moved to the primary position rather than the closing offer. The Early-to-Established reclassification is not a failure; it is a recognition that the probable root cause has shifted from pure onboarding failure toward something more complex, and the intervention should shift accordingly.

For Established ghosts (31–90 days): the graduation threshold is two direct messages plus one hold offer. The two direct messages (personal reference + peer connection, 14-day gap between them) address the recoverable causes: programming void, goal drift that is still recoverable, life circumstances that are temporary. If neither message produces a response, the hold offer is presented once. If the hold offer is accepted, the member moves to the hold track; the operator’s next action is to welcome the member back when they return, not to send additional reactivation messages during the pause. If the hold offer is declined or receives no response within 7 days, the member moves to passive monitoring. Total Established ghost outreach before graduation: 3 messages over approximately 5–6 weeks.

For Terminal ghosts (90+ days): the graduation threshold is one hold offer, presented once near renewal. If the hold offer is accepted, the member enters the hold track. If declined or no response, the member moves to passive monitoring immediately. Terminal ghosts who have not responded to a hold offer are not reachable through direct outreach at any reasonable cost-per-response ratio. No additional individual messages should be sent. The Terminal ghost track from initial classification to passive monitoring is one message: the hold offer.

Passive monitoring is a defined operational state, not an informal neglect of the member. In passive monitoring, the ghost member remains on the community roster, receives any community-wide communications they are opted in to (announcements, newsletters, event invitations), and is not the subject of individual direct outreach. The operator checks the passive-monitoring roster once per month for two signals. The first signal is spontaneous re-activation: the member posts in a channel, attends a call, or responds to a community-wide communication without prompting. When this happens, the operator treats it as a new activation — they apply the same welcome-back response they would give to any returning member, without reference to the ghost period. “Great to see you in [channel] — welcome back. [Peer name] is working on something similar if you want an intro.” The ghost period is not mentioned; the member’s return is treated as a clean restart. The second signal is an approaching renewal date. A passive-monitoring member approaching renewal who has not been active is, at that point, either going to cancel at renewal or continue paying. The operator does not send a reactivation message at this point; the hold offer has already been presented and either accepted or declined. What the operator does is note the renewal in their log: if the member renews without reactivating, they remain in passive monitoring. If the member cancels at renewal, they exit the community cleanly.

The graduation criteria feel counterintuitive to operators who have built their community management practice around personal, high-touch relationships. Stopping active outreach after three messages feels like giving up. The reframe is: you are not giving up on the member. You are right-sizing the operator attention spent on a member who has demonstrated through non-response that they are not in a re-engageable state at this time. The same attention applied to Early ghosts — who are in a re-engageable state and have a 35–50% response rate — produces a substantially larger retention outcome per hour. The graduation criteria are a resource allocation framework, not an abandonment framework.

The general principle: the reactivation window closes whether you act or not

The ghost member problem is underestimated because engagement metrics do not distinguish between the three states — ghost, at-risk, churned — that produce them. An operator whose monthly active rate drops from 72% to 64% sees an 8-point engagement decline. Whether that decline came from 12 active members becoming at-risk, or from 16 new members failing to activate and entering the Early ghost tier, or from a mix of both, is not visible in the monthly active rate alone. The diagnostic requires per-member categorization, not aggregate monitoring.

The Early ghost window closes at Day 30 whether the operator has reached out or not. A member who is an Early ghost on Day 15 will be an Established ghost on Day 31, with a lower response rate, a different probable root cause, and a different intervention required. The window is not paused by operator inaction; it is only acted on or missed. This is why the three-touch onboarding sequence — Day 0 DM, Day 3 conditional nudge, Day 7 scorecard review — is designed to identify non-activating members at Day 7, before the Early ghost window has moved toward its lower-response-rate middle. A Day 7 review that surfaces the non-posting members in the cohort gives the operator three weeks of the Early ghost window to work with. A monthly active rate review gives the operator a population of ghosts with no window information: some are Early, some are Established, some may be approaching Terminal, and the operator cannot distinguish them without per-member history.

The systems that make reactivation tractable — per-member activation tracking, ghost tier classification, conditioned Day 3 nudges, Day 7 health scorecard reviews — are not features that operators build because they have sophisticated retention programs. They are features that become necessary at a certain community size when the operator realizes that manual tracking is producing a systematic blind spot: Early ghosts are aging into Established ghosts before the operator knows they exist. The paid community onboarding health check surfaces the Day 7 review question — what percentage of your most recent cohort posted at least once in a non-introduction channel within seven days? — alongside the four other questions that predict Early ghost formation rate. A five-minute diagnostic is often the fastest path to identifying which of the five root causes is dominant in a specific community and which prevention investment would produce the largest reduction in the recurring reactivation workload.

Foothold automates the three-touch sequence and generates the Day 7 health scorecard as a weekly operator summary: who activated, who stalled, who to personally follow up with — tiered by ghost classification so the operator’s outreach effort goes to the Early ghosts first, every week, without manual tracking. The reactivation window still closes whether you act or not. Foothold’s job is to make sure you know it’s open before it closes.