> ## Documentation Index
> Fetch the complete documentation index at: https://docs.salesfinity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Frameworks for before and after a call

> Five emails that work with your dials: The Heads-Up, The Double Tap, The Recap, The Right Person and The Not Now.

Most email advice treats email as the whole play. On a team that calls, the best emails are the
ones wrapped around a dial: one that makes the call expected, one that follows a missed call while
your name is still on their phone, and one that turns what was said into the next step.

Read [how placeholders work](/sequencer/email-frameworks#placeholders) before you paste one into a
step. Text in square brackets is for a person to write.

## The Heads-Up

**Use it when** you are about to call someone cold and want the call to feel expected.

**Step type:** **Email**, placed one day before a **Call** step.

**The shape**

1. Why them, in one line.
2. That you will call, and roughly when.
3. A way out, so it reads as a courtesy and not a threat.

```text theme={"system"}
Subject: calling you tomorrow

Hi {{first_name}},

I work with [their role] on [the problem], and {{company}} looked like a fit.

I'll try you by phone tomorrow. It will take two minutes to know if it's worth a longer talk.

If email is easier, just reply here.

[Your name]
```

**Why it works.** A cold call is easier to take when the name on the screen is one they have
seen. It also gives the rep an honest opener: "I sent you a note yesterday."

**Make it yours**

* Put a note on the call step that follows: "Reference the heads-up email."
* Don't promise a time you can't keep. "Tomorrow" is enough.

## The Double Tap

**Use it when** you called and didn't reach them. Send it within minutes, while the missed call or
voicemail is still fresh.

**Step type:** **Email (you send it)**, set to **Right after the previous step**, straight after a
**Call** step. It lands in your **Tasks** as soon as you log the call.

**The shape**

1. You just called.
2. The one reason, in a sentence.
3. A question they can answer without calling back.

```text theme={"system"}
Subject: just tried you

Hi {{first_name}},

I just called and missed you.

The short version: [the one reason you are reaching out, in a sentence].

Is that worth five minutes this week, or is it the wrong time?

[Your name]
```

**Why it works.** Two touches minutes apart read as a person trying to reach them, not a campaign.
The email does the job of a callback they were never going to make.

**Make it yours**

* If you got through, skip the task, or send [The Recap](#the-recap) instead.
* If you left a voicemail, start with "I just left you a voicemail" so the two line up.

## The Recap

**Use it when** you had a real conversation and want what was said in writing.

**Step type:** **Email (you send it)**, right after the call.

**The shape**

1. What you heard, in their words.
2. What you agreed.
3. The next step, with a date.

```text theme={"system"}
Subject: what we covered

Hi {{first_name}},

Thanks for the time just now. What I heard:

- [Their situation, in their words]
- [The thing they want to fix]

We agreed [the next step] on [date].

Did I get that right?

[Your name]
```

**Why it works.** People hold themselves to what they have seen in writing. "Did I get that
right?" invites a correction now, instead of a no-show later.

**Make it yours**

* Use their words, not yours. If they said "our reps are drowning", write that.
* If your team uses [Live Assist](/live-assist/overview), the recap on the Live Assist card lists
  what came up on the call. Write the email from it while it is still on screen.

## The Right Person

**Use it when** someone told you "that's not my area", or a contact has gone quiet and you suspect
you have the wrong person.

**Step type:** **Email (you send it)**.

**The shape**

1. Say plainly that you may have the wrong person.
2. What you are trying to solve, in one line.
3. Ask who owns it.

```text theme={"system"}
Subject: wrong person?

Hi {{first_name}},

I may be asking the wrong person.

I'm trying to reach whoever owns [the problem] at {{company}}.

Who would that be?

[Your name]
```

**Why it works.** It costs the reader nothing to answer, and it takes the pressure off them. A
name from inside the company also makes your next email the warmest one you will send.

**Make it yours**

* When they name someone, open your email to that person with the referral: "\[Name] on your
  team pointed me to you."
* If a call ended this way, you already have the name. Log the call, then enroll the new contact.

## The Not Now

**Use it when** a prospect said "not now" and gave you a time: next quarter, after the launch,
when the new VP starts.

**Step type:** **Email (you send it)**, on the date they named.

**The shape**

1. Remind them what they said, and when.
2. One thing that has changed since, if anything has.
3. Ask whether the timing still holds.

```text theme={"system"}
Subject: you said [month]

Hi {{first_name}},

When we spoke in [month], you said to come back after [the thing they were waiting for].

[One line on what has changed since, on your side or theirs.]

Is now a better time, or should I try again later?

[Your name]
```

**Why it works.** You did what they asked, on the date they asked for. That is rare enough to be
noticed.

**Make it yours**

* Write down their exact words at the time. A [call note](/calls/call-history) or the
  [Nurture AI](/calls/nurture-ai) follow-up date is where to look.
* If nothing has changed, cut the middle line. A short honest email beats a padded one.

## Next steps

<CardGroup cols={2}>
  <Card title="Follow-up and closing frameworks" icon="reply" href="/sequencer/frameworks-follow-ups">
    The Nudge, The New Angle, The Clean Exit, The No-Show Rescue and The Second Look.
  </Card>

  <Card title="Cold email playbooks" icon="list-check" href="/sequencer/email-playbooks">
    Full sequences that chain these frameworks with call steps.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.