When to use it
When you have a description of a product, service or offering and you need a "Frequently asked questions" section for a landing page, a product card, a support bot or a knowledge base — one that actually clears up doubts and objections rather than answering "How do I sign up?". The role is a copywriter plus a support agent who thinks on the customer's behalf. The output: a FAQ built from real questions (including the awkward ones — price, guarantees, "what if it is not for me"), grouped by stage, with honest short answers.
The prompt (grab it and paste)
You are a copywriter and support agent who thinks ON the customer's behalf and is not afraid of awkward questions. Put together a FAQ section.
PRODUCT/SERVICE: "<PASTE THE DESCRIPTION: what it is, who it is for, how it works, price/terms, specifics>". WHERE THE FAQ WILL LIVE: <landing page / product card / support bot / knowledge base>.
COMMON CUSTOMER OBJECTIONS/DOUBTS (if I know them): "<…>".
Do this:
1. Generate the REAL questions a customer asks, grouped by stage: BEFORE buying (is it right for me, why is it better, how much does it cost, what guarantees), DURING (how to order/pay, timelines, how to get started), AFTER (support, refunds, what if it does not work out).
2. Be sure to include the AWKWARD questions and objections: "why is it so expensive / so cheap", "why are you better than <a competitor/the free option>", "what if it is not for me / does not work", "is it safe", "are there hidden fees". Do not hide them — these are exactly what stops people buying.
3. For every question — a short HONEST answer in plain words, in the customer's language, that removes the doubt (not a marketing brush-off). Where the answer depends on your terms — leave a "<…>" placeholder, do not invent facts (prices, timelines, guarantees).
4. Mark the 5–7 MOST important questions that definitely belong at the top.
Tone — <friendly / businesslike>. Do not invent product features that are not in the description. Where you are unsure of a fact — leave "<…>" for me.
Filled-in example
Product: an online Python course for beginners, 3 months, with homework review and mentor support, price 30,000 ₽, instalments available. Where: a landing page. Tone: friendly.
Expected AI response: BEFORE — "Is it right for me if I am a complete beginner?", "Why is it better than free YouTube videos?", "How much is it and are there instalments?", "What if I do not understand the material?"; the awkward ones — "30,000 — why not cheaper?" (the answer covering homework review and a mentor, not just videos), "What if I quit halfway?", "Is there a money-back guarantee?"; DURING — "How many hours a week does it take?", "How do I pay?"; AFTER — "Do I keep access?", "Will you help with job placement?"; honest answers in a beginner's language, prices and guarantees left as placeholders for your real terms; the top 7 questions pulled to the top. No invented features.
Variations
- From reviews/support threads. "Here are real questions from support and reviews — turn them into a FAQ with answers" (see "Review analysis").
- For a bot. "Format it as question→answer pairs for a chatbot, with short phrasing and variants of how a customer might ask the same thing."
- Objection handling for a landing page. "Just the 'doubts and objections' block — the 5 biggest ones, with answers that move people toward buying."
Pro tips
- The power of a FAQ is in the AWKWARD questions: price, guarantees and "why are you better than the free option". People tend to hide them, and those are exactly what blocks the purchase. Insist the AI includes objections, not just "how do I register".
- Answer in the customer's language and answer honestly: a marketing brush-off ("our product is unique") does not remove doubt, it deepens it. And do not let the AI invent your terms — plug in prices, timelines and guarantees yourself (the "<…>" placeholders), otherwise untrue claims end up on your landing page, which is also an advertising-law problem.
- The best source of questions is your actual support queue, reviews and the objections that come up in sales: top up the generated FAQ with what customers really ask. And keep the answers short — people skim a FAQ at the moment of doubt.