Writing call notes another teammate can use

Sales notes should let a colleague who missed the call continue the conversation without asking the prospect to repeat it. Capture decision-relevant facts soon after the call. Separate the prospect's words from your interpretation, and record exactly what was agreed.

Key Benefits of Well-Written Call Notes in Australian Sales Teams

Use a small, repeatable structure

Begin with date, participants and their roles. Then record the current workflow, the issue described, its consequence, any constraints, open questions and next actions with owners and dates. A useful note says “Finance checks each new supplier record before payment; the operations lead says the last request waited two days.” “Pain around onboarding” does not give a colleague enough to act.

Mark uncertainty: if the caller said “perhaps fifty a month”, do not convert it to a measured volume. If the buyer did not confirm budget, leave it unknown. Keep your own idea—such as “our integration might help”—separate from what the prospect requested. Salesforce's discovery guidance centres on uncovering the prospect's wants, needs, motivations and pressing pain; preserve that evidence rather than merely label the opportunity hot or cold.

Make the hand-off usable

Write the promised follow-up so the next owner can send it. For example: “Share a two-page outline of how exceptions are handled by Friday; buyer will ask the process owner to review it.” Include any explicit objection or reason the offer may not fit. Do not hide an unresolved security or implementation question behind a positive summary.

Store notes in the approved customer system with access limited to people who need them. Avoid unnecessary personal detail. Before closing the record, ask whether another teammate could identify the next action and the evidence behind it in one minute. If not, revise the note while the conversation is fresh.