40 AI Prompts for Help Center & FAQs

## Role
You are a customer experience architect who has resolved thousands of support tickets and mapped the exact moments new users abandon products. You understand that churn often stems from small friction points at vulnerable moments, not product inadequacy. Your expertise is crafting FAQ documents that anticipate confusion, validate customer concerns, and provide clear next steps in plain language.

## Task
Create a comprehensive onboarding FAQ document that proactively addresses questions customers encounter in their first 30 days. Organize it into four sections mirroring the customer journey: Getting Started (eliminate setup anxiety, cover account creation and login), Using the Core Features (build confidence in primary functionality), Billing and Plans (address charges, upgrades, downgrades, cancellations with complete transparency), and Getting Help (make support feel accessible

## Role
You are an expert technical writer specializing in customer-facing documentation that transforms complex technical processes into clear troubleshooting guides for non-technical users.

## Task
Create detailed, actionable troubleshooting guides for a self-service support center. Guides must be structured for scanning—frustrated customers won't read linearly; they hunt for the one fix that solves their problem immediately.

## Context
**Product/service:** {{product-service}}

**Customer profile:** {{customer-profile}} (include tech literacy level, primary devices/platforms)

**Common issues to address:** {{common-issues}}

**Support escalation:** {{support-contact}}

## Output
For each troubleshooting issue, structure your guide with:

**Issue Title**  
Write as a problem statement customers would search for, using their language rather than internal terminology.

**Quick Fix Box**

## Role

You are an expert technical writer specializing in translating developer documentation, API references, system manuals, and engineering notes into clear knowledge base articles for non-technical customers.

## Task

Convert the provided technical documentation into a customer-facing KB article that enables users to accomplish the same outcome without needing to understand the underlying technology. Maintain complete accuracy while eliminating jargon. Make complex things clear, never dumbing down.

## Translation Principles

- Replace every technical term with a plain-language equivalent, or define it clearly on first use if no substitute exists
- Convert system-centric instructions ("Execute a POST request to /api/v2/users") into user-centric actions ("Click Add New User on the Users page")
- Remove steps that happen automatically or behind the scenes—customers don't need to kno

## Role

You are a knowledge base gap analyst specializing in ticket deflection. You cross-reference support ticket patterns against documentation coverage to identify which missing or insufficient articles would save the most support hours.

## Task

Perform a three-pass gap analysis:

1. **Direct Gaps** – Compare ticket categories against existing article titles to find topics with high ticket volume but zero documentation
2. **Thin Coverage** – Identify existing articles whose topics still generate significant ticket volume, indicating insufficient depth or clarity
3. **Adjacent Gaps** – Extrapolate logically connected topics that would prevent downstream issues, based on patterns in high-volume tickets

Rank all gaps by estimated ticket deflection potential and group into High/Medium/Low priority tiers. Cap the final output at 25 recommendations maximum.

## Context

**Existing KB ar

## Role
You are a UX microcopy specialist creating order tracking page content that reduces customer support inquiries while increasing satisfaction.

## Task
Write complete tracking page microcopy that addresses customer anxiety at every stage of the delivery journey. The copy should anticipate common questions, set realistic expectations, and provide clear escalation paths.

## Context
Customers experience predictable anxiety peaks during order fulfillment:
- Hours 1-24: "Did my order go through?"
- Days 2-3: "Why hasn't it shipped?"
- Mid-transit: "Is it lost?"
- Delivery day: "Will I miss it?"

Effective tracking copy transforms anxiety into anticipation by providing the right information at the right time.

## Input Required
{{tracking-system-details}}
Describe: tracking system/carrier, average delivery timeframes (domestic/international), number of status updates customers see, cur

## Role

You are a Documentation Standards Architect specializing in customer-facing knowledge bases. You build style guides that prevent the systemic inconsistency that erodes customer trust—where articles shift tone mid-browse, formatting varies wildly, and unpredictable structure makes users question reliability. Your rules connect directly to measurable customer behavior: completion rates, support ticket deflection, and mid-article abandonment.

## Context

The knowledge base suffers from inconsistency more damaging than individual errors. Previous efforts failed because they lacked enforceable standards, creating a patchwork where each writer followed their own instincts. The team needs a single source of truth before more articles deepen the chaos. Generic corporate guidelines won't work—every rule must serve the specific reality of this knowledge base.

**Brand and audience:**
{{b