Most sales follow-ups are written an hour or two after the call, from memory and a few scribbled notes. They thank the prospect for their time, restate what you sell and suggest a next step. The prospect, who was on the same call, can usually tell the email could have gone to anyone.
If your calls run on Microsoft Teams, you already have a better source to write from. Teams can produce a full transcript of each meeting with every speaker named, and that transcript holds the prospect's own words: the problem they described, the objection they raised halfway through, and the date they mentioned for making a decision. Writing follow-ups from that record instead of from memory is a small change in process, and it can make each email far more specific.
Getting the transcript out of Teams
Transcription has to be switched on during the meeting. The organiser, co-organisers and presenters can start it from the meeting controls, and once the call ends the transcript appears in the meeting event on your calendar, or under Recap in the meeting chat, according to Microsoft's support documentation. It is stored in the organiser's OneDrive, and organisers and co-organisers can download it as a .docx or .vtt file.
Microsoft also makes transcripts available through its Graph API, which lets a CRM integration or automated workflow collect them without anyone downloading files. Guides to getting a transcript cover the permission involved, OnlineMeetingTranscript.Read.All, which an administrator has to approve, and the WebVTT format the transcript comes back in, with a timestamp and a speaker tag on each line and alternative Microsoft Teams APIs to get transcripts allow you to skip the complex permission flows.
On a sales call the prospect is usually from another organisation, and people from another organisation cannot view or download the transcript after the meeting. The same goes for anyone who dialled in by phone. The rep needs to be the organiser to get the file, and since colleagues in your own company cannot download it by default either, ask your IT admin to adjust the policy if a manager or sales engineer needs access.
What to pull from the transcript before writing
A transcript of a 45-minute call can run to several thousand words, and most of them will not make it into an email. Before drafting anything, read through and pull out five things:
- The problem in their words. If the prospect said "we lose about a day a month reconciling invoices", use that phrasing rather than your product page's version.
- Objections and hesitations. "We tried something similar two years ago" is an objection even when it is said in passing.
- Questions you did not fully answer. These give the follow-up a reason to exist beyond checking in.
- Other people involved. A finance director or team lead who "would need to see this" may be who the next email has to reach.
- Commitments and dates. Anything either side agreed to do, and any timeline the prospect gave for a decision.
The .vtt file carries timestamps, so if a passage needs context you can jump to that point in the recording instead of rereading the whole call.
Writing the first follow-up
The first email after the call has three jobs: show you listened, move one open question forward, and confirm the next step.
Say the owner of a 12-person accounting practice told you their team spends "most of the last week of every month chasing client paperwork", asked whether your tool works with Xero, and said their business partner would want to see pricing before the end of the quarter. A follow-up written from memory might read: "Thanks for your time today. As discussed, our platform can help streamline your month-end process. Let me know if you have any questions."
Written from the transcript, the same email opens with their own description of the month-end chase, confirms the Xero integration, and attaches a one-page pricing summary their partner can read without needing a call. The last line proposes a specific date for a second meeting with both partners, before the quarter ends, because that is the timeline they gave you.
Every line of the second version refers to something the prospect said, and the next step arrives with a date and a reason.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Using the transcript for later follow-ups
Later emails in a sequence produce most of the replies. In an analysis of more than 7.5 million outreach emails sent in 2025, Belkins found that steps two to six of a sequence generated 58.6% of replies, and the third email alone drove 35.6% of the meetings booked through email. Those figures come from prospecting sequences rather than post-call follow-ups, but the same principle applies after a sales call: the later emails do much of the work, provided each one gives the prospect a new reason to reply.
The transcript is a good source of those reasons. One follow-up can address the objection the prospect mentioned in passing, with a short example from a client who had the same concern. Another can go to the stakeholder they named, with a summary written around that person's priorities. A third can return to a detail from the call, such as a busy season they mentioned, timed to arrive a few weeks before it starts.
Each of these is harder to write from memory a fortnight later, once the specifics of one call have blurred into the next. Attaching the transcript to the deal record in your CRM lets anyone who picks up the account later write from the same source.
Doing this for every call
Reading and summarising transcripts by hand is manageable for a founder running a few calls a week and harder for a team running dozens. Many people paste the transcript into an AI assistant with a prompt asking for the five items above and a draft email, then edit the draft before sending. If you do, check what your company's data policy allows, since a sales call can include client names and commercial details.
The next step up is an off-the-shelf notetaker, which joins the call, transcribes it and drafts a summary automatically.
Building your own makes more sense for agencies and software companies whose call data needs to sit inside systems they control, such as a customised CRM or a client reporting dashboard. Most of that build is their own logic: which deal fields update, what the AI is asked to draft, and who reviews it before it goes out.
The recording layer underneath that build can be bought rather than written. Recall.ai, an API for capturing recordings, transcripts and metadata from meetings, is the top provider in this category and is used by over 3,000 companies. It works across Teams, Zoom, Google Meet and the other major platforms, so a team does not have to build and maintain a separate integration for each one its prospects happen to use. It is also the cheapest option on the market for startups, which pay $0.25 per recording hour for their first 10,000 recording hours through Recall.ai's startup programme.
Whichever route you take, the first change is a setting you can make before your next sales call: switch on transcription, and make sure the rep is the organiser. The follow-up written afterwards can then quote the prospect's own words back to them, answer the question they asked, and propose a next step on the timeline they set.
