Defuse angry and unsubscribe replies with an exit that protects your domain
Produces the two-sentence exit that keeps an angry prospect from escalating to a spam complaint — the deliverability event that actually damages your sending domain. Past-tense removal confirmation, zero defensiveness, zero selling. Includes the full suppression checklist and CRM note so the contact never resurfaces in anyone's sequence, plus a legal-language flag when replies mention GDPR or CCPA.
You are a deliverability-minded outbound operator. You treat angry replies and unsubscribe demands as domain-reputation events first and lost deals second — because one spam complaint hurts more than a hundred ignored emails, and the reply you send determines whether the prospect hits 'report spam' after hitting send. The goal is a graceful exit: fast, human, zero friction, zero selling. Draft ONE reply to an angry or unsubscribe response. Rules: - 2 sentences maximum, under 40 words. - Sentence 1: confirm the removal as already done, past tense — 'You're removed' beats 'I'll remove you'. - Sentence 2 (optional, only if their tone allows): one human, non-salesy sign-off. A genuinely angry reply gets sentence 1 only. - Absolutely banned: apologizing at length, explaining your intentions, defending cold email, asking why they're upset, any link, any signature block with booking links, and any attempt to salvage the deal. - Match their formality: terse if terse. Also give me: (a) the suppression checklist — every place this contact must be removed (sequencer, CRM, teammate lists, future data imports), and (b) a one-line note format for the CRM so nobody ever emails them again. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. Paste their exact reply, including anything hostile — I need the real temperature. 2. What sending tool do you use (Smartlead, Instantly, something else), and is this contact in more than one sequence or list? 3. Has this domain had complaint or bounce issues recently? Once you have my answers, write the reply, the suppression checklist, and the CRM note. If their message threatens legal action or mentions GDPR/CCPA specifically, flag it and adjust the reply to acknowledge the request formally.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Paste their reply verbatim — tone-matching only works with their real words.
- 3
Execute the suppression checklist immediately, before sending the reply, so 'you're removed' is true when they read it.
- 4
Log the CRM note and add the domain to your do-not-contact list if the anger came from the company, not just the person.
Best practices
Speed is the deliverability play: an angry prospect who gets a removal confirmation within the hour rarely bothers with the spam button.
Resist every instinct to explain yourself — each additional sentence in your reply raises the odds of a second angry email.
Audit your suppression flow quarterly: most 'we removed you' failures happen because the contact lived in a second sequence or a teammate's CSV.
In Smartlead or Instantly, add the contact to the global block list, not just the campaign — campaign-level removal doesn't survive the next import.
Example: what this looks like in practice
An SDR team lead at an outbound-heavy SaaS company gets 'REMOVE ME FROM THIS LIST. This is the third email. Absolutely shameless.' She pastes it, notes the contact is in two Smartlead campaigns and a teammate's nurture list. The model returns a one-sentence reply — 'You're removed from everything, effective now.' — plus a checklist: Smartlead global block list, both campaigns, the teammate's list, CRM do-not-contact flag, and the suppression file used for future Clay imports. It also flags that 'third email' means their sequence-exit logic failed and suggests checking why replies aren't auto-pausing sequences. No spam complaint follows, and the team fixes the real bug.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Two sentences maximum: confirm their removal in the past tense, and — only if their tone allows — one human sign-off. No apologizing at length, no explaining, no defending cold email, no links. The objective isn't saving the deal; it's preventing the spam complaint that damages your domain. Remove them everywhere first, reply fast, and move on.
More reply & objection handling prompts
Convert a positive reply into a booked meeting before it cools off
Closes the gap where outbound pipelines leak most — between 'interested' and 'booked'. The reply answers their question in one line, offers two concrete times plus a link, and names the meeting payoff, all under 70 words. The pre-written 48-hour bump catches the prospects who meant yes but got busy, which is most of them.
Handle 'we already have a vendor' without trashing the competitor
Turns the most common outbound objection into a wedge conversation. Instead of attacking the incumbent or retreating, the reply legitimizes the prospect's choice and probes one specific gap as a question — the only competitive angle that doesn't insult their judgment. The interview forces you to name a provable differentiator, and the model pushes back if it's generic.
Answer 'can you guarantee results?' without overpromising or dodging
Answers the guarantee question the way buyers actually mean it — proof, downside protection, and shared risk — without the overpromise that becomes churn or the dodge that reads as no confidence. If your interview answers reveal you have no real risk-reversal structure, the model says so and proposes guarantee structures instead of writing copy that papers over the gap.