MSP Discovery Call Follow-Up Email Templates

The discovery call went well.

The prospect’s current provider takes days to answer tickets. Their backups have never been tested. The owner is frustrated and said so twice. You ended the call with the line every AE says: “I’ll send over a recap and next steps.”

Then the afternoon happened. A renewal call ran long. A client escalation needed you. The recap slid to tomorrow, and then to Thursday.

By the time it goes out, it’s generic. “Great speaking with you! Let me know if you have any questions.” The owner who was fired up on Monday has moved on to something else.

The follow-up is where good discovery calls go to die. Here’s how to write one that keeps the deal moving, plus five templates you can copy. If you want the short version of how Go Fig drafts these for you, it’s on our page for IT MSPs.

When should you send the follow-up?

The same day. Ideally within a few hours of the call.

Their words are fresh, and so are yours. The details that make a follow-up feel personal, like the exact way they described the problem, fade fast. A same-day recap also tells the prospect something about how you’d run their account.

What should a discovery call follow-up include?

Five parts, in this order:

1. Their problem, in their words. Not your pitch. If they said “our backups have never been tested,” write that.
2. What you learned about their environment. The number of users, the locations, the key applications, and who supports them today. It shows you listened, and it’s what your engineers will ask for anyway.
3. What you promised. The assessment, the proposal, or the answer to the question you couldn’t answer on the call.
4. One next step with a date. One. Not three options.
5. Your name. That’s it.

What to leave out: the capability deck, a stack of attachments, three different calls to action, and “just checking in.” Every extra thing is one more reason not to reply today.

Keep it short enough to read on a phone. If it scrolls, cut it.

Five follow-up email templates for MSP sales

Copy these, then make them yours. Anything in brackets is a placeholder.

1. The same-day recap

Subject: Recap from today and next step

Hi [First name],

Thanks for the time today. Here’s what I heard:

• [Problem one, in their words]
• [Problem two, in their words]
• [What a good outcome looks like for them]

Where you are today: [number] users across [number] locations, running [key applications], supported by [current provider or in-house IT].

What I promised: [the thing] by [day].

Next step: [the step] on [date]. Does [time] work for you?

[Your name]

2. The assessment invite

If your process runs through a network or security assessment before a proposal, use this one when that’s the next step.

Subject: Assessment for [Company] on [date]

Hi [First name],

As promised, here’s how the assessment works.

We’ll spend [length of time] looking at [what you review]. You’ll get a written summary of what we found, ranked by risk, and we’ll walk through it together.

To get started, I need [access or contact] and [one detail]. I’ve held [date and time] for the walkthrough.

Does that work?

[Your name]

3. Sending the proposal

Subject: Proposal for [Company]

Hi [First name],

The proposal is attached. The short version:

• What’s included: [scope in one line]
• What it fixes: [their problem, in their words]
• When it starts: [start date]

I’d like to walk through it with you rather than leave you to read it alone. Do you have time on [date]?

[Your name]

4. The deal that went quiet

Never send “just checking in.” Send something new.

Subject: [Their problem] at [Company]

Hi [First name],

When we spoke, you mentioned [their problem]. [One new, useful thing, like the answer to an open question or a short idea for their situation.]

Is this still a priority this quarter, or should I check back in [month]?

[Your name]

Giving them an easy way to say “not now” is honest. And a clear “not now” beats silence, because it tells you when to come back.

5. After a QBR

This one is for existing clients. A QBR is where projects start, so treat its follow-up like a sales follow-up.

Subject: QBR follow-up and next steps

Hi [First name],

Thanks for the time today. Here’s what we agreed:

• [Recommendation one and who owns it]
• [Recommendation two and who owns it]

You also mentioned [the new office, the aging hardware, or the compliance deadline]. I’ll send a short proposal for that by [date].

Our next QBR is on [date].

[Your name]

What subject line should a follow-up email use?

A plain one that names them. Their company, their problem, or the next step.

“Recap from today and next step” tells the prospect exactly what’s inside. “Assessment for [Company] on [date]” puts the commitment in the inbox before they open anything. Both are easy to find again when the owner forwards it to their office manager.

Skip the clever ones. “Quick question,” “Touching base,” and “Following up” all say the same thing, which is that there’s nothing new inside. If you can’t write a specific subject line, the email probably doesn’t have a specific point yet.

One more rule: once the prospect replies, answer on that same thread so the whole history sits in one place for both of you. Start a new thread only when the email starts something new, like the proposal.

Can software draft follow-up emails automatically after an MSP sales call?

Yes. The good ones don’t just fill in a template. Here’s what to look for:

• It reads the call. A transcript or the meeting notes, not just a few CRM fields.
• It reads the deal. The history on the record and the thread with the prospect, so the draft knows what happened before.
• It writes in your voice. A recap that sounds like a robot undoes the point of sending one.
• It sends from your mailbox. The prospect should hear from you, not from a shared address.
• It waits for your approval. A follow-up to a prospect is the last thing you want going out unread.
• It logs to the CRM. The email and the next step belong on the deal.

Go Fig is built around that list. After a discovery call or a QBR, it drafts the follow-up from what was said and what was promised. It’s written in your voice with the deal history in it. The draft waits in your Feed, and you can approve it, edit it, or skip it from the Feed, Slack, or email. Approved replies go out from your own Gmail or Outlook.

It reads the deal history from HubSpot or Salesforce, and it reads call transcripts from Fathom or Dialpad. Calls, emails, and stage changes are logged to the CRM for you, with the same approval.

It also catches the follow-up nobody sent. When a deal goes quiet, Go Fig spots it and drafts the check-in before it slips. When a prospect asks for time, it can draft the calendar invite and wait for your OK before it goes out. The hub has the short version under follow-up emails.

One timing note. Drafts that start from a call transcript show up after Go Fig’s next sync with your recorder. That’s once a day by default, at a time your team sets, and every hour or every 15 minutes on larger plans.

Approve every follow-up at first

My rule for anything a client reads is simple: draft, never send, until the tool has earned more.

Every team starts with everything waiting for its OK. Logging a note can graduate to running on its own early. Client emails should be the last thing you let go, and you can always take that back.

The point isn’t to stop writing follow-ups. It’s to stop starting them from a blank page at 6 PM, three days after the call.

Get the follow-up out the same day

A solutions engineer can connect your CRM and inbox and show you follow-ups drafted from your own calls.

Schedule a demo →

Or start with a gut check on your sales system: Take the Agent Readiness Assessment →