Sales Follow‑Up Email
1. Overview
This process creates a personalized, context‑rich email that nudges a prospect toward the next step in the sales conversation. It uses details from the most recent interaction with the prospect and the Account Executive’s (AE) product knowledge to craft a professional and friendly email ready to be sent.
2. Business Value
A well‑crafted follow‑up increases response rates, shortens sales cycles, and builds confidence with the prospect. By standardising the draft‑creation process, AEs can spend more time on conversations and less time on writing, while maintaining a high‑quality, consistent voice.
3. Operational Context
-
When to use it:
- After an introductory call, demo, or proposal has been delivered and a response is needed.
- When a prospect has not replied for 3‑7 days and a gentle reminder is required.
- When the AE wants to send a tailored follow‑up after a meeting, webinar, or event.
-
Who uses it: Account Executives (or Sales Development Representatives) who are responsible for moving prospects through the pipeline.
-
Frequency: One run per prospect per follow‑up email. If multiple follow‑ups are needed, run the process again with updated interaction details.
4. Inputs
For each email, the following information must be provided. All items pertain to the single prospect being contacted.
| Name / Label | Type | Details Provided |
|---|
| Prospect Name | Text | Full name (e.g., “Jane Doe”). |
| Prospect Company | Text | Company name (e.g., “Acme Corporation”). |
| Prospect Title | Text | Role or title (e.g., “Vice President of Marketing”). |
| Recent Interaction Summary | Text | Brief (1‑2 sentences) describing the most recent contact (e.g., “30‑minute discovery call on Mar 15 where they discussed challenges with lead‑nurturing”). |
| Key Pain Points | Text | One to three specific challenges the prospect shared (e.g., “low lead‑scoring accuracy, low conversion rates”). |
| Desired Next Action | Text | What the AE wants the prospect to do (e.g., “schedule a 30‑minute product demo”). |
| Product/Service Summary | Text | Short description of the product or service being offered (e.g., “automated lead‑scoring platform that integrates with Salesforce”). |
| AE Name | Text | Full name of the Account Executive (e.g., “John Smith”). |
| AE Email Signature | Text | Full signature block (e.g., name, title, company, phone, email, and optional disclaimer). |
| Additional Context (Optional) | Text | Any recent news, events, or personal details about the prospect or their company that could be referenced (e.g., “Acme launched a new product line last week”). |
| Previous Email Content (Optional) | Text | The content or a short summary of the most recent email sent to the prospect (if the follow‑up references it). |
| Email Subject Preference (Optional) | Text | Desired subject line or any keywords the AE wishes to include. |
| Desired Tone | Text | Desired voice: “friendly”, “formal”, “professional”, or “neutral”. |
5. Outputs
The process yields a ready‑to‑send email (subject line + body) in plain text, respecting the requested tone and formatting conventions.
| Name / Label | Contents | Formatting Rules |
|---|
| Draft Follow‑Up Email | Subject line followed by a blank line, then the email body. The body contains: greeting, reference to the recent interaction, brief reminder of the prospect’s pain points, a concise value proposition, a clear call‑to‑action, a friendly closing, and the AE’s signature. | • Plain‑text format (no markdown or HTML). |
| • Use title‑case for the subject line. | | |
| • Body paragraphs no longer than 2 sentences each. | | |
| • Use the prospect’s first name in the greeting. | | |
| • Include the AE’s signature exactly as provided. | | |
| • Maintain the requested tone (e.g., “friendly” = conversational, “formal” = business‑like). | | |
6. Detailed Plan & Execution Steps
-
Gather Input Data
- Collect each item listed in the “Inputs” table from the AE or CRM system.
- Verify that Prospect Name, Key Pain Points, Desired Next Action, and AE Email Signature are present; if any are missing, move to the “Special Rules / Edge Cases” section.
-
Set the Email Tone
- Review the “Desired Tone”. If none is specified, default to “professional and courteous”.
-
Craft the Subject Line
- Use the Email Subject Preference if provided; otherwise, combine a reference to the prospect’s company or a benefit statement (e.g., “Next steps to boost Acme’s lead conversion”).
-
Write the Greeting
- Begin with “Hi [Prospect First Name],”.
-
Reference the Recent Interaction
- Include one sentence that mentions the date and nature of the last meeting or call.
-
Re‑State the Prospect’s Pain Points
- Summarise the key pain points in a concise sentence.
-
Present the Value Proposition
- Connect the product/service to the pain points in one sentence, emphasizing a benefit or result.
-
Add the Call‑to‑Action
- Clearly state the Desired Next Action (e.g., “Could we schedule a 30‑minute demo next week?”).
-
Close with a Friendly Closing
- Use “Best regards,” or “Thanks,” followed by the AE Email Signature.
-
Apply Formatting Rules
- Ensure plain‑text formatting, proper line breaks, and correct capitalization.
-
Perform Validation Checks (see Section 7).
-
Finalize
- Output the Draft Follow‑Up Email (subject line + body) in the format described in the “Outputs” table.
7. Validation & Quality Checks
-
Presence Checks
- Confirm the greeting includes the prospect’s first name.
- Ensure the email references the recent interaction (date or event).
- Verify at least one of the identified key pain points is mentioned.
- Confirm a clear call‑to‑action is present.
- Verify the AE’s signature appears exactly as provided.
-
Tone & Length
- Total email body ≤ 5 paragraphs (≈ 150‑200 words).
- Sentence length ≤ 20 words per sentence.
-
Grammar & Spelling
- Run a spell‑check and grammar check.
-
Tone Consistency
- Ensure the language matches the specified tone (e.g., no overly informal language if “formal” is chosen).
-
Formatting
- Subject line in title case, no trailing spaces.
- Blank line between the subject line and body.
If any check fails, return to the step where the deficiency originated and correct it before proceeding.
8. Special Rules / Edge Cases
| Situation | Action |
|---|
| Missing Prospect Name | Do not proceed. Flag the record for manual review; “Hi” cannot be personalized. |
| Key Pain Points Missing | Use a generic benefit statement (e.g., “I understand many teams face challenges in …”) and mark the email for a quick review. |
| No Desired Next Action Provided | Prompt the AE to specify a clear next step before drafting. |
| No AE Signature Provided | Insert a standard placeholder signature (“[Your Name], [Title], [Company]”) and flag for later replacement. |
| Length Exceeds Limits | Trim non‑essential sentences, focusing on the three core components: reference, value, CTA. |
| Tone Mismatch | Adjust wording to align with the desired tone; if unsure, default to “professional and courteous”. |
| Multiple Prospects in One Input | Split into separate runs; the SOP is single‑instance only. |
| Conflict Between Desired Next Action and Company Policy | Flag for manual review; do not generate output. |
9. Example
Input (for a single prospect)
- Prospect Name: Jane Doe
- Prospect Company: Acme Corporation
- Prospect Title: Vice President of Marketing
- Recent Interaction Summary: “30‑minute discovery call on March 15 where Jane shared that her team is struggling with low lead‑scoring accuracy and a 20 % drop in conversion rates.”
- Key Pain Points: “Low lead‑scoring accuracy; declining conversion rates.”
- Desired Next Action: “Schedule a 30‑minute product demo next week.”
- Product/Service Summary: “Our AI‑driven lead‑scoring platform integrates with Salesforce to automatically prioritize high‑value leads, increasing conversion rates by up to 30 %.”
- AE Name: John Smith
- AE Email Signature:
John Smith
Account Executive | XYZ Solutions
(555) 123‑4567 | john.smith@xyz.com
- Additional Context: “Acme launched a new product line last week.”
- Desired Tone: Friendly
Output (Draft Follow‑Up Email)
Subject: Next steps to boost Acme’s lead conversion
Hi Jane,
I enjoyed our conversation on March 15 about the challenges your team at Acme is facing with lead‑scoring accuracy and the recent dip in conversion rates. Our AI‑driven lead‑scoring platform integrates seamlessly with Salesforce and has helped customers lift their conversion rates by up to 30 % while automatically prioritising the most promising leads.
Would you be open to a 30‑minute demo next week to see how it can address the scoring issues you described and help reverse the recent dip in conversions?
Thanks,
John Smith
Account Executive | XYZ Solutions
(555) 123‑4567 | john.smith@xyz.com
Appendix A – FAQ
Q1: I don’t know the prospect’s first name. What should I do?
A: If the full name is “Jane Doe”, use “Jane”. If only a company name is known, use a generic greeting such as “Hi there” and flag the email for manual review.
Q2: What if the prospect has a preferred title?
A: Use the title as provided (e.g., “VP of Marketing”). If the title is missing, omit it from the greeting.
Q3: How far should I personalize the email?
A: Include the prospect’s name, company, and any specific pain points discussed. Avoid unrelated personal details.
Q4: The prospect is in a different time zone. Does that affect the email?
A: Not in the draft itself, but the AE should schedule the call appropriately; this SOP only handles email content.
Q5: Should I attach any files?
A: This SOP only generates the email body. Attachments (e.g., a brochure) are added later by the AE.
Q6: My company requires a disclaimer in every email. Where do I put it?
A: Add the disclaimer after the signature as a separate line if required by policy.
Q7: What if the prospect has responded with a question already?
A: This SOP is for “nudge” emails. If the prospect asks a question, the AE should answer directly rather than using a generic follow‑up.
Q8: Can I use emojis?
A: Only if the “Desired Tone” is “friendly”. For “formal” or “professional” tones, avoid emojis.
Q9: What if the AE wants to include a link to a calendar?
A: The AE may insert a calendar link in the CTA sentence (e.g., “Please pick a time that works for you via my calendar link”). This SOP does not generate the link.
Q10: How do I handle a prospect who is unresponsive after three follow‑ups?
A: This SOP is only for a single follow‑up. After multiple attempts, follow the company’s “lead‑re‑engagement” policy (outside the scope of this SOP).
Appendix B – Glossary
| Term | Definition |
|---|
| Prospect | A potential customer who has shown interest in your product or service. |
| Follow‑Up Email | An email sent after a prior interaction to keep the conversation alive and move the prospect toward a next step. |
| Key Pain Point | A specific problem or challenge the prospect has shared. |
| Call‑to‑Action (CTA) | The clear, single next step you request from the prospect (e.g., schedule a demo). |
| AE | Account Executive – the salesperson responsible for the prospect. |
| Tone | The overall voice of the email: friendly, formal, professional, etc. |
| Subject Line | The brief title that appears in the recipient’s inbox. |
| Plain‑Text | Text without any HTML tags, markdown, or special formatting; just regular characters. |
| Signature | The block of contact information the AE includes at the end of the email. |
| CRM | Customer Relationship Management system (the source of most inputs). |
| Nudge | A gentle reminder or encouragement to respond. |
Appendix C – Style & Reference Guides
C1. Subject‑Line Guidelines
- Length: 6‑8 words, ≤ 50 characters.
- Structure: [Action] + [Benefit] + [Company or Product] (e.g., “Boost Acme’s Lead Conversion”).
- Tone: Reflect the desired tone: friendly = “Quick question about your new product line”; formal = “Follow‑up on our recent discussion”.
- Avoid: ALL CAPS, exclamation points, “Urgent”, “Free”, or any language that could be flagged as spam.
C2. Email Body Guidelines
- Greeting: Use the prospect’s first name. If unavailable, “Hi there”.
- Paragraph Count: 4–5 paragraphs, each 1–2 sentences.
- Sentence Length: ≤ 20 words.
- Structure:
- Greeting.
- Reference recent interaction (date and context).
- Summarize 1‑2 key pain points.
- Present a concise value proposition.
- Clear CTA (include “next week” or a specific timeframe if possible).
- Closing (e.g., “Thanks,” or “Best regards,”).
- Tone Consistency:
- Friendly: Conversational, uses “we”, “you”, light adjectives.
- Professional: Formal language, no slang, use “I” or “we” but with a polite tone.
- Formal: Very structured, may use “Dear [Title] [Last Name]”.
- Personalisation: Include the prospect’s company and product name where appropriate.
- Avoid Jargon: Unless the prospect explicitly uses technical terms.
C3. Signature Guidelines
- Required Elements:
- Full name.
- Title.
- Company name.
- Phone number (with area code).
- Email address.
- Optional Elements:
- Company logo (handled separately, not part of the plain‑text SOP).
- Legal disclaimer (if required by policy).
- Formatting: Each element on its own line, as shown in the “Outputs” table.
C4. Quality Assurance Checklist (for reviewers)
C5. Sample Email Templates (for reference)
Template 1 – Friendly Nudge
Subject: Quick question about your new product line
Hi [First Name],
I enjoyed our chat on [Date] about the challenges you're seeing with lead‑scoring accuracy at [Company]. Our AI‑driven platform helps teams automatically prioritize high‑value leads, which can improve conversion rates by up to 30 %.
Would you have 30 minutes next week to see it in action?
Thanks,
[AE Name]
[Title] | [Company]
[Phone] | [Email]
Template 2 – Formal Follow‑Up
Subject: Follow‑up on our March 12 discussion
Dear [Title] [Last Name],
Thank you for meeting on March 12 to discuss the challenges Acme is facing with lead‑generation. Our solution’s automated scoring can reduce manual effort and increase conversion rates, aligning with your goal to improve pipeline quality.
Could we schedule a 30‑minute call next week to walk through a demo?
Sincerely,
[AE Name]
[Title] | [Company]
[Phone] | [Email]
These templates illustrate how to adapt the core structure to different tones while maintaining the required elements.
Additional Notes
- Version Control: Keep a record of each version of the SOP and the date it was last updated.
- Training: New AEs should practice drafting a few sample emails using the template before applying it to real prospects.
- Continuous Improvement: Review email responses weekly; adjust wording or structure based on what generates the best response rates.
- Document Storage: Store this SOP in the shared Sales Operations folder for easy access and reference.
