30 Claude Prompts That Write FAQ Sections

You are a product marketer and support content lead who writes clear, honest FAQs. <context> I need a complete, ready-to-publish FAQ section for my software product, delivered as a self-contained artifact with clean question-and-answer pairs plus matching FAQPage JSON-LD schema so it can rank as a rich result. </context> <inputs> - Product and what it does: [ONE-LINE DESCRIPTION] - Who it is for: [TARGET USER] - Top things people misunderstand: [COMMON CONFUSIONS] - Platforms and requirements: [WEB / IOS / ANDROID / BROWSERS] - Key limits or gotchas: [SEATS, LIMITS, WHAT IT DOES NOT DO] - Support and trial: [SUPPORT CHANNELS, FREE TRIAL DETAILS] </inputs> <task> Write 12-15 real FAQ questions in the natural voice a prospect would type, grouped under short headers (Getting Started, Features, Compatibility, Support). Answer each in 2-4 sentences, factually, resolving the misunderstandings above. Order questions from most-asked to niche. </task> <constraints> - Questions phrased as a person actually searches; no marketing fluff or hype. - Answers self-contained and accurate to the inputs; say plainly when something is not supported. - Each answer stands alone for schema without needing the others. </constraints> <format> Return the FAQ as a formatted artifact (grouped Q/A), followed by a valid FAQPage JSON-LD block, then a one-line note on where to place it on the page. </format>

You are a technical writer who documents individual product features for non-technical users. <context> I need a focused FAQ that answers every practical question about one specific feature, delivered as a self-contained artifact with clean Q/A and matching FAQPage JSON-LD. </context> <inputs> - Feature name and what it does: [FEATURE PLUS OUTCOME] - How to turn it on or find it: [LOCATION / STEPS] - Who can use it: [PLAN, ROLE, OR PERMISSION NEEDED] - Common mistakes or edge cases: [WHAT TRIPS PEOPLE UP] - Limits and defaults: [CAPS, DEFAULTS, DEPENDENCIES] </inputs> <task> Write 8-12 questions covering what the feature is, when to use it, how to enable it, who can access it, limits, and how it interacts with other features. Answer each in 2-4 concrete sentences with the exact steps or values from the inputs. </task> <constraints> - Reference real UI locations and steps, not vague "go to settings". - Be explicit about plan or permission gating. - No filler; every answer removes a real point of confusion. </constraints> <format> Return the FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a short note on linking it from the feature's help doc. </format>

You are a product marketer who writes honest comparison content that reduces buyer hesitation. <context> I need a comparison FAQ that answers the "which one is right for me" questions across my plans or versus a common alternative, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Product: [NAME AND CATEGORY] - Plans or options to compare: [E.G. STARTER / PRO / ENTERPRISE OR US VS COMPETITOR] - Key differences that matter: [LIMITS, FEATURES, SUPPORT LEVELS] - Who each option fits: [USE CASES PER OPTION] - Switching or upgrade rules: [HOW TO MOVE BETWEEN OPTIONS] </inputs> <task> Write 8-12 decision-oriented questions such as which plan fits a given team size, what the real difference is between two tiers, and when to upgrade. Answer each in 2-4 sentences that guide the reader to the right choice without dishonestly bashing alternatives. </task> <constraints> - Fair, specific, and grounded in the inputs; no invented features. - Frame trade-offs plainly so a reader can self-select. - Avoid superlatives; let the facts do the selling. </constraints> <format> Return the comparison FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on where to place it relative to the pricing table. </format>

You are a product launch lead who prepares support and comms materials for a release. <context> We are shipping a new feature and I need a launch FAQ that pre-answers the questions users and support will have, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Feature and what changed: [WHAT IS NEW] - Why we built it: [PROBLEM IT SOLVES] - Rollout: [WHO GETS IT, WHEN, GRADUAL OR ALL AT ONCE] - Impact on existing behavior: [WHAT CHANGES FOR CURRENT USERS] - Price or plan impact: [FREE / INCLUDED / PAID ADD-ON] - Where to learn more: [DOCS OR CHANGELOG LINK] </inputs> <task> Write 8-12 questions covering what shipped, why, who gets it and when, what changes for existing workflows, whether it costs anything, and how to opt in or out. Answer each in 2-4 sentences, calmly addressing any migration or disruption. </task> <constraints> - Address disruption honestly; do not bury behavior changes. - Concrete dates and rollout details from the inputs, no vague "soon". - Neutral, reassuring tone; no hype adjectives. </constraints> <format> Return the launch FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on which two questions to also paste into the in-app announcement. </format>

You are a developer-relations writer who documents integrations and APIs for a mixed technical and non-technical audience. <context> I need an FAQ that covers how my product connects to other tools and its API, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Product and what it integrates with: [NAME PLUS KEY INTEGRATIONS] - Native vs third-party connections: [BUILT-IN, ZAPIER, WEBHOOKS, API] - Auth method: [API KEY / OAUTH / TOKEN] - Rate limits and data scope: [LIMITS, WHAT DATA SYNCS] - Setup difficulty and who needs it: [NO-CODE / DEVELOPER] - Common connection errors: [TYPICAL FAILURES] </inputs> <task> Write 8-12 questions covering which tools connect, how to authenticate, whether coding is required, sync direction and frequency, rate limits, and what to do when a connection fails. Answer each in 2-4 sentences with accurate technical detail from the inputs. </task> <constraints> - Distinguish clearly between no-code and developer paths. - State auth method and limits precisely; no hand-waving. - Give an actionable first step for the common errors. </constraints> <format> Return the integration FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on linking each answer to the relevant setup doc. </format>

You are a support-content specialist who turns recurring tickets into self-serve help. <context> I need a troubleshooting FAQ that lets users fix the most common problems themselves, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Product: [NAME AND CATEGORY] - Top recurring issues: [3-6 COMMON PROBLEMS OR ERRORS] - Known causes for each: [WHAT USUALLY CAUSES THEM] - Fix steps you know: [ANY KNOWN RESOLUTIONS] - When to contact support: [WHAT USERS SHOULD ESCALATE] </inputs> <task> Write an FAQ where each question is a symptom in the user's words (for example "Why won't my file upload?") and each answer is a short, numbered fix sequence ending with a clear escalation path. Cover 8-12 issues, ordered by frequency. </task> <constraints> - Each answer gives ordered steps, not a wall of prose. - Always end with what to do if the steps fail. - Accurate to the inputs; do not invent fixes that were not provided. </constraints> <format> Return the troubleshooting FAQ artifact (Q/A with numbered steps), then a FAQPage JSON-LD block, then a note on which three answers deserve their own help article. </format>

You are a support writer who documents account access clearly and securely. <context> I need an FAQ covering account, login, and access issues, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Product and login methods: [EMAIL / GOOGLE / SSO] - Password and reset flow: [HOW RESET WORKS] - Two-factor authentication: [OPTIONAL / REQUIRED / HOW] - Common access blockers: [LOCKOUTS, EXPIRED LINKS, WRONG EMAIL] - Account changes: [CHANGE EMAIL, MERGE, DELETE] - Where to get help: [SUPPORT CHANNEL] </inputs> <task> Write 8-12 questions covering how to reset a password, recover a locked account, set up two-factor, change the account email, and what to do about "link expired" or "account not found" errors. Answer each in 2-4 clear steps. </task> <constraints> - Never expose insecure workarounds; keep security guidance sound. - Give exact steps and where to click from the inputs. - Reassure on data safety where relevant. </constraints> <format> Return the account FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on which answers to surface directly on the login screen. </format>

You are a customer-support operations lead who sets clear expectations about getting help. <context> I need an FAQ that explains how customers reach support and what to expect, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Support channels: [EMAIL / CHAT / PHONE / COMMUNITY] - Hours and time zone: [WHEN SUPPORT IS AVAILABLE] - Response times by plan: [SLA PER TIER IF ANY] - Self-serve resources: [DOCS, STATUS PAGE, COMMUNITY] - What to include when reaching out: [DETAILS THAT SPEED RESOLUTION] </inputs> <task> Write 8-12 questions covering how to contact support, hours and expected response times, how to escalate an urgent issue, what info to include, and where to self-serve first. Answer each in 2-4 sentences with concrete channels and times. </task> <constraints> - State real hours, channels, and SLAs; no vague "we respond quickly". - Guide users to self-serve before contacting where sensible. - Set honest expectations to reduce follow-up tickets. </constraints> <format> Return the contact FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on placing it on the contact and help-center pages. </format>

You are a support-content writer who handles outages, bugs, and status communication. <context> I need an FAQ that tells users how to report bugs and check service status, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - How to report a bug: [FORM / EMAIL / IN-APP] - What makes a good report: [STEPS, SCREENSHOTS, BROWSER] - Status page location: [URL OR CHANNEL] - How incidents are communicated: [BANNER, EMAIL, STATUS PAGE] - Typical fix or acknowledgement timeline: [EXPECTATIONS] </inputs> <task> Write 8-12 questions covering how to report a bug, what to include, how to know if an issue is already known, where to check status, and what happens after a report is filed. Answer each in 2-4 sentences with the concrete process. </task> <constraints> - Encourage reproducible detail without overwhelming the user. - Point to the status page before duplicate reports. - Set realistic expectations on acknowledgement, not fix promises. </constraints> <format> Return the bug and status FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on linking it from the in-app help menu. </format>

You are a mobile support specialist who writes help content for iOS and Android users. <context> I need an FAQ for mobile app users covering the issues unique to phones and tablets, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - App name and platforms: [IOS / ANDROID / BOTH] - Minimum OS versions: [SUPPORTED VERSIONS] - Common mobile issues: [CRASHES, SYNC, NOTIFICATIONS, LOGIN] - Offline and storage behavior: [WHAT WORKS OFFLINE] - Update and permissions guidance: [HOW TO UPDATE, PERMISSIONS NEEDED] </inputs> <task> Write 8-12 questions covering app crashes, sync problems, push notifications not arriving, offline use, storage or cache clearing, and updating. Answer each in 2-4 steps with platform-specific instructions where iOS and Android differ. </task> <constraints> - Note platform differences explicitly when steps diverge. - Give exact settings paths for each OS from the inputs. - Keep steps short enough to follow on a phone screen. </constraints> <format> Return the mobile support FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on linking it from the app's in-app help. </format>

You are a pricing-page copywriter who removes purchase hesitation with clear answers. <context> I need an FAQ that answers the money questions on my pricing page, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Plans and prices: [TIERS WITH PRICES] - Billing periods: [MONTHLY / ANNUAL, ANY DISCOUNT] - What counts toward limits: [SEATS, USAGE, PROJECTS] - Free option: [FREE PLAN / TRIAL / NONE] - Currency, tax, and payment methods: [ACCEPTED, VAT HANDLING] </inputs> <task> Write 8-12 questions covering how pricing works, monthly versus annual, what the limits mean, whether there is a free option, accepted payment methods, and taxes. Answer each in 2-4 sentences with exact numbers from the inputs. </task> <constraints> - Use the real prices and limits; never invent figures. - Be transparent about what is and is not included. - Address the hidden-cost worry head on. </constraints> <format> Return the pricing FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on placing it directly under the pricing table. </format>

You are a billing-operations writer who documents invoicing and payment questions. <context> I need an FAQ covering invoices, receipts, and billing details, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Where invoices live: [DASHBOARD / EMAIL] - Billing date logic: [WHEN CHARGES OCCUR] - Editing billing info: [VAT ID, COMPANY NAME, ADDRESS] - Failed-payment handling: [RETRY, GRACE PERIOD, DUNNING] - Receipts and history: [HOW TO DOWNLOAD PAST INVOICES] </inputs> <task> Write 8-12 questions covering where to find invoices, when charges happen, how to add a VAT ID or company details, what happens when a payment fails, and how to download past receipts. Answer each in 2-4 concrete steps. </task> <constraints> - Precise steps and exact locations from the inputs. - Explain failed-payment grace and retry clearly to prevent panic. - Cover finance-team needs like VAT IDs and company names. </constraints> <format> Return the billing FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on linking it from the billing settings screen. </format>

You are a customer-experience writer who explains refunds and cancellations transparently. <context> I need an FAQ covering how to cancel and how refunds work, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - How to cancel: [SELF-SERVE STEPS OR PROCESS] - What happens after cancelling: [ACCESS UNTIL PERIOD END, DATA] - Refund policy: [WINDOW, ELIGIBILITY, PRORATED OR NOT] - Refund timeline: [HOW LONG TO PROCESS] - Reactivation: [HOW TO COME BACK] </inputs> <task> Write 8-12 questions covering how to cancel, whether access continues until the period ends, refund eligibility and window, how long refunds take, what happens to data, and how to reactivate. Answer each in 2-4 clear sentences. </task> <constraints> - State the real policy exactly; do not soften terms into vagueness. - Give the cancel steps so users are not forced to contact support. - Be honest about non-refundable cases. </constraints> <format> Return the refunds FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on which answer to also show on the cancel-confirmation screen. </format>

You are a lifecycle marketer who reduces trial anxiety with straight answers. <context> I need an FAQ that answers everything a prospect wonders before starting my free trial, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - Trial length and what is included: [DAYS, FEATURES] - Card required or not: [CREDIT CARD UP FRONT?] - What happens at trial end: [AUTO-CHARGE, DOWNGRADE, LOCK] - How to cancel during trial: [STEPS] - Trial limits: [USAGE OR FEATURE CAPS] - Extending the trial: [POSSIBLE OR NOT] </inputs> <task> Write 8-12 questions covering trial length, whether a card is needed, what happens when it ends, how to cancel before being charged, what is limited during the trial, and whether it can be extended. Answer each in 2-4 reassuring, factual sentences. </task> <constraints> - Be crystal clear about auto-charge and how to avoid it. - No dark-pattern phrasing; the goal is trust. - Exact days and limits from the inputs. </constraints> <format> Return the trial FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on placing the 'do I need a card' answer near the signup button. </format>

You are a billing-experience writer who explains plan changes and proration in plain language. <context> I need an FAQ covering how upgrading, downgrading, and proration work, delivered as a self-contained artifact with clean Q/A and FAQPage JSON-LD. </context> <inputs> - How to change plans: [SELF-SERVE STEPS] - Upgrade billing: [CHARGED IMMEDIATELY, PRORATED HOW] - Downgrade behavior: [WHEN IT TAKES EFFECT, FEATURE LOSS] - Seat changes: [ADD OR REMOVE SEATS MID-CYCLE] - Annual-to-monthly rules: [SWITCHING BILLING PERIODS] </inputs> <task> Write 8-12 questions covering how to upgrade or downgrade, when charges or credits apply, how proration is calculated, what happens to features and data on downgrade, and how mid-cycle seat changes are billed. Answer each in 2-4 sentences with concrete examples. </task> <constraints> - Use a simple worked example to explain proration. - Be explicit about what is lost on downgrade. - Accurate to the billing logic in the inputs. </constraints> <format> Return the plan-change FAQ artifact (Q/A), then a FAQPage JSON-LD block, then a note on linking it from the change-plan modal. </format>