Build your prompt panel

A prompt panel is the fixed list of questions you put to answer engines on a schedule, worded the same way every time. Start with 20 to 30 prompts chosen from the decisions your buyers actually make, label each one by type and journey stage, and log the platform, locale and date of every run. Without a stable panel, you cannot tell whether a change in answers came from your work or from chance.

Start from decisions, not keywords

Keyword lists describe what people type into a search box. Prompts describe what people ask an assistant, which is longer, more specific and full of context: who they are, what they need, what they have already tried. Begin with the decisions a buyer makes on the way to choosing you. Which problem do they have? Which kinds of solution do they consider? What do they compare? What do they need to verify before they commit?

Sales calls, support tickets, reviews and your own site search are the best raw material. Write prompts in the buyer's words, with a realistic constraint or two, and avoid stuffing them with your product terms.

Four kinds of prompt, measured separately

Mixing these types into one number makes visibility look better than it is: branded prompts mention you by definition. Keep unbranded prompts as the core of the panel, because they show whether assistants reach for you without being told your name.

Keep the wording stable

Once a prompt is in the panel, do not edit it. Small wording changes can change the answer, and an edited prompt breaks the history you are trying to build. When you want to test a variation, add it as a new, named prompt and keep the original running beside it.

Log every run

For each answer, record the engine, the locale and language, the date, whether you were logged in, and the full text of the answer with any sources it showed. That sounds like a lot; it is what turns a pile of screenshots into evidence. Answers vary between runs, so repeat each prompt more than once per cycle and look at how often an outcome occurs rather than at any single answer.

Worked example: Lumen CRM

Lumen CRM's team pulls twenty recent sales-call notes and highlights the questions prospects asked before booking a demo. They group them into four stages: noticing the problem (“why do deals stall after the first call?”), exploring solutions (“what kind of CRM suits a five-person team?”), comparing (“Lumen or a bigger suite?”) and verifying (“does Lumen integrate with our email?”).

They end up with twenty-four prompts: fourteen unbranded, four comparison, three branded and three fact-check. Each gets an id such as SOL-03, a stage and a type. They run the panel on two engines, twice each, and log the results in a shared sheet. The first run is their baseline; nothing is changed on the site until it is recorded.

How big should the panel be?

Big enough to cover your important decisions, small enough that someone reads every answer. Twenty to thirty prompts is a practical start for one product or location. Add prompts when you launch something new or enter a new market, not because a larger number looks more thorough. A panel nobody reads is worse than a short one somebody acts on.