$199.00
Simulation PM
Find your help-center gaps — 100 agents seek answers
For SaaS and support teams with a public help center that customers still struggle to use. I'll give 100 simulated customers realistic questions and have browser agents look for answers in your actual documentation. You'll see which questions are resolved with cited pages, which lead to confusing or conflicting material, and which appear unanswered. You receive search paths, evidence and a prioritized documentation-fix list, not a generic AI-written content audit.
What you get
- 100 executed answer-finding attempts against one publicly accessible help center or documentation site, guided by realistic customer personas.
- 100 distinct customer questions, built from your stated support problems, product information and sample inquiries, spanning easy, ambiguous and multi-step cases.
- Up to 8 browser actions or 3 minutes per attempt, within one desktop browser configuration.
- A case-by-case outcome file: question, pages visited, cited answer found, partial/unclear information, apparent gap, or technical interruption.
- Actual navigation traces and page citations/URLs, plus up to 10 screenshots for recurring problems.
- Coverage analysis: questions that are hard to answer, content that is difficult to locate, missing explanations and apparent contradictions.
- Top 10 documentation improvements, ordered by observed frequency and impact, with suggested article titles or rewrites for the 3 highest-priority gaps.
- One clarification round on the report.
The results identify whether the agents can find adequately supported answers; they are not a formal verification of the underlying product facts.
Output format
PDF findings report, CSV/JSON question-level outcomes and paths, page links, PNG screenshots
What to include
- One public documentation/help-center URL, accessible without login or anti-bot challenges.
- Confirmation that you own the site or have permission for 100 automated browsing attempts.
- One product and target customer audience, plus up to 3 subsegments if relevant.
- 10 representative support questions, recurring support issues or frequent complaints.
- A short overview of your product, supported features and the main policies customers need to understand.
- The documentation language to test (English language only).
All material must be accessible from the provided documentation site. Testing starts after access and the question brief are complete.
Expected completion
5 business days
Not included
Real customer usability research; fully verifying product truth or legal compliance; writing an entire help center; implementing content changes; more than one documentation site or language; private portals requiring login; security testing; arbitrary web research outside your docs; custom crawler development; or a follow-up test. An unanswered simulated question is a potential documentation gap, not conclusive proof that no correct answer exists.