Now hand the work to your agent. Work through the steps below in your AI tool's chat. Replace the names in square brackets with your own project and topic names.
Step 1. Ask the Agent to Find Outdated Topics
Paste a prompt like this into your agent, naming the project you want to check:
Look through the [Project Name] project in my ClickHelp portal and list the topics that look out of date. For example, topics that haven't been updated in a long time, or that mention old version numbers, removed features, or steps that no longer match the product. For each topic, give me its title and a short reason why it looks outdated. Don't change anything yet.
What you'll see: the agent searches the project and comes back with a list of topics, each with a short explanation — for example, "Importing Content — still describes the old import wizard and references version 7." Nothing has been changed; this is a report for you to review.
Step 2. Pick a Topic and Ask for a Proposed Fix
Choose one topic from the list and ask the agent to look closer and suggest changes:
Open the topic [Topic Title]. Show me exactly which parts look outdated and explain why. Then propose updated wording — but don't apply any changes yet.
What you'll see: the agent reads the topic and shows you the specific sentences or steps that look stale, with a suggested rewrite for each. You can ask follow-up questions, push back, or refine the wording before anything is saved.
Step 3. Approve the Change and Send It for Review
When you're happy with the proposal, tell the agent to apply it and move the topic to a review status:
That looks good. Please apply those changes to the topic and set its status to [your review status] so a writer can check it before it's published.
What you'll see: the agent updates the topic in your portal and changes its workflow status. Open the topic to confirm the new wording is there, and check that it now appears in your review queue. Because the change went to a review status rather than straight to published, a human still has the final say.
| Status names depend on your portal's workflow. Use whatever your team uses for "ready to review" — for example, Under Review or Needs Review. You can ask the agent which statuses are available if you're not sure. |
Step 4. Scale It Up (Optional)
You just refreshed one topic. The same approach works across a whole project at once:
Go through every topic in [Project Name], update the ones that are clearly outdated the same way, and set each updated topic to [your review status]. Give me a summary of what you changed.
You can also pull in other sources within the same chat. If your agent is connected to your issue tracker through its own MCP server, you can ask it to compare a release's tickets against your documentation and point out — or draft — whatever isn't covered yet, without copy-pasting between the two tools. You stay in control throughout: the agent responds to your prompts in the chat, step by step, rather than running on its own.
Want This for Your Portal?
If you don't have the add-on yet, this is what it unlocks: handing real documentation work to an AI agent in plain language, directly inside ClickHelp. The Authoring MCP Server is part of the REST API & MCP add-on — see the pricing page to enable it, or talk to our team about your use case.
Already have the add-on? Explore Authoring MCP Server Use Cases for more ways to put it to work, from documenting a codebase to auditing translations.