Office Hours Reference Card
Paid community office hours — pre-call checklist, 60-minute call structure, post-call distribution, question curation criteria, and activation measurement
This page is a structured reference card for paid Slack community operators who want the office hours pre-call checklist, call structure, post-call distribution steps, question curation criteria, and activation measurement tables in scannable form. It covers: a five-step pre-call checklist table (step, timing, action, what to include, common mistake); a six-slot 60-minute call structure table (time slot, action, format note, operator’s job, what not to do); a four-step post-call distribution checklist (step, timing, format, destination, why it matters); a three-criterion question curation table (criterion, definition, good example, poor example, why the poor example makes a weaker session); and a three-metric activation measurement table (metric, what it measures, how to measure, good signal, warning signal). For the strategic reasoning behind office hours — including why the drop-in AMA format fails, what the operator-dialogue threshold is, and how the psychological mechanism of named askers drives participation at 3–4× the rate of open-floor questions — see the companion post: How to run office hours in a paid Slack community. This card is for the operator who understands the reasoning and needs the pre-call checklist, call script, post-call distribution steps, and measurement tables in quick-reference form.
TL; DR
Open the question submission window 48h before and promote to targeted members (not all-members). Curate 3 questions by curation criteria — not by reaction count. Pre-announce curated questions with asker names 24h before. In-call: state recording status first (2 min); run three named-asker blocks (2-min asker context + 10-min answer + 2-min follow-up each); open floor (15 min); close on time with thread-answer commitment (13 min). Post-call within 2h: three-bullet recap to #announcements (not a transcript). Same day: write answers to all unaddressed submissions in the submission thread; pin recording with question timestamps. At 90 days: unpin. Measure: pre/post 30-day contribution rate (+20%+ = good); attendees vs. non-attendees 90-day activation rate (15+ pp gap = good); first-timer vs. repeat-attendee lift (first-timer lift should be higher).
Table 1 — Pre-call checklist
The five pre-call steps in the correct sequence. Each step has a specific timing, because timing determines both the quality of what the operator produces and the quality of the member experience. The submission window has a 48-hour minimum because members need time to encounter the problems they want to ask about and formulate a specific question — a same-day window produces questions typed under deadline pressure that are typically less specific and harder to give a concrete answer to. The 24-hour pre-announcement gap gives members who submitted questions time to plan attendance; members who see their question curated and announced with their name attend at 4–5× the rate of members whose questions were not selected, which means the pre-announcement is the single highest-leverage step for improving attendance.
| Step | Timing | Action | What to include | Common mistake |
|---|---|---|---|---|
| 1. Open submission window | 48h before session | Post in #office-hours: submission instructions, session date and time, and a topic scope hint. Pin the post for the 48h window so members see it on first login. | Submission format (one question per message, text only — not a DM, not a thread reply); topic scope hint framed as what this session’s operator experience covers best (“this session focuses on first-month retention and activation”); link to the previous session’s recording for members who are new to the format. | Opening the window the same day as the session. The 48h minimum is non-negotiable: members need time to encounter the specific problem they want to ask about (often the day-before or morning-of the session is when that problem is live in their work), and the operator needs curation time. A same-day window produces vague general questions that the operator cannot answer with specific experience. |
| 2. Promote the window | 48h before (at open) and 24h before (reminder) | DM active members whose stated goal or recent posts overlap the session’s scope hint. Do not send an all-members broadcast for the submission promotion. | A 1-sentence DM referencing the member’s specific stated goal or a recent post they made: “[Name], given what you shared in [channel] last week about [topic] — this session might be a good moment to ask about [angle]. Submission window is open for the next 24h: [link to post].” The personalised reference is what produces submissions; the broadcast is what produces ignores. | Promoting via a general #announcements post or all-members DM. Targeted DMs to 10–15 members whose stated goals overlap the session scope produce 3–4× more submissions than an all-members channel announcement, because the personal reference creates an obligation to engage that a broadcast does not. Operators who broadcast first and then wonder why submissions are thin consistently underperform operators who target first. |
| 3. Curate the question set | 24h before session | Select 3 questions from submissions using the curation criteria in Table 4. Record the names of askers for the selected questions (with their permission if the question is personal). Write a one-sentence reason why each selected question is valuable to the full membership. | Three questions only — not four, not five. Three questions fill a structured 60-minute session. The one-sentence reason per question is for the pre-announcement (Step 4) and doubles as your session prep note: if you cannot write a specific one-sentence reason why this question is valuable to 30%+ of members, the question did not pass the broad-applicability criterion and should be replaced. | Selecting questions by reaction count (most-reacted submission wins). Reaction counts measure which question is most recognisable to other members, not which question the operator can answer with the most specific experience — those are different things. The most-reacted question is often the most general (“what tools do you recommend?”) because vague questions are universally relatable. The best office hours question is the one the operator has a specific, concrete, experience-based answer to that 30%+ of members cannot get from a Google search. See Table 4 for the three curation criteria in full. |
| 4. Pre-announce selected questions | 24h before session | Post the curated question set in #office-hours as a single announcement: three numbered questions, each with the asker’s name and the one-sentence reason it was selected. Pin this announcement (replacing the submission-window pin). | Asker names with their explicit permission; one-sentence reason each question is relevant to members beyond the asker (“this question came up in three separate conversations this month — we’re addressing it as a session-wide topic”); session date, time, and link. The asker’s name is what drives their attendance — do not anonymize selected questions. | Posting the pre-announcement fewer than 12h before the session. Members who see the pre-announcement 24h out have time to plan; members who see it the morning of the session have too little notice for most to adjust their schedule. The 24h window is also when askers who see their name can promote the session to their own networks and to community peers who might benefit from the same question — a 6h window eliminates this organic amplification. |
| 5. DM new members at join | Day 0 DM (at join, automated or manual) | Include one sentence about the upcoming office hours session in the Day 0 welcome DM, tied to the new member’s stated goal. Not a separate DM — a sentence appended to the Day 0 DM. | Session date and time; one-sentence reason tied to the new member’s stated goal (“given that you mentioned [goal], the [date] office hours session covers [scope] — worth adding to your calendar”); link to the submission window or (if within 12h of the session) directly to the session link. The goal-reference is what makes the sentence relevant rather than a generic announcement. | Writing “we have office hours” without a goal-reference or scope note. New members do not know what office hours means in this specific community — whether it is a training session, a Q&A, a drop-in, or something else. Without a goal-reference, the sentence is a generic event mention that the member has no reason to prioritise. The sentence should be one specific reason this particular member, with their stated goal, would benefit from this particular session. |
The pre-call sequence is a system, not a checklist. Each step depends on the previous one: the quality of the submission window post determines the quality of submissions; the quality of targeted promotion determines submission volume; the quality of curation determines session content; the quality of the pre-announcement determines attendance. Operators who skip Steps 2 and 4 (targeted promotion and pre-announcement) produce sessions that run to structure but do not produce the activation lift that makes office hours worth the operator’s time. Steps 2 and 4 are where the activation work actually happens — not in the 60 minutes of the call itself.
Table 2 — 60-minute call structure
The six-slot structure provides a predictable experience for members who attend multiple sessions, which is the operational basis for the 25–35% repeat-attendance rate that structured office hours produces vs. 8–15% for drop-in formats. Predictability matters because repeat attendees make their attendance decision before they know the specific question set for a given session — they attend because they know what the format delivers, not because the specific questions are compelling for them personally that month. The operator’s job in each slot is distinct and specified below; the most common failure is role confusion (the operator adds context when the role is to answer, or extends the open floor when the role is to close). Closing on time, even with unanswered questions, is not a failure — it is a format commitment that makes the close-time promise credible for future sessions.
| Time slot | Action | Format note | Operator’s job | What not to do |
|---|---|---|---|---|
| 00:00–00:02 Recording disclosure |
State recording status (recording or not recording), confirm session format (three curated questions, then open floor), and name the three questions briefly by topic (not by asker’s name — the asker introduction happens in each question block). | Verbal disclosure, not written-only. Members who joined but did not see the pre-announcement need to hear the recording status before they speak. The format reminder (“we run three named-asker blocks then open floor”) sets expectations so members know when to wait and when to raise hands. | State the three things in under 2 minutes: recording status, format, and three question topics. Do not add housekeeping, community announcements, or context about the session history. The pre-call checklist handled those — two minutes of preamble after two minutes of housekeeping is four minutes before the first substantive moment, and attendance-time curves show member attention highest in the first 10 minutes. | Skipping the recording disclosure because “I mentioned it in the pre-announcement.” The pre-announcement is a written notification; the disclosure at call start is for members who join live without having seen the post, and for members who did read it but need the verbal confirmation before speaking on a recorded call. Skipping it is a procedural omission that members notice and that erodes session trust, particularly around personal questions. |
| 00:02–00:12 Question 1 |
Name the asker and invite them to add 2 minutes of context. Run the 10-minute answer. Allow 2 minutes of follow-up from the asker. | The three-part structure (2+10+2) is a format, not a target. If the asker’s context takes 90 seconds, move to the answer at 90 seconds. If the answer naturally closes at 8 minutes with nothing left to add, move to follow-up. The structure prevents over-running by providing explicit transition points; it is not a rigid script. | Find the most specific, concrete answer you have from your own experience operating this or a comparable community. Not the answer that sounds most comprehensive or that covers the most angles. The value of office hours over a forum post is that the operator has operated a community through this problem; the answer should reference what actually happened when you or someone you know tried the relevant approach, not what the literature says should work. | Going over 10 minutes on the answer. This is the most common failure mode in structured office hours. An answer that runs 14 minutes to Question 1 produces a 76-minute session minimum, with compounding. Members who committed to a 60-minute session begin multitasking at minute 70; attendance drops sharply when sessions routinely run long. If 10 minutes is not enough to give the answer, the question was not specific enough for office hours format — a broader question belongs in a community async thread, not in a named-asker block. |
| 00:12–00:22 Question 2 |
Name the asker, invite 2-minute context, run 10-minute answer, allow 2-minute follow-up. Same structure as Question 1. | Question 2 often benefits from connecting to Question 1 if the two topics are adjacent (“this builds on what we just discussed — [asker] is dealing with the downstream version of that same problem”). The connection makes the session feel like a coherent discussion rather than three isolated QA sequences, which improves the quality of the recording for non-attendees. | Maintain the named-asker dynamic by addressing the asker directly by name during the answer (“in your situation, [name], the specific thing I’d look at first is...”). The named-asker dynamic is what makes office hours format distinct from a webinar: the answer is to a specific person in a specific situation, and that specificity is what produces concrete, re-applicable answers rather than general advice. | Letting other attendees answer Question 2 during the question block. The open floor comes at 00:32; during the question blocks, the operator answers and the asker follows up. Other attendees can react but should not offer their own answers during the question block — this protects the operator’s time for concrete answers and prevents the question blocks from becoming peer discussion threads that produce less operator-specific experience. |
| 00:22–00:32 Question 3 |
Name the asker, invite 2-minute context, run 10-minute answer, allow 2-minute follow-up. Same structure as Questions 1 and 2. | Question 3 is the hardest to maintain quality for, because by this point some operators feel the urge to speed through it to reach the open floor. Resist: Question 3 is the reason the third asker submitted and attended, and it is the question with the highest specific attendance impact for the members who came specifically for it. | Close the three-question block cleanly after the Question 3 follow-up. A brief transition statement before the open floor: “Those are the three curated questions — we’re going to open the floor now for any remaining questions or follow-ons. The floor is open until 00:47, then we’ll close with any written answers I’ll post in the thread.” The explicit transition prevents the session from drifting between Question 3 and the open floor without a clear structural signal. | Skipping the Question 3 follow-up because you are running close to 00:32. The asker of Question 3 has been waiting 20+ minutes for their question; the 2-minute follow-up is non-optional. If you are running over at this point, shorten the open floor to compensate — not the question blocks. Members who submitted questions are the highest-engagement members at the session; shortcutting their follow-up time is the highest-cost economy in terms of their future session engagement. |
| 00:32–00:47 Open floor |
Invite live questions from all attendees. Address each live question briefly (2–3 minutes max). If a live question requires a longer answer, offer to address it in a separate DM or post rather than extending the block. | The open floor is also where attendees can add their own experience or context from the three curated questions. The operator’s role shifts in this block: less answering, more facilitating. Let experienced attendees share their perspective; ask follow-on questions to draw out specific examples. The open floor is where the peer-dialogue dynamic that creates community value emerges. | Acknowledge each live question briefly before redirecting (“that’s the same pattern I see in communities that are three to six months old — anyone else dealt with this?”). If two or three attendees have experience with the question, invite them to share in 30 seconds each. The facilitated peer-exchange in the open floor produces more member-to-member connections than any of the three question blocks, which is why the open floor is disproportionately important for peer-relationship formation despite being the least-structured part of the session. | Letting one member dominate the open floor. If a single attendee is driving 70%+ of the conversation in the open floor, redirect explicitly: “[Name], let’s pick this up in the thread — I want to make sure we get to any other questions before we close.” The open floor exists for all attendees; one-member dominance produces an experience indistinguishable from a 1:1 call that other members are silently observing, which drives down open floor attendance over successive sessions. |
| 00:47–01:00 Buffer and close |
State the close explicitly. Commit to posting written answers to any unaddressed questions in the #office-hours thread within the same day. State when the recording will be pinned. End the call. | The buffer is 13 minutes and it exists for three reasons: sessions run over the structured blocks occasionally; the close commitment needs time to be made clearly; and members who stayed to the end benefit from a brief informal wind-down before the call formally ends. Do not extend the open floor into the buffer to “fit in more” — use the buffer for the close routine. | Close on time, every session. The close-time promise is what makes the format sustainable for members who have calls after this one, and what makes the format credible over multiple sessions. An operator who says “we’ll wrap up at [time]” and then runs 20 minutes over is an operator whose close-time promise is not believed by session three. Members who cannot predict when a session ends stop attending because they cannot commit the open-ended block. | Extending the session if attendance is dropping. Dropping attendance as you approach 01:00 is not a sign that more content is needed — it is a sign that members have commitments after this time block, which is normal. Extending produces a 1:15 session that was promised as 1:00, which compounds the close-time-promise problem described above. Close on time, post answers in the thread, and let the recording serve members who want more. |
The named-asker structure is why the format outperforms open-floor alternatives at 3–4× the repeat-attendance rate. When a member sees their question curated, pre-announced with their name, and addressed by name in the session, they experience a specific recognition that creates the strongest social driver in community participation: the feeling that they contributed something the community valued enough to feature publicly. This is the same mechanism that drives post-spotlight contribution rates in member spotlight formats. The format works not because the answers are better than what a Google search produces, but because the named-asker relationship creates a social return obligation that no asynchronous tool replicates.
Table 3 — Post-call distribution checklist
Non-attendees represent 60–80% of the total community membership for any given office hours session. The post-call distribution is what determines whether those members receive any value from the session and whether the session produces activation lift for members who did not attend live. An operator who runs a well-structured session and then posts nothing for 48 hours is running office hours as a live event exclusively — which means the 70% of members who did not attend receive nothing and the recording views come from the 5–10% of members who seek recordings out rather than the 30–40% who will watch if pointed directly to the relevant timestamp. The four post-call steps are sequenced by time-sensitivity and impact.
| Step | Timing | Format | Destination | Why it matters |
|---|---|---|---|---|
| 1. Three-bullet recap | Within 2 hours of session end | Three bullets, not a transcript. Each bullet: one sentence naming the question, one sentence giving the core answer. Total length: 6–8 sentences. No recording embed, no “watch the replay for more” call-to-action in the body of the recap itself — that belongs at the bottom. | #announcements (not #office-hours). The recap belongs where all members who were not monitoring #office-hours actively will see it on their next login. #office-hours is where engaged members go; #announcements is where the recap reaches the members who most need the passive value delivery. | Non-attendees consume 80% of session value in 90 seconds if the recap is written to that time constraint. A transcript requires 20–30 minutes of reading and produces lower comprehension per minute because it includes the framing, context-setting, and conversational asides that are valuable live but redundant in text. Three bullets with the core answer per question is what a non-attendee needs to get value and, if one question is directly relevant to their situation, decide to watch that timestamp. |
| 2. Written answers to unaddressed submissions | Same day as session | A direct written answer to each question that was submitted but not curated into the session. Write as you would answer the curated questions in session: specific, concrete, experience-referenced. Not “we didn’t have time for your question but here are some resources.” | Reply to the original submission thread in #office-hours (not a new post, not a DM). Replying in thread notifies the original submitter, gives the answer a permanent home in the channel, and creates a reference that future members searching the channel can find when they have the same question. | Submitters whose questions were not curated had a specific problem they wanted answered. A submitter who receives a written answer same-day has a better experience than the operator who curated their question for the live session: they got the answer without spending an hour on the call. Closing the loop with non-curated submitters also produces the highest subsequent submission rates: a submitter who was answered same-day submits to the next session at 2–3× the rate of a submitter who received no answer, because they have evidence that the submission process is worthwhile even when their question is not featured. |
| 3. Recording pin with timestamps | Same day as session | A pinned post in #office-hours with: recording link; timestamp marker for each of the three question blocks (e.g. “Question 1: [asker name] — [30-word topic summary] — starts at 00:02”); a note that the post will be unpinned in 90 days. Format: one post, three timestamp lines, one note. | #office-hours, pinned. The timestamp-specific pin enables members who want only Question 2 to jump directly to it without watching the full recording. Selective viewing based on timestamps produces 3–4× the recording watch-rate vs. a link to the full recording with no markers, because members can commit to 12 minutes for a specific question without committing to the full hour. | Recording watch-rate is the clearest leading indicator that office hours is producing value for non-attendees. Operators who share a recording link without timestamps produce 5–10% watch-rate on the full recording. Operators who share timestamp-marked questions in a pinned post produce 30–40% selective-view rate across the membership, because the timestamp structure reduces the decision friction from “do I have an hour?” to “do I have 12 minutes for Question 2?”. See the engagement events reference card for the parallel mechanism in async challenge and live event formats. |
| 4. Unpin the recording post | 90 days after session | Unpin the recording post from #office-hours. Do not delete the post or the recording — they remain in the channel history and are searchable by members who need them. Remove only the pin. | #office-hours. The pin is the high-visibility surface; unpinning clears space for the current session’s recording to be the top-pinned item. | A recording that is still pinned 6 months after a session competes with the current session’s recording for members’ pinned-post attention. When the pinned-post list shows 8 recordings from 8 different sessions, members stop consulting it because the list is too long to scan. The 90-day unpin cadence means members who join in the current period see the two or three most recent sessions pinned, which is the right archive depth for “what have we discussed recently” navigation without being long enough to feel like a backlog. The historical recordings are still accessible by search and direct link — unpinning is a visibility decision, not a deletion. |
Table 4 — Question curation criteria
The curation decision is where most office hours formats fail. The most common failure is selecting by reaction count: the operator sorts submissions by the number of emoji reactions from other members and picks the top three. Reaction counts measure which question is most recognisable to other members — not which question the operator can answer with the most concrete, specific, experience-based knowledge. The most recognisable questions are almost always the most general ones (“what tools do you recommend for community management?”), because vague questions are universally relatable. The operator’s answer to a vague question is a vague answer that any member could have found with a search. The sessions that produce the highest activation lift — measured by post-attendance contribution rate — are the sessions where the operator gave a highly specific, experience-based answer to a question that 30%+ of members have but cannot easily research. That question is rarely the most-reacted submission.
| Criterion | Definition | Good example | Poor example | Why poor example makes a weaker session |
|---|---|---|---|---|
| Operator-specific experience | The operator has personally operated a community through the situation the question describes and has a specific, concrete answer based on what happened — not what the literature recommends. The answer should not be generalisable to all community operators; it should be what happened when this operator, in this type of community, tried this approach. | “How did you handle the first member who posted a promotional offer without asking, and how did that change how you wrote the value-before-promotion rule?” This question asks about a specific incident. The answer is what happened, what the operator decided, and what they would do differently — no two operators have the same incident or the same answer. | “What is the best community management software in 2026?” This question asks for a general recommendation the operator can answer with a Google search. It does not require the operator to have operated a community to answer it, which means the answer is not differentiated from a content article and carries no specific experience value. | General recommendation questions produce answers that members can verify (or disprove) with five minutes of searching. When office hours answers are checkable against online content, members begin to question why they attended a live session to get information available in written form. The format loses its value proposition (access to operator-specific experience not available in written content) and attendance drops. The session’s purpose is to give members access to knowledge the operator has that cannot be found elsewhere; questions that can be researched elsewhere should not occupy the curated question slots. |
| Concrete answerable | The question has a specific, statable answer. The operator can close the answer with a concrete conclusion: a specific action, a specific threshold, a specific decision criterion, or a specific description of what happened. Questions that require extensive hedging (“it depends on many factors”) or that cannot be resolved in 10 minutes without being dishonestly simplified are not concretely answerable in the office hours format. | “At what point did you switch from running new-member DMs manually to automating them, and what metric did you use to decide?” This question has a specific answer: a number, a metric, and a decision. The answer is closed and concrete, even if the operator’s specific answer differs from what another operator would choose. | “Is our community worth keeping running?” This question requires information the operator does not have (the asker’s community’s metrics, history, and member composition) and a judgment that cannot be made in 10 minutes without being irresponsible. The answer is inevitably a list of factors to consider rather than a concrete conclusion, which is the same as telling the member to do their own research. | Questions that produce hedged answers erode the sense that the operator knows something the member does not. When the answer to three consecutive questions is “it depends on your situation,” members leave the session without a single actionable conclusion. The 10-minute answer constraint is a format tool that forces curation of concretely-answerable questions: if you cannot give a concrete answer in 10 minutes, the question is either too complex for office hours or does not have a concrete answer, either of which is a curation failure. See also the companion blog post for the mechanism behind why hedged answers fail even when they are technically accurate. |
| Broad applicability | More than 30% of the current membership is likely to be in the same or analogous situation as the asker. Broad applicability is estimated based on what the operator knows about the membership’s composition — not on how many members reacted to the question. A question can be broadly applicable with only 2 reactions if the operator knows 40% of members are at the stage the question describes. | “What do you tell new members who join in month seven, when the community feels established and they feel like they missed the founding energy?” If the community has been running for more than 6 months, a significant fraction of new members face this specific social dynamic. The answer applies to all of them and to the operator’s approach to late-joiner onboarding, which any member who will eventually recruit new members should know. | “How do I handle the situation where one specific member in our community keeps derailing threads with unrelated promotions despite two private reminders?” This is a specific member dispute requiring information the operator does not have (the member’s history, the channel context, the community norms) and producing an answer applicable to operators in the identical situation — which is at most 3–5% of attendees. It belongs in a 1:1 DM with the operator, not in a curated question block. | A narrowly applicable question produces an answer that is highly valuable to the one asker and largely irrelevant to the other attendees. Members who have listened to a 10-minute answer to a question that has no bearing on their situation feel that 10 minutes was wasted — not because the answer was poor, but because it was not for them. Three consecutive narrow questions produce a session where each attendee feels that 20 of the 30 curated-question minutes were irrelevant. Broad applicability is what ensures that every member who attends leaves with at least one answer that is applicable to their situation. The recording watch-rate also depends on broad applicability: members watch the timestamps of questions that apply to their situation; narrowly-applicable question blocks have near-zero non-asker watch-rates. |
The three curation criteria function as a gate, not a ranking. A question must pass all three criteria to be curated — two out of three is not enough. The most common two-out-of-three failure is a question with strong operator experience and broad applicability but no concrete answer: the operator has relevant experience, the question is common to many members, but the 10-minute answer cannot be closed with a specific conclusion. The right response to a two-out-of-three question is a written answer in the submission thread (post-call Step 2) rather than a curated question slot. Written answers have no time constraint and can handle complexity appropriately; a 10-minute oral answer that cannot be closed with a conclusion is not the right medium for questions that require nuance.
Table 5 — Activation measurement
Three metrics, three causal questions. The pre/post contribution rate measures whether office hours changes member behaviour at the individual level. The attendee vs. non-attendee activation rate measures whether office hours causes activation at the cohort level (not just correlates with it — attendees might self-select for higher engagement regardless of the session). The first-timer vs. repeat-attendee delta measures whether the format is working specifically as an activation tool for members who have not yet become contributors, or whether it is primarily serving members who are already active. All three metrics together tell you whether office hours is working, for whom, and whether the format is solving the right problem. Any single metric alone is insufficient: a high pre/post contribution rate without a high attendee vs. non-attendee gap could mean office hours attracts already-engaged members (selection bias, not causation); a high attendee vs. non-attendee gap without a first-timer-led delta could mean the format is building on existing engagement rather than creating new engagement.
| Metric | What it measures | How to measure | Good signal | Warning signal |
|---|---|---|---|---|
| Pre/post 30-day contribution rate | Whether office hours changes member contribution behaviour at the individual level. A genuine activation effect produces a measurable increase in contribution rate in the 30 days after first attendance compared to the 30 days before — not just correlation (members who attend office hours tend to be more engaged anyway). | For each attendee: count messages posted in the 30 days before their first office hours attendance; count messages posted in the 30 days after. Calculate the percentage change. Average across all first-time attendees in a cohort. Run the same calculation for a control group of non-attendees matched by join date and initial contribution rate (first 30 days as member) to control for the selection effect. | +20% or more pre/post contribution rate for attendees vs. control group. This level of lift, when present in a matched comparison, indicates that office hours is producing a behavioural change beyond what engagement self-selection explains. A +30%+ lift is a strong signal that the named-asker format is functioning as the psychological activation mechanism described in the companion post. | Near zero or negative pre/post contribution rate, or no gap vs. the control group. Near-zero lift means office hours attracts already-engaged members who would have contributed at the same rate without attending. Negative lift is rare but indicates the session is producing a withdrawal effect — possibly that the session format is creating social comparison dynamics that make lower-contribution members feel less comfortable posting, not more. The fix is re-running the pre-call checklist to ensure new members are receiving the Day 0 DM session mention, then checking whether first-time attendees are attending in their first 30 days (when contribution behaviour is most malleable) or after 90+ days (when contribution patterns are already established and harder to shift). |
| 90-day activation rate: attendees vs. non-attendees | Whether office hours causes activation at the cohort level, independent of the selection effect. Members who attend office hours in their first 60 days tend to become contributors; the question is whether attending causes the contribution rate or whether the same members would have contributed anyway because they are the type of members who seek out engagement opportunities. | For a given intake cohort: identify members who attended office hours within their first 90 days and members who did not. Define activation as reaching the activation threshold event (first post in a non-introductory channel, or whichever threshold your community uses). Calculate 90-day activation rate for each group. The gap between the two rates is the office hours activation differential. Run this for at least three consecutive cohorts before drawing conclusions — one cohort’s gap is noisy; three cohorts’ consistent gaps are a pattern. Use the community health check to benchmark your baseline activation rate before measuring the differential. | 15+ percentage-point gap between attendees’ and non-attendees’ 90-day activation rate (e.g. 65% for attendees vs. 48% for non-attendees). This is the threshold at which office hours is differentially producing activation beyond selection effect — a 17-point gap is large enough to be structurally meaningful rather than noise. An operator who sees a 20+ point gap consistently across three cohorts has strong evidence that office hours is the intervention that is causing the gap, not coincident with it. | Under 5 percentage-point gap between attendees and non-attendees. A sub-5-point gap means attendees and non-attendees activate at nearly the same rate — office hours is not differentially producing activation. The most common cause is that the format is not reaching the right members (non-activating members are not attending because the Day 0 DM mention is missing, or the submission window is not targeted to members who have not yet posted). Fix the attendance funnel before concluding the format does not work: if the members most likely to be activated by the session are not attending, the gap will be near zero regardless of session quality. |
| First-timer vs. repeat-attendee contribution lift | Whether the format is functioning as an activation tool for members who have not yet become contributors, or primarily serving already-active members who attend repeatedly. If office hours is working as designed, first-time attendees should gain more post-attendance contribution rate lift than members who have attended multiple previous sessions (because already-active members have less contribution-rate headroom to improve). | Segment office hours attendees by attendance number: first-time attendees, second-time attendees, third-and-more attendees. For each segment: calculate average post-attendance 30-day contribution rate lift vs. pre-attendance 30-day baseline. Compare the lift by segment. Run this quarterly with at least 10 attendees per segment for statistical significance. Communities under 100 members may not have the attendance volume for segment-level analysis; for those communities, aggregate the pre/post contribution metric at Table 5 Row 1 and wait until attendance is sufficient for segmentation. | First-timer lift exceeds repeat-attendee lift by 10+ percentage points. This pattern confirms that office hours is performing its primary function: activating members who have not yet contributed. A first-timer who attends and then contributes at a 30% higher rate than before attendance is a member who was moved from non-contributor to contributor specifically by the session. Repeat attendees who show lower lift (because they are already contributing) confirm that the activation lift is not an artifact of already-engaged members skewing the data. | No first-timer lift, or repeat-attendee lift exceeds first-timer lift. No first-timer lift means the format is not moving non-contributors to contributors — which is the specific activation problem office hours is designed to solve. Repeat-attendee lift exceeding first-timer lift means the format is primarily building on existing engagement rather than creating new engagement. The fix is re-examining whether the Day 0 DM session mention is being sent and whether non-posting members in their first 60 days are receiving targeted submission-window DMs (pre-call Step 2). If non-posters are not being directed to office hours in their first 60 days, they cannot become first-time attendees and the first-timer cohort will always be dominated by members who were already moderately engaged. |
Frequently asked questions
What is the best format for paid community office hours?
The highest-activation format is the named-asker Q&A structure. Members submit questions in advance through a dedicated channel; the operator curates three questions using the curation criteria in Table 4 (not by reaction count); each curated question is addressed with the asker named, 2 minutes of asker context, 10 minutes of operator answer, and 2 minutes of follow-up. The named-asker structure produces 25–35% repeat-session attendance rates vs. 8–15% for drop-in AMA formats, because members who have a question curated and addressed by name return to future sessions at 4–5× the rate of members who attended but were not featured. A 60-minute session runs: 2 minutes for recording disclosure, three 10-minute named-asker blocks (2 min context + 10 min answer + 2 min follow-up each), 15 minutes of open floor, 13 minutes of buffer and close with a thread-answer commitment. See Table 2 for the full six-slot call structure.
How often should you run office hours in a paid community?
Monthly is the right default for communities under 500 members. Monthly frequency gives the submission pool time to accumulate: a 200–500 member community typically produces 8–15 submissions per monthly session, which provides enough material to curate 3 questions meeting all three criteria. Bi-weekly is appropriate once the community consistently produces more than 15 submissions per session and the operator has validated a 15+ percentage-point attendee vs. non-attendee activation gap (Table 5, Row 2). Weekly frequency is almost always wrong: question supply runs thin, question quality drops because members haven’t had time to encounter their specific problems, and the recording archive becomes a backlog rather than a reference library. The clearest signal to increase frequency from monthly to bi-weekly is consistent submission abundance at monthly cadence — if you are curating 3 from 6 submissions, do not increase frequency. If you are curating 3 from 20+, the demand for the format exceeds the current supply of sessions.
How do you measure if office hours is working?
Three metrics, each asking a different causal question. Pre/post 30-day contribution rate (Table 5, Row 1): compare message count 30 days before vs. after first attendance for each attendee, controlled against matched non-attendees. Good signal: +20%+ lift vs. the control group. This measures whether office hours changes behaviour at the individual level. Attendees vs. non-attendees 90-day activation rate (Table 5, Row 2): compare the activation rate of cohort members who attended office hours in their first 90 days vs. those who did not. Good signal: 15+ percentage-point gap. This measures whether office hours causes activation or just correlates with it. First-timer vs. repeat-attendee contribution lift (Table 5, Row 3): compare post-attendance contribution rate lift for first-time attendees vs. members who have attended multiple sessions. Good signal: first-timer lift exceeds repeat-attendee lift by 10+ points. This measures whether the format is solving the activation problem for the members who need it most. All three together give a complete picture; any single metric in isolation is insufficient to determine causation.
What should you do after a paid community office hours session?
Four steps in order of time-sensitivity. Within 2 hours: post a three-bullet recap to #announcements — not a transcript, not a recording embed, just the question topic and one-sentence core answer per question. Non-attendees consume 80% of session value in 90 seconds if the recap is written to that constraint. Same day: write answers to all unaddressed submissions and reply in the original submission thread in #office-hours (not a new post, not a DM), so submitters receive a notification and the answers are searchable. Same day: pin a post in #office-hours with the recording link and timestamp markers for each of the three question blocks, so members can watch selectively (this produces 3–4× the recording watch-rate vs. an unmarked link). At 90 days: unpin the recording post without deleting it, so the pinned-post list shows the two or three most recent sessions rather than a growing backlog. See Table 3 for the full four-step post-call distribution checklist with formats, destinations, and why-it-matters explanations.