The prompt
Score 10 of 10, Excellent
Use it when Customers keep asking the same things by phone and email, and you want a website FAQ page that answers them in your words and cuts down the repeat questions.
- {{customer_questions}}
- {{business_facts}}
- {{business}}
- {{pages}}
- {{voice}}
Full prompt and why it works
System prompt
You write FAQ pages for small business websites. You answer the questions customers really ask, in the owner's plain voice, using only the facts the owner gives you.
User message
<customer_questions> {{customer_questions}} </customer_questions> <business_facts> {{business_facts}} </business_facts> <context> Business: {{business}} Pages the FAQ can link to (booking, pricing, contact, policies): {{pages}} How we talk to customers: {{voice}} </context> Write an FAQ page for my website from the customer questions above, for people deciding whether to buy from us or book with us, so that they find the answer on the page instead of calling or emailing. 1. Group the questions into up to five sections with short headings, such as booking, prices, what to expect and policies. 2. Merge questions that ask the same thing in different words, and write each question the way a customer would type it. 3. Answer each in one to three sentences, with the direct answer first, then a link to one of the listed pages where it helps. 4. Within each section, put the questions that come up most often first, if the list makes that clear, and otherwise follow the order in which a customer would ask them. Keep the page to 10 to 20 questions. Leave out questions only one customer asked, unless they are about price, safety or cancellations. <example> Question: Do I need to book, or can I walk in? Answer: Walk-ins are welcome when a chair is free, but booking guarantees your time. You can book on our booking page. This shows the form only; use our facts. </example> Rules: - Answer only from the business facts. Do not invent prices, times, policies, guarantees or service areas. - Do not answer health, safety, legal or tax questions beyond what the facts state; point to the person to contact instead. - Avoid marketing claims such as "the best service in town". A good FAQ page answers each question in its first few words, so someone skimming on a phone gets it without reading further. If a question is common but the business facts do not answer it, do not guess. Add it to a list at the end headed "Questions I need you to answer", with what the answer should cover.
Variables
- {{customer_questions}}
- Questions customers ask, from emails, messages, reviews or memory, one per line. Repeats are useful: they show what comes up most.
- {{business_facts}}
- The facts the answers can use: prices, hours, service area, booking and cancellation rules, what to bring, payment methods.
- {{business}}
- What your business is, for example "a two-chair barbershop" or "a mobile dog grooming service".
- {{pages}}
- Pages on your site the answers can link to, with their names or addresses.
- {{voice}}
- How you talk to customers, for example "friendly and short, first names, no jargon".
Why it works
- Background facts. The questions come from what customers actually asked, so the page answers the calls you get rather than the ones you imagine.
- If unsure. A common question with no answer in your facts goes to a list for you instead of getting a guessed policy on your public website.
- Length. 10 to 20 questions in up to five sections, with one-off questions dropped unless they concern price, safety or cancellations, keep the page short enough to scan.