The fastest follow-up is not always the best follow-up.

Fathom notes are source material. A good customer follow-up should be shorter, clearer, and more carefully reviewed than the raw meeting summary.

Start With the Customer's View

Before drafting, ask:

  • What did the customer need from this meeting?
  • What was confirmed?
  • What decisions were made?
  • What happens next?
  • What does the customer need to do?
  • What should stay internal?

The customer email should answer those questions without making them re-read the meeting.

Extract the Building Blocks

Pull out:

  • Confirmed facts.
  • Decisions.
  • Open questions.
  • Customer-owned tasks.
  • Internal-owned tasks that are safe to share.
  • Dates or timing.
  • Links to ticket, doc, or next meeting.

Do not include every transcript detail. Most customer follow-up is better when it is concise.

Remove Internal Context

Before writing the email, remove:

  • Debugging speculation.
  • Internal risk notes.
  • Private product feedback.
  • Pricing or renewal thoughts.
  • Names of internal teams that do not need to be mentioned.
  • Unreviewed AI language that sounds too certain.

If the customer needs an update later, keep internal details in the ticket or account note.

Follow-Up Email Template

Subject: Follow-up from [meeting topic]

Hi [Name],

Thanks for walking through [topic] today.

Here is what we confirmed:
- [Confirmed fact 1]
- [Confirmed fact 2]

Next steps:
- [Owner] will [task] by [date or timing].
- [Owner] will [task] by [date or timing].

Open question:
- [Question, if any]

I'll update [ticket/doc/project] after [next event].

Best,
[Name]

Example

Subject: Follow-up from SSO troubleshooting review

Hi Jordan,

Thanks for walking through the SSO behavior today.

Here is what we confirmed:
- The 403 appears after the IdP redirect, not before login starts.
- The issue is intermittent and affects two customer admins.

Next steps:
- Northwind will reproduce the issue with Preserve log enabled and upload a sanitized HAR.
- Support will compare the failed request flow against the latest successful login trace.

I'll update the ticket after reviewing the capture.

Pre-Send Review

  • The subject is specific.
  • Customer name and account are correct.
  • Confirmed facts are actually confirmed.
  • Action items have owners.
  • Dates are accurate.
  • Internal-only context is removed.
  • Links point to the right ticket or doc.
  • The email sounds like a person, not a transcript dump.

FAQ

Should I attach the full Fathom notes?

Usually no. Send a concise recap and keep the full notes as internal source material unless the customer explicitly needs the full record.

Should I include action items from every attendee?

Only include action items that were agreed to and are useful for the customer to see.

Can AI write the follow-up email?

AI can draft it, but a person should review ownership, dates, customer-safe language, and commitments.

What if the meeting had no clear next step?

Say that. A short "we will review internally and follow up by Friday" is better than inventing a task.

CTA

Koda Sidecar's Fathom Action Items & Exporter helps review Fathom action items, draft customer follow-up, and export meeting records from Chrome.