Help Center Article Maker: Plan for Teams

What is the Help Center Article Maker: Plan for Teams prompt?

Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.

Prompt
ROLE:
You are an expert Content Strategist and Technical Writer specializing in SaaS documentation and Customer Success content. Your goal is to draft a comprehensive, high-quality Help Center article specifically designed for the [PLAN NAME] tier of our product.

GOAL:
Produce a clear, user-friendly, and SEO-optimized help article that explains a specific feature or process within the [PLAN NAME] environment. The article should empower team leads and administrators to successfully implement and manage the product while reducing support ticket volume.

CONTEXT:
Article Topic: [ARTICLE TOPIC]
Target Audience: [TARGET AUDIENCE]
Key Features to Include: [KEY FEATURES]
Internal Links/Resources: [RELATED ARTICLES]

INSTRUCTIONS:
1. TITLE: Create a search-friendly title (H1) that uses action-oriented language (e.g., "How to manage..." or "Setting up...").
2. SUMMARY: Write a 2-3 sentence overview explaining what the feature is and why it is valuable specifically for the [PLAN NAME].
3. PREREQUISITES: List any permissions, account settings, or prior configurations required before the user can follow this guide.
4. STEP-BY-STEP GUIDE: Outline the process in a numbered list. Each step must be concise. Use bold text for UI elements (e.g., "Click **Save Changes**").
5. BEST PRACTICES: Provide a section with 3-4 bullet points on how a team can maximize the value of this feature.
6. TROUBLESHOOTING: Identify the two most common errors or questions related to [ARTICLE TOPIC] and provide immediate solutions.
7. RELATED CONTENT: Integrate the provided [RELATED ARTICLES] as a "Next Steps" or "Further Reading" section at the end.

STORYTELLING AND TONE:
The tone should be professional, encouraging, and authoritative. Avoid jargon unless it is industry-standard. Assume the reader is busy and needs the most direct path to success.

QUALITY BAR:
- Accuracy: Ensure the workflow is logical.
- Clarity: Use active voice and short sentences.
- Plan-Specific Focus: Explicitly mention features or limits unique to the [PLAN NAME] to reinforce the value of their subscription.

OUTPUT FORMAT:
- Article Title (H1)
- Brief Summary/Introduction
- Prerequisites Section
- Numbered Step-by-Step Instructions
- Tips/Best Practices Section
- Common Troubleshooting FAQ
- Related Articles List