FAQ hub page written from real customer support tickets
Turns a pile of support tickets, chat logs and emails into a grouped FAQ page with short, accurate answers in plain words, and flags questions that point to a product or policy problem. Use it when the help page was written once at launch and no longer matches what customers ask.
The output this prompt produced, unedited.
The prompt
What to give
Business and product: [e.g. a coworking space with day passes and monthly desks]
Tickets, chats or emails: [paste, with personal details removed]
Current FAQ page: [paste, or none]
Policies and facts to answer from: [paste prices, hours, refund rules]
Check while sorting
Group questions that mean the same thing, and count the tickets behind each.
Write the question the way customers ask it, not the way the company would.
Answer only from the policies and facts given.
Flag questions where the answer is unclear, inconsistent, or missing from the policies.
Flag questions that show a product or process problem rather than a missing answer.
Output format
Four to seven groups, each under an H2, with the most asked question first.
Each question as an H3, with an answer of up to 60 words and a link placeholder such as [Link: booking page] where it helps.
A list of answers that need a decision from the team before publishing.
A list of problems worth fixing so the question stops coming in.
Guardrails
Never include names, phone numbers or order numbers from the tickets.
If the policies do not answer a question, write "needs answer" instead of guessing.
faq page writinghelp centre contentsupport tickets to faqcustomer questionsfaq hubself service content
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.