Analyze the support and help requests already on file to surface the topics your team keeps asking about but hasn't documented, ranked by volume, with a prioritized list of what to write first.
Look through our support and help requests from [time period] and find the topics people keep asking about that we haven't documented. Rank the biggest gaps by how many requests hit each one, then tell me what to document first.
An illustrative example. Your output will reflect your own sources, data, and prompts.
I went through the 612 support and help requests from the last 90 days, grouped them by topic, and checked each against what's in your Knowledge Center. Five topics account for most of the repeat questions and have nothing documented behind them.
Across the 612 requests, five topics keep coming back with nothing in the Knowledge Center to answer them. The chart ranks them by how many requests each one generated.
Undocumented topics by support requests (last 90 days)
Here's what to document first, starting with the topics driving the most requests.
Start with the top two: password resets and the billing module together account for 260 of the 612 requests, so documenting them clears the most volume for the least writing.
Want me to draft the password reset how-to first, or map all five gaps into a documentation backlog you can work through?
Knowledge Gap Analyzer reads the support and help requests already in your workspace, groups them by topic, and checks each one against what's in your Knowledge Center. The result is a ranked list of the questions people keep asking that have no documented answer.
Make sure your support and help requests are in the workspace, tickets, a shared inbox, or a help log in your Knowledge Center. Joy reads what's there.
Ask Joy to find the topics people keep asking about that aren't documented, and to rank them by how many requests hit each one.
Get a ranked chart of undocumented topics plus the evidence behind each one, how many requests it drove and what people were actually asking.
Ask for a prioritized writing list, then copy it into your documentation backlog or hand each topic to whoever owns it.
Save this ask as a custom command on the assistant your team already uses, connect it to your support sources, and re-run the analysis whenever you want a fresh read.
Gaps are ordered by how many requests they actually drive, so you write what people ask about most.
Joy compares each topic to what's already in your Knowledge Center, so you only see the true gaps.
Every topic comes with the request count and examples of what people asked, not just a label.
The output is a prioritized list you can drop straight into your documentation queue.
Narrow the analysis to one product or team to plan its documentation.
Compare gaps across periods to see whether new docs are reducing repeat questions.
Split gaps by customer versus internal requests to know which knowledge base needs the work.
Have Joy draft the top article as soon as the biggest gap is identified.
Joy reads the support and help requests in your workspace, groups them by topic, and compares each topic to what's in your Knowledge Center. Topics with lots of requests and no documentation surface as your biggest gaps, ranked by volume.
A topic that people keep asking about but that has no matching answer in your Knowledge Center. Joy flags these by checking the questions in your support requests against your existing documentation.
It works with the support and help requests connected to your workspace, including tickets, chat transcripts, shared inboxes, and escalations. It compares them against your Knowledge Center to find what's missing.
Gaps are ranked by how many requests each topic drives, so the questions your team fields most often rise to the top. Each gap comes with its request count and examples so you can sanity-check the order.
Yes. Ask again whenever you want a fresh read, and Joy analyzes the latest requests on file. Comparing runs over time shows whether the docs you've written are reducing repeat questions.
Join the waitlist and be first to try this workflow when JoySuite launches.