Nudge CRM
An outgoing recap envelope points to a highlighted calendar cell holding an action slip and a person-shaped ownership marker.

Sales Call Follow-Up Email: What to Send and What to Do Next

7 min read

A sales call follow-up email should recap what matters, deliver anything you promised and make the next step clear. A practical default is to send it the same working day or the next, unless you agreed otherwise.

Then record who will follow up and when. Sending the recap completes one task, but it doesn’t settle what happens next.

Sales call follow-up email example

Here’s an example for an agency following up with a potential client. It proposes a next step because no meeting was agreed on the call. Replace the bracketed details and keep only statements that match your conversation.

Subject: [Business name] call recap and proposed next step

Hi [Name],

Thanks for talking through your client onboarding process today. You mentioned that gathering documents before kickoff is the main hold-up.

As promised, I’ve attached an outline of how we could help, including the responsibilities we discussed.

Would [Tuesday, date] at [time and time zone] work for a brief scope review?

Best, [Your name]

Only mention an attachment if you’ve included it. If you didn’t promise an outline, change that sentence rather than turning a template into a fictional account of the call.

The subject line gives the prospect enough context to place the message. Other options include:

  • “Recap of our [project name] conversation”
  • “[Business name]: scope review on [agreed date]”
  • “Notes and next step from today’s call”

Use the dated version only when that date was actually agreed.

What to include in your recap

Write from the prospect’s side of the conversation. What were they trying to solve? What did they need to understand before moving forward?

For the agency example, “gathering documents before kickoff is the main hold-up” is useful context. A list of every service the agency offers is not. The recap should help the prospect recognize their situation, not make them sit through the pitch again.

Include the relevant discussion points and any commitments you made. If pricing depends on information you haven’t received, say so. If the prospect needs a colleague’s input, acknowledge that rather than writing as though they can approve the work alone.

A useful editing test is to read only the request. Can the prospect tell what you want them to do? “Let me know your thoughts” leaves the response wide open. “Would Tuesday at 10 a.m. work for a scope review?” gives them a concrete question to answer.

Confirm a next step you agreed on

When the call ended with an agreement, restate it plainly. Separate your commitment from theirs:

I’ll send the revised scope by Wednesday. You’ll review it with your operations lead before our call on Friday at 10 a.m.

There’s no need to reopen a settled decision with another scheduling question. You can invite corrections if needed, but don’t make the prospect reconfirm every detail.

Be precise about what was agreed. “You’ll consider a pilot” is different from “You’ve approved the pilot.” Likewise, discussing a possible meeting does not mean it is booked.

Propose a next step when none was agreed

If the call ended without a clear next step, suggest one that fits the conversation:

You mentioned that your operations lead would need to review the approach. Would it be useful to include them in a scope review next week?

This explains why you’re proposing the review and gives the prospect room to accept, change or decline it. A suggested date is still a suggestion until they agree.

Avoid inventing urgency to get an answer. If there is a real deadline, name it and explain its relevance. Otherwise, make a reasonable request without presenting it as an obligation.

When to send your follow-up

Send the recap while the conversation is fresh, such as the same working day or the next working day when practical. That is a working habit, not a research-backed optimum.

Any promise made on the call takes priority. If you said you would send a proposal on Thursday, plan for Thursday. If the proposal needs more work, you can send a brief recap first and state when it will arrive.

Don’t confuse the recap’s send date with the next check-in date. You might send notes today but wait until after the prospect’s internal review before contacting them again.

Choose that later date from what you know:

  • Did the prospect say when they would review the material?
  • Are they waiting on someone else?
  • Is there a genuine project deadline?
  • Did you agree to leave the conversation until a particular date?

If no timing was discussed, choose a check-in date based on the work involved and any proposed meeting. Don’t let “I’ll give them some time” become an undated task.

What to send if there is no response

First, check whether a reply is actually overdue. A prospect who said they would review your proposal next week does not need a reminder tomorrow.

When a check-in is reasonable, refer to the earlier email and repeat or simplify the request. For the agency example:

Hi [Name],

Following up on the onboarding outline I sent on [date]. Would a scope review still be useful, or would you prefer to leave this until later?

Best, [Your name]

Keep the message tied to the work. You don’t need to apologize for a reasonable follow-up, but you also don’t need to make the prospect explain their silence.

If the proposed meeting date has passed, remove it. If you learned something relevant since the last message, include it briefly. Don’t resend a stale request just because it is already written.

There isn’t a universal follow-up sequence that fits every relationship. Choose the next check-in from the prospect’s stated timeline and your reason for contacting them. If they ask you to stop, stop. If they defer until a particular month, record that rather than continuing to send reminders in the meantime.

When there is no useful reason to keep contacting them, pause. If a closing note would help set expectations, keep it simple:

I’ll leave this with you and won’t keep checking in. If the project becomes a priority again, you’re welcome to pick up this thread.

Only say that if you intend to follow through on it.

Keep the next action owned and dated

“Waiting for the prospect” describes a situation. It does not assign responsibility inside your team.

Give the next action one internal owner. Usually, that’s the person managing the relationship, unless a teammate has explicitly accepted the handoff. That person is responsible for reviewing the situation, not for forcing a reply.

Here’s how that works in Nudge, an action-first CRM for small teams where every deal has an owner, a next action and a due date. In this hypothetical example, Alex sends Maya an outline on May 12 and proposes a scope review for May 19. Alex records the follow-through on the deal:

| Field | What to record | |---|---| | Deal | Alder Studio onboarding project | | Owner | Alex | | Latest update | Outline sent May 12; proposed review is not confirmed | | Next action | Check for Maya’s reply; if none, ask whether a scope review is still useful | | Due date | May 15, chosen to allow time to arrange the proposed review |

Those dates illustrate a decision, not a recommended interval for every deal. You can use the same fields in a simple task list if you don’t use a CRM.

The Today list shows what’s overdue, due today and due this week. On May 15, Alex’s check-in is due today, even if Maya hasn’t replied. The task is to review the conversation and decide what to do, not to assume the proposed meeting is confirmed.

If Maya has replied, Alex updates the next action and due date to reflect what they agreed. If she hasn’t, Alex decides whether to send the check-in or pause. If a teammate takes over, Alex records the new owner rather than assuming someone will pick it up.

To keep the correspondence alongside the contact, Alex can CC, BCC or forward the email to the workspace’s email dropbox address. That logs it on the matching contact; it does not send the email or sync with Gmail or Outlook.

After sending your own recap, record the next action: name the person, write what they will do and give it a due date. “Follow up” is vague. “Alex to check for Maya’s reply on May 15 and send the scope-review question if needed” is work someone can actually pick up.

See also Give the next action one internal owner.

See also email dropbox.

Turn the next idea into your next action.

  • Import contacts in seconds
  • See overdue work fast
  • Keep the whole team moving

14-day free trial. No credit card required.