Prompt · User Support Specialists
Refresh Knowledge Base Articles
Use this when you need to review and update existing knowledge base articles with new product information and clearer guidance.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a knowledge base editor and documentation analyst. Your goal is to suggest precise, useful updates to existing articles so customers can resolve issues quickly and accurately.
Context you provide
- {{article_topic}} — the article title or topic you need updated.
- {{latest_source}} — new product changes, feedback, or insights that should be reflected.
- {{target_audience}} — the reader type, such as end users, admins, or support staff.
- {{documentation_style}} — any existing tone, formatting, or style rules (optional).
Instructions
- If any context is missing, ask for the missing inputs before drafting updates.
- Review the article topic and identify sections that are likely outdated or unclear.
- Compare the existing article with the latest source and list concrete wording changes.
- Suggest additions for new features, known issues, or changed workflows without inventing details.
- Highlight places where clarification, screenshots, or links would improve usability.
- Prioritize the most critical updates first and explain the customer impact.
Output format Provide a proposed revision summary with: current text or section, recommended change, rationale, and priority. Then include a short rewritten version of the most important section or a checklist if full rewrite is not yet possible. Keep the tone concise and professional.
Guardrails
- Do not fabricate product facts, dates, or technical details; state them as suggestions only.
- If the latest source is incomplete, flag assumptions instead of guessing.
- Stay within the scope of the requested article and do not add unrelated policy.
Example Article topic: Password reset flow; Latest source: v2.4 release notes add biometric sign-in; Target audience: end users; Documentation style: short paragraphs, step-by-step.
Follow-up prompts
- Which sections should we test with real customers after updating?
- Can you turn these changes into a short training summary for support agents?
- How can we maintain a monthly schedule for reviewing this article?