Outbound

Follow up email template

Four to six touches that each add a new angle — with timing, exit criteria, and a breakup that closes cleanly.

  • AgentAlpha
  • JobCreation
  • CategoryOutbound
  • Integrations
    • Instantly / Smartlead
    • HubSpot / CRM
    • Outreach
    • Slack
  • Last updatedAugust 2026
  • AuthorNarayan Prasath
AlphaComplete
  • HubSpot / CRM
  • Slack

Build a 5-touch follow-up sequence for the content-hiring cold email. Include a LinkedIn step.

  1. Reused the original triggerContent hiring; avoided repeating the cycle-time claim
  2. Assigned an angle per touchProof point, second consequence, resource, LinkedIn touch, breakup
  3. Set cadenceDays 3, 7, 12, 16 (LinkedIn), 22 (breakup)
  4. Defined exit criteriaAny reply, bounce, or if the roles get filled

Five touches over 22 days, each with its own angle: a customer proof point, the review-bottleneck consequence, a useful brief template, a LinkedIn note, then a breakup. Sequence exits if the roles are filled, since the trigger would no longer be true.

The problem with most follow up email templates is that touch three has nothing to say. This one generates the whole arc at once, assigning each message a different angle — a new proof point, a different consequence, a lighter ask — so nobody has to write "just checking in" under pressure.

What is a follow up email template?

A planned sequence of messages after the first touch, where each one has a defined job: add evidence, reframe the problem, lower the ask, or close the loop. Timing and exit criteria are part of the template, not improvised afterwards.

Plan the whole arc up front

  • Assign each touch a distinct angle and job
  • Vary length and ask across the sequence
  • Reference the original trigger without repeating it
  • End with a breakup that makes silence easy

Set timing and exit rules

  • Space touches wider as the sequence progresses
  • Define exit criteria on reply, bounce, or stale trigger
  • Note where a channel switch beats another email

Keep it defensible

  • Use only claims your proof points support
  • Keep links minimal for deliverability
  • Flag touches that would read as pressure

How many follow-ups should a cold email sequence have?

Four to six touches over two to three weeks. Fewer leaves replies on the table, since many arrive after touch three; more starts producing complaints that cost you domain reputation.

How do you write a follow up email without "just checking in"?

Give the message a reason to exist. A relevant proof point, a second consequence of the same problem, a shorter question, or a genuinely useful resource. If a touch has no new angle, the right move is to end the sequence rather than pad it.

What timing works for an email cadence?

Roughly two to four days between the first touches, widening to five or seven later. Same-day and next-day follow-ups read as pressure, and gaps beyond ten days lose the thread of the original message.

When should someone exit the follow up sequence?

On any reply, on a clear no, on a bounce, or when the trigger you referenced stops being true. Sequences that continue after a soft no are the main source of the complaints that damage sender reputation.

How the follow up email template works across your stack

The agent reuses the research and trigger from the first touch, pulls additional proof points from workspace Knowledge for later messages, and reads reply data from your sequencer or CRM to learn which angles land. The full sequence exports to Instantly, Smartlead, HubSpot, or Outreach with timing attached.

  • Instantly / Smartlead
  • HubSpot / CRM
  • Outreach
  • Slack

Who uses this follow up email template

SDR teams
Ship complete sequences instead of writing touch four the morning it sends.
Founders selling directly
Follow up consistently without sounding like you are nagging.
Agencies
Keep sequence quality even when the person writing them changes.

How to run this follow up email template in Metaflow

  1. Point the agent at the first touch

    It reuses the original trigger and research so the sequence stays coherent.

  2. Set the sequence length and cadence

    Number of touches, spacing, and whether a call or LinkedIn step belongs in the middle.

  3. Review each touch and its angle

    Every message shows the job it does, so you can see whether any is filler.

  4. Push to your sequencer

    Export with timing and exit criteria, then let reply data inform the next iteration.

What you provide

  • The first-touch email and its trigger
  • Sequence length and cadence
  • Proof points available for later touches

What you get back

  • Four to six drafted touches with assigned angles
  • Send timing per touch
  • Exit criteria
  • Breakup email

Why use this follow up email template?

  • Every touch gets an assigned angle, so filler is visible and removable

  • Exit criteria are part of the sequence, protecting sender reputation

  • Later touches use different proof points rather than repeating the first

  • Ends with a breakup that closes the loop without guilt

Follow up email template FAQs

How do you politely write a follow-up email?

Reference the original point briefly, add something new, make the ask smaller than last time, and give an easy exit. Politeness comes from being short and making it easy to say no — not from apologizing for emailing.

What is a good template for a follow-up email?

Two or three sentences: a one-line reminder of the context, one new piece of value, and a question shorter than the one you asked before. Anything longer restates rather than advances.

What is the 3 email rule?

A common convention that you send three follow-ups before stopping. Treat it as a floor, not a ceiling — replies do arrive at touch four and five, and what matters more is whether each touch has something to say.

Should follow-ups be in the same thread?

The first two, yes, so the context travels. Later touches often perform better as fresh threads with a new subject, because a long unanswered thread signals its own history.

Key takeaways

  • Plan the whole arc so touch four has a reason to exist
  • Widen the spacing and shrink the ask as the sequence progresses
  • Exit rules protect your domain more than any copy tweak