TL;DR: Here are 30 AI prompts covering the entire outbound motion, not just the first email: trigger research, first touch, four follow-ups, a breakup, a LinkedIn touch, a referral ask, re-engaging a closed-lost deal, and replies to interested, not-now, wrong-person, and hostile responses. Each stage gets its own prompt because each one needs a different reason to exist.
What are the best AI prompts for outbound email in 2026?
The best AI prompts for outbound email are staged to match the sales motion itself, not just the first message. A prompt for researching a trigger produces different output than a prompt for a fourth follow-up or a reply to a hostile response, and using one generic "write a cold email" prompt for all of them is why most sequences read like the same email sent five times. This set has 30 prompts split across eight stages, from the first signal you find to the reply you write back.
If you want the actual tool that turns a signal into a personalized first email in one click, our free cold email prompt generator does exactly that. This post is the prompt pack for everything around it: the research before the first email, the four follow-ups after it, and the replies once someone actually writes back.
Most "cold email prompt" lists stop at email one, because email one is the easiest part to write and the easiest part to sell a template for. The harder, more valuable half of an outbound motion is everything that happens after silence: what the second email says that the first one didn't, when to stop, and what to actually type back when a reply finally lands. That is the half this post covers.
| Stage | Prompts | Run it |
|---|---|---|
| Trigger research | 1–4 | Before you build the list |
| First touch | 5–9 | Once per prospect, per channel |
| Follow-ups 2–5 | 10–13 | Spaced out, roughly D3 through D20 |
| Breakup | 14–15 | After 4–5 silent touches |
| LinkedIn touch | 16–18 | Parallel to the email sequence |
| Referral ask | 19–20 | Mid-sequence or after a stall |
| Re-engaging closed-lost | 21–22 | When a real trigger reappears |
| Reply handling | 23–30 | The moment any reply lands |
Why do most follow-up sequences get weaker instead of stronger?
Most follow-up sequences get weaker because each email repeats the first one's ask, just phrased more apologetically. "Just following up," "wanted to bump this to the top of your inbox," and "checking in one more time" all say the same thing: I have nothing new to tell you, please answer anyway. A prospect who didn't reply to the original ask has no new reason to reply to the identical ask restated at a higher volume.
The fix is structural, not stylistic. Every touch after the first needs its own reason to exist: a new proof point, a new resource, a new angle on the same problem, or a more direct question. The table below shows the difference on the same four-follow-up sequence.
| Touch | Repeats email one (fails) | New reason to exist (works) |
|---|---|---|
| Follow-up 2 | "Just following up on my note below" | Opens with a specific result from a comparable customer |
| Follow-up 3 | "Wanted to bump this back to the top of your inbox" | Shares a relevant resource, no ask attached |
| Follow-up 4 | "Circling back one more time" | Ties a specific outcome to their stated priority |
| Follow-up 5 | "Last call before I close this out" | Asks one direct, decision-forcing question |
A prospect scans a subject line and the first few words of a preview pane in about a second. That is long enough to recognize "just following up" as the same email as last week, and short enough that it gets archived without ever being opened. A new proof point, a resource, or a direct question in that same preview space earns a second look precisely because it does not pattern-match to the thing they already ignored.
What AI prompts turn a buying signal into a personalized first touch?
A trigger is a specific, verifiable fact about one account, not a demographic guess. These four prompts turn a raw signal, funding, a job posting, a leadership change, or a tool switch, into the one sentence that makes touch one impossible to mistake for a mail-merge.
1. Funding round trigger
Company: [company name]. Signal: raised [round type, e.g. Series B] of [$X]
on [date]. Source: [link to the funding announcement or press release].
Write 3 one-sentence trigger lines connecting this raise to a problem
companies at this stage typically hit: headcount growth, new tooling,
scaling process. Each line must reference the raise specifically, not
generically ("congrats on the round"). No exclamation points.
The trigger line becomes the opening sentence of the first email, not a separate paragraph tacked onto a generic template. See prompt 5.
2. Job posting or hiring signal
Company: [company name]. Job posting found: [role title], posted [date],
listing includes: [paste 2-3 key requirements or responsibilities verbatim].
My product or service solves: [one sentence].
Write 3 trigger lines connecting this specific hire to the problem I solve.
Reference the role title and one requirement directly. Do not infer anything
the posting doesn't actually say.
Naming the actual requirement, not just the job title, is what separates a trigger line from a generic "I see you're hiring" opener. The requirement is evidence you read the posting; the title alone is something a scraper could have pulled.
3. Leadership change signal
Company: [company name]. New hire: [name], [new title], started [month/year].
Their previous company: [name, if known].
Write 2 trigger lines a rep could use to open a message to this new leader,
referencing the timing of the move without implying I already know their
priorities. Frame each as a question, not an assumption.
4. Tech-stack or tool-adoption signal
Company: [company name]. Tool or technology detected: [tool name, from a
job posting, a technographic source, or a case study].
How this tool relates to what I offer: [one sentence: complement, gap, or
overlap].
Write 2 trigger lines referencing the specific tool without sounding like
a generic "I see you use X" opener. Each should imply a real consequence of
using that tool, not a vague benefit.
The instruction to imply a consequence rather than state a benefit is deliberate. "You use [tool], and we integrate with it" is a feature statement about your product. "Teams on [tool] usually hit [specific limitation] around this stage" is a statement about their situation, which is the one worth opening an email with.
What makes a first outbound email worth replying to?
A first email has one job: earn a reply, not close a deal. These five prompts cover the two most reliable first-touch email structures, the cold call, an async video, and the warm-intro variant, so the channel matches the strength of the signal you actually have.
5. Observation-led cold email
Prospect: [name, title, company]. Trigger or observation: [paste from
prompts 1-4, or a specific fact you found].
What I do: [one sentence]. Specific value to this prospect: [one
sentence, not a generic feature list].
Write an 80-word cold email. Open with the observation, not an
introduction. No mention of my company name or product until sentence two.
Single ask: one specific, low-friction question, not "let's hop on a call."
6. Pain-led cold email (no usable observation)
Prospect: [title, industry]. No specific trigger available: this is a cold
list send.
The most common pain this role has with [problem area]: [describe, based
on real customer conversations, not a guess].
Write a 70-word cold email that opens with the pain stated as a question,
not a claim about their company. Do not phrase it in a way that implies
personal research I haven't actually done.
Most outbound volume runs through this prompt, not the observation-led one, because a real trigger for every account on a 500-name list rarely exists. Honesty about that in the prompt itself, no fabricated observation, is what keeps a high-volume list from reading like a bad mail merge.
7. Warm-intro or mutual-connection email
Prospect: [name, title, company]. Mutual connection: [name, how we know
each other and them].
Context: [what the mutual connection said, if anything, or how I found
this connection].
Write a 60-word email naming the mutual connection in sentence one,
stating what I do in one sentence, and asking a single specific question.
Do not claim the connection "suggested I reach out" unless that is true.
8. Cold call opening script
Prospect: [title, company]. Trigger or reason for the call: [specific
signal or context].
Write a 20-second cold call opener, roughly 45 words spoken. Structure:
state name and company in one breath, name the specific reason for
calling, ask a permission-based question ("Is now a bad time, or do you
have 90 seconds?"). No scripted enthusiasm. No "how are you today."
9. Async video prospecting script
Prospect: [name, title, company]. Screen or product moment to show:
[describe what's on screen].
Trigger: [specific reason this prospect, now].
Write a 45-second video script, roughly 110 words. Structure: name them
in the first 3 seconds, state the specific reason for the video, describe
one thing on screen in a single sentence, single next-step ask.
Tone: conversational, like a voicemail for a colleague.
A video only earns its extra production time when the signal is strong enough to justify it, an observation or a job posting, not a cold pain-led send. Reserve prompts 7 through 9 for accounts worth the additional five minutes.
For subject line variants to test against these opens, our conversion copywriting prompt set has a dedicated cold-outreach subject line batch.
What should follow-ups 2 through 5 actually say?
Each follow-up needs the new reason named in the table above, not a repeat of the first ask in different words. These four prompts operationalize that: a proof point for the second touch, a resource with no ask for the third, an outcome tied to their stated priority for the fourth, and a direct, decision-forcing question for the fifth.
10. Follow-up 2, new proof point (roughly D3-4)
Original email sent: [D0, paste subject or first line for context]. No
reply yet.
New angle for this touch: a specific result from a comparable customer,
[name or describe the customer type], outcome: [specific number or
result, verified].
Write a 50-word follow-up. Do not use "following up" or "checking in."
Open directly with the proof point. One CTA, phrased differently than
the first email.
11. Follow-up 3, resource share, no ask (roughly D7-8)
Prospect: [title, industry]. Relevant resource: [an article, benchmark,
or short guide you can genuinely point them to, not a repackaged pitch].
Write a 45-word email sharing the resource with one sentence on why it's
relevant to their specific situation. No CTA beyond an implicit open door.
Do not ask for a meeting in this email.
A no-ask email breaks the pattern a prospect expects from a sales sequence, which is exactly why it works. Every prior touch asked for something; this one gives something, and that alone is often enough to earn a reply on the next one.
12. Follow-up 4, outcome tied to their priority (roughly D12-14)
Prospect's stated or inferred priority: [from trigger research or a
previous reply, e.g. reducing time-to-hire, cutting review cycles].
Comparable customer outcome: [specific result tied to that same priority].
Write a 60-word email connecting that outcome directly to their priority.
Name the mechanism in one sentence, not just the result. One CTA.
13. Follow-up 5, direct decision-forcing question (roughly D18-20)
Context: 4 prior touches, no reply. What changes for them if they say yes:
[one sentence].
Write a 40-word email asking one direct, closed-ended question that makes
it easy to say not now honestly, for example: "Is this worth 15 minutes,
or should I check back next quarter?" No guilt. No "final attempt."
A closed-ended question is a kindness at this stage, not a pressure tactic. It gives someone who has been meaning to reply for three weeks a one-word way to finally close the loop, instead of another open-ended paragraph they have to find time to answer properly.
How do you write a breakup email that doesn't burn the relationship?
A breakup email is a genuine exit, not a manufactured threat. It either gets a real answer or closes the loop while leaving the door open for a future trigger. These two prompts cover the straight version and the single-question variant.
14. Breakup email, graceful close
Context: [N] touches sent over [X weeks], no reply.
Write an 80-word breakup email. State plainly this is the last message on
this topic. Offer one easy path back in: a specific trigger to watch for,
or an open invitation to reply anytime. No guilt-tripping language. No
fake deadline.
15. "Should I stop" data-point variant
Context: [N] touches, no reply, but [any engagement signal you have:
opened emails, a pricing page visit, or none at all].
Write a 50-word breakup email framed as a single yes-or-no question:
"Should I stop reaching out, or is the timing just off?" Make replying
"no, not now" as easy as replying "yes."
Either breakup prompt works; pick 14 when you want a clean close and 15 when there's still a live signal, an open email, a page visit, worth one more direct question before you let the account go quiet.
What AI prompts work for a LinkedIn touch alongside email?
LinkedIn works as a parallel channel, not a replacement for email. A connection request, a post-accept message, and a genuine comment warm up a prospect who hasn't opened anything you've sent yet. These three prompts keep each one specific instead of templated.
16. Connection request note
Prospect: [name, title, company]. Shared context: [mutual connection,
group, recent post, or a genuine reason for connecting].
Write a 250-character connection request note. Lead with the shared
context, not a pitch. No mention of my product or company name.
17. Post-accept DM
Prospect: [name, title, company]. They accepted my connection request
[X days] ago. Context from their profile or recent activity: [something
specific and real].
Write a 60-word DM referencing that specific context, stating what I do
in one sentence, and asking a single low-pressure question, not a
meeting ask.
18. Comment-then-message sequence
Prospect's recent post: [paste the topic or a one-line summary].
Write a genuine, specific comment (30 words) responding to the substance
of the post, not generic praise. Then write a follow-up DM (50 words),
sent 2 days later, referencing the comment and my company in one line,
with a single question.
The comment has to be about the substance of what they wrote, not the fact that they wrote it. "Great post!" is invisible; a specific reaction to the actual point they made is what makes the DM two days later feel like a continuation of a conversation instead of a cold open.
How do you ask for a referral without sounding like you're giving up?
A referral ask works two ways inside one account: mid-sequence, when you've reached the wrong level, and after a stall, when your champion has gone quiet. Both frame the ask as removing friction for the recipient, not escalating around them.
19. Mid-sequence, wrong level
Contact reached: [name, title], likely not the decision-maker for [type
of purchase]. Context: [what they said, if they replied at all].
Write a 60-word email asking directly who owns this decision, offering to
loop them out of future emails if they'd prefer. Make it easy to redirect
in one line.
20. Post-stall, ask the champion for an internal intro
Contact: [name, title], engaged positively [X weeks] ago, then went quiet.
Likely blocker: [budget cycle, competing priority, reorg, if known].
Write a 70-word email asking whether there's someone else worth looping
in, given the likely blocker. Frame it as removing pressure from them, not
going over their head.
Naming the likely blocker before asking for the intro matters. It shows the ask isn't "you went quiet, so I'm going around you," it's "I understand what probably happened, and here's a way forward that doesn't put you on the spot."
How do you re-engage a deal that went closed-lost?
A closed-lost deal isn't dead, it's dated. These two prompts revisit the stated reason for passing and reopen the conversation only when something material has actually changed, which is what separates a legitimate re-engagement from a nagging re-send.
21. Revisit the stated reason for passing
Deal closed-lost [X months] ago. Stated reason: [price, timing, feature
gap, chose a competitor, verbatim if you have it].
What has changed since then: [specific: new pricing tier, new feature,
budget cycle reset].
Write a 70-word email that names the original reason honestly, states
what changed, and asks one direct question about whether it's worth
revisiting.
22. New trigger after months of silence
Deal closed-lost or gone cold [X months] ago. New trigger: [funding, a
new hire, a tool change, from prompts 1-4].
Write a 60-word re-engagement email. Do not apologize for the gap in
contact. Open with the new trigger, connect it briefly to the earlier
conversation, single low-friction ask.
Skipping the apology is deliberate. "Sorry it's been a while" centers the silence; opening with the new trigger centers the reason the email exists today, which is the only thing that actually justifies writing to a cold account again.
How do you reply to interested, not-now, wrong-person, and hostile responses?
The reply is where most sequences actually fail, not because the news is bad, but because the response to it is generic. A sequence can nail the trigger, the first touch, and every follow-up, and still lose the deal in the first reply if that reply reads like a canned template instead of a response to what the person actually wrote. Four reply types need four different structures, and none of them should re-pitch the product from scratch.
23. Interested, booking the call
Reply received: [paste or summarize, e.g. they said yes or asked to
schedule].
Write a 40-word reply. Thank them briefly, one clause, not a paragraph.
Propose 2 specific time windows and include a scheduling link if I have
one. No re-pitching the product in this email.
24. Interested, but they asked a specific question first
Reply received: [paste their question].
Answer: [the actual factual answer, do not invent one].
Write a 60-word reply. Answer their exact question directly in sentence
one. Do not pivot straight back to booking a call, offer it as the second
step, not the only one.
A prospect who asks a specific question is testing whether you'll actually answer it or use it as a pretext to schedule a call. Answering first, thoroughly, is what earns the right to suggest the call as a next step rather than a redirect.
25. Not now, timing objection
Reply received: [paste, e.g. "not a priority right now" or "check back
in Q3"].
Write a 50-word reply that accepts the timing at face value, asks one
clarifying question about what would need to be true for the timing to
change, and confirms a specific date to follow up rather than "I'll check
in later."
26. Not now, budget or priority objection this cycle
Reply received: [paste, e.g. "no budget this quarter"].
Write a 50-word reply. Do not argue with the objection. Ask whether the
constraint is this specific project or budget broadly, and offer to send
one relevant piece of information for when the cycle resets, framed as
useful, not as another pitch.
Distinguishing "no budget for this" from "no budget for anything right now" changes what you do next. The first is a scoping conversation worth continuing; the second is a timing problem, closer to prompt 25 than to an active objection worth arguing.
27. Wrong person, redirect ask
Reply received: [paste, e.g. "this isn't my area, try [name/department]"].
Write a 35-word reply. Thank them for the redirect specifically. Ask if
they're comfortable making the introduction, or if I should reach out
directly using their name as reference.
28. Forwarded internally, no response yet
Context: original contact said they'd forward to [name/department]
[X days] ago. No reply from either party since.
Write a 40-word follow-up to the original contact only, asking if the
forward went through and if there's a better way to reach the right
person directly.
Going back to the original contact rather than guessing at the new one respects the redirect they already gave you. Reaching out cold to whoever you think received the forward, without confirmation, is how a polite wrong-person reply turns into two annoyed people instead of one helpful one.
29. Hostile or annoyed, de-escalate and exit clean
Reply received: [paste, e.g. an annoyed tone, "stop emailing me"].
Write a 35-word reply. No defensiveness, no apology-flooding. Confirm
they will not hear from me again on this topic. One sentence, then stop.
30. Formal opt-out or spam complaint
Reply received: [paste, e.g. "remove me" or "reporting as spam"].
Write a 25-word reply confirming immediate removal from all future
outreach on this list, with no additional pitch, question, or explanation
attached.
Once you have a few real replies to compare, pasting one into a prompt as context is a form of few-shot conditioning: the model matches the register of what was actually said instead of guessing at a generic tone. Treat the 30 prompts above as a reusable prompt template set, not one-off drafts, and once you have two or three variants worth comparing, our guide to A/B testing your prompts covers how to isolate what's actually working. If you're running this solo against individual clients rather than an account list, the freelancer-specific version of these lives in 40 AI prompts for freelancers.
The three habits that separate a sequence that compounds from one you rebuild every quarter: fill every bracket before running the prompt, so the output is specific enough to send, not generic enough to guess at; name the new reason for each touch before you write it, not after; and save the reply-handling prompts once they produce a version your own voice would actually send, so the next hostile reply or wrong-person redirect takes thirty seconds instead of ten minutes.
None of that requires a different tool for each stage. The same 30 prompts run in ChatGPT, Claude, or Gemini, and the only thing that changes across a sequence is which one you reach for and what you paste into the brackets.
Stop rewriting prompts. Start shipping.
Works with ChatGPT, Claude, Gemini, Grok, Midjourney, Ideogram, Veo3 & Kling. 5.0★ on the Chrome Web Store.
Create An Account