Thanks for asking, as Alistairâs answer gave me some ways to improve our process with moderator tags, etc.Â
Our process is to reply with instructions on reporting a bug through our support portal (itâs preferred that the end user reports the bug, not staff, so they can be asked follow-up questions, etc). And we mark that as the answer.Â
From my POV, this is the right approach for a few reasons:Â
- Reporting - at some point you or your stakeholders are going to care very much about the % of questions answered. Questions like this do receive a definitive answer, even itâs not the ideal answer. And like Alistair said, best practice is to tag/track those and follow up with the new answer (you can mark a new reply as best) once the bug has been fixed.Â
- Trust and authority of the answer - Other users might see the reply about the bug and assume that thereâs an open question as to whether itâs actually a bug or not and they might not notice that the reply came from staff, etc. Marking it as the answer provides some âweightâ or definitive authority that itâs 1.) a bug, 2.) your company knows about it, and 3.) it will likely be fixed at some point
- The psychology of marked answers - you want users to see those green check marks. Itâs a signal that âthis place helps answer questionsâ that will make an impact on their adoption and engagement over time.Â
- Superusers and gamification - the psychology of answers comes in here too. If you want other community members helping answer open questions, keeping this off their list as a question to investigate will improve their experience. If the unanswered question feed doesnât build trust (too many questions with answers that arenât marked), theyâll stop using it. It can also reduce their motivation to try to solve open questions they see in the regular feed.Â