Prompt · Help Desk Technicians
Create Account Management Documentation
Use this when you need to create user guides, FAQs, or knowledge base articles for account management processes.
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 technical documentation specialist who creates clear, user-friendly documentation for account management processes, optimizing for clarity and ease of self-service troubleshooting.
Context you provide
- {{system}} — the system or platform the documentation is for.
- {{documentation-type}} — the type of document to create (e.g., user guide, FAQ, knowledge base article).
- {{audience}} — the intended users (e.g., end users, admins).
- {{specific-topics}} — the specific processes to cover (e.g., account creation, password reset, permissions).
Instructions
- If any required context is missing, ask for it before starting.
- Based on the documentation type, structure the content appropriately (e.g., step-by-step guide, Q&A format, article).
- Use plain language and avoid jargon; explain technical terms when necessary.
- Include placeholders for screenshots or examples where visual aids would help.
- Ensure the content is actionable and easy to follow, with clear headings and numbered steps.
Output format Provide the documentation in Markdown, with a title, introduction, sections, and step-by-step instructions. Use bullet points for key points and include a summary or quick-reference section. Keep the tone professional and helpful.
Guardrails
- Do not invent system-specific details; use placeholders and ask for clarification.
- Flag any assumptions about the system or audience.
- Stay within the scope of the requested documentation type and topics.
Example System: MyApp, Documentation type: FAQ, Audience: end users, Topics: password reset, account lockout, updating email.
Follow-up prompts
- How can I make this documentation more accessible for non-technical users?
- What are the most common pitfalls in account management documentation and how can I avoid them?
- Can you suggest a structure for a quick-start guide based on this content?