Show members what a useful request looks like
Include an example question in your welcome materials. Show the subject, a short description of the problem, and a concrete request. New members shouldn't have to guess how much detail to include or whether it's acceptable to ask.
A vague message often needs a conversation before anyone can decide whether to help. A little context can save that round trip. The free WhoCan question builder gives members a structure they can fill in and copy into Slack.
Who can review our onboarding flow? We're losing track of which welcome message new members see first. I've mapped the current steps. I'd like someone to check for gaps before we change it.
Give unanswered questions a next step
Choose a person or small group to review unanswered requests as part of community moderation. They don't have to know every answer. They need to notice when a question could use more context, a different skill, or an introduction.
With WhoCan, an asker can confirm a search from Slack and let the bot ask members with relevant skills. Helpers can accept, decline, or suggest someone else. Explain that choice when introducing the bot, so members understand why they're receiving a request.
Bring the useful part back to the thread
An introduction may lead to a direct conversation. Ask the original poster to return with a short summary when it's appropriate to share: what worked, what remains open, and where to find the details. Remove private information before posting.
Thank the person who helped and be specific about what they contributed. That gives future askers useful context and lets other members see how they might contribute too.
Review the journey from question to useful help
Track the steps separately. A posted question, a confirmed search, an accepted introduction, and a resolved problem are different outcomes. Counting all four as engagement makes it hard to see where people get stuck.
Compare periods of the same length, and note changes in the number of active members or questions. Start with the step that loses the most people. If askers never confirm a search, explain the prompt. If searches get no acceptances, review skill coverage and the requests themselves.
- How many questions received a useful reply?
- How many WhoCan searches were confirmed?
- How many introductions were accepted?
- Did askers say their problem was resolved?
Try this in your workspace
Write a clear request with the question builder, or follow the setup guide to find help with WhoCan.