Reference card — paid community operations

Paid community member reactivation

Q: What should the first personal DM to a ghost member say, and how long should you wait before sending it?

The first personal DM to a ghost member should contain four elements: a specific reference to something from the member’s history in the community (a post they made, a question they asked, a goal they stated at join), an honest observation about their recent absence without pressure or accusation, one specific reason to return right now (a relevant conversation that is currently active, an event happening this week, or a resource that just appeared in the community that matches their stated goal), and a genuinely optional close (“let me know if you want me to send you anything specific, or if you’re just in a busy stretch and plan to return”). The message must not contain a hold offer, a discount, or any suggestion that they are at risk of losing access, because a reactivation DM that implies financial consequence reads as a retention pitch rather than a community outreach, and the member who receives it is more likely to cancel preemptively than to re-engage. For an Early ghost (7–30 days silent): send the first DM when the member crosses 10–14 days of silence, which is far enough into the ghosting pattern to indicate the absence is not just a busy week, but close enough to the last active period that the specific reference feels fresh rather than reaching back to an old memory. For an Established ghost (31–90 days silent): send on day 35–40, after confirming the member is still paying. The DM at this stage should reference something more recent in the community rather than a historical post, because a 40-day gap feels less personal if the reference point is two months old. The no-response protocol is described in Table 3: one personal DM is the full active intervention for an Early ghost; an Established ghost gets a second touch after 14 days if the first produced no response.

Q: What re-activation offer should you make to a member who has been silent for 60 or more days?

An Established ghost who has been silent for 60 or more days is approaching the terminal ghost boundary, and the offer framework changes significantly from the Early ghost outreach. The correct offer at the 60–90 day mark is a hold offer (a one-time pause on billing) rather than a discount or an urgent return invitation. The hold offer works for three reasons specific to this tenure window. First, a member at 60–90 days of silence is likely not ghosting because the community lacks value; they are ghosting because a life or work circumstance displaced their community habit, and the displacement has now lasted long enough that returning feels like restarting rather than resuming. A pause removes the cost of the displacement period without requiring the member to decide whether the community is still worth paying for. Second, a hold offer signals that the operator understands the absence is circumstantial rather than intentional, which produces more goodwill than a discount that the member reads as a sign the community is financially stressed or the operator is panicked. Third, an accepted hold offer produces a defined return-activation date, which gives the operator a structured opportunity to send a welcome-back sequence when the pause ends, rather than hoping the member returns organically after receiving a discount. The offer structure: offer 30 days of pause, clearly stating that billing resumes automatically after the pause period and that the member can cancel before the pause ends if they prefer. Do not make the offer contingent on the member re-engaging during the pause — the pause is an expression of goodwill, not a conditional incentive. See Table 5 for the full offer decision table across Early, Established, and Terminal ghost tiers.

How to identify, classify, and re-engage ghost members in a paid Slack community: three ghost tiers (Early 7–30 days / Established 31–90 days / Terminal 90+ days) with renewal rate benchmarks and expected reactivation rates; five root causes of member ghosting with behavioral signatures and operator-fixable classification; the reactivation sequence structure for each tier including timing, channel, message format, and the no-response protocol at each step; response rate benchmarks by community size and price tier for three outreach channels; an offer decision table for when to use a hold offer versus a peer connection versus no offer; a priority matrix for allocating reactivation effort versus churn prevention and acquisition; and per-tier graduation criteria for moving a non-responsive member from active outreach to the win-back sequence. Companion to the member health score reference card (which defines the health tier framework that classifies ghost members) and the win-back email sequence reference card (the post-cancellation sequence that follows failed reactivation).

TL;DR

Ghost members — paying members who have gone quiet in the Slack workspace — are not a single problem. An Early ghost (7–30 days silent) has a 35–55% reactivation rate with a single personal DM sent at day 10–14; an Established ghost (31–90 days) has a 15–28% reactivation rate with two personal DMs and an event invitation; a Terminal ghost (90+ days) has a 4–9% reactivation rate with a single reactivation touch before moving to the win-back queue. These rates are not fixed: they depend on the root cause of the ghosting (onboarding failure is the hardest to reverse; programming void is the most responsive; life circumstances is outside operator control), the offer type (a hold offer for Established ghosts outperforms both a discount and no offer at every community size and price tier studied), and the timing of the first outreach (the single largest predictor of Early ghost reactivation is whether the first DM is sent within the 10–14 day window versus later). Table 1 classifies ghost members by tier with reactivation benchmarks. Table 2 identifies the five root causes with operator-fixable status. Table 3 gives the reactivation sequence structure for each tier. Table 4 provides response rate benchmarks by community size and price tier. Table 5 gives the offer decision table. Table 6 is the priority matrix for allocating reactivation effort. Table 7 gives graduation criteria for ending active outreach per tier.

Why ghost member reactivation is different from churn prevention and win-back

The three intervention types that paid community operators use to reduce revenue loss from disengaged members — churn prevention, ghost member reactivation, and win-back — target different populations at different tenure points, and conflating them produces the wrong intervention at the wrong time. Churn prevention targets members who are at risk of cancelling in the next 30 days but have not yet cancelled: the behavioral signature is declining engagement that is still measurable (posts dropping from 8 per month to 2, replies reducing, event attendance dropping). Ghost member reactivation targets members who have already crossed into silence (no measurable Slack activity in 7+ days) but are still paying: the billing system has not been triggered, but the community behavior has flatlined. Win-back targets members who have already cancelled: they are no longer paying, the relationship is disrupted, and the intervention is a post-cancellation email sequence asking them to return at some future point when circumstances change.

The practical significance of these distinctions is operator time allocation. Churn prevention has the highest ROI per hour of operator time because the at-risk member is still engaged enough to respond to a targeted re-engagement prompt, and the probability of converting the intervention into a continued subscription before the renewal date is 35–65% depending on the tenure stage. Ghost member reactivation has moderate ROI: the probability of reactivation drops significantly with each day of silence, the optimal window for each ghost tier is specific (10–14 days for Early, 35–40 days for Established, first-touch only for Terminal), and the intervention outside the optimal window produces significantly worse results than intervention within it. Win-back has the lowest per-hour ROI because the cancellation event is already a disruption to the relationship that even a well-crafted three-email sequence overcomes only 12–20% of the time. An operator who spends equal time on all three areas is over-investing in win-back (low base rate, high effort) and under-investing in churn prevention (high base rate, lower effort per prevented churn) relative to the revenue impact of each area. See the churn prevention reference card for the detection benchmarks that distinguish at-risk from ghost members before the silence boundary is crossed.

Ghost member reactivation also intersects with the two-churn-cliff model for paid communities. The first churn cliff (month one) is driven primarily by non-activation: members who never completed the Day 0 checklist and never posted are the majority of month-one cancellations. Ghost member reactivation is most relevant at the second churn cliff (months three through six), when members who activated in week one, participated actively in months one and two, and then went progressively quieter until they crossed the silence boundary in month three or four. This is the population where the reactivation intervention has the highest probability of success, because the member has demonstrated they can participate actively — the ghost formation is a disruption to a pattern that existed, not an absence of a pattern that never formed. See the onboarding metrics reference card for the week-one activation benchmarks by tier that predict which members are most likely to ghost in months three through six.

Table 1: Ghost member classification and reactivation benchmarks

Three ghost tiers defined by days of silence, with the estimated population share in a typical paid Slack community, the month-three renewal rate without operator intervention, the recommended intervention window, and the expected reactivation rate with a correctly executed intervention for that tier. Reactivation rate is defined as the member returning to visible Slack activity (posting, replying, or reacting) within 30 days of the operator’s outreach. The renewal rate without intervention is the probability that a member in each ghost tier renews at their next billing cycle if the operator takes no reactivation action. Population share estimates are from communities running three-touch onboarding (Day 0, Day 3, Day 7); communities without automated onboarding see higher ghost population shares, particularly in the Established and Terminal tiers, because the non-activation rate is higher and produces more members who ghost before ever contributing.

Ghost tier	Definition	Estimated % of typical paid community	Month-3 renewal rate without intervention	Optimal intervention window	Expected reactivation rate with correct intervention
Early ghost	No visible Slack activity (post, reaction, reply, or thread participation) for 7–30 days. Member is still paying. Includes two sub-populations: Never-activated ghosts (members who joined but never completed the Day 0 checklist and never posted — these are better described as activation failures than true ghosts, and they carry higher month-one cancellation probability than lapsed-contributor ghosts) and Lapsed-contributor ghosts (members who posted actively in weeks one through three and then fell silent beginning in weeks four through eight). The never-activated sub-population is more urgent: their silence started at day one, and their probability of cancelling before the first renewal is 40–60% without an active Day 3 conditional nudge. The lapsed-contributor sub-population is more receptive to reactivation: they demonstrated they could participate, and their ghost formation is more likely to be circumstantial than motivational. When segmenting Early ghosts for outreach, address never-activated members with a modified Day 3 nudge and lapsed-contributors with the Early ghost personal DM described in Table 3.	18–35% of the total paying member base at any given point in time. Skews toward never-activated in communities without automated onboarding (30–45%) and toward lapsed-contributor in communities with a structured three-touch sequence (12–22%). Communities that have recently experienced a programming gap (no events or async content for two or more weeks) see temporary spikes in Early ghost formation as members who were participating in the programming cadence go quiet when the cadence breaks. These spikes are programming-gap ghosts rather than true disengagement, and they self-resolve at a higher rate than either sub-population when the programming resumes.	45–65% without intervention — lower than might be expected, because Early ghosts include both the never-activated sub-population (30–45% renewal rate) and the lapsed-contributor sub-population (60–75% renewal rate). The blended rate masks the bimodal structure of the population. For decision-making purposes, treat never-activated Early ghosts as high-risk (churn prevention priority) and lapsed-contributor Early ghosts as moderate-risk (reactivation priority).	Day 10–14 of the silence period for lapsed-contributors; day 3–5 for never-activated members (which is when the Day 3 conditional nudge fires in a structured onboarding sequence). The 10–14 day window for lapsed-contributors is the product of two competing forces: early enough that the specific reference to the member’s history in the community feels fresh (they can remember the last conversation they participated in), and late enough that the absence is clearly not just a busy week (sending on day 4 or 5 catches members who are simply between login sessions and produces a lower response rate than a day 10–14 DM to members who have genuinely fallen off the community rhythm). Outreach at day 20–30 (late Early ghost) still produces reactivation outcomes but at a significantly lower rate (22–35%) than the day 10–14 window (45–55%).	35–55% for lapsed-contributor Early ghosts with a single personal DM in the day 10–14 window; 20–35% for never-activated Early ghosts with a Day 3-equivalent conditional nudge; 22–35% for lapsed-contributor Early ghosts contacted after day 20. The gap between the 10–14 day window and the 20–30 day window is the primary argument for monitoring ghost member status weekly rather than running monthly audits: a member who crosses into the Early ghost tier on day 7 is reachable at a 45–55% rate on day 10–14 and at a 22–35% rate on day 25. A monthly audit that catches this member on day 30 misses the highest-yield intervention window entirely.
Established ghost	No visible Slack activity for 31–90 days. Member is still paying. At this stage the ghost pattern has persisted through at least one full billing cycle, which means the member made a renewal decision (or an inertia decision) while silent. This is the defining characteristic of the Established ghost: they are not ghosting because they forgot to cancel; they are ghosting while continuing to pay, which indicates that the membership has residual perceived value (they have not concluded it is worth zero) even though active participation has stopped. The Established ghost who has been silent for 60+ days is also approaching the boundary where a hold offer (one-time billing pause) is more effective than a re-engagement DM, because the length of silence indicates a life or work circumstance that displaces the community habit rather than a content or programming reason for disengagement.	10–20% of the total paying member base at any given point in time. Established ghost population is relatively stable in a well-operated community because the inflow (Early ghosts who do not reactivate) is offset by the outflow (Terminal ghosts who eventually cancel). In a community with a low reactivation rate for Early ghosts (which happens when the operator is not monitoring ghost status weekly), the Established ghost population grows because the inflow exceeds the outflow; in a community with high Early ghost reactivation, the Established ghost population is smaller because fewer members graduate from Early to Established.	28–45% without intervention. The renewal rate for Established ghosts is higher than the Terminal ghost rate and lower than the Early ghost rate; it reflects the inertia dynamic described above. Established ghosts who are still paying after 60 days have already passed the strongest cancellation trigger (the second billing cycle at which the absence is most salient in memory) and are now in the window where the membership fee is a background cost that is not actively evaluated each month. This is both a vulnerability (they will eventually cancel when a budget review or an annual renewal triggers active evaluation) and an opportunity (the inertia means there is still time for a personal reactivation touch before the evaluation is triggered).	Day 35–42 for the first personal DM (5–6 days into the Established ghost window), with a second touch 14 days after the first if there is no response. The total intervention window is 35–56 days from the start of the Established ghost period. Outreach at day 80–90 (late Established ghost / approaching Terminal ghost boundary) still produces some reactivation outcomes but at approximately half the rate of day 35–42 outreach, and is more efficiently classified as Terminal ghost outreach with the simplified single-touch protocol from Table 3.	15–28% for the full two-DM-plus-event-invitation sequence in the day 35–56 window. The 15% lower bound applies to communities where the Established ghost population is dominated by programming-void ghosts (members who participated actively but left when the content calendar became inconsistent — see Table 2); the 28% upper bound applies to communities where the Established ghost population is dominated by circumstantial ghosts (members who went quiet due to a temporary life circumstance). The hold offer (Table 5) increases the reactivation benchmark by 5–10 percentage points for Established ghosts at the 60+ day mark because it converts the decision from “re-engage or cancel” to “re-engage, pause, or cancel” — and the pause option captures the members who intend to return but are not ready to re-engage in the current billing period.
Terminal ghost	No visible Slack activity for 90+ days. Member may or may not still be paying. Terminal ghosts who are no longer paying have already cancelled and belong in the win-back sequence, not the reactivation sequence. Terminal ghosts who are still paying are in one of two situations: genuine long-term inertia (the membership fee is below their active review threshold and they are paying without noticing or actively deciding), or external circumstance (an extended leave, a work crisis, or a life event that will eventually resolve and bring them back). Both situations resolve the same way: a single personal reactivation touch, no pressure, a hold offer, and then graduation to the win-back pre-queue regardless of response. The Terminal ghost population should not receive multiple outreach touches in the reactivation sequence; the probability of response decreases with each additional touch without a corresponding increase in reactivation probability, and repeated outreach to a Terminal ghost increases the probability that the member cancels out of annoyance rather than continuing in inertia.	5–12% of the total paying member base. The Terminal ghost population is the most variable across communities because it is the accumulation of all the Early and Established ghosts who did not reactivate over the prior 3–9 months. Communities with effective Early and Established ghost reactivation programs have Terminal ghost populations at the low end of this range; communities that do not monitor ghost status until the quarterly renewal review have Terminal ghost populations at the high end or above it. A Terminal ghost population above 15% of the paying member base indicates that the reactivation intervention is not being executed within the optimal windows for Early and Established ghosts, and the fix is upstream of Terminal ghost outreach.	15–30% without intervention. The renewal rate for Terminal ghosts is the lowest of the three tiers for obvious reasons: members who have been silent for 90+ days are approaching the point where the membership fee will trigger an active evaluation at the next renewal cycle, and without a personal reactivation touch that reconnects them to the community’s value, most will not renew. The 15% lower bound is for communities where Terminal ghosts are predominantly price-inertia subscribers (members who renew each month without actively using the community but who do not cancel because the fee is below their review threshold); these members will eventually cancel at an annual budget review even without any change in the community. The 30% upper bound is for communities where Terminal ghosts are predominantly circumstantial (they genuinely intend to return when their situation resolves), and the probability of renewal is driven by whether the circumstance resolves before the renewal date.	Single touch only, timed to day 95–100 of the silence period (the first week of the Terminal ghost tier), regardless of when the next billing event is. The timing rationale: early in the Terminal ghost window is still within the period where a personal message can feel specific to the member’s community history rather than generic; a message sent at day 130 or 150 is too far from the member’s last active experience to anchor the outreach in a community-specific reference. If no response in 21 days, graduate immediately — no second touch at the Terminal tier.	4–9% with the single-touch protocol. The low reactivation rate for Terminal ghosts is expected and not a sign that the intervention is incorrectly designed. The value of the Terminal ghost touch is not primarily the 4–9% who reactivate; it is the prevention of pre-cancelled inertia in the remaining 91–96%, and the generation of goodwill that produces a higher win-back rate (12–18% versus 6–10%) when these members eventually do cancel and receive the post-cancellation sequence. A Terminal ghost who received a personal reactivation touch in the 95–100 day window and did not respond at the time is more likely to respond to the win-back sequence at cancellation than a Terminal ghost who was never contacted.

The most important operational implication of the three-tier classification is the monitoring cadence. Weekly ghost status checks for a 200-member community take approximately 15 minutes using the manual channel scan method described in the FAQ below; monthly checks miss the Early ghost optimal window (day 10–14) for the majority of Early ghosts, because most Early ghosts will have crossed into the Established ghost tier by the time a monthly audit identifies them. If you cannot run weekly checks, a bi-weekly cadence (every 14 days) captures most of the Early ghost optimal window with a small drop in reactivation rate relative to weekly monitoring. Monthly cadence is operationally simpler but produces significantly worse Early ghost reactivation outcomes than bi-weekly. Use the member health score reference card for the automated scoring approach that surfaces ghost tier status without manual channel scans.

Table 2: Root cause taxonomy for member ghosting

Five root causes of ghost member formation, with the behavioral signature that identifies each cause, the typical onset timing (when in the member tenure the ghost pattern begins), the operator-fixable classification (whether the operator can change the cause with a community or onboarding change), and the expected reactivation rate with a correctly designed intervention. Operator-fixable status is binary for clarity, but in practice some causes are partially fixable: onboarding failure can be fixed for future cohorts but not retroactively for members who already failed to activate, and programming void is fixable for the community’s future content calendar but does not guarantee that members who ghosted during the void will return when the calendar resumes. The reactivation rate column reflects what is achievable with the cause-specific intervention described in the “intervention” column; the general reactivation sequence in Table 3 produces lower rates for cause-specific ghosts because it does not address the root cause directly.

Root cause	Behavioral signature	Onset timing	Operator-fixable?	Cause-specific intervention	Expected reactivation rate with cause-specific intervention
Onboarding failure (never-activated)	Member joined, may have logged in once, but never posted in any channel, never replied to the Day 0 DM with a goal statement, and did not complete the Day 0 checklist. The ghost pattern begins at day one and never breaks. The behavioral signature distinguishing this cause from lapsed-contributor ghosting is the absence of any post or reaction in any channel at any point in the member tenure: if there is no post in the member history, this is an onboarding failure ghost, not a lapsed-contributor ghost. The silent new-member baseline in the Week 1 health score is the leading indicator: if more than 25% of new members are still at Silent tier at day 7, the onboarding failure ghost formation rate will be elevated in the Established and Terminal tiers 60–90 days later.	Days 1–7 (onset is immediate; the member joins and never develops a participation habit). The never-activated ghost is the most predictable ghost type because the Day 7 scorecard surfaces them specifically: members who have not posted, not replied to the DM, and not subscribed to two channels by day 7 are the never-activated population. The Day 7 scorecard is the earliest structural opportunity to catch and intervene on onboarding failure ghosts before they persist into the Established tier.	Partially fixable — fixable for future cohorts by improving the Day 0 DM, the checklist design, and the channel architecture that new members encounter; not retroactively fixable for members who already failed to activate in week one without a dedicated Day 7 personal intervention that restarts the activation sequence for that specific member.	A Day 7 personal re-activation DM (distinct from the standard Day 7 scorecard) sent directly to never-activated members, naming the one specific checklist step they have not completed (usually the introduction post), lowering the bar explicitly (“a one-sentence intro is enough — here’s the exact channel and format”), and offering a peer introduction from the operator to one specific member the operator believes matches their stated goal category. The peer introduction offer is the highest-converting intervention for onboarding failure ghosts because it makes the first post about responding to a real connection rather than broadcasting into a public channel — the social pressure dynamic that makes the introduction post feel risky is neutralised when the member is responding to a specific person rather than performing for an audience.	22–38% with the Day 7 peer introduction intervention. The rate is lower than the lapsed-contributor Early ghost reactivation rate because onboarding failure indicates a structural barrier to first posting (the member found the first post too high-stakes, did not understand which channel to use, or arrived with a goal that the community’s current structure did not immediately match) that a single DM does not fully resolve. Members who reactivate through the peer introduction intervention have significantly higher month-three renewal rates than members who eventually post without the intervention, because the peer introduction creates the named-peer connection that is the primary predictor of renewal at month three.
Programming void	Member participated actively — posted, replied, attended events — for 4–12 weeks, and then went progressively quieter as the community’s content calendar became inconsistent or the events that attracted them stopped appearing. The behavioral signature is declining activity that correlates with operator programming output: if the operator can trace the member’s last post to the period when weekly threads, live events, or prompt posts became less frequent, this is likely a programming void ghost rather than a lapsed-contributor ghost with an external cause. Programming void ghosting typically affects the Outcomes and Validation member segments most strongly (see the member segmentation reference card): these members joined specifically for the structured output that the programming calendar provided, and when the output stops, they stop returning to the workspace.	Months 2–4, which is when the operator’s early-stage programming enthusiasm often gives way to the operational cost of maintaining a consistent content calendar. The community’s programming output is typically highest in month one (launch energy) and months two through three (the founding cohort period), and the first content calendar gaps appear in month four or five when the initial program exhausts the operator’s pre-prepared content library. Members who formed their community habit during high-output months are the most likely to ghost when the output decreases below the level that sustained their habit.	Yes — fixable — both for future ghost formation (by maintaining a consistent programming cadence as described in the channel architecture reference card) and partially for existing programming void ghosts (by resuming the content calendar and notifying affected members specifically). The notification is critical: a programming void ghost who does not know the calendar has resumed will not return organically, because the habit of checking the workspace was disrupted and does not automatically restart when new content appears.	A personal DM notifying the member of a specific new piece of programming that matches their stated goal category and directly addresses the type of content that was absent during the void period. The DM references the specific content type the member engaged with most during their active period (“we started running [format] again — you participated in the last three before we took a break, and this week’s is specifically on [topic matching their goal]”). The DM includes a direct link to the new content and a low-bar action (a reaction, not a required post). Programming void ghosts who respond to this DM with even a reaction have a 55–70% probability of returning to active posting within 14 days, which is significantly higher than the general Established ghost reactivation rate.	28–45% with the programming-specific notification DM. The higher reactivation rate relative to other ghost causes reflects the fact that the member’s community habit was intact; it was the absence of programming to respond to that disrupted the habit, not a change in the member’s relationship to the community. When the programming resumes and the member is notified specifically, the probability of habit resumption is substantially higher than for ghosts whose silence reflects a more fundamental change in engagement motivation.
Goal drift	Member participated actively in their goal track (Outcomes, Connection, Learning, or Validation) for 4–16 weeks, then went quiet as the community’s content and programming became less relevant to their evolving situation. The behavioral signature is gradual disengagement from goal-track channels (progressively fewer posts and reactions in their primary goal-track channel) followed by a complete stop, with no corresponding increase in other channels. Goal drift ghosts typically do not complain and do not contact the operator; they simply stop returning because the community is no longer matching where they are in their professional journey. Two sub-types: Goal-achieved drift (the member accomplished the specific goal that brought them to the community — hired the team, launched the product, landed the job — and the original motivation for membership has resolved) and Goal-redirected drift (the member’s priorities shifted — a new project, a new role, a new market — and the community’s content no longer matches the direction they are moving).	Months 3–9, which is the typical timeline for members to either achieve the specific goal they joined to accomplish or to experience a significant enough professional shift that their community needs change. Goal-achieved drift is positive evidence that the community delivered its value proposition; these members are the most likely to refer new members who are in the stage they just graduated from, and the correct operator response is a structured exit conversation that collects the specific outcome they achieved and converts it into a referral and a testimonial, not a reactivation pitch. Goal-redirected drift may be responsive to reactivation if the community has evolved to serve their new direction.	Partially fixable — goal-achieved drift is not fixable for the individual member (the goal is resolved; re-engagement requires a new goal that the community serves), but it can be mitigated at the program level by ensuring the community’s programming evolves with the member lifecycle (advanced content for members who have progressed, a graduate or alumni track for members who have achieved their original goal). Goal-redirected drift may be fixable if the community’s current programming covers the member’s new goal direction, but requires identifying the new direction first — which the reactivation DM must surface.	A structured exit conversation (for goal-achieved drift) that collects the specific outcome achieved, asks for a referral to someone in the stage they just left, and requests a testimonial. For goal-redirected drift: a check-in DM that asks one open question about where their work focus is now, with the explicit framing that the community is evolving and you want to know if there is a way to serve their current direction. If the community can match their new direction, follow up with one specific example of current programming that is relevant. If it cannot, the honest answer is to acknowledge that the community may not be the right fit for their current stage and offer a cancellation with a standing re-invitation if they return to the original use case.	12–25% reactivation rate for goal-redirected drift with the check-in DM; 3–8% for goal-achieved drift (where reactivation means finding a new goal rather than resuming the original one). The low rate for goal-achieved drift is expected and not a signal of failure; the correct metric for goal-achieved ghosts is referral rate (35–55% of goal-achieved ghosts who receive a structured exit conversation refer at least one qualified candidate), not reactivation rate.
Life circumstances	Member participated actively and without visible disengagement signals, and then went quiet abruptly following an external event: a health issue, a family emergency, a job loss, a significant life transition. The behavioral signature distinguishing this cause from programming void or goal drift is the abruptness: no gradual decline, no correlation with a programming calendar change, often preceded by a normal or above-average activity period. Life circumstances ghosts frequently DM the operator (or another community member) to explain their absence when they are ready to return; they do not disengage because the community failed them but because external circumstances temporarily removed the bandwidth for community participation.	Any tenure stage. Life circumstances ghosting is not tenure-dependent; it appears at month one and at month eighteen with equal probability because it is driven by external events rather than community-engagement dynamics. The absence of tenure-correlation is itself a diagnostic signal: if you observe a ghost pattern that does not correlate with any change in your programming calendar, your onboarding quality, or the member’s stated goal progression, life circumstances is the most likely explanation.	Not fixable by operator — the cause is external to the community, and the operator cannot change the circumstance. The operator can, however, choose whether to hold space graciously (a brief check-in DM that acknowledges the absence without pressure and offers a hold option), which significantly affects the probability that the member returns when their circumstances allow. Members who receive a no-pressure check-in DM during a life circumstances absence return at higher rates than members who receive no communication (self-resolved) or who receive a reactivation pitch focused on community value (which reads as tone-deaf to members who are aware their absence is circumstantial and not community-driven).	A brief, low-pressure personal DM sent at the 30–45 day mark of the silence: “Just checking in — I noticed you’ve been quiet for a few weeks and wanted to make sure everything is okay. No pressure to be active in the community right now; if you want, I can pause your membership while you’re busy so you can return when the timing is better.” No follow-up DMs if there is no response. The DM is not a reactivation pitch; it is a welfare check with a hold offer attached. Members who respond and accept the hold are significantly more likely to return at the end of the pause than members who self-manage their absence without operator contact.	40–65% eventual return rate for members who received a no-pressure check-in DM and accepted the hold offer. The timeframe for return is longer than typical reactivation (30–90 days from the pause end rather than 7–14 days from the reactivation DM), but the quality of re-engagement is higher: members who return after a hold tend to participate more actively than their pre-ghost baseline, possibly because the pause period crystallised the community’s value relative to the circumstances that had been competing for their attention. Members who did not accept the hold but acknowledged the DM also return at higher rates than non-contacted life-circumstances ghosts (25–40% versus 10–18%).
Price-inertia subscriber	Member never fully activated, or activated briefly and disengaged early (months one through two), and has continued paying for 3–12 months primarily because the membership fee is below their active review threshold. The behavioral signature is extended silence (Established or Terminal ghost) with regular monthly payments and no cancellation attempt. Price-inertia subscribers are a distinct population from life-circumstances ghosts because there is no external event causing the absence — they simply did not develop a strong enough community habit to sustain active participation, and the fee is small enough that they have not made a deliberate decision to cancel. This population eventually cancels at an annual budget review, a fee increase, or a financial stress event, not because of any specific community failure.	Months 2–4 for onset (the ghost formation happens early in the tenure), with sustained inertia potentially extending 6–18 months before a cancellation trigger. The price-inertia subscriber ghost pattern is most common in communities priced at $49–$79/month (below the typical monthly subscription review threshold for professional buyers) and least common in communities priced above $149/month (where the fee is large enough to trigger monthly evaluation). This is one of the mechanisms by which lower-priced communities accumulate high ghost member rates even as their cancellation rate remains low: members are paying without engaging, which inflates the member count while depressing the engagement metrics.	Limited — the underlying issue is that the community did not deliver a compelling enough activation experience to make the habit stick, which is a product problem that the reactivation DM does not resolve. The operator can fix the upstream cause (onboarding quality and activation sequence) for future cohorts, but the price-inertia subscriber who is already in the ghost tier is unlikely to be reactivated by community outreach because their inertia is driven by the absence of an activation habit, not by a temporary disruption to an existing habit. The most effective intervention for this population is one that brings the value question into focus before the annual cancellation trigger does it adversarially (with a fee statement).	A value-reset DM sent at the 60–90 day mark (when the member is clearly in the Established ghost tier): “You’ve been a member for [X] months and I want to make sure you’re getting value. If the community isn’t fitting into your current work right now, I’d rather help you figure out if it makes sense for you than have you paying for something you’re not using. Would you be open to a quick DM conversation about where your focus is right now?” The goal of this DM is not to retain the subscriber at all costs but to convert an inertia-driven non-decision into a conscious one: either the member re-engages with a clear understanding of the value (a better subscriber), or they cancel now (which produces the win-back sequence earlier than the annual trigger, giving the operator more time to win them back before they have forgotten the community exists entirely).	8–18% reactivation rate and 20–35% voluntary cancellation rate in response to the value-reset DM. The voluntary cancellation response is not a failure: it converts an inertia subscriber who was going to cancel in 3–9 months into a cancelled member who is now in the win-back sequence at a point where their community memory is fresh, giving the win-back sequence a higher conversion rate (18–28% versus 6–12% for cancellations that occur much later after a long inertia period). The 8–18% reactivation rate produces genuine re-engaged members rather than continued inertia: members who choose to stay after the value-reset conversation have made a conscious decision that the community is worth their attention, and their subsequent engagement rate is significantly higher than their pre-conversation baseline.

Root cause identification is not always possible from behavioral data alone, and the operator should not invest significant time trying to diagnose the cause before sending the first personal DM. The first DM itself is diagnostic: the member’s response (if any) will almost always indicate the cause within the first exchange. A member who says “I’ve been swamped with [external event]” is a life-circumstances ghost; a member who says “I felt like the community content stopped being as relevant” is a programming void or goal drift ghost; a member who says “honestly I’ve been meaning to use it more but haven’t found the time” is likely a price-inertia subscriber. Design the first DM to surface the cause in the response rather than to diagnose it before sending. See the engagement benchmarks reference card for the behavioral thresholds at each tenure stage that signal when a member is transitioning from at-risk engagement to the Early ghost tier.

Table 3: Reactivation sequence structure by ghost tier

The intervention sequence for each ghost tier, with the timing, channel, message format, and the no-response protocol at each step. The no-response protocol is the most frequently omitted element in community reactivation programs: operators who send a single DM and then send additional DMs when there is no response are not following a protocol — they are escalating contact based on anxiety, which produces worse outcomes than the defined protocol. The protocol specifies exactly when to stop and what to do next, so the operator does not face an open-ended decision each time a member does not respond. Total operator time per ghost member (across all touches) should be under 10 minutes for an Early ghost and under 20 minutes for an Established ghost; if individual touches take longer than this, the DM templates are too long or too customised for the volume of ghosts the community is producing.

Ghost tier	Touch 1	No-response protocol after Touch 1	Touch 2 (Established only)	No-response protocol after Touch 2	Touch 3 (Established only)	Final step & graduation
Early ghost (7–30 days)	Day 10–14: Personal Slack DM from the operator (not an automated message). Format: 3–5 sentences. Content: (1) specific reference to the member’s most recent post or reply, by name and topic; (2) one specific thing happening in the community this week that is relevant to their stated goal category; (3) a single low-bar action (a thread to react to, a channel to browse, a question they might have an answer to); (4) an explicit opt-out (“if you’re just in a busy stretch, totally fine — I can flag this back to you in two weeks when things settle”). Do not ask whether they are still getting value or whether they want to continue. The DM does not mention billing, membership status, or the observation that they have been quiet — the observation is implied by the outreach timing, and making it explicit reads as surveillance rather than community care.	Wait 14 days with no further outreach. If the member is still an Early ghost at day 28–30 (with no response to the first DM), graduate to Established ghost tier at day 31 and begin the Established ghost sequence at day 35–42. Do not send a second Early ghost DM. One DM is the full Early ghost intervention; the 35–55% reactivation rate for this tier is achieved with one touch, not two, and a second touch within the Early ghost window decreases the response rate for the second DM relative to a fresh outreach in the Established ghost window.	N/A for Early ghost	N/A for Early ghost	N/A for Early ghost	Graduate to Established ghost tier at day 31. No action required at graduation other than flagging the member in the billing system for review at their next renewal date. Add to the Established ghost monitoring queue for first-touch at day 35–42.
Established ghost (31–90 days)	Day 35–42: Personal Slack DM. Format: 4–6 sentences. Content: (1) the operator’s honest observation that it’s been a few weeks since they’ve been around, framed with warmth not judgment; (2) one specific community development since their last active period that is relevant to their goal category; (3) for members at the 60–90 day mark or approaching their next billing date: include the hold offer explicitly (“if you’re in a stretch where the timing doesn’t work, I can pause your membership for a month so you can come back when you’re ready”); (4) an explicit opt-out with no pressure. For members at the 35–45 day mark: the hold offer is optional; reserve it for the second touch if the first touch produces no response. The first touch at this stage is still a re-engagement invitation, not a billing conversation. The hold offer becomes appropriate when the silence has lasted long enough that re-engagement in the current billing period is unlikely.	Wait 14 days. If no response after 14 days, proceed to Touch 2. Do not add the hold offer to this response; send a second DM as a separate message, not as a follow-up in the same thread (threads imply the member has already seen the first message, which creates a social pressure dynamic that is counterproductive).	Day 49–56: Second personal DM, shorter than the first (2–3 sentences). Content: (1) acknowledge that they may have seen the first message and not had time to respond; (2) include the hold offer explicitly if not included in Touch 1; (3) one question: “Is there anything specific you’d want to see in the community that would make it more useful for where your work is right now?” This question serves two purposes: it gives the non-responsive member a lower-friction way to re-engage (responding to a question is easier than responding to an invitation) and it surfaces any programming void or goal drift cause that the first DM did not surface. If the member responds with a programming suggestion, act on it and notify them specifically when the content appears.	Wait 21 days. If no response after 21 days, proceed to Touch 3 (event invitation). This is a distinct channel from the two prior DMs, and the gap gives the member time to process the two DMs without feeling pressured. The 21-day gap also means Touch 3 occurs at approximately day 70–77 of the Established ghost period — within the window where a final outreach can still produce a response before the member enters the Terminal ghost tier.	Day 70–77: Community event invitation, sent via email if the member’s email address is available, or as a third Slack DM if not. Format: 3–4 sentences. Content: an invitation to a specific upcoming community event that directly matches their goal category (not a general “we have an event this week” announcement). Include the exact date, time, and one sentence on what they will get from attending. No hold offer in the event invitation; the hold offer has been made in Touch 1 and/or Touch 2, and repeating it in the event invitation conflates two different asks. The event invitation is a re-entry path for members who are not ready to re-engage with the async community but might attend a live event that creates the peer connection that re-activates the participation habit.	After Touch 3 (event invitation) with no response or no attendance in 21 days: graduate to Terminal ghost tier at approximately day 98. Add to Terminal ghost monitoring queue for the single Terminal touch at day 100–105. Add to billing system watch list for renewal review. If the member cancels before the Terminal touch is sent, move directly to the win-back sequence; do not combine the Terminal ghost touch with the win-back sequence even if the timing coincides.
Terminal ghost (90+ days)	Day 95–105: Personal Slack DM, brief (2–3 sentences). Content: (1) acknowledge the member has been away for a while, no pressure; (2) hold offer (explicit — 30-day pause on billing, resumes automatically, no commitment required); (3) a single honest question: “Is there anything the community could do differently that would make it worth coming back to?” This question is the most important element of the Terminal ghost DM: it signals that the operator is interested in the member’s feedback rather than just their continued payment, which is the framing that most often produces a response from a Terminal ghost who otherwise would not reply to a re-engagement pitch. The feedback the member provides (if any) is also operationally valuable: Terminal ghost feedback surfaces structural community problems that active members do not mention because they have adapted to work around them.	21 days. If no response in 21 days: graduate immediately. No second Terminal ghost touch. The decision to end active outreach after a single touch for Terminal ghosts is not based on giving up; it is based on the marginal productivity of additional outreach. A Terminal ghost who does not respond to one personal DM with a hold offer and an open feedback question has a below-2% probability of responding to a second or third touch, and the operator time invested in additional touches produces higher return when allocated to Early ghost monitoring and Established ghost reactivation.	N/A for Terminal ghost	N/A for Terminal ghost	N/A for Terminal ghost	At graduation (21 days after Touch 1 with no response): add to win-back pre-queue. When the member cancels (which typically occurs at the next billing review after the Terminal touch, often 30–60 days after graduation), move to active win-back sequence. See the win-back email sequence reference card for the three-email post-cancellation sequence. The Terminal ghost touch is the last operator-initiated outreach before the win-back sequence begins; do not re-initiate active outreach in the Terminal tier after the single touch.

The hold offer (one-month billing pause) appears in the Established and Terminal ghost sequences but not in the Early ghost sequence, because a hold offer at day 10–14 introduces a billing conversation into a re-engagement DM that should be purely community-focused. An Early ghost who receives a hold offer in their first reactivation DM is more likely to interpret it as the operator suggesting they cancel than as a genuine expression of flexibility. The hold offer is appropriate when the silence has lasted long enough (31+ days for Established ghosts, 90+ days for Terminal ghosts) that the practical question of “should I keep paying for something I’m not using?” is already present in the member’s mind — and proactively naming the pause option is a demonstration of good faith rather than a cancellation suggestion.

Table 4: Reactivation message response rate benchmarks

Response rate benchmarks for three outreach channels (personal Slack DM, email, event invitation) by community size band and membership price tier. Response rate is defined as the member sending a reply within 14 days of the outreach; it is not the same as reactivation rate (which requires the member to post, react, or reply in the community within 30 days). Response rate is a leading indicator of reactivation: a member who responds to the outreach DM but does not immediately re-engage in the community has a 40–60% probability of returning to active posting within 30 days, compared to a 5–12% probability for members who do not respond at all. Communities at the lower end of each size band see higher response rates because the member-to-operator relationship is more personal; at larger community sizes, the personal DM is less likely to feel like a genuine personal connection and more likely to feel like an automated outreach from a community management system.

Community size	Price tier	Personal Slack DM response rate (Early ghost, day 10–14)	Personal Slack DM response rate (Established ghost, day 35–42)	Email response rate (Established ghost Touch 3)	Event attendance rate (Established ghost Touch 3 invite)
Under 100 members	$49–$99/mo	45–62%	28–42%	18–30%	12–22%
Under 100 members	$100–$299/mo	52–68%	35–50%	22–35%	18–30%
100–300 members	$49–$99/mo	38–55%	22–35%	12–22%	8–16%
100–300 members	$100–$299/mo	45–60%	28–42%	15–25%	12–22%
300–600 members	$49–$99/mo	28–42%	15–25%	8–15%	5–12%
300–600 members	$100–$299/mo	35–50%	20–32%	10–18%	8–16%
600+ members	Any tier	22–35%	12–20%	6–12%	4–10%

The price tier effect on response rates reflects the self-selection dynamic described in the engagement benchmarks reference card: higher-priced communities attract members who made a larger commitment signal at the purchase decision, and members who paid more for the community are more likely to respond to a personal outreach DM because the relationship with the operator feels more like a genuine partnership (the member paid enough that they expect a personal relationship) and less like a product subscription. This dynamic means that higher-priced communities have both lower ghost formation rates (the commitment signal predicts better activation and engagement) and higher reactivation response rates when ghost formation does occur. The operator time cost of ghost member reactivation per revenue-dollar retained is therefore lower at higher price tiers, which is an additional argument for the price-appropriateness-for-ICP framework discussed in the pricing reference cards.

Table 5: Offer decision table

Three offer types available in ghost member reactivation outreach, with the appropriate ghost tier for each, the expected reactivation conversion rate with the offer versus without it, the operator time cost, and the adverse selection risk. Adverse selection risk refers to the probability that the offer attracts responses from members who are motivated primarily by the offer terms (free pause, discount) rather than by genuine re-engagement intent; high adverse selection produces responses that convert to reactivation at lower rates than the response rate implies. The “no offer” row is included because it is the correct baseline for Early ghost outreach and the correct choice in specific Established ghost scenarios where an offer would be premature or confusing.

Offer type	Appropriate ghost tier	Description	Reactivation rate with offer vs. without	Operator time cost	Adverse selection risk	Do NOT use when
No offer (community re-engagement only)	Early ghost (all sub-populations). Established ghost (day 35–42 first touch only, unless circumstantial signals suggest life circumstances or goal drift).	The outreach DM references a specific community development, offers a low-bar re-entry action, and includes an explicit opt-out. No billing mention, no discount, no pause. The absence of a financial offer frames the DM as a genuine community check-in rather than a retention pitch, which produces better response quality (members who respond are doing so because the outreach resonated, not because of an incentive) even if the raw response rate is lower than with a hold offer.	Early ghost: 35–55% reactivation rate. No meaningful lift from adding a hold offer at this tier; in some communities, the hold offer at day 10–14 slightly depresses the reactivation rate by introducing a billing discussion into a context where the member was not yet thinking about their membership cost. Established ghost (first touch, day 35–42): 15–22% reactivation rate without offer vs. 18–28% with hold offer. The lift is modest enough at first touch that the no-offer first touch is defensible; the hold offer is better reserved for the second touch where the first DM has already demonstrated that the member is not re-engaging from community motivation alone.	Low (5–8 minutes per member for a personalised DM that references a specific post or community moment).	Low. Members who respond to a no-offer DM are responding to the community outreach; there is no incentive to capture beyond the community itself.	The member has been silent for 60+ days; at this stage the no-offer DM is unlikely to produce re-engagement, and the hold offer should be included. Also avoid the no-offer approach for Terminal ghosts, where the outreach must include the hold offer to have a meaningful response rate.
Peer connection offer	Early ghost (never-activated sub-population). Established ghost (programming void root cause, where a specific peer connection can restart the participation habit).	The operator identifies a specific community member who matches the ghost member’s stated goal category and who the ghost member has not yet connected with, and offers to make the introduction via a DM. The peer connection offer is not a formal introduction request (which requires the connected member to opt in and creates operator overhead); it is an offer to point the ghost member toward a specific person or conversation: “There’s a member who posted something this week that I think would be directly useful for [the ghost member’s stated goal] — would it be okay if I tagged you in that thread?” A tag-in requires much less social courage from the ghost member than an unsolicited introduction to a stranger.	Early ghost (never-activated): 28–42% reactivation rate with peer connection offer vs. 15–25% without. The lift is significant because never-activated ghosts are typically stuck at the first-post threshold; a specific person or thread to respond to lowers the barrier to a first post from “post to an audience I don’t know” to “respond to a specific conversation the operator pointed me toward.” Established ghost (programming void): 22–35% reactivation rate with peer connection offer vs. 15–22% without. The lift is smaller but meaningful for the programming void population, where the ghost formation was triggered by content-relevance decay rather than social anxiety about first posting.	Medium (8–15 minutes to identify a relevant peer connection and frame the offer specifically). The operator must have enough community knowledge to identify a genuinely relevant match; a generic “let me introduce you to someone great” offer without specificity produces the same response rate as the no-offer approach.	Low to moderate. Members who respond to a peer connection offer are responding to the prospect of a specific useful connection; adverse selection is low because the offer does not provide a financial incentive. The risk is that the matched peer member is not interested in receiving the connection, which is why the offer is framed as a tag-in (a less intrusive mechanism) rather than a bilateral introduction that requires the connected member’s advance agreement.	The operator does not know the ghost member’s goal category or recent interests well enough to identify a specific, relevant peer match. A non-specific peer connection offer (“I know people who might be useful for you”) is worse than no offer because it implies the operator does not have a specific match, which undermines the personalised community value proposition.
Hold offer (one-month billing pause)	Established ghost (second touch and beyond, or any touch at day 60+ of silence). Terminal ghost (all outreach). Also appropriate for life-circumstances Early ghosts where the operator has explicitly identified an external circumstance as the cause.	The operator offers a 30-day pause on billing, with automatic resumption at the end of the pause period. The pause is offered unconditionally (not contingent on re-engagement during the pause) and with explicit terms: billing resumes on a specific date, the member can cancel before that date at no penalty, and the hold does not extend the membership duration (it is a pause, not a free extension). The unconditional framing is critical: a conditional hold (“I can pause your membership if you attend at least one event during the pause”) reads as a retention mechanism rather than a genuine expression of flexibility, and conditional holds produce lower acceptance rates and higher cancellation rates than unconditional holds.	Established ghost: 18–28% reactivation rate with hold offer vs. 15–22% without (at first touch) and 12–20% without vs. 15–25% with (at second touch). The lift at second touch is more meaningful than at first touch. Terminal ghost: 4–9% reactivation rate regardless of whether the hold offer is included, but the hold offer acceptance rate at the Terminal tier (12–22% of members who receive it) is significant as a churn-delay mechanism: an accepted hold gives the operator 30 days to design a welcome-back sequence for the hold end date, which produces higher reactivation probability than no structural re-entry moment. Members who accept the hold and then cancel at hold end (rather than returning) enter the win-back sequence with a documented 30-day future return intention, which the win-back sequence can reference.	Low (2–3 minutes to add the hold offer to the existing DM). If the billing system requires manual hold setup, add 5–10 minutes per accepted hold. Communities using Foothold can automate the hold offer notification via the Day 7 at-risk flag, which surfaces Established and Terminal ghost members for manual hold-offer outreach from the operator dashboard.	Low to moderate. The hold offer attracts responses from two populations: genuinely circumstantial ghosts (who intend to return and accept the hold as relief from paying while they are unable to engage) and price-inertia subscribers (who may accept the hold as a delay of the cancellation they were going to make anyway). The second population produces accepted holds that convert to cancellations at hold end rather than reactivations, which has a short-term churn-delay effect but does not improve reactivation. Distinguishing the two populations in advance of hold acceptance is not reliably possible, which is why the hold offer is presented unconditionally and the hold-end reactivation sequence is used to convert as many accepted holds as possible into genuine re-engagements.	The member is in the Early ghost tier and has shown no signs of a life circumstance or circumstantial absence. Introducing billing conversations into Early ghost outreach is counterproductive in most cases. Also avoid the hold offer for members who are less than 30 days from their annual renewal, where the hold may create confusion about annual billing terms.

Table 6: Reactivation vs. prevention priority matrix

When to allocate limited operator time to ghost member reactivation versus churn prevention versus new member acquisition, based on the two highest-signal metrics for operator time allocation decisions: the current week-one activation rate (the leading indicator for ghost formation rate in 60–90 days) and the current ghost member percentage (the lagging indicator for whether past activation quality has produced a ghost-heavy membership). The two-metric diagnostic identifies four operator situations, each with a different allocation recommendation and a specific highest-leverage action. Revenue impact estimates assume a 200-member community at $99/month ARPU; scale proportionally for different community sizes and price tiers.

Situation	Week-one activation rate	Current ghost member %	Primary allocation	Secondary allocation	Highest-leverage single action	Expected revenue impact (200 members, $99/mo)
Healthy pipeline, manageable ghost rate	45%+ week-one activation	Under 15% ghost members	New member acquisition (50% of reactivation-prevention-acquisition time). The community’s onboarding is producing good activation, and the ghost population is small enough that reactivation is a maintenance task rather than a revenue emergency. This is the situation where adding new paying members produces the highest marginal revenue return per operator hour because the activation funnel is working and will convert a high proportion of new members into long-tenure contributors.	Ghost member reactivation (30% of time) for the existing 15% ghost population. Early ghost monitoring (weekly) is sufficient at this ghost rate; Established ghost outreach for the smaller fraction who graduate from Early without reactivating. Churn prevention at 20%: focus on members who are declining from Healthy to At-Risk tier before they cross into ghost status.	Maintain and improve the Day 3 conditional nudge to keep the week-one activation rate above 45%. At 45% activation with a 200-member community and $99/mo ARPU, a 5pp improvement in activation rate (to 50%) produces approximately $3,960 in additional annual cohort LTV from the improved reactivation rate and reduced ghost formation.	Adding 10 new members per month at 45% activation produces $5,346 additional annual LTV per new member cohort. Combined with the low ghost rate (minimal revenue leakage), this is the highest-return situation for acquisition investment.
Strong activation, growing ghost backlog	45%+ week-one activation	15–30% ghost members	Ghost member reactivation (50% of time). The activation funnel is healthy, but the ghost member population is larger than the healthy baseline, indicating that either the Established ghost reactivation has not been executed consistently (Early ghosts are graduating to Established without intervention), or the community’s programming void rate has been high enough to produce a spike in Established ghost formation. Reactivation is the priority because the ghost population represents an immediate revenue leakage (15–30% of paying members are at elevated churn risk) and the activation funnel is already working well enough that new member investment has a good base to land on.	Churn prevention (30% of time): ensure at-risk members (Healthy to At-Risk transitions) are caught before they cross into ghost status, which would increase the ghost backlog further. Acquisition at 20%: do not pause acquisition while addressing the ghost backlog, but reduce the investment relative to the Healthy pipeline situation.	Execute the Established ghost sequence (two DMs plus event invitation) for all members at day 35–56 of their silence period. At a 15–28% reactivation rate for Established ghosts, reactivating 25% of the ghost population (at a 20% ghost rate in a 200-member community = 40 ghosts, 10 reactivated) produces approximately $11,880 in retained annual revenue at $99/mo per reactivated member.	At $99/mo ARPM and a 20% ghost rate, the 200-member community has 40 ghost members generating above-average churn risk. Moving 10 of those 40 from ghost to active status prevents approximately $11,880 in annual churn at the average ghost member churn rate (65–75% annual churn for Established+Terminal ghosts vs. 20–30% for active members).
Activation crisis, low ghost rate	Below 30% week-one activation	Under 15% ghost members	Onboarding improvement (60% of time) — not reactivation. A below-30% activation rate means the community is generating a high volume of never-activated ghosts in every new cohort; fixing the onboarding sequence is the highest-leverage action because every percentage point of activation improvement prevents future ghost formation at a cost structure that is far lower than retroactive reactivation outreach. The Day 3 conditional nudge is typically the highest-leverage single fix: communities that do not have an active Day 3 nudge see never-activated rates of 35–55% vs. 15–25% with the nudge.	Ghost member reactivation at 25% (for the current under-15% ghost population, which is a manageable maintenance task). Churn prevention at 15%: the activation crisis will begin producing Established ghosts in 60–90 days as the high never-activated rate from current cohorts matures, so upstream churn prevention for current active members is more valuable than it will be once the ghost backlog grows. Acquisition at 0%: pause new member acquisition until the activation rate is above 35%; adding new members to a community with a below-30% activation rate grows the ghost population without proportionally growing the revenue, because the non-activated ghosts are high-churn-probability members.	Implement or fix the Day 3 conditional nudge (fires only to members who have not posted at Day 3). At a 200-member community with 30% activation vs. 45% activation with a functioning Day 3 nudge, the improvement in activation rate produces 30 additional activated members per 100 new joins, each with a 72–88% three-month renewal rate vs. 30–45% for never-activated members — a difference of approximately $4,752–$5,148 in three-month cohort revenue per 100 new joins.	The revenue impact of fixing the activation crisis (15pp improvement in activation rate) exceeds the revenue impact of reactivating the current small ghost population by a factor of 3–5x over a 12-month horizon, because the activation fix applies to every future cohort while the reactivation benefit is one-time for the current ghost population.
Activation crisis, large ghost backlog	Below 30% week-one activation	Over 30% ghost members	Triage mode: split operator time between onboarding improvement (40%) and Established ghost reactivation (35%), deferring acquisition entirely and reducing churn prevention to a monitoring function (25%). This is the most resource-constrained situation: the high ghost rate indicates historical activation failures are accumulating, and the low current activation rate indicates the problem is ongoing. Neither problem can be addressed first without the other getting worse, so triage mode allocates roughly equal time to fixing the cause (onboarding) and managing the most urgent downstream effect (Established ghost reactivation, where the intervention window is closing).	Terminal ghost triage at 10% of time: do not invest significant time in Terminal ghost reactivation while the crisis is active; a single touch per Terminal ghost (hold offer only, no peer connection, no programming reference) is the maximum appropriate investment at this stage. Early ghost monitoring at 15%: flag Early ghosts weekly but focus first-touch resources on the 10–14 day window for lapsed-contributors; delay the never-activated sub-population to the Day 3 nudge fix (part of the onboarding improvement work). Pause new member acquisition: adding more members to a community with a high ghost backlog and a low activation rate grows the ghost backlog faster than it grows active membership.	Two parallel highest-leverage actions: (1) Implement Day 3 conditional nudge for new cohorts starting immediately. (2) Execute hold-offer DMs for all Established ghosts in the day 35–70 window. The combination of activating new cohorts at a higher rate and converting some of the Established ghost population through hold offers produces the fastest stabilisation of the ghost rate before it reaches 40%+ of the membership (at which point the community’s activity density drops below the threshold that makes it feel worth participating in for any member, creating a spiral that is very difficult to reverse).	At a 30% ghost rate in a 200-member community ($99/mo ARPM), approximately 60 members are ghost-tier high-churn-risk. At 65–75% annual churn for Established+Terminal ghosts, this population is losing approximately $46,200–$53,460 per year in annual revenue to ghost-driven churn. A 25% reactivation success rate for the Established ghost population (15 members of the 60) prevents $17,820 in annual churn, less the operator time cost of the reactivation sequence.

Table 7: Graduation criteria and when to stop

The specific conditions that trigger graduation from active reactivation outreach to the win-back pre-queue, with the final action to take at graduation, the expected reactivation probability if outreach is eventually resumed (it is not resumed — this is the win-back probability), and the note on what makes each tier’s graduation criteria different. Graduation is not failure; it is the correct operational decision when the intervention probability drops below the threshold that justifies continued operator time investment relative to the other operator responsibilities competing for the same time. The graduation criteria are calibrated to the intervention probability data in Table 1 and the operator time cost data in Table 5; communities with significantly higher or lower operator capacity may adjust the criteria, but the current calibration represents the point where additional reactivation outreach produces less than $50 of expected retained revenue per hour of operator time invested — below the threshold that makes it a better use of time than Early ghost monitoring or churn prevention.

Ghost tier	Graduation trigger	Final action at graduation	Win-back probability (if member eventually cancels)	Why this criteria, not more or fewer touches
Early ghost	One personal DM sent in the day 10–14 window with no response within 14 days. The member then advances to the Established ghost tier at day 31; graduation from the Early ghost active outreach phase occurs at day 24–28 (14 days after the single DM was sent). No additional Early ghost outreach is sent; the Established ghost sequence begins fresh at day 35–42 without referencing the Early ghost DM that did not receive a response.	Flag the member in the billing system for monitoring at the next renewal date. Do not note the lack of response to the first DM in the member record in a way that will colour the Established ghost outreach; the Established ghost DM should not reference the unanswered Early ghost DM, because referencing an unanswered message in the next message creates a passive-aggressive dynamic that is counterproductive. The Established ghost DM is a fresh outreach.	15–25% win-back probability for Early ghosts who eventually cancel without reactivating. The win-back probability is higher than for Established and Terminal ghost cancellations because Early ghosts who cancel are typically in the month-one churn cliff, where the cancellation is often driven by expectations-mismatch or onboarding failure rather than a fundamental community-value verdict. Month-one cancellations are more reversible at 90–180 days than month-three or month-six cancellations because the member’s professional context is more likely to have returned to a state where the community’s value is relevant.	One DM within the optimal window is the full Early ghost intervention because the marginal value of a second touch is low relative to the first: response rate data shows that members who do not respond to a day-10–14 DM respond to a second Early ghost DM at rates below 10%, which does not justify the operator time investment compared to the 35–55% response rate for the first Established ghost DM in the day 35–42 window. Sending a second Early ghost DM also reduces the response rate for the first Established ghost DM by making the member feel that the operator is escalating contact rather than transitioning to a new outreach cadence.
Established ghost	Two personal Slack DMs (Touch 1 and Touch 2 per Table 3) with no response to either, followed by one event invitation (Touch 3) with no attendance or response within 21 days. Total elapsed time from first Established ghost touch to graduation is approximately 35–42 days (Touch 1 at day 35–42, Touch 2 at day 49–56, Touch 3 at day 70–77, graduation at day 91–98). If the hold offer was accepted in Touch 1 or Touch 2, graduation from active reactivation occurs when the hold period ends without the member returning to active posting. Hold-end graduation triggers the Terminal ghost sequence (one final touch at the hold-end date) before the win-back pre-queue.	Flag for Terminal ghost sequence initiation at day 95–105 (or at the hold-end date, if earlier). Add to billing system watch list for renewal review. If the member cancels before the Terminal ghost touch is sent, move immediately to the win-back active sequence without first sending the Terminal ghost touch — the cancellation event supersedes the Terminal ghost sequence and triggers the win-back three-email sequence directly.	10–18% win-back probability for Established ghosts who eventually cancel without reactivating. Lower than Early ghost win-back probability because Established ghost cancellations are more likely to be intentional decisions (the member evaluated the community during the silence period and concluded it was no longer worth paying for) than Early ghost cancellations (which are more likely to be onboarding failures that could be addressed with an improved reactivation offer). Established ghosts who received a hold offer and declined it (choosing to stay rather than pause, but still not re-engaging) have a higher win-back probability (18–28%) than those who did not receive a hold offer, because the hold offer conversation gave the operator information about the member’s circumstance that the win-back sequence can reference.	Three touches over 35–42 days represents the intervention ceiling for the Established ghost tier based on the probability-per-touch data: Touch 1 produces a 15–28% reactivation rate, Touch 2 produces an incremental 6–12% (for members who did not respond to Touch 1), and Touch 3 (event invitation) produces an incremental 3–7%. A fourth touch at day 95+ would produce below-3% incremental reactivation probability while consuming operator time that produces higher return in Early ghost monitoring and Terminal ghost touches.
Terminal ghost	One personal DM (with hold offer) sent at day 95–105 with no response within 21 days. Total elapsed time from Terminal ghost tier entry to graduation: 21 days. This is the shortest graduation timeline of the three tiers, reflecting the low marginal reactivation probability for Terminal ghosts who do not respond to a single personal outreach. If the hold offer in the Terminal touch is accepted, the graduation is delayed until the hold period ends (typically 30 days from acceptance). Hold-accepted Terminal ghosts who return to posting at hold end are moved to the Early ghost monitoring queue (they are newly re-active but at elevated re-ghosting risk); hold-accepted Terminal ghosts who do not return to posting at hold end are graduated to the win-back pre-queue immediately.	Add to win-back pre-queue (active monitoring for the cancellation event). Do not initiate any additional active outreach. When the cancellation event occurs (the member cancels or payment fails), activate the win-back three-email sequence described in the win-back email sequence reference card. The Terminal ghost touch is the last operator-initiated communication until the win-back sequence, which is triggered by the member action (cancellation), not by operator schedule. Between graduation and cancellation, the only operator action is to ensure the renewal is processed correctly (no billing errors that could trigger a customer service interaction that should be handled as a separate matter from the reactivation/win-back relationship).	6–12% win-back probability for Terminal ghosts who eventually cancel. The low probability reflects that Terminal ghosts who cancel are typically at the end of the inertia period described in the root cause taxonomy (Table 2), where the cancellation decision was triggered by a budget review or an active fee evaluation rather than a specific community-value verdict. Members in this category have typically not been thinking about the community for months; the win-back sequence must first re-establish their community memory before making a re-enrollment invitation, which is a longer and less certain process than the win-back for a month-one canceller whose community memory is fresh. Terminal ghosts who received the Terminal touch and responded (even without reactivating) have higher win-back probabilities (12–18%) because the Terminal touch conversation kept the community relationship active even as the billing relationship was approaching its end.	One touch only for Terminal ghosts because the probability data is unambiguous: response rate to a first Terminal ghost touch is 8–18%, and response rate to a second Terminal ghost touch (without a new trigger event like a community milestone or a programming change that specifically matches the member’s goal category) is below 4%. The operator time cost of the second Terminal ghost touch ($0.50–$2 of expected retained revenue per hour at below-4% marginal reactivation probability) is lower than the alternative use of that time (Early ghost monitoring at $50–$120 of expected retained revenue per hour at 35–55% reactivation probability). The single-touch protocol is not an expression of giving up on the member; it is a resource allocation decision that produces better community-level outcomes by concentrating limited reactivation time in the highest-yield windows for each tier.

The win-back probability data in Table 7 (6–25% depending on ghost tier at cancellation) is the reason that preventing ghost formation — through the Day 0/Day 3/Day 7 onboarding sequence — is more valuable per operator hour than even the best-executed reactivation program. A member who activates in week one, builds a peer relationship by day 30, and renews at month three represents retained revenue that did not require any reactivation investment. A member who ghosts in month two and is successfully reactivated in month three represents retained revenue at the cost of 8–20 minutes of operator reactivation outreach. A member who ghosts in month two, fails to reactivate, cancels at month four, and is won back after cancellation represents retained revenue at the cost of the full reactivation sequence plus the win-back sequence. The cost and probability structure of these three paths makes the Day 0 onboarding sequence the highest-ROI intervention in the member lifecycle, and the Foothold three-touch system — Day 0 DM, Day 3 conditional nudge, Day 7 scorecard — is specifically designed to minimise ghost formation before it requires the reactivation investment described in this reference card. Use the Foothold community health check to see how your current activation rate compares to the benchmarks in this reference card and which ghost tier your community is most likely producing at its current onboarding quality level.

Frequently asked questions

What counts as a ghost member in a paid community, and how do you identify them without Slack analytics?

A ghost member is a paying member who has not posted, reacted, or replied in the Slack workspace for a defined period — the standard threshold is 30 days of no visible Slack activity, but the operationally useful definition segments by tier (7–30 days = Early ghost, 31–90 days = Established ghost, 90+ days = Terminal ghost). Without Slack analytics, the practical identification method is a member export cross-referenced with a manual channel scan: export the Slack member list, sort by last-active date if your plan surfacess it, and scan your primary activity channels for member names that have not appeared in the past 30 days. For a 200-member community this takes approximately 15–20 minutes and produces a sufficiently accurate ghost member list to begin targeted outreach. The most important segmentation is between never-activated ghosts (no post in any channel ever) and lapsed-contributor ghosts (posted previously, now quiet), because these two populations require different interventions: never-activated ghosts need a re-try of the activation sequence; lapsed-contributor ghosts need a community re-entry prompt. See the member health score reference card for the automated four-tier scoring system that replaces the manual channel scan with a systematic weekly health score per member.

What should the first personal DM to a ghost member say, and how long should you wait before sending it?

For an Early ghost (lapsed-contributor sub-population): send the first DM at day 10–14 of the silence period. The DM contains: (1) a specific reference to the member’s most recent post or community interaction by name and topic; (2) one specific community development this week that is relevant to their stated goal category; (3) a low-bar re-entry action (a thread to react to, a question they can answer); (4) an explicit opt-out without pressure. Do not mention billing, membership status, or the observation that they have been quiet. For a never-activated ghost: send a Day 7 peer introduction DM (part of the three-touch onboarding sequence) at day 7 — this is the appropriate intervention for never-activated members before they graduate from Early ghost to Established ghost. The timing data is specific: an Early ghost lapsed-contributor DM sent at day 10–14 produces a 45–55% reactivation rate; the same DM sent at day 25–30 produces a 22–35% reactivation rate. The 14-day window is the single largest determinant of Early ghost reactivation success, which is why weekly ghost monitoring is more effective than monthly monitoring for this tier.

What re-activation offer should you make to a member who has been silent for 60 or more days?

A member at 60+ days of silence is in the Established ghost tier (day 35–90) or approaching the Terminal ghost boundary, and the correct offer is a hold offer (30-day billing pause, unconditional, billing resumes automatically) rather than a discount or a community re-engagement pitch. The hold offer works at this silence duration because it addresses the practical barrier that a 60-day-silent member faces: “should I keep paying for something I’m not using?” The hold converts a forced binary choice (keep paying or cancel) into a three-option decision (keep paying, pause, or cancel), and the pause option captures members who intend to return but are not ready to re-engage in the current billing period. A discount offer at this stage is less effective than a hold because it addresses a price concern that most Established ghosts do not primarily have; the barrier is motivation and habit, not price. See Table 5 for the full offer decision table and the adverse selection risk profile for each offer type.

When is it time to stop trying to reactivate a ghost member and move them to the win-back sequence?

Per-tier graduation criteria: Early ghost: one personal DM with no response in 14 days → graduate to Established ghost monitoring queue. Established ghost: two personal DMs with no response to either, plus one event invitation with no attendance in 21 days → graduate to Terminal ghost sequence initiation. Terminal ghost: one personal DM with hold offer with no response in 21 days → graduate to win-back pre-queue. The graduation criteria are not arbitrary patience thresholds; they are calibrated to the marginal reactivation probability per additional touch for each tier. A Terminal ghost who has not responded to one personal DM with a hold offer has a below-4% probability of responding to a second touch, which does not justify the operator time relative to Early ghost monitoring or Established ghost outreach. Graduation is the correct operational decision at these points, not a failure. See the win-back email sequence reference card for the three-email post-cancellation sequence that follows from the win-back pre-queue.