Write a follow-up your customer can act on

Your personal note records a workflow review with Acme: reporting fits their needs, but budget remains unresolved. A pilot was discussed without approval, and Maya agreed to send an outline by 16 November. The note suggests 19 November with their sales director to review scope and approval requirements. It also contains an internal discount ceiling of 15%, a forecast marked likely and an impression that the director seems skeptical.
A useful meeting recap includes brief context, the outcome, open questions, agreed actions with owners and dates, and the purpose and participants of the next conversation. Keep proposals explicitly unconfirmed, remove sensitive internal observations and review the message before sending it yourself. Use this as a practical editing format, with the customer’s concerns and commitments guiding what stays.
Prepare a separate message from the note
The Acme note above is a fictional example. It contains information for two different uses: following through with the customer and assessing the opportunity internally. Preparing the email means selecting the facts the recipient needs, including concerns that remain unresolved.
- Export the personal note from Noats as Markdown. Keep it available while you prepare a separate message in your email application. The export gives you the material to work from; selecting and editing that material is your next step.
- Select the customer-relevant facts. Retain the reporting outcome, unresolved budget, unapproved pilot and Maya’s commitment with its date. Retain the suggested conversation with the sales director, including its purpose and proposed date. Remove the discount ceiling, forecast and speculative judgment about the director.
- Draft the message from those selected facts. For this example, Maya can send the following on behalf of the sales team.
Thanks for reviewing the reporting workflow. We agreed it covers your reporting needs. Budget remains open, and the pilot is not yet approved.
Maya will send the pilot outline by 16 November. Could we meet with your sales director on 19 November to review the scope and approval requirements? That date is a proposal. Please flag any corrections.
The opening preserves the positive outcome without suggesting a purchase decision. The budget concern stays because it affects what can happen next. The pilot remains unapproved, and the suggested date remains a request. Sending an outline is the commitment already made.
HubSpot’s guidance on sales follow-ups recommends covering buyer challenges, suggestions discussed and mutually agreed next steps. Its example also names a sales director and the purpose of involving them. Here, reviewing scope and approval requirements gives the proposed conversation a specific job while the budget remains unresolved.
Check the promises before you send
Compare the draft with the personal note before sending it through your own email application. Read for changes in meaning, especially where a shorter sentence could turn a possibility into a commitment. Our guide to preserving owners, dates and conditions explains that compression check in more detail.
- Review the message against the note. Confirm that Maya owns the outline and that 16 November is the agreed delivery date. Check that 19 November remains proposed, the pilot remains unapproved and budget remains open. Confirm that the internal discount limit, forecast and judgment about the director have been removed.
The deletions serve a specific purpose. A discount ceiling describes your negotiating position, and a forecast describes your internal assessment of the opportunity. An impression about a stakeholder is speculation. The unresolved budget belongs in the message because it is a customer concern that still needs an answer.
Where a note lacks an owner or deadline, mark that detail as needing confirmation. Do not supply a date merely to complete the format. Resolution’s guidance on decisions and actions supports naming owners and deadlines; the date in your message should reflect what was actually agreed.
If you use AI to draft the email, keep the same review step. Microsoft’s guidance for sellers instructs the sender to check suggested content for accuracy and appropriateness. Compare names, dates, commitments and tentative language with the note, then send the reviewed text yourself.
The customer can expect the promised document by the stated deadline. Funding and authorization are still open questions. The proposed follow-up conversation requires confirmation.
More from the blog
· 4 min read
Four jobs behind your meeting notes
Follow a meeting through capture, transcription, speaker separation and notes. Check Noats’s Mac requirements, local defaults and optional cloud connections.
Noats·Meetings·Local AI
· 4 min read
Dictate a client follow-up from your meeting notes
Turn meeting notes into a spoken follow-up draft with Noats, then check names, amounts and commitments before sending.
Noats·Product
· 4 min read
Keep the commitment intact when the meeting becomes a note
Preserve decisions, owners, dates and the words that qualify a commitment. Follow one promise from the transcript to the written-up note.
Noats·Meetings