Retention & Lifecycle
Paid community offboarding: the three-touch departure sequence that recovers what cancellations cost
When a member cancels their paid community subscription, most operators do nothing. The billing tool processes the request, Stripe sends a churn notification, Slack removes the member’s workspace access, and the relationship ends. The operator’s involvement is passive — they receive the notification, they absorb the MRR loss, and they move on. The reason this costs more than operators realise is not just the immediate revenue loss; it is the information loss. Every cancelled member carries a reason for leaving that, if surfaced and acted on, would prevent the next several members with the same profile from leaving for the same cause. Most operators never collect it. The three-touch departure sequence — a hold offer before the cancellation processes, a qualitative exit interview within 24 hours of confirmation, and a time-limited reactivation invitation at 60 days — addresses both losses simultaneously: it recovers a meaningful fraction of would-be permanent departures and generates the diagnostic data that prevents the next wave.
The default offboarding protocol and what it costs
Paid community operators who have not deliberately designed an offboarding protocol typically experience cancellations as a one-way valve. A member opens a cancellation link, fills out a “reason for cancelling” dropdown with one of five pre-set options, the billing tool confirms the cancellation, and access is removed. If the billing tool sends an automated cancellation confirmation email, the operator might reply to it. Most do not. The member is gone.
The cost of this default is higher than the MRR number suggests. Consider a 200-member paid community at $99/mo with a 4% monthly churn rate — approximately 8 cancellations per month, which is a healthy rate for this community size. Each cancellation represents $1,188 in expected LTV lost (at a typical 12-month average tenure for a cancelling member). Eight cancellations per month is $9,504 in expected LTV leaving the community monthly. Across 12 months, that is approximately $114,000 in expected LTV that is permanently gone — because no structured attempt was made to recover any fraction of it, and because the diagnostic data from each departure was never collected and never used to close the causal loop upstream.
The operators who do run structured offboarding protocols report two categories of return. The first is direct recovery: hold offers convert 24–36% of cancellation intents into pauses rather than departures; 60-day reactivation invitations convert 12–20% of departed members back into active members. In a community with 8 cancellations per month, a 30% hold offer acceptance rate means 2–3 members per month who would have left are instead taking a 30-day pause — and approximately 60% of pause-takers renew after the pause period. The 60-day reactivation invitation at 15% acceptance means roughly 1 member per month returning from a recent departure cohort. Together, these two recovery mechanisms return $200–$500/mo in MRR to a 200-member community at $99/mo, or $2,400–$6,000/yr, at an operator time cost of approximately 15 minutes per week. The ROI on structured offboarding at this community size is typically among the highest of any retention investment available to the operator.
The second return is diagnostic: exit interviews generate the qualitative data that reveals the specific systemic causes of departure. Aggregated over a quarter (24–32 exit interviews at 35–55% response rate), this data almost always reveals one or two dominant causes responsible for 60–70% of all cancellations. Addressing those causes in the onboarding sequence, programming calendar, or messaging reduces the cancellation rate for the next cohort. The diagnostic return compounds in a way the direct recovery does not: a reduced monthly churn rate on a growing community is worth substantially more than a slightly higher recovery rate on departing members.
Touch 1: the hold offer before the cancellation processes
The first touch in the departure sequence is a hold offer — an alternative to outright cancellation presented to the member before the cancellation is processed. The most common form is a pause option: the member’s subscription is frozen for 30 or 60 days at the same rate, with automatic reactivation at the end of the pause period unless they explicitly cancel during the pause window. A secondary form is a downgrade path: if the community has a lower-priced tier (or a free alumni access level), offering the member a downgrade rather than a departure preserves the relationship and keeps a future reactivation path open. A third form is a one-time concession: a 50% discount for the next billing cycle presented as a loyalty acknowledgement rather than a desperation offer.
Timing is the most critical variable in hold offer performance. An offer presented before the cancellation processes converts at 24–36% for personalised messages at $49–$99/mo price points. The same offer presented 24 hours after the cancellation has been confirmed converts at under 8%. The reason is not primarily about the financial appeal of the offer — it is about the member’s mental state. Before the cancellation processes, the member is still in an active decision frame. They are weighing whether to leave against whether not to leave; the offer gives them a third option they had not considered. After the cancellation processes, the member has closed the decision. They have left. Opening a new decision about whether to return requires a significantly higher perceived benefit to overcome the inertia of departure. A pause offer at 24 hours post-cancellation is asking a fundamentally different question than a pause offer at the moment of cancellation intent.
The practical implementation for a community without automated cancellation flow tooling is a personal Slack DM sent within the first hour of the cancellation intent signal. If the operator’s billing tool sends a churn alert (Stripe does; Memberstack does; most tools above $100/mo do), that alert is the trigger. The DM format: one sentence acknowledging you received their cancellation request, one sentence asking if a 30-day pause would be useful given whatever context you know about their situation, and a direct question requiring a yes or no. The message should be personal — referencing the member’s name, their area of focus in the community, or a recent thing they mentioned or posted — not templated. Operators who send a personalised DM in this window see significantly higher acceptance rates than those who send a generic “we noticed you cancelled” message, because the personalised version signals that a real human operator noticed and cared, whereas the generic version reads as automated and is dismissed accordingly.
The hold offer should not include a discount or price concession unless the member has explicitly cited price as their cancellation reason. Offering a discount to a member who is leaving because of an engagement deficit signals that the operator thinks the problem is price, which is wrong, and converts acceptance into a price-anchoring trap: the member returns at the discounted rate, does not re-engage at a higher level, and cancels again at the end of the discounted period. Reserve the discount variant for members whose exit interview or stated reason confirms price misalignment as the primary cause. For all other causes, a pause or downgrade preserves the relationship without setting a discount precedent.
For deeper context on the rate benchmarks for pause acceptance by community size and price tier, the paid community cancellation rate reference card includes the intervention ROI table comparing hold offer performance against post-cancellation win-back across each root cause category.
Touch 2: the exit interview within 24 hours
The second touch runs within 24 hours of cancellation confirmation — regardless of whether the hold offer was accepted or declined. Its purpose is diagnostic, not recovery: the exit interview is the mechanism for collecting the qualitative data that reveals why the member left and what pattern that data point belongs to across the broader departure cohort. A member who accepts the hold offer should still receive the exit interview message, because even a member who paused has signalled that something pushed them to the cancellation decision, and that signal is worth understanding before the pause ends and the member either renews or departs for real.
The format that generates the highest response rate is a short personal message containing one open question. Not a survey link. Not a multi-question form. One question, asked conversationally, with a one-sentence framing that explains why you’re asking. The question: “What was the one thing that would have made you stay?” The framing: “I’m asking every member this one question when they leave — not to change your mind, but so the next person who joins doesn’t run into the same thing.”
This framing is load-bearing. It accomplishes three things simultaneously. First, it signals that the message is genuinely diagnostic rather than a retention pitch — the member is not being pressured to return; they are being asked to help the operator improve the community for the next person. This significantly reduces the member’s defensive response pattern, which is the most common reason for non-response in exit surveys: the member does not want to be argued with, does not want to re-litigate their cancellation decision, and does not want to feel obligated to soften their criticism out of politeness. The “not to change your mind” framing explicitly removes all three of these concerns. Second, it invokes reciprocity — the member has been part of a community, has received value from it at some point, and is being asked to contribute something small in return. Third, the forward framing (“so the next person doesn’t run into the same thing”) makes the respondent feel that their answer has a direct impact on the community’s future — which it does, if the operator actually uses the data.
The single question format also outperforms multi-question surveys on data quality, not just response rate. When asked to select from a list of reasons or to rate multiple dimensions of their experience, members tend to distribute their responses across several dimensions even when one cause was genuinely primary. The single open question — “the one thing” — forces ranking. The answer names the cause that was actually load-bearing for the cancellation decision, rather than the full list of things that could have been better. Over a quarter of exit interviews (typically 8–18 responses at 35–55% response rates on 24–32 departures), the single-question format generates a data set where the top one or two causes visibly dominate — which tells the operator exactly where to invest improvement effort. Multi-question formats diffuse this signal across five to ten rated dimensions and make it difficult to identify the one intervention that would have the most impact on the next cohort’s retention.
Typical exit interview responses cluster into four categories, which map directly to the four churn root causes covered in the paid community churn reference: expectations misalignment (“the community was less active than I expected”, “the level of discussion was more beginner than practitioner”); engagement deficit (“I read a lot but never found a reason to post”, “I didn’t know anyone and felt awkward jumping in”); programming void (“I got what I came for in the first two months and ran out of things to do”, “the content felt repetitive after month four”); and pricing misalignment (“I wasn’t using it enough to justify the cost”, “I’m pausing spending across the board”). The job of exit interview analysis is not to read each response individually but to count the theme distribution across a quarter of departures and find the category with the highest concentration. That category is the primary systemic cause in the current community state, and it is almost always tractable with a specific structural intervention.
One important operational note: the exit interview response should receive a reply, even if brief. If the member says “I never felt like I knew anyone” and the operator says nothing in response, the member departs with the impression that the exit interview was a data-extraction exercise rather than a genuine conversation. A two-sentence reply (“that’s genuinely useful to hear, and it’s not the first time someone has said that to me. We’re working on building peer introductions into the first week for new members. Thank you for taking the time.”) closes the loop, leaves the member with a positive impression of the operator, and keeps the 60-day reactivation path warm.
Touch 3: the reactivation invitation at 60 days
The third touch runs 60 days after the cancellation was confirmed. It is a personal message — not an automated re-engagement campaign, not a discount offer blast, not a “we miss you” template — that does three things: acknowledges the time that has passed, names a specific change or development in the community that has happened since the member left, and extends a time-limited invitation to return at the original rate with no new onboarding overhead.
The 60-day timing is not arbitrary. At 30 days, the member is still in a post-cancellation transition period: they have just recently left, they may have not yet found a replacement for the value they were getting, and a message this early reads as a retention scramble. At 90 days, the member has settled into a new rhythm that does not include your community — the cognitive cost of re-integrating is higher, the urgency of the opportunity is lower, and acceptance rates reflect both. The 60-day window captures members who are far enough removed that they can evaluate the invitation calmly, but close enough that the community is still familiar and the reactivation overhead is perceived as low. Acceptance rates for personalised reactivation invitations at 60 days are 12–20% for communities where the exit interview suggests a fixable cause; at 90 days, this rate drops to under 8%.
The “specific change or development” element is what separates a reactivation invitation from a win-back email. A win-back email says: “We’d love to have you back, here’s 20% off.” A reactivation invitation says: “When you left in May you mentioned that you found it hard to meet other members in the early-stage operator cohort. We added a monthly small-group cohort for that exact group in June — it’s been running for two months and the three members in your role category have all stuck around. There’s a spot for you if you want to rejoin at your original rate before the next cohort starts July 15th.” The specificity demonstrates that (a) the operator remembered what the member said, (b) the operator acted on it, and (c) there is now something in the community that addresses the specific cause of departure. This is a substantially different value proposition than a generic discount, and members respond to it accordingly.
This is why the exit interview data matters not just for improving the community in the abstract but for making the reactivation invitation specific and credible. An operator who collects exit interviews and acts on the data has, at 60 days, a genuine community development to point to. An operator who did not collect exit interviews is sending a generic win-back message that cannot reference anything specific, because there is nothing specific to reference. The three touches in the departure sequence are not independent: exit interview data fuels reactivation invitation specificity, and reactivation specificity drives the 12–20% acceptance rate that makes the 60-day touch worth running.
For the complementary perspective on re-engagement — the DM protocol for members who have not yet cancelled but show 21-day silence signals — see the win-back DM guide for cancelled Slack community members, which covers the language and timing for outreach to members at the departure boundary before a formal cancellation intent has been signalled.
Working out the math: 200-member community at $99/mo
The following is a worked example for a 200-member paid Slack community at $99/mo. The numbers use benchmarks from operators running structured offboarding protocols; they are meant to illustrate order of magnitude, not exact projections for any specific community.
Baseline (no offboarding protocol): At 4% monthly churn, approximately 8 members cancel per month. All 8 cancellations process immediately. The community loses $792/mo in MRR and $9,504/mo in expected LTV at a 12-month average cancellation-tenure. Annualised: $9,504/mo in MRR lost, $114,048 in expected LTV lost permanently. The operator recovers zero from departures. The only offsetting factor is new member acquisition.
With hold offer at 30% acceptance: Of the 8 cancellation intents per month, 2–3 members accept a 30-day pause offer. Assuming 60% of pause-takers renew after the pause (typical for members whose exit interview reveals a transient cause such as a busy period or a temporary budget constraint): 1.5 members per month stay as active subscribers who would otherwise have left permanently. At $99/mo, this is $148.50/mo in retained MRR from the hold offer alone, or $1,782/yr. The operator investment: approximately 8 minutes per cancellation intent (time to send a personalised DM, respond to the reply, and log the outcome) × 8 cancellation intents per month = approximately 64 minutes per month of operator time at the hold offer touch.
With exit interviews at 45% response rate: Of the 5–6 members who did not accept the hold offer and cancelled, 2–3 per month respond to the exit interview question. Over a quarter, the operator collects 6–9 exit interview responses. By month 3, a pattern is visible in 70–80% of these cases. If the dominant pattern is an engagement deficit cause (the most common pattern in communities 150–300 members, per the cancellation rate by tenure analysis), the operator implements a targeted Day 30–45 re-engagement protocol for members with low contribution counts. Conservative estimate: this reduces the monthly churn rate from 4% to 3.2% over 60 days of operation (0.8 percentage point reduction). In a 200-member community, 0.8 percentage points = 1.6 fewer departures per month = $158.40/mo in retained MRR, or $1,900/yr. This is a compounding benefit: as the community grows, the absolute MRR retained from the churn rate reduction grows proportionally.
With reactivation invitations at 15% acceptance: From the monthly cohort of 5–6 permanent cancellations (after hold offer acceptances), the operator sends personalised reactivation invitations at 60 days. At 15% acceptance: 0.75–0.9 reactivations per month from the 60-day touch. At $99/mo: $74–$89/mo in recovered MRR, or $889–$1,068/yr. The operator investment: approximately 6 minutes per outreach (reviewing exit interview notes, drafting a specific invitation, logging the outcome) × 5–6 messages per month = approximately 33 minutes per month.
Combined recovery and prevention: Across the three touches, the operator’s structured offboarding protocol returns approximately $320–$400/mo in direct MRR recovery (hold offer + reactivation) and approximately $158/mo in prevented future departures (churn rate reduction from exit interview data use) — totalling $478–$558/mo, or approximately $5,700–$6,700/yr, against a 200-member community that was losing $9,504/mo in expected LTV at baseline. Total operator time cost of the protocol: approximately 97 minutes per month, or roughly 24 minutes per week. The hourly ROI on this time investment, at community median price of $99/mo, is approximately $290–$345 per operator hour — comparable to the ROI of the Day-3 onboarding intervention on non-activated new members, which the paid community member LTV reference puts at $345–$730 per operator hour depending on community size and price tier.
What to do with exit interview data
Exit interview data has two uses: immediate (informing the reactivation invitation) and systemic (informing structural changes to the community). The immediate use runs automatically when the three-touch protocol is followed: the exit interview response at 24 hours becomes the source material for the personalised reactivation invitation at 60 days. If the member said “I never found a first contribution moment that felt natural,” the 60-day invitation references a specific addition to the community’s onboarding protocol that addresses this (a Day 14 contribution prompt, a new member spotlight format, a weekly thread designed for first posts). If there is nothing to reference yet — because the exit interview pattern has not yet generated a community change — the invitation is still personalised but leans more on the relationship and on the time-limited offer than on a specific community development.
The systemic use requires aggregation. Individual exit interview responses are anecdotes; a quarter’s worth of responses with a clear dominant theme is a finding. The operator’s job is to accumulate exit interview responses in a simple log — a spreadsheet row with the member’s name, tenure at cancellation, exit interview response (verbatim), and the cause category it belongs to (expectations misalignment, engagement deficit, programming void, pricing misalignment) — and review the log quarterly to identify the dominant pattern.
The quarterly review produces one actionable finding in the vast majority of cases: a single cause category producing 50–70% of all departures. In a community where 60% of exits over the past quarter cited engagement deficit causes (“I never felt like I knew anyone”, “I didn’t know where to post”, “I ran out of people to talk to”), the structural intervention is a new member introduction protocol that creates a specific named peer connection within the first 14 days. Operators who run this intervention in response to a dominant engagement deficit signal typically see a 0.8–1.5 percentage point churn rate reduction in the following quarter.
The compounding effect is the overlooked return on exit interview investment. A single member’s exit interview response is worth the 6 minutes it takes to send and read. A quarter’s worth of exit interview responses that identify a fixable systemic cause is worth 0.8–1.5 percentage points of churn rate reduction on a growing community — which, at $99/mo and 200 members growing at 5% per month, compounds to $18,000–$30,000 in additional cumulative retained MRR over 12 months. This is the reason the exit interview is the most analytically valuable touch in the departure sequence even though it produces zero direct revenue recovery. Its value is upstream prevention, not downstream recovery.
The NPS question — a common alternative to the exit interview — produces a number but rarely produces an actionable finding because it does not force ranking. A departing member with an NPS of 7 (“passive”) could be leaving for any of the four root causes; the NPS score does not distinguish them. The single open question produces the ranking that the NPS score hides. If you are currently collecting departure NPS and finding it difficult to act on the data, the paid community NPS guide covers why NPS is most useful as a cohort-level metric rather than an individual departure diagnostic, and what to pair it with to make individual departure data actionable.
The 15-minute-per-week manual protocol
The three-touch departure sequence described above is fully implementable by a solo community operator with no automation tools beyond a basic billing platform. The total time commitment is approximately 24 minutes per week for a community with 4–8 monthly cancellations. The following is the specific implementation protocol.
Monday morning (10 minutes): Check the billing platform for cancellations processed in the prior week. For each new cancellation, review the exit interview log to determine whether the member responded. If they have not responded within 48 hours, send a follow-up exit interview message that is slightly different from the first: same framing (“not to change your mind”), but acknowledging that you know they’ve moved on and making the question even shorter (“one-line answer totally fine — what was the main thing that tipped the decision?”). Log the response if it arrives. Flag the cancellation date for the 60-day reactivation touchpoint.
Monday morning (5 minutes): Check the reactivation log for members who cancelled approximately 58–62 days ago. Review their exit interview note. Draft a personalised reactivation invitation that references the specific community change most relevant to their stated cause. Send the invitation. Log the outcome (accepted, declined, no response).
When a new cancellation intent alert arrives (immediate, ~8 minutes): Send the hold offer DM within 60 minutes. Log the member’s stated reason in the exit interview log (even if not yet confirmed — having the initial reason helps if the hold offer declines and the exit interview question arrives). If the hold offer is accepted, log the pause end date and add a calendar reminder to check in 5 days before the pause expires.
Monthly (5 minutes, first Monday of each month): Review the exit interview log for the prior month. Count the cause-category distribution. If one category is above 50%, note it as the current primary systemic cause and add one specific intervention to the community’s monthly priorities. This does not require a comprehensive community audit — just a count of the cause tags in the log and a single action added to the operator’s next-30-days list.
The full weekly time commitment for this protocol is approximately 15 minutes for a community with 4–8 monthly cancellations, rising to approximately 25 minutes for a community with 10–16 cancellations per month (a larger community or a higher churn rate). The Monday morning batching approach means the operator is never reacting in real-time to cancellation data except at the hold offer touch, which genuinely does require same-day response. Everything else — exit interview follow-up, reactivation invitations, log review — can be batched into a Monday morning slot without materially reducing the performance of any touch.
When to automate the departure sequence
The three-touch departure sequence is designed to be run manually, and the manual version outperforms automated versions in every community below 500 members where personalisation is achievable by a single operator. The reason is not sentimental: it is functional. The hold offer DM that names the member’s specific area of focus and references their recent contributions converts at 24–36%; the generic automated pause-offer email converts at 8–12%. The exit interview question sent from the operator’s personal Slack account within 24 hours generates 35–55% response rates; an automated survey link generates 8–16%. The reactivation invitation that mentions the specific community development tied to the member’s stated exit reason generates 12–20% acceptance; a generic “we miss you” campaign generates 3–6%. Across all three touches, the personalised manual version generates approximately three times the return of the automated version — which means the operator needs three times as many cancellations per month before automation becomes economically rational.
The crossover point is approximately 25–30 cancellations per month (a community of 500–700 members at 4–5% churn). At that volume, the manual protocol requires 60–75 minutes per week, and the quality of personalisation begins to deteriorate as the operator cannot research each departing member’s exit interview context in the time available. Automation at that scale is a concession to volume rather than a quality improvement, and the operator should expect automated conversion rates (8–12% for hold offers, 8–16% for exit interview responses, 3–6% for reactivation) in exchange for the time saved. Below that volume, manual operation is the higher-ROI choice by a meaningful margin.
The exception is the exit interview data collection, which should be logged systematically from the first week regardless of community size. The manual exit interview message is always preferable for response rate; the logging of responses into a structured cause-category framework is automatable from the beginning. Even a simple spreadsheet with five columns (member name, cancellation date, tenure, response verbatim, cause category) produces the quarterly pattern analysis that drives the systemic prevention return. The cost of not logging is that the individual exit interview responses remain isolated anecdotes rather than accumulating into a finding — and the systemic prevention return, which is the largest component of structured offboarding’s total return over 12 months, never materialises.
If you want to assess how your current onboarding protocol is performing on the activation benchmarks that most directly predict month-2 and month-3 cancellation rates, the Foothold Onboarding Health Check identifies the specific gap in your day-0, day-3, and day-7 sequence in five questions — a scored result and the single intervention most likely to reduce your next month’s cancellation rate. Reducing the inflow of departures is the complement to running a structured offboarding protocol: the protocol recovers what the onboarding flow misses; the onboarding flow reduces what the protocol has to recover.
Frequently asked questions
What should you do when a paid community member cancels?
When a paid community member signals cancellation intent, the most effective protocol is a three-touch departure sequence rather than immediately processing the cancellation. The first touch is a hold offer — a pause option (30–60 days, same billing rate) or a downgrade path presented before the cancellation processes, typically via a personal DM or a cancellation-flow page. At $49–$99/mo, pause acceptance rates of 24–36% are typical when the offer is personalised and presented at cancellation intent rather than after confirmation. The second touch is an exit interview within 24 hours of cancellation confirmation — a short, personal message (not an automated survey link) asking one open question: what was the one thing that would have made you stay? This generates diagnostic data, not a recovery attempt, and response rates of 35–55% are achievable with a personal message vs. 8–16% for survey links. The third touch is a reactivation invitation at 60 days post-cancellation: a brief, personal message noting that a specific change or addition to the community happened since they left, with a time-limited invitation to return at the original rate. At 60 days, 12–20% of departed members accept reactivation when the invitation is personalised and tied to a specific community development.
What is a community offboarding protocol?
A community offboarding protocol is the structured sequence of operator actions that begin when a member signals cancellation intent and continue for 60–90 days after the cancellation processes. The purpose is twofold: recovery (converting a cancellation into a pause, downgrade, or future reactivation) and diagnosis (collecting qualitative data about why the member left so that root causes can be addressed before the next cohort encounters the same experience). Most paid community operators have no offboarding protocol — the billing tool processes the cancellation automatically, Slack removes the member’s access, and the operator’s involvement begins and ends with the churn notification. A structured three-touch protocol — hold offer at cancellation intent, exit interview within 24 hours, and reactivation invitation at 60 days — is the minimum viable offboarding process for a community above 50 members. Communities running this protocol typically recover 25–40% of would-be permanent cancellations and generate 3–5 qualitative exit data points per month that, aggregated over a quarter, reveal the specific systemic issue responsible for the largest fraction of departures.
What is the best exit interview question for a cancelled community member?
The single highest-yield exit interview question for a cancelled paid community member is: “What was the one thing that would have made you stay?” This question outperforms multi-question surveys because it forces the respondent to rank causes rather than listing everything that was imperfect, and because it is forward-looking rather than retrospective — the phrasing “would have made you stay” produces actionable answers about what to build or fix, whereas “why did you cancel?” produces backward-looking answers about what failed. The question is short enough to ask in a single personal Slack DM or email, which substantially improves response rates vs. survey links. Ask it with one sentence of context: “I’m asking every departing member one question — not to change your mind, but to make the community better for people who join after you.” At $49–$199/mo, departure is almost always about one primary cause even when the member perceives multiple friction points — forcing them to name the one thing surfaces the cause that was actually load-bearing for their retention decision.
How long should you wait before reaching out to a cancelled community member?
Timing varies by the purpose of the contact. For the hold offer, timing is critical: the offer should be presented before the cancellation processes, at the moment of cancellation intent, not after confirmation. Hold offers presented before processing convert at 24–36%; hold offers presented 24 hours after processing convert at under 8%. For the exit interview, the optimal window is within 24 hours of cancellation confirmation — at this point the member’s reasons are concrete and salient; by day 3 the departure is receding and responses become more abstract. Response rates within 24 hours run 35–55% for a personal Slack DM; by day 5 the rate drops below 20%. For the reactivation invitation, the optimal timing is 60 days post-cancellation. At 30 days most members are in a transition period and a message feels premature; at 90 days they have settled into a new routine without your community. At 60 days, acceptance rates for personalised reactivation invitations are 12–20%; at 90 days, under 8%.