Customer Discovery Conversation
A 45-minute customer discovery conversation guide for sales and solution teams, with a timed agenda, open prompts, evidence-capture guidance, and a structured close. Use it to understand the customer's situation before discussing solutions.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Business services · Software and technology · Consulting
Overview
The Customer Discovery Conversation page is a reusable 45-minute guide for sales and solution teams who need to understand a customer's problem before proposing an answer. Its agenda divides the conversation into opening context, understanding the current process, exploring evidence, and agreeing a next step. The time boxes are facilitation guidance, not a live workflow.
The page includes open-ended prompts for walking through a process, recalling a recent example, discussing impact and workarounds, clarifying estimates, and defining meaningful improvement in the customer's own terms. A capture section shows what to record: the situation, roles, sequence, reported scale, impact, workaround, and unanswered questions. Its fictional Northstar Services example demonstrates how to label a customer report, a customer estimate, a team hypothesis, and an unknown separately; the example does not provide measured results.
Use this guide when the problem or process is not yet clear, or when a team needs a neutral way to gather evidence before exploring options. It is not a product demonstration script, a qualification scorecard, a technical discovery questionnaire, or a CRM record. Do not use it as a substitute for customer-specific data-handling rules or for a separate deep-dive when multiple processes and stakeholder groups need attention. After the call, store notes and follow-up through your organization's approved CRM process.
Standards & compliance context
- Use the approved CRM process for customer-specific notes and follow-up; this page does not itself store or submit conversation records.
- Follow organizational requirements for customer information, consent, retention, and access because the template does not define those controls.
- Attribute reported facts and estimates to the customer or participant role, and keep internal hypotheses visibly separate from verified information.
- Keep the page readable with a clear heading hierarchy and accessible text alternatives for its illustrative image, consistent with WCAG 2.1 AA practices.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Understand the problem before proposing a solution
Use the fictional Northstar scenario to frame the discussion around the customer's process and desired improvement rather than a predetermined answer.
-
Northstar Services is a fictional example. Its customer operations team reports that staff sometimes re-enter request details as work moves between teams. Use this conversation to understand what happens, when it matters, and what the customer considers a worthwhile improvement—not to pitch a predetermined answer. Keep customer-specific notes and follow-up in your organization's approved CRM process.
A focused 45-minute agenda
The time boxes help the facilitator reserve space for context, a concrete problem example, evidence, and an agreed next step.
-
Reusable example agenda; these are facilitation time boxes, not a live workflow. Time Focus Intended output 0–5 min Opening context Shared purpose, participant roles, and permission to ask and clarify 5–20 min Understand the problem A clear account of the current process and a recent example 20–35 min Explore evidence Reported impact, frequency or scale, workarounds, and unanswered questions 35–45 min Agree the next step A corrected summary, one question to resolve, and an agreed follow-up owner and timing
Prompts that uncover the customer's experience
These open questions help the customer describe actual work, impact, and workarounds without being led toward a proposed solution.
-
Ask one question at a time. Follow the customer's account before exploring possible improvements. Open with the current process “Could you walk us through what happens from the moment a request arrives to the point it is ready for the next team?” Ask for a recent example “Thinking about the most recent time this happened, what did each person or team do?” Explore impact and workarounds “What changed for the people involved?” and “What do you do today to keep the work moving?” Clarify scale and variation “How often does this come up, based on what you can observe?” and “Does it differ by request type or handoff?” Record estimates as the customer's estimates. Define meaningful improvement “What would be different in the work if this improved?” Let the customer describe a useful outcome in their own terms. Turn a leading question into an open one Instead of “Would an automated form solve this?”, ask “Where do details get lost or repeated, and what happens next?” The open version explores the experience without presuming a solution.
Capture evidence without mixing it with interpretation
Separate customer-reported details, your team's hypotheses, and unanswered questions so the discovery record stays clear about what is known.
-
Record what the customer described, what your team inferred, and what remains unknown as separate things. What to capture For each concrete example, note the situation, roles involved, sequence of events, reported frequency or scale, impact, workaround, and unanswered questions. Attribute statements to the customer or participant role rather than presenting them as independently verified facts. Recent example: which request and handoff the customer described Roles involved: who entered, checked, or received the information Impact and workaround: the effects and compensating steps the customer reported Unknowns: details to verify before drawing a conclusion Worked example: repeated request details In the fictional Northstar conversation, the customer operations lead describes a recent request whose details were entered by one team and re-entered when another team picked it up. The lead estimates that this occurs on several requests in a typical week; no measured count is supplied. Customer-reported: a recent request was entered twice during a handoff Customer estimate: the pattern occurs on several requests in a typical week Team interpretation: the handoff may not carry all needed context; this is a hypothesis, not a confirmed cause Unknown: which request types are affected and whether the estimate can be checked against an approved source
Close with an agreed next step
A neutral summary, customer corrections, and a named follow-up owner give both sides a clear close to the conversation.
-
A useful close gives the customer a chance to correct the record and leaves both sides clear about what happens next. The conversation itself does not submit or store a record. Put customer-specific notes and follow-up in your organization's approved CRM process. Summarize what you heard State the current process, the example discussed, the reported impact, and the workaround in neutral language. Invite corrections Ask, “What have we misunderstood or left out?” Update your summary based on the customer's response. Name the question to resolve Choose one open question that would change your understanding, such as which request types are affected. Agree who follows up and when Confirm an owner and a mutually agreed timing aloud. Record the customer-specific agreement in the approved CRM process.
How to use this template
- Choose the customer process to explore, identify a facilitator and note-taker, and invite participants who can describe the work firsthand.
- Review the 45-minute agenda and tailor its time boxes and prompts to the meeting while preserving time for a recent example and a clear close.
- Open by explaining the conversation's purpose, asking about participant roles, and inviting the customer to clarify or correct your understanding.
- Follow the prompts to trace the current process and a recent instance, recording reported impact, workarounds, estimates, hypotheses, and unknowns as distinct items.
- Summarize the account neutrally, invite corrections, identify one question that could change your understanding, and confirm a follow-up owner and mutually agreed timing.
- Enter customer-specific notes and follow-up in your organization's approved CRM process, since this page does not submit or store a record.
Best practices
- Ask one open question at a time, then let the customer finish describing the process before introducing a follow-up prompt.
- Anchor the discussion in a recent example and record the sequence of actions and handoffs the customer describes.
- Attribute reported frequency and impact to the customer, and label estimates as estimates rather than measured counts.
- Keep customer statements, team interpretations, and unknowns in separate notes so a hypothesis does not become an asserted cause.
- Use neutral wording that explores where information changes or gets lost without presuming that automation or another solution is needed.
- Reserve the final minutes to restate the process, impact, and workaround, then ask the customer what you misunderstood or left out.
- Confirm the follow-up owner and timing aloud, and put the agreement in the approved CRM process rather than relying on memory.
- If one conversation uncovers several distinct processes, capture the boundary and arrange focused follow-up instead of compressing them into the same agenda.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this customer discovery template designed to cover?
It guides a 45-minute conversation from opening context through problem exploration, evidence gathering, and agreement on a next step. Prompts help uncover the customer's current process, a recent example, reported impact, workarounds, and what improvement would mean to them. It is for understanding the problem, not presenting a predetermined solution.
Who should facilitate the conversation, and who should attend?
A sales or solution team member can facilitate, with customer participants who understand the process being discussed. Clarify each participant's role during the opening so you can distinguish firsthand experience from interpretation. The template does not assign a specific internal owner; your team should decide who leads and who records notes.
How often should we use this guide?
Use it for an individual discovery conversation when you need to understand a customer's problem before proposing an approach. The 45-minute agenda is a reusable time-boxed example, not a required cadence or live workflow. If the problem involves several processes or stakeholder groups, schedule separate conversations rather than rushing through unrelated topics.
Does this template meet a regulatory or compliance requirement?
It is a conversation guide, not a compliance checklist or a substitute for your organization's policies. It advises teams to keep customer-specific notes and follow-up in the approved CRM process and to distinguish customer reports, team hypotheses, and unknowns. Follow your organization's rules for customer information, retention, consent, and approved recordkeeping.
How should we handle estimates or claims we cannot verify during the call?
Attribute estimates to the customer and record the basis as reported, rather than presenting them as measured facts. Keep your team's interpretation separate from the customer's account, and label unresolved points as unknowns. Agree on a specific question to resolve and use an approved source if verification is appropriate.
Can we customize the agenda and prompts?
Yes. Adapt the time boxes, examples, and questions to the customer's process and the available meeting time, while retaining space to hear a recent example and agree a next step. Replace the fictional Northstar scenario with a clearly identified example relevant to your audience, or remove it. Keep questions open-ended and avoid wording that assumes a particular cause or solution.
Does the template integrate with a CRM or store conversation notes?
No CRM connection or record submission is described in this page. The guide explicitly says the conversation itself does not submit or store a record. Transfer customer-specific notes and follow-up into your organization's approved CRM process using your existing procedures.
What should we do after the conversation?
Summarize the process, example, reported impact, and workaround in neutral language, then invite the customer to correct anything you misunderstood. Identify one open question that could change your understanding, and confirm who will follow up and when. Record the agreement in the approved CRM process; do not treat the sample agenda as an automated workflow.
How is this better than an unstructured discovery call?
The timed agenda helps reserve time for the current process, evidence, and a clear close instead of allowing the meeting to become an early pitch. The prompts encourage specific examples and observable details, while the capture guidance separates customer-reported information from team interpretation. It still depends on the facilitator listening carefully and documenting the conversation accurately.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Customer Discovery Conversation ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
