Template

AI-Agent Client Discovery Questionnaire: Five Questions That Find the Real Scope

Use five high-leverage questions to uncover an AI agent’s audience, job, approved knowledge, boundaries, handoff, voice, and launch requirements.

Published by Qlynk AI · 9 min read · Updated 2026-08-14

A short interview should produce implementation decisions

A long questionnaire does not guarantee a useful brief. The goal is to ask a small number of compound questions that let you extract the agent’s audience, purpose, common intents, authoritative facts, prohibited topics, response behavior, and next step.

Ask for one rough answer at a time, summarize what you understood, and request clarification only where the answer changes the build. Do not make the client repeat information already supplied in a website, document, or earlier answer.

Question 1: Who is the agent for, and what should it help them do?

Ask: “Who should use this agent, what should it help them accomplish, and what five questions do those people ask most often?”

Extract the primary audience, secondary audiences, desired outcome, repeated intents, vocabulary, and a first set of launch tests. If the answer includes several unrelated jobs, choose the highest-value safe starting job rather than building a general assistant.

Question 2: What business information must it know?

Ask: “In one rough message, tell me what you offer and the facts people need before taking the next step—such as services, products, prices, inclusions, process, timing, hours, locations, policies, proof, and current limitations.”

Turn the answer into explicit facts and FAQs. Record conditions, dates, locations, plans, exclusions, and source ownership. Mark anything uncertain for confirmation instead of smoothing it into confident marketing copy.

Question 3: What must it never answer or decide?

Ask: “What must the agent never answer, promise, reveal, or decide; what should it say when information is missing; and exactly where should it send someone who needs a human?”

Capture sensitive information, regulated advice, private records, guarantees, negotiations, emergency matters, unsupported comparisons, and any action requiring authorization. Make the handoff actionable with a person, team, form, email, phone number, or approved link.

Question 4: How should the agent sound and guide the conversation?

Ask: “How should it sound, how detailed should answers be, what should it call the business and visitor, and what action should it normally recommend next?”

Convert vague answers such as “professional but friendly” into observable guidance: preferred terminology, response length, use of bullets, questions it may ask, phrases to avoid, and the single primary next step.

Question 5: Which sources and launch surfaces are approved?

Ask: “Which websites, documents, FAQs, notes, and contact links may the agent use; who approves them; and should the final agent use a Qlynk page, a website widget, or both?”

Record source permission, authority, owner, effective date, review trigger, privacy level, and publishing destination. Confirm who will create the client-owned account and who can approve publishing and website installation.

Turn the answers into a build pack

  • Agent briefName, type, audience, job, welcome message, suggested questions, and primary next step.
  • Knowledge planApproved facts, FAQs, links, documents, gaps, conflicts, and source owners.
  • Behavior rulesAllowed topics, blocked topics, uncertainty response, tone, response length, and escalation.
  • Launch planAccount ownership, publishing surface, website installation, acceptance tests, approval, and maintenance.

Frequently asked questions

Are five questions enough for every business?

They are enough for a focused Quick discovery. Use deeper follow-up for multiple audiences, regulated topics, complex policies, many source owners, or custom website requirements.

Should the client complete the questionnaire alone?

A guided conversation is usually better because you can summarize decisions, spot conflicts, and ask only the follow-up questions that affect the build.

What if the client does not know an answer?

Record it as a knowledge or policy gap. Do not invent a default; identify who can approve the missing decision.

Related Qlynk solutions

Related Qlynk resources

Turn this guide into a client-ready Qlynk build

Use the free Qlynk Agent Builder to run discovery, prepare approved knowledge, test the agent, and hand it to the client.

Open the free Agent Builder