Turn Pasted Customer Questions into a Clear FAQ Page with Short Answers
You get a ready-to-publish FAQ page with duplicate questions merged, answers under 60 words drawn only from your facts, and a list of gaps.
Prompt
You are a customer support lead who writes help-center FAQ pages.
After this message I will paste two things: raw customer questions (emails, chat logs, tickets, reviews) and the facts you may use (policies, product notes, pricing, shipping details). If I paste only questions, ask me for the facts and wait before writing.
Your job: turn the questions into a clean FAQ page customers can scan in under two minutes.
Rules:
1. Merge questions that ask the same thing in different words into one entry, and count how many times it came up.
2. Write each question the way a customer would type it, in plain words, under 15 words.
3. Answer each question in under 60 words, using only the facts I provide. Never guess prices, dates, timelines or policies.
4. Start every answer with the direct answer (yes, no, a number or the first step), then add one line of detail or the next step.
5. Group entries into topic sections and order entries by how often they were asked.
Output format:
- Page title
- Topic sections as H2 headings, each with Q&A pairs: question in bold, answer below, then (asked X times)
- Table titled Questions I Could Not Answer: Question | Times asked | Fact needed
- List titled Duplicates Merged: the original wordings combined into each entry
Finally, flag any facts that conflict or look out of date, and name the answers that depend on them.Example output
Tips and common edits
Why this works
- Merging duplicates with counts shows which questions matter most and keeps the page short.
- Limiting answers to your facts stops the model from inventing refund rules or delivery dates.
- The 'could not answer' table turns gaps into a clear to-do list for your policy docs.
Use when your inbox keeps repeating the same questions. Paste 20-100 real questions plus your policies or product notes into ChatGPT, Claude or Gemini. More real wording gives better merging.
Common edits
- Change the 60-word limit to 30 words for an in-app help widget or chatbot.
- Ask for the output as HTML with FAQ schema markup so you can paste it into your site.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Find Help Center Gaps by Matching Support Tickets to Existing Articles
Get a ticket-to-article match table and a ranked list of new help articles to write, with ticket counts and deflection potential for each.
Audit a Help Center Article for Gaps, Jargon and Outdated Steps
Paste a help center article and get a pass/fail checklist scorecard plus a line-by-line fix list ranked by customer impact, without a full rewrite.
Turn Feature Notes into a Step-by-Step Help Center How-To Guide
Paste rough notes about a product feature and get a customer-ready how-to guide with one action per step, bold UI labels, expected results and a troubleshooting section.
Turn Support Ticket Topics into a Help Center Category Structure and Article List
Groups your pasted ticket topics into 5-8 customer-language categories, flags duplicates and orphans, and ranks proposed article titles by ticket volume.
Write Help Article Titles and Meta Descriptions in Your Customers' Words
Get help article titles that start with the customer's task verb and meta descriptions within search length limits, each with a character count and the customer phrase it matches.
Build a Yes/No Troubleshooting Decision Tree for a Recurring Product Issue
You get a step-by-step yes/no troubleshooting tree ordered from fastest, most likely checks to slowest, with ready-to-send customer messages and a clear escalation point.