TL;DR
- Most of the rewriting is removal. Internal notes carry champion doubts, pricing strategy and competitor mentions that must never reach the customer.
- The three follow-up situations need different structures: a clear next step, an unanswered question, and a next step discussed but never agreed.
- The third case is where AI recaps fail hardest, because they confidently state an action nobody committed to.
- Check commitments before polishing prose. A well-written email containing a promise nobody made is worse than a rough one that is accurate.
"Thanks for the productive discussion" does not tell the buyer what happens next.
Neither does a six-paragraph summary of topics they just spent an hour discussing. A good follow-up makes it easy for the buyer to confirm the next step, forward the relevant information internally or correct something you misunderstood.
Judge the email by that standard. Can the recipient act on it without translating a recap back into a plan?
Magic Screen's notes workflow supports custom formats and follow-up drafting. The useful setup is a saved customer-facing format, with a separate place for anything that still needs your review. 1 2
Decide what the email must accomplish
Different meetings call for different follow-ups.
After discovery, the buyer may need a clear explanation of the problem you understood and the specific workflow you will show next. After a technical review, they may need answers, open items and the owner of each unresolved question. After a commercial conversation, the important details may be the offer's scope, conditions and the approval sequence.
Use the meeting's purpose to determine the email's structure. Avoid forcing every conversation into the same enthusiastic paragraph followed by a generic request for another call.
A useful draft usually contains a short opening, the relevant substance and a clear next action. The length should come from the amount of information the buyer needs, not an arbitrary desire to look thorough.
Separate internal notes before generating the email
An internal note can contain concerns that should never appear in a customer-facing draft: uncertainty about a champion, negotiation strategy, a competitive assessment or a manager's interpretation of the opportunity.
Create separate output instructions for the two audiences. Do not generate an internal account summary and rely on the rep to spot every sentence that should be removed before forwarding it.
The same distinction applies to information from other meetings. A broad account document may contain conversations with several stakeholders. Having access to those facts does not mean each person should receive all of them.
For the customer draft, prefer shared facts from the relevant meeting and explicitly approved supporting material. Where context from elsewhere is necessary, review whether it is appropriate to disclose.
Example 1: discovery with a clear next step
The following examples are fictional and written to demonstrate the format. They are not customer testimonials or generated product-test results.
Meeting facts: The buyer's operations team manually reconciles weekly reports. They want to see a location-level approval workflow. The seller agreed to send a sample using fictional data. A demonstration was agreed for Tuesday at 11 a.m. Pacific.
Draft:
Subject: Sample report and Tuesday's approval-workflow review
Hi Maya,
Your team's main priority is reducing the manual work involved in reconciling weekly reports. For Tuesday, I will focus the demonstration on location-level approvals and how exceptions reach the right reviewer.
I will send the sample report before the session using fictional data, as discussed.
We are set for Tuesday at 11 a.m. Pacific. Please include the regional lead who owns the current approval process so we can check the workflow against their requirements.
Thanks, Alex
The email names the buyer's priority and connects it to the next meeting. It does not replay every discovery question.
Before sending, the seller should verify the actual calendar date, time zone, attendees and the commitment to send the sample. If the regional lead's attendance was never agreed, the request should remain a request.
Example 2: technical review with an unanswered question
Meeting facts: The buyer asked about a permission requirement. The seller did not know whether a specific restriction was supported. The seller agreed to check with engineering. The buyer will provide a fictional example of the required access pattern. No response date was agreed.
Draft:
Subject: Follow-up on the regional access requirement
Hi Jordan,
I am checking the regional access requirement with our engineering team. I have not confirmed support for the specific restriction we discussed.
Please send the example access pattern using fictional users and locations. That will let us evaluate the exact requirement rather than answer a broader permissions question.
Once we have reviewed it, I will send a written response covering what is supported and any remaining limitation. We have not set a response date yet; I will confirm timing after the technical review is assigned.
Thanks, Alex
This draft preserves the unknown. It does not turn "I will check" into "we support it." That is the most important part of the message.
It also avoids adding a deadline because the customer sounded urgent. If the deadline matters, ask for it and establish whether the team can commit.
Example 3: the next step was discussed but not agreed
Meeting facts: The buyer likes the workflow but has not identified the person who owns budget approval. They suggested reconnecting after an internal discussion. No meeting or date was confirmed.
Draft:
Subject: Budget approval and the next review
Hi Priya,
The workflow appears relevant to the reporting issue we discussed. Before arranging another session, it would help to identify who owns budget approval and what they need to evaluate.
You mentioned discussing this internally. Please let me know whether the next useful step is a short review with that person or a written summary they can assess first.
I have not put another meeting on the calendar.
Thanks, Alex
The email respects the actual stage of the conversation. It asks for the missing information rather than asserting that the buyer agreed to a next step.
A stalled deal rarely benefits from an assistant making the record more optimistic. The follow-up should help resolve the uncertainty, not conceal it.
A reusable follow-up template
Use instructions like these for a dedicated customer-facing output:
Draft a sales follow-up email from the relevant meeting content. Do not send it. Audience: the customer participants in this meeting. Purpose: confirm useful shared facts and the next action. Include: - A specific subject line. - The customer's relevant priority in plain language. - Promised materials or answers. - Agreed next steps with owners and dates only when stated. - One clear request if a necessary next step remains unresolved. Rules: - Do not recap every topic. - Do not imply that interest equals approval or purchase intent. - Preserve dependencies and conditions. - Do not invent dates, attachments, recipients or completed work. - Do not say an item is attached unless that is confirmed separately. - Exclude internal scoring, negotiation strategy and speculation. - Avoid exaggerated praise and generic sales language. After the email, create a separate section titled INTERNAL REVIEW. List unresolved facts, promises, recipients and attachments to verify. Keep this section outside the customer-facing draft.
The internal-review section is a control for the drafter, not content to send. Your email workflow should make that separation obvious. If people regularly copy the whole result, produce two distinct notes rather than relying on a warning inside one document.
Make the format reusable in Magic Screen
Create a named snapshot note template for the follow-up. Attach it to the meeting alongside any internal note format you use. Magic Screen documents end-of-meeting generation for queued templates, so the instructions do not have to be rewritten after each call. 3 2
Use a name that reflects the audience, such as "Customer follow-up draft." Keep the internal decision note separately named. A rep should not have to inspect the prompt to understand which output is safe to review for external use.
This setup reduces repeat drafting and formatting. It does not establish that an email was sent or that a CRM contact was selected correctly. Treat sending as a deliberate step unless a separately verified integration and approval process handles it.
Check commitments before polishing the prose
Selected meeting-assistant reviews describe correcting action owners and other output details. That is a reason to check the fields that can become customer promises, even when the email reads naturally. 4
Start with the recipient and the purpose. Then inspect names, amounts, dates, product answers and anything the seller promised to do. Check that attachments are actually present and accessible to the intended recipient.
Only after that should you edit tone. A slightly plain sentence is less important than an invented deadline or an unsupported product claim.
The review should also catch accidental overreach. A buyer agreeing to evaluate a sample has not approved a pilot. A stakeholder volunteering to circulate a document has not accepted responsibility for budget approval. Keep the description tied to what was said.
Give the buyer something they can forward
A useful follow-up often becomes an internal message on the buyer's side. Write it so another stakeholder can understand the requirement and the next decision without reading your entire meeting history.
Include the relevant scope. Explain why the promised material matters. Make the unresolved question explicit. Remove conversational filler that does not help someone evaluate the request.
When the buyer needs a detailed technical answer, put that answer in a clearly organized section or an appropriate linked document. Do not make the email artificially short at the expense of necessary qualifications.
Save the follow-up template in Magic Screen, test it on an approved conversation and compare the draft with what you would actually send. Refine the instructions around repeated edits. The result should be a reliable starting point that gets closer to the finished email with each useful revision.
Frequently asked questions
How do I turn meeting notes into a follow-up email?
Start by removing rather than writing. Internal notes carry champion doubts, pricing strategy and competitor mentions that must not reach the customer, and that deletion is most of the work.
What if no next step was agreed on the call?
Say so plainly and propose one. This is the case AI recaps handle worst, because they confidently state an action nobody actually committed to.
Should I send the AI summary directly to the customer?
No. Check every commitment in it first. A polished email containing a promise nobody made costs more than a rough one that is accurate.
Sources
- Magic Screen. Magic Notes. Checked September 10, 2026.
- Magic Screen. Notes and Templates Overview. Checked September 10, 2026.
- Magic Screen. Creating Note Templates. Checked September 10, 2026.
- G2 / Fireflies reviewers. Fireflies reviews: pros and cons. Individual reviews; experiences and dates vary. Checked September 10, 2026.