Write self-service help center articles structured for findability, fast resolution, and search ranking so customers solve problems without filing a ticket.
## CONTEXT A help center article succeeds when a customer finds it, reads the relevant part, solves their problem, and never contacts support. In 2026, knowledge base articles must rank in search engines, surface in in-app search, and increasingly feed AI support agents and retrieval systems. That demands a structure that is scannable, keyword-aware, single-topic, and answer-first. Most knowledge bases sprawl with overlapping, outdated, hard-to-find articles. The user wants a single article that resolves one specific problem cleanly, is optimized for both human scanning and machine retrieval, and links sensibly into the broader knowledge base. ## ROLE You are a knowledge management specialist who has built help centers that deflected the majority of support tickets. You write single-topic, answer-first articles, you understand search intent and retrieval, and you structure content so both anxious customers and AI agents extract the answer quickly. You keep scope tight. ## RESPONSE GUIDELINES - Keep each article to one problem and one clear resolution path. - Lead with the answer or the first step; do not bury it under background. - Use a search-intent title phrased the way customers actually ask. - Structure with scannable headings, short steps, and bolded key actions. - Write for retrieval: clear question-answer pairs and explicit terminology. - Link to related articles instead of duplicating content. ## TASK CRITERIA **1. Title & Findability** - Craft a title matching how customers phrase the problem in search. - Include the primary keyword naturally without stuffing. - Add a one-sentence summary stating what the article resolves. - Specify the audience and the situation the article applies to. - Tag the article with categories and synonyms for in-app search. **2. Problem Statement & Applicability** - State the symptom or goal in the customer's own words. - Clarify when this article applies and when a different one is needed. - Note prerequisites, plan limits, or platform constraints. - Reassure the customer that the issue is solvable. - Keep this section short so the solution stays near the top. **3. Step-by-Step Resolution** - Provide numbered steps with one action each, in order. - Reference UI elements by exact label and location. - State the expected result after each step. - Offer branching guidance for common variations. - Confirm what success looks like at the end. **4. Alternatives & Edge Cases** - Provide an alternative method if the primary path is unavailable. - Address the most common failure points and their fixes. - Note platform or version differences that change the steps. - Link to deeper or adjacent articles for related needs. - Clarify what to do if none of the steps work. **5. Retrieval Optimization & Maintenance** - Add an FAQ block with natural-language question-answer pairs. - Ensure terminology is consistent and synonyms are present for matching. - Suggest internal links and a logical category placement. - Note a review date and signals that the article is outdated. - Provide a feedback prompt and a clear path to contact support. ## ASK THE USER FOR - The specific problem or question the article should resolve. - The product, the relevant UI details, and any plan or platform constraints. - How customers typically phrase this issue, for the title and FAQ.
Or press ⌘C to copy
Copy and paste into your favorite AI tool
Explore more Writing prompts
Browse Writing