AI agent for user support specialists
Support Knowledge Repair Agent
Help articles answer real customer questions correctly, verified against resolved tickets.
What it does
When a help article is outdated, support agents keep correcting it in tickets instead of fixing the article. Customers who self-serve still get the wrong steps. This agent runs weekly, finds repeated corrections in resolved tickets that are backed by verified resolutions, and picks the article section with the most corrections. It drafts a revised section and tests it against past cases: does the new text answer the resolved tickets correctly, and do answers that were already right stay right? If any answer gets worse, it revises or restores that part. When the product changelog and the ticket resolutions disagree, it asks the product owner. The knowledge-base owner reviews and publishes the revision. Edge case: an article serving two product versions gets a version note rather than losing the older steps.
How it works
Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.
Read the steps as a list
- Weekly run or product change
- Find repeated corrections in resolved tickets
- Pick the article section with the most corrections
- Draft the revised section
- Test retrieval against resolved cases before and after
- Do answers improve without breaking correct ones?If not: revise or restore the section. Back to step 4.
- Knowledge-base owner reviews and publishesThe agent waits here for your OK.
- Tested article revision ready
How it decides
It ranks articles by how often agents corrected them, edits the most-corrected section first, and accepts a draft only when retrieval tests improve without breaking previously correct answers.
- Which article first: most corrections.
- Accept a draft: only when the test set improves overall and no answer gets worse.
- Ask the product owner: when the changelog and resolutions disagree.
Make it yours
Every agent is a starting point. You choose these settings for your own situation.
- Minimum repeated corrections before an article is picked (default 5 in 30 days)
- Size of the test set of resolved cases (default up to 50 per article)
- Run schedule (default weekly, plus after each product release)
- Who is asked when the changelog and tickets disagree (default the product owner)
- Who publishes (default the knowledge-base owner)
What keeps you in control
It always asks you first
- Publishing
- Statements not supported by product documentation
Hard limits
- Drafts only; never publishes.
It stops when
- Done: draft passes tests.
- Needs a human: documentation contradicts resolutions.
Set it up
We guide you through the set-up, step by step
Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.
- One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
- The agent then walks you through connecting your own data, one source at a time
- A downloadable copy with the flow chart, the rules and the full guide