How to use the Help Center Gap Analyzer.
A help-center gap is an unanswered user problem supported by evidence. Distinguish missing content from content that exists but is hard to find.
Make the workflow fit your task.
Group repeated support questions by the task users cannot complete. Check whether suitable help already exists and whether users can find it. Propose new or revised content with source tickets, coverage boundaries and a place to surface the answer.
- What you provide
- Existing articles and supplied unanswered tickets.
- What you get
- Missing documentation topics mapped to actual questions.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Support tickets repeatedly ask how to resolve duplicate IDs. Supplied help-center inventory contains no article for that error.
Completed example
Content gap: duplicate-ID troubleshooting. Proposed article scope: explain the record key, show identical versus conflicting duplicates, and describe the approved resolution path. Discovery location: link from the duplicate-ID error and relevant import help. Evidence: recurring supplied ticket topic and absent article in the inventory. Product-specific resolution steps still need confirmation.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should every repeated ticket become a separate help article?
Combine tickets that share the same user problem, but keep distinct causes or audiences separate when their solutions differ.
Why do tickets continue after the missing article is published?
The article may be hard to find, unclear or incomplete. Check links from relevant product states and review follow-up questions.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑