A question from Tuesday
A student posts in your community on Tuesday evening. She is stuck on the pricing exercise in module four and has a specific question about her own offer. By Wednesday morning, her post is below twelve introductions, three celebration posts and a thread about someone's new logo. Nobody has answered.
On Friday you scroll back, find it, and reply. She thanks you, but she has already decided the course is harder than she expected. Two other questions from the same week are further down still, and you do not find them at all.
Why questions sink
Communities are built for conversation, not for support. Feeds are ordered by recent activity, so a question with no replies falls out of sight as soon as other people post. Moderators, if you have them, see the feed like everyone else. You see it in bursts, between everything else you do. Nobody has a list of what is unanswered.
- Questions are mixed in with introductions, wins and chat.
- Feeds reward activity, so unanswered posts drop down.
- Moderators do not know which questions are theirs to answer.
- Many questions are already answered in a lesson the student has not reached.
- Nobody tracks how long students wait.
What silence in the community costs
The community is often why people choose a course over a book or a free video. When questions go unanswered, the promise of support feels empty, and students conclude they are on their own. They progress less, engage less and are less likely to renew or buy again. Meanwhile you feel guilty every time you open the app, which is not a good way to run a business.
A triage queue for your community
- New posts and comments are read from your community platform through its API or a bot, as they arrive.
- A language model, such as OpenAI's or Anthropic Claude, sorts each one: question, win, introduction, feedback, off topic, or needs a human urgently.
- Questions go into a queue with the student's name, their progress in the course and how long they have been waiting.
- For each question, the system suggests relevant lessons and a draft answer based on your course material and past answers.
- You or a moderator picks up the question, edits or writes the reply, and posts it in the community as normal.
- Questions not picked up within the time you set are raised to you directly.
- A weekly summary shows the questions asked, how long they waited and which topics keep coming up.
| Post type | Where it goes | Who acts |
|---|---|---|
| Question about a lesson | Queue, with a draft answer and lesson links | Moderator or you |
| Question about their own business | Queue, flagged for you | You |
| Win or introduction | Left in the feed | Community |
| Access or billing problem | Support inbox | Your assistant |
| Distress or conflict | Raised to you straight away | You |
Drafts are never posted by themselves. Students get answers from people, with the searching done for them.
A community where questions get answers
Go back to the Tuesday pricing question. Within minutes it is in the queue, marked as being about her own offer, with the module four lesson and two past answers on pricing linked beside it. A moderator sees it that evening, knows it needs you, and passes it on. You reply on Wednesday morning with the draft as a starting point and her details in front of you.
Every question is on a list until someone answers it, so nothing sinks. Moderators know what is theirs. You spend your community time on the questions that need your judgement. The weekly summary shows which lessons generate the most questions, which tells you where to add an example or a short video.
Does your community feel like this?
- Student questions sit unanswered for days.
- You find old questions when scrolling back.
- Moderators are unsure which posts they should answer.
- The same question is asked every cohort.
- You feel you have to read everything to be sure nothing is missed.