Skip to main content

Use Case: Sales Page FAQ Section (Works with Your CRM + Gmail)

Turn buyer questions into FAQ copy for your sales page.

V
Written by Victor Couto

🔌 Works best with your CRM or inbox. Connect GoHighLevel or Gmail and Jeremy AI finds the questions buyers really ask. It only reads.

Paste the questions buyers ask and the facts you can state. Get one file back: a question map, FAQ copy for the questions you can answer, a gaps list and a claims check. It restates only your facts. Nothing is published or sent.

It opens with a short "Here's what you'll get" preview. You'll see the SAMPLE questions pasted in with the rules, the FAQ built at about 14x speed (a real wait of about 58 seconds shows in about 4), the file saved with nothing published, the question map, the two not-provided rows plus the scoreboard content, the answers using stated facts only and the claims check.

What this use case does and who it's for

A sales page needs a FAQ. It's where buyers look right before they decide. But FAQ answers are where owners slip. A made-up price. A promise you can't keep. A "most clients" line you can't back up.

Here's the shortcut. List the questions and the facts you're able to state. Jeremy AI turns that into a FAQ you can paste into your page. Four parts:

  1. A question map. Three columns: question, fact used and answer status. One row per question. Status is "answered" or "not provided."

  2. FAQ section copy. A heading, a one-line intro and a Q and A for each answered question. Each answer is under 30 words.

  3. A gaps list. The questions with no stated answer, each marked "not provided."

  4. A claims check. Three columns: claim, source and status. Every claim ties back to a fact you gave.

It's for agency owners, coaches and course creators who need a FAQ block without making things up. It's a draft. Jeremy AI doesn't publish or send anything.

What you need before you start

  • A Jeremy AI account. Nothing to connect to try the sample.

  • A list of the questions buyers actually ask, with a stated fact next to each one. The sample is made up: eight questions for SAMPLE Lumen Growth, a paid-ads agency for gym owners. Questions like "Who is this for?", "What happens on the first call?" and "How much does it cost?"

  • Honest gaps. In the sample, price and other industries are "not provided." That's on purpose. If you haven't decided something, say so.

  • The rules for what the FAQ must never do. The sample uses HARD RULES: restate only the stated facts, never turn a fact into a promise, never use words like "guarantee," "typically," "usually" or "most," never calculate a new number, never invent a price, testimonial, deadline or policy, no offers, and never address you by name.

How to set it up

You use the default Jeremy AI worker. There's nothing to build.

  1. Open Jeremy AI. From the dashboard, type in the main box. Check the worker selector says Jeremy AI.

  2. Paste the prompt below. Swap your own questions and facts in where the sample ones are.

  3. Click Send message.

  4. Wait. The walkthrough speeds this up to about 14x. In real time it took about a minute.

  5. When it says the file is saved, read the chat summary first.

  6. Open the file card and read the question map.

  7. Scroll to the FAQ copy. Read every answer against your facts.

  8. Read the gaps list and the claims check.

The prompt

This is the exact prompt from the walkthrough. The company, the facts and every number are SAMPLE and made up. Replace them with yours.

Act as my "Sales Page FAQ" worker for SAMPLE Lumen Growth, a paid-ads agency for gym owners (all data below is made up). Turn the SAMPLE buyer questions and stated facts below into a FAQ section for the sales page. Create ONE file named faq-section.md using the file tool (reply with a short summary only) with: 1) a QUESTION MAP table with exactly 3 columns (question, fact used, answer status), one row per buyer question, where answer status is "answered" or "not provided", 2) FAQ SECTION COPY: a heading, a one-line intro, and a Q and A for each answered question only (each answer under 30 words, using only the stated fact), 3) a GAPS list of the questions with no stated answer, each marked "not provided", 4) a CLAIMS CHECK table with exactly 3 columns (claim, source, status). HARD RULES: answers restate only the stated facts, never turn a fact into a promise, never use words like "guarantee", "typically", "usually" or "most"; never infer a tool, owner or detail not stated; write "not provided"; every table has 4 columns or fewer, short cell text of 12 words or fewer; exact numbers only, never calculate a new number such as a total, difference or multiple, never invent a result, testimonial, price, deadline or policy; no general claims beyond the facts and no claims about what most owners experience; never offer or mention discounts, bonuses, free trials, giveaways, pauses or downgrades; never address me by name anywhere in the chat reply or the file. Drafts only, nothing is published or sent.
BUYER QUESTIONS AND STATED FACTS (SAMPLE):
1) "Who is this for?" Fact: gym owners with 2 or more locations.
2) "What do you change first?" Fact: one campaign per location, keep the 2 best ads and stop the rest, one booking page per location.
3) "Do you have an example?" Fact: SAMPLE Redwood Fitness Studio, 3 locations, cost per member $190 to $128, 6 to 17 new members per month, $4,000 monthly ad budget, 90 days.
4) "What happens on the first call?" Fact: it is a 20-minute strategy call.
5) "Who will I work with?" Fact: Dana K leads the strategy calls.
6) "How is the work reported?" Fact: a monday scoreboard, with the content of the scoreboard not provided.
7) "How much does it cost?" Fact: not provided.
8) "Do you work with other industries?" Fact: not provided.

Prompting tips and how to adapt it

  • Pair every question with a fact. One question, one stated fact. If the fact is missing, write "not provided." The question lands on the gaps list instead of getting a made-up answer.

  • Fill the gaps before you publish. The sample leaves price and other industries blank. A real page needs real answers. Add your price and your policy as stated facts, then run it again.

  • Keep facts plain. "It is a 20-minute strategy call" works. "Great call" doesn't.

  • Ban promise words. The prompt says never use "guarantee," "typically," "usually" or "most." That stops soft claims from sneaking in.

  • Ban new numbers. The prompt says never calculate a total, difference or multiple. In the sample, the Redwood numbers appear exactly as given: $190 to $128, 6 to 17 new members per month, $4,000 monthly ad budget and 90 days.

  • Keep answers short. The prompt says under 30 words each.

  • Ask for the claims check. It's how you confirm every line in a couple of minutes.

  • Adapt it. Swap in any offer: a course, a coaching program, a retainer or an event. Keep every table to 4 columns or fewer.

The result to expect

One Markdown file named faq-section.md, titled "Sales Page FAQ Section (Draft)." With the sample data you should see:

  • A 3-column question map with eight rows. Who is this for: gym owners with 2 or more locations. What do you change first: one campaign per location, keep 2 best ads and stop the rest, one booking page per location. Do you have an example: Redwood Fitness Studio sample data. What happens on the first call: a 20-minute strategy call. Who will I work with: Dana K leads the strategy calls. How is the work reported: Monday scoreboard. How much does it cost: not provided. Do you work with other industries: not provided.

  • FAQ section copy for the answered questions. A heading, "Frequently Asked Questions," a one-line intro saying the answers use only the stated facts, then a Q and A for each. For example: "Q: What happens on the first call? A: It is a 20-minute strategy call."

  • A gaps list. "How much does it cost? Not provided." "Do you work with other industries? Not provided."

  • A 3-column claims check with ten rows. Each claim is tied to a numbered fact you gave, and each is marked "stated fact."

The walkthrough shows the reply chat chips "Looks good, done" and "Tighten the example answer." Ignore them, or use the second one if you want a shorter answer.

The chat reply summarizes the file and offers follow-ups, like tightening the example answer. Nothing is published.

These are sample results from a made-up agency. Wording changes from run to run. Read every line before you put it on your page.

Check the "answered" status

This part matters. Look at the "How is the work reported?" row. In the sample, the fact says the work is reported on a Monday scoreboard, and the content of the scoreboard is not provided. The question map still marks it "answered."

That's only half true. You can say how it's reported. You can't say what's in it. The FAQ copy handles it well: "Work is reported on a Monday scoreboard. Scoreboard contents: not provided." But on your page, you'd want to fill that in.

So whenever a fact has a "not provided" part, check the status column. If it says "answered," read the answer. Then either add the missing detail as a fact, or tighten the prompt: "If any part of a fact is not provided, mark the status 'partly answered.'"

Common mistakes and fixes

  • A price shows up that you never gave. Delete it. Say: "Never invent a price. Write 'not provided.'"

  • A question marked "answered" has a missing part. Say: "If any part of a fact is not provided, mark the status 'partly answered.'"

  • An answer sounds like a promise. Rewrite it. Remind it: "Never turn a fact into a promise."

  • "Guarantee," "typically," "usually" or "most" appears. Delete it. Remind it: "Never use these words."

  • A new number appears. Delete it. Remind it: "Never calculate a new number such as a total, difference or multiple."

  • An answer is too long. Say: "Keep every answer under 30 words."

  • A table has more than 4 columns. Remind it: "Every table has 4 columns or fewer."

  • An offer shows up. Delete it. Remind it: "Never offer or mention discounts, bonuses, free trials, giveaways, pauses or downgrades."

  • You publish it as is. Don't. Read it once, fill the gaps, then put it on your page yourself.

Did this answer your question?