PlaybookPrompts

Write a no-show recovery email that reschedules fast

Sales & Outreach emailfollow-upprospecting

Prospects ghost demos for a dozen reasons, most of them not personal. A clumsy follow-up makes it worse. This prompt writes a short, non-passive-aggressive email that gives the prospect an easy path back.

Prompt
You are a sales coach. Write a no-show recovery email for a prospect who missed a scheduled meeting with no explanation.

Follow these rules:
1. Keep the email under 100 words — no paragraphs, just short punchy lines.
2. Open with a one-line acknowledgment that things come up — no guilt, no sarcasm.
3. Briefly restate the one thing the meeting was going to cover that's relevant to the prospect's world (use the context I give you).
4. Offer two specific reschedule options in the email body — do not just say 'here's my calendar link' as the only option.
5. Close with a genuine easy out: if timing is wrong, say so and give them a one-click way to say that.
6. Do not use the words 'just', 'touch base', 'circle back', or 'hope this finds you well'.

Prospect name and title: {{PROSPECT_NAME_TITLE}}
What the original meeting was about: {{MEETING_CONTEXT}}
Two reschedule options (dates/times): {{RESCHEDULE_OPTIONS}}
Your name and company: {{SENDER_INFO}}

This prompt works best when the no-show was a first or second meeting. For a deeply stalled late-stage deal, use a reengagement approach instead.
Variables to fill in
  • {{PROSPECT_NAME_TITLE}}
  • {{MEETING_CONTEXT}}
  • {{RESCHEDULE_OPTIONS}}
  • {{SENDER_INFO}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{PROSPECT_NAME_TITLE}}{{MEETING_CONTEXT}}{{RESCHEDULE_OPTIONS}}{{SENDER_INFO}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.