To run a Q&A thread in Skool, publish one post with a clear window ("Ask anything about X until Thursday 5 PM"), ask members to post one question per comment with context, then answer every question in the comments before the window closes. Finish with a short recap post of the best answers so the thread keeps working after it ends.
It sounds simple, and it is. The details below are what make people actually ask.
Step 1: Pick a topic and a window
An open "ask me anything" can work, but a focused thread usually gets better questions. "Ask me anything about pricing your first offer" gives people a starting point. Then set a time window, like 24 or 48 hours. A deadline gets people to post instead of saving their question for "later".
Step 2: Write the post
Title: "Q&A: ask me anything about [topic] (open until Thursday 5 PM)"
Body:
• One sentence on what you'll cover and who it's for.
• How to ask: one question per comment, with a line of context ("I have 30 members and charge $20...").
• When you'll answer: "I'll reply to every question by Thursday evening."
• An example question so people see the format.
Step 3: Seed the first question
Empty threads stay empty. Post the first question yourself, or ask a regular member ahead of time to kick it off. The first comment lowers the bar for everyone else.
Step 4: Answer in the comments
Reply directly under each question, so the answers stay attached to the context. Keep each answer focused. If one question needs a long answer, give a short version in the thread and say you'll turn it into a full post. If a question is really a private support issue, like access or billing, take it out of the public thread. We covered how to route those in the Skool Automation community: how to escalate support questions from Skool. Use short video replies when it helps
If a question is easier to show than explain, record a quick video and drop the link in your reply. Screen recordings work well for "how do I set this up?" questions.
Step 5: Let members answer too
Before you reply, give it a few hours. Often another member answers first, and that's a good thing. Like their answer and add to it. A Q&A where members help each other builds more community than one where only the owner talks.
Step 6: Close and recap
When the window ends, add a comment saying it's closed and when the next one is. Then post a recap: "Top 5 questions from this week's Q&A, with short answers." The recap helps members who missed it, and if your community is public, it's the kind of post that can show up on Google.
Make it a ritual
A Q&A that happens every week on the same day becomes something members plan around. "I'll save that for Thursday's Q&A" is exactly what you want to hear. Rituals like this keep a community active with less effort than new content every day. I wrote more about that in Skool engagement is built through rituals. Async Q&A vs live Q&A
• Async (in the feed): works across time zones, gives you time to think, and leaves a searchable record.
• Live (on a call from the Calendar): more energy and faster back-and-forth, but some members can't make it.
Many communities do both: collect questions in a feed thread before a live call, answer them live, and post the recap afterward.
Mistakes to avoid
• No deadline, so the thread drags on for weeks.
• Answering in DMs, so nobody else learns from it.
• Leaving questions unanswered. One ignored question can stop people from asking again.
• Making the topic so broad that people don't know where to start.
A quick template for the recap
Title: "Q&A recap: [topic]"
Body: three to five questions, each with a two to three line answer, plus a link back to the full thread.
What topic would you pick for your first Q&A thread if you ran one this week?