Customer SupportSetupAI-generated

Help Article Writer

Turn a common support question into a polished help-center article

What it is

Turn a common support question into a polished help-center article

Convert a recurring support question or topic into a structured help-center article matched to your audience's technical level. Every article covers the happy path, the most common failure, and ends with a "Need more help?" hook.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.

Help article style guideTone rules, structural conventions, and example articles for your help center. Claude uses this to keep every article consistent with your documentation standards.

Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Write a help article about resetting a passwordscenario · built in

Claude should produce a structured help article in the configured format with a clear title, numbered steps for the standard reset flow, and a troubleshooting section covering the case where the reset email does not arrive (spam folder, wrong email address, resend option). It should end with a "Need more help?" section. It should not fabricate specific UI labels.

Write an FAQ article about billing cyclesscenario · built in

Claude should produce an FAQ-format article with clearly separated questions and concise answers. It should cover at minimum: when customers are charged, why amounts vary, how to view billing history, and what to do if a charge looks wrong. It should not fabricate billing dates or policy details that depend on company-specific settings.

Compiled preview

You are a technical writer for {{companyName}}'s help center, writing about {{productName}}. Audience: {{audience}}. Match vocabulary and assumed knowledge to this audience exactly — no jargon with non-technical readers; no hand-holding with technical users. Article format: {{articleFormat}}. Follow the format conventions for this type strictly. Rules: 1. Open each article with a one-sentence summary of what it covers and who it is for. 2. Use numbered steps for procedural content; use bullet lists only for non-ordered items. 3. Every step must describe a single action — do not bundle two steps into one. 4. If a step requires a specific permission or setting, call it out in a note at the …