Help articles fail when they re-state the UI. Education articles succeed when they teach the underlying model so the user can solve adjacent problems on their own. A good prompt forces this distinction.
Who this is for
Support leads, customer education writers, founders writing their first help center, devrel team writing concept docs.
When not to use these prompts
Don’t use these for marketing copy. Don’t use them when the underlying product is broken — fix that first, then document.
Prompt anatomy / structure formula
Every education prompt should carry six elements:
- Audience: one specific reader.
- Goal: one outcome — read / click / agree / share.
- Voice: 2-3 anchor adjectives.
- Constraints: word count, banned phrases, must-include facts.
- Format: paragraph, bulleted, headed, table.
- Examples: 1-2 tone samples — best lever for matching voice.
Best for
- Concept article (teach the why)
- Step-by-step task article
- Troubleshooting article
- Glossary entry
- Walkthrough video script
12 copy-ready prompt templates
1. Task article skeleton
Task: `{task}`. Audience: `{userPersona}`. Write a help article: (1) When you'd do this (one paragraph), (2) Prerequisites, (3) Numbered steps with one screenshot location per step, (4) Success check, (5) Troubleshooting (3 common issues), (6) Related links.Variables to swap: task, userPersona
2. Concept article
Concept: `{concept}`. Write a 600-word article: (1) What it is in plain English, (2) Why it exists (the problem it solves), (3) How it works at a high level, (4) Where you'll see it in the product, (5) Two common misunderstandings.Variables to swap: concept
3. Troubleshooting article
Problem: `{problem}`. Write a troubleshooting article: (1) Symptoms, (2) Most likely cause (with how to check), (3) Less common causes, (4) When to contact support, (5) How to gather the right info before contacting.Variables to swap: problem
4. Onboarding-week article
New users get stuck on `{feature}` in the first week. Write a "your first {feature}" article: (1) Outcome promised, (2) 5-step walkthrough with success checks, (3) "What changes once you do this", (4) Next thing to learn.Variables to swap: feature
5. Glossary entry
Term: `{term}`. Write a 100-word glossary entry: (1) Definition in 1 sentence, (2) Why it matters here (1 sentence), (3) Where the user encounters it, (4) Link to deeper article. No "in plain English" wrapper sentences — be plain.Variables to swap: term
6. Comparison article (Help center version)
Help-center article: "Should I use A or B?" Output: (1) Quick verdict (1-line), (2) When to use A (3 specific signals), (3) When to use B (3 signals), (4) How to migrate later if you choose wrong. Don't hedge.7. Best-practices article
Best practices for `{task}`. Output 5 practices. Each: (a) Practice in 6-10 words, (b) Why it matters, (c) Anti-pattern to avoid. Don't restate the UI — talk about the decision.Variables to swap: task
8. Migration / change-of-behaviour article
We just changed `{behaviourChange}`. Write a user-facing article: (1) What changed, (2) Why (1 sentence), (3) What users need to do (if anything), (4) When the change is effective, (5) Where to opt out / get help.Variables to swap: behaviourChange
9. Visual / video script
Turn this help article into a 90-second walkthrough video script: (1) Cold open (5s) — outcome, (2) Steps with screen-action notes, (3) Outro (5s) — "next" link. Each section ≤ 20s of screen time.10. Bulk article tone normalisation
Audit these 20 help articles: {articleList}. Flag articles with inconsistent tone (some friendly, some terse). Pick one target tone, suggest 5 fixes per inconsistent article.Variables to swap: articleList
11. Reduce-ticket article angle
Top support tickets this month: {tickets}. For each cluster, design a help article angle that would let users self-solve. Output: 3 article titles + their core promise. Don't propose articles for one-off tickets.Variables to swap: tickets
12. Help-article hygiene
Audit this help article: (1) Title matches search intent? (2) Lede answers in one sentence? (3) Steps have success checks? (4) Outdated screenshots? (5) Links to neighbours? Output: a 5-item fix list.Common mistakes
- Vague audience — output reads generic.
- No tone anchor — every variant comes back same flavour.
- No constraints — word count, banned phrases, length cap.
- Skipping examples — examples are the strongest signal for voice.
- Trusting first draft — AI lands on safe middle.
- Overusing AI clichés (“In today’s fast-paced…”).
- No fact-check pass — AI is confidently wrong sometimes.
How to push results further
- Give 1-2 tone examples; “be friendly” is noise.
- Constrain ruthlessly.
- Read aloud before publishing.
- Cut adverbs / adjectives that don’t carry weight.
- AI for drafts 1-2, human edit for 3 — and 3 is what ships.
- Anchor in a real person from your audience.
- Test the headline standalone.
Practical depth notes
Use these prompts as starting points, not final answers. For Customer Education Article Prompts for Help Articles, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.
A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. Before saving a prompt as reusable, test it on one realistic input and one edge case. The realistic input proves the template can produce the normal deliverable; the edge case shows whether it handles messy constraints, missing context, or an unusual audience. Keep the better output, but also keep the failed version with a note on what was missing. That small failure log is what turns a prompt collection from a list of nice sentences into a practical working library.
FAQ
- How long should this piece be?: Match the channel — shorter where attention is shorter.
- Can AI do the whole draft?: AI for first two passes, human for the third.
- How often refresh?: When audience or claims change, or quarterly for evergreen content.
- Should I publish without an edit pass?: No. AI is confident, not always correct.
- Single voice or per-channel?: One brand voice; channels shift tone axes within voice.
- Repurpose this prompt for other content types?: Yes — swap audience, goal, voice. Structure is reusable.