Break-up email to revive a silent prospect
Use as a final follow-up when a prospect has gone dark, to trigger a reply through graceful closure.
You write tactful break-up (last-touch) sales emails.
Prospect: {{prospect_name}} at {{company}}.
Number of unanswered touches so far: {{touch_count}}.
What we discussed or what I offered: {{context}}.
Write a break-up email that:
- Assumes the timing is simply wrong, not that they are rude.
- Gives them an easy out (a one-word reply or "not now").
- Leaves the door open without sounding needy.
- Optionally includes one small parting value item: {{parting_value}}.
Tone: calm, professional, zero guilt-tripping. Under 80 words. Provide one subject line that implies closure.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{prospect_name}}
- {{company}}
- {{touch_count}}
- {{context}}
- {{parting_value}}
Related prompts
You are an experienced B2B sales rep who writes short, human cold emails that get replies. Write a first-touch cold email to {{prospect_name}}, who is {{prospect_role}} at {{prospe...
You are a sales copywriter. Create three distinct cold email variations for the same prospect so I can A/B test them. Prospect: {{prospect_role}} at {{prospect_company}} What I sel...
You write natural LinkedIn connection notes that do not feel like a pitch. Write a connection request note to {{prospect_name}}, {{prospect_role}} at {{prospect_company}}. Reason f...
You are a social-selling expert. Build a 4-message LinkedIn DM sequence for a prospect who just accepted my connection request. Prospect: {{prospect_role}} at {{prospect_company}}...
You write follow-up emails that add value rather than nag. Write a follow-up to {{prospect_name}} who did not reply to my first email. Original email was about: {{original_topic}}...
You are a sales cadence specialist. Design a 5-email follow-up sequence for a cold prospect. Prospect type: {{prospect_role}} at companies like {{target_company_profile}} What I se...
0 Comments
Loading discussion...