Email Writing Prompts for Cold Emails & Follow-Ups
Email is where deals stall, tickets sour, and newsletters get ignored, usually because of the wording rather than the idea. A good prompt hands the AI the context it needs (the recipient, the goal, the tone) so the draft comes back ready to send instead of ready to rewrite. These five cover the emails operators and teams send most: cold outreach, follow-ups, newsletters, and support replies.
You're staring at a blank compose window for a cold email and don't want to sound like every other pitch in the prospect's inbox.
A prospect, candidate, or vendor went quiet, and you need a follow-up that adds a reason to reply instead of just 'bumping this.'
Your weekly or monthly newsletter is due and you need a subject line and structure that actually get opened on a phone.
Support tickets are stacking up and every reply has to sound human, stay on-brand, and genuinely resolve the issue.
You're rolling out a product change and have to tell thousands of users without triggering a wave of confused replies.
Mistakes to avoid
Asking for 'a professional email' with no context. Without the recipient, the goal, and one proof point, the AI gives you generic filler that reads like spam.
Treating the subject line as an afterthought. Much of your open rate lives in those few words, so prompt for the subject separately and ask for three options.
Not pasting the actual thread or customer message. The AI can't match tone or reference specifics it never saw, so support and follow-up replies come out hollow.
Accepting the first draft's length. AI emails default to padded and polite, so if you don't cap the word count, your one clear ask drowns in throat-clearing.
Prompts you can copy
01
Cold outreach email
You are an SDR writing a cold email to a {prospect role} at {company}, a {industry} business. We help teams {core outcome}, and recently {proof point or customer result}. Write a cold email under 90 words with a subject line under six words. Open with a specific observation about their world, not about us. Include one concrete benefit with a number, and close with a low-friction yes/no ask. No buzzwords, no 'hope this finds you well.' Output the subject line, then the body.
02
Follow-up after no reply
You are following up on an email you sent {number} days ago to {name} about {topic} that got no reply. Write a follow-up under 60 words that adds new value instead of just bumping the thread. Restate the original ask in one line, give one fresh reason to act now ({new angle, resource, or deadline}), and make replying effortless. Keep the tone warm and confident, never guilt-tripping. Output a subject line plus the body.
03
Newsletter issue
You are the editor of {newsletter name}, a {frequency} newsletter for {audience}. Draft one issue on the theme {topic}. Include a subject line and preview text, both under 50 characters, a two-sentence personal intro, three short sections that each open with a bolded takeaway followed by 2-3 sentences, and one clear call to action to {desired action}. Write in a {tone, e.g. practical and conversational} voice that scans easily on a phone, with no filler. Output the full email as plain text with section labels.
04
Customer support reply
You are a support agent replying to {customer name}, who wrote in {frustrated / confused / neutral} about {issue}. Their message: {paste the customer's message}. Write a reply that acknowledges the specific problem in the first line, explains what happened in plain language, lists the exact steps to fix it, and sets a realistic expectation ({timeframe}). Use a {brand tone} voice, stay under 120 words, and never blame the customer or hide behind policy. Output a subject line plus the reply body.
05
Product update announcement
You are a product marketer announcing {feature or change} to existing users of {product}. Lead with the benefit to the user, not the feature name. Include a subject line under 45 characters, one sentence on what changed, a 'why it matters' line tied to a real user pain, a short step for trying it, and a single CTA button label. Flag any action users must take before {date}. Keep it under 130 words with no hype. Output the subject line, preview text, body, and CTA label.
How to keep them in PromptAtlas
Create one folder for the job or channel.
Add clear tags so search still works later.
Turn changing details into variables.
Save better versions instead of overwriting useful attempts.
Export your library when you need a backup.
FAQ
How do I get AI to write emails that don't sound robotic?
Give it a voice reference and hard constraints. Paste two or three of your own past emails, name the tone (for example 'direct but warm'), and ban stock phrases like 'I hope this email finds you well.' Concrete examples beat adjectives every time.
What's the best prompt structure for a cold email?
Lead with the context the AI needs: who the recipient is, what they care about, and one concrete result you've delivered. Then ask for a short email with a specific subject line, one benefit backed by a number, and a low-friction call to action. Cap it under 90 words.
Can I reuse the same email prompt for different recipients?
Yes, and that's the whole point of {curly} placeholders. Save the prompt once with variables for the name, company, and pain point, then swap those in for each send. A prompt manager like PromptAtlas lets you fill the blanks without rewriting the whole thing.
How long should an AI-written email be?
Shorter than the AI wants it to be. Cold emails work best under 90 words, follow-ups under 60, and support replies under 120. Always put a word cap in your prompt, because models pad with pleasantries that push your real ask below the fold.
{A}
Build your prompt library
Save the prompts that work, add variables, keep versions and find them again in seconds.