Your support team gets the same question for the third time this week: "How do I add a second admin to my account?" The feature exists. It has existed for a year. There is even a help article about it. And yet users keep asking.
That question is telling you something specific about your documentation. Repeated feature questions are rarely about the feature. They are about the docs. This checklist helps you read those questions properly and fix the underlying gap, so the question stops arriving.
The checklist
Work through these for each repeated question. Each item tells you what kind of documentation gap you have.
1. Does an answer exist anywhere? Search your docs, help centre and release notes. If nothing covers it, you have a missing page. This is the simplest gap to fix: write the article.
2. Does the article use the user's words? Users ask about "adding a second admin." Your article might be titled "Managing workspace roles and permissions." Both describe the same thing, but nobody searching for the first will find the second. Add the user's phrasing to titles, headings and the first paragraph.
3. Is the article current? Check screenshots, menu names and steps against the product today. After a redesign, old articles become wrong in small ways that stop people following them.
4. Is it findable from where the question happens? If users ask this question from the settings page, a link to the article on the settings page may solve it. Docs that are correct but far away are nearly as bad as missing ones.
5. Does it answer the follow-up question? Often an article explains the main step and skips the thing people ask next, like "does the second admin need a paid seat?" Add the follow-ups.
6. Is it a docs problem at all? Sometimes repeated questions mean the product is confusing. If users keep asking where a button is, moving the button may beat any article. Pass these to the product team.
7. Is the answer clear to a new user? Read it as someone on day two of a trial. Jargon and assumed knowledge are common in docs written by the people who built the product.
Want a 24/7 AI Employee for Your Website?
See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.
Where to find the questions
You need a steady list of what users ask. The common sources are support tickets, help centre searches with no clicks, and chat conversations.
A website assistant is useful here because it answers what it can and records what it cannot. SpideyChat for SaaS companies logs unanswered questions as knowledge gaps, so each week you get a ready-made list of where your docs fall short. The setup is covered in how to train a website assistant on product docs.
A weekly review that takes thirty minutes
Keep the routine small or it will not survive:
- Pull the ten most frequent unanswered or poorly answered questions.
- Run each through the checklist above.
- Fix the top three.
- Note the rest for next week.
After a month, you will have fixed a dozen of the most painful gaps in your documentation. After a quarter, the list will be noticeably shorter.
Why this matters beyond support
Better docs reduce tickets, but the effect goes further. Trial users find answers and stay. Buyers on your pricing page find the limits and plans they were looking for, which removes the delays described in pricing page questions that delay a SaaS purchase. And clear, specific help pages are exactly what people search for, so your documentation starts bringing in visitors.
Every business has a version of this. Online stores see it with product details, as in what an unanswered product question costs a small store. The fix is always the same: treat the question as feedback on the content.
The mistake to avoid
The common failure is fixing the answer in a support reply and never touching the docs. The support team writes an excellent explanation, sends it to one user, and the next user asks again.
Make it a rule: any answer written twice goes into the docs. It feels like extra work for a week, then it saves work every week after.
Try it with your own questions
Take your five most repeated support questions and run them through the checklist today. Then see how your current docs perform when users ask directly. You can build a free assistant from your docs site and put the five questions to it. Where it struggles, you have found your first gaps. For more on the rest of what it does, see the features page.