flownote / Templates
Short answer
Useful sales call notes separate facts from the seller’s interpretation. Record the buyer’s goals, current process, impact, decision criteria, stakeholders, timing, concerns, and an agreed next step with an owner and date. Leave unknown fields unknown instead of filling them with guesses.
Editorial note: This guide was prepared with AI-assisted research, reviewed against the cited public documentation, and uses no customer recordings or private meeting data. Examples are explicitly fictional.
The discovery-call template
Copy and edit
Account — Call type — Date
Participants — Names, roles, and relationship to the decision.
Why now — The event or pressure behind the conversation, in the buyer’s words.
Current process — Tools, people, workflow, and where it breaks.
Desired outcome — What would be different if the problem were solved?
Impact — Operational, financial, customer, or personal consequences the buyer stated.
Requirements — Capabilities, security, integration, procurement, and implementation needs.
Decision process — Stakeholders, criteria, steps, timing, and budget status.
Concerns — Questions, objections, risks, and unresolved assumptions.
Next step — One concrete action, owner, and agreed date.
Evidence — Short buyer quotations or transcript references where authorized.
Facts, interpretations, and unknowns
| Type | Example | How to record it |
|---|---|---|
| Buyer fact | “Legal review normally takes two weeks.” | Attribute it to the speaker and preserve the context |
| Seller interpretation | Legal may be a timeline risk | Label it as an interpretation, not a buyer commitment |
| Unknown | Who signs the agreement? | Keep it as an open question with a follow-up owner |
| Decision | Buyer agreed to a technical review Tuesday | Record the exact next step, attendees, owner, and date |
CRM data becomes unreliable when empty fields are filled with optimistic assumptions. A visible unknown is more useful than a fabricated answer.
A fictitious completed example
Copy and edit
Juniper Works — Discovery — Aug. 15
Participants — Dani (operations lead), Noor (account executive).
Why now — The fictional company added two support regions and handoffs are inconsistent.
Current process — Team leads write recaps manually and copy tasks into a tracker.
Desired outcome — A consistent recap within the team’s existing workflow.
Requirements — Desktop support, export, and a security review before any pilot.
Decision process — Dani evaluates workflow; security reviews vendor; budget owner not yet identified.
Concern — Whether speaker labels remain clear in hybrid meetings.
Next step — Noor will send security materials by Aug. 18; Dani will invite IT to a test on Aug. 21.
Note — Juniper Works and all details are fictional.
Questions that create better notes
- What changed that made this worth solving now?
- Walk me through the current process from the first step to the last.
- Where does that process create rework, delay, risk, or frustration?
- Who else experiences the problem or helps choose a solution?
- What would your team need to see to feel confident moving forward?
- What happens if the current approach stays in place?
- What is the smallest useful next step, and who should join it?
Do not ask every question mechanically. The template is a coverage check, not a script that should interrupt the buyer’s train of thought.
From consented call to CRM-ready recap
- 1
Confirm capture
Tell participants what will be recorded and why, and follow the customer’s and your company’s rules.
- 2
Use the right structure
Select a sales-discovery output style so the first draft prioritizes buyer context and next steps.
- 3
Verify the evidence
Check commercial terms, stakeholder roles, dates, and attributed statements against the transcript.
- 4
Separate internal analysis
Keep seller strategy and sensitive internal judgment out of any note shared with the customer.
- 5
Send the mutual next step
Use the approved facts to create a short recap that both sides can correct.
Flownote’s Sales Discovery style can create the initial structure, while Ask AI can help locate a stated concern or next step. A seller remains responsible for the final CRM record and customer communication.
Frequently asked questions
What should sales call notes include?
Include participants, why now, current process, desired outcome, impact, requirements, decision process, concerns, unknowns, and an agreed next step.
Should sales notes include direct quotes?
Short attributed quotations can preserve important customer language when recording and use are authorized. Keep context, avoid unnecessary personal data, and follow your organization’s policy.
Should AI write directly into the CRM without review?
For consequential customer facts, a seller should verify the generated draft first. Names, terms, dates, stakeholder roles, and commitments deserve explicit review.
Related guides