Prompts

Free email prompts that write the words.

Copy an email prompt, paste it into ChatGPT, Claude or Gemini, and get clean plain-text email copy back.

These prompts write the words. If you need the HTML too, here is the method.

The library

Every free email prompt, in one place.

Welcome SaaS Friendly

Day-one welcome for a new free trial

Get them to complete the one action that makes the product make sense.

Write a plain-text day-one welcome email from [SENDER] to someone who just started a free trial of [PRODUCT]. Words only — no HTML, no layout notes.

The single action this email drives: [THE FIRST ACTION].

Rules:
- 100 to 140 words. Short sentences.
- Do not tour the product. Name one action and explain what it proves: [WHAT IT PROVES]. A list of five features is a list of five ways to do nothing.
- Say what the trial is in concrete terms: [TRIAL LENGTH], including whether a card is required and what happens on the last day. Vagueness here is what makes people cancel early out of caution.
- One ask, written as an ordinary sentence with the link inside it. No second link, no help-centre tour, no calendar booking.
- Invite a reply and mean it. One line, at the end, from a person.
- Do not congratulate them for signing up. They did not achieve anything yet.
- Never invent a number, statistic, customer count or time saving. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the first action. Return subject, preheader, body, sign-off.

Generate your own

Abandoned cart Ecommerce Friendly

Browse abandonment email for a viewed product

Bring them back to the product page with one useful thing they did not have.

Write a plain-text browse abandonment email from [BRAND] to someone who looked at [THE PRODUCT] and left without adding it to a cart. Words only — no HTML, no layout notes.

They did not choose anything. They looked. Write accordingly.

Rules:
- 80 to 120 words. Three short paragraphs.
- Do not say "we noticed you were looking" or anything else that describes the tracking. Nobody enjoys being told they were watched.
- Lead with the product and one genuinely useful thing about it: [THE USEFUL THING]. That fact is the reason this email is allowed to exist.
- Do not offer a discount. They have not shown enough intent to be worth margin.
- One ask, written as an ordinary sentence with the link inside it, pointing at the product page.
- Mention at most one alternative, and only as an aside. A grid of six alternatives says you did not understand what they came for.
- Never invent a number, statistic, rating or review count. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters about the product, not about their behaviour. Return subject, preheader, body, sign-off.

Generate your own

Announcement Local service Friendly

New location or opening hours notice

Make sure nobody arrives at the wrong place or the wrong time.

Write a plain-text notice from [SENDER] at [BUSINESS] about a practical change: [WHAT CHANGED], from [FROM WHEN]. Words only — no HTML, no layout notes.

The job of this email is that nobody turns up at the wrong place or the wrong time.

Rules:
- 90 to 130 words. Plain language.
- Lead with the change and the date. Both in the first sentence.
- Give [THE PRACTICAL DETAIL] its own short paragraph. Parking, which door, the nearest stop, whether the old address still works for a while. This is the part customers actually need and the part most of these emails leave out.
- Do not turn it into a celebration. A new address is news, not an achievement, and a paragraph about our exciting new chapter delays the information people opened for.
- No offer, no discount, no invitation to book. One quiet line about how to reach you is enough.
- Never invent a number, statistic, address detail or opening time beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the change concretely. Return subject, preheader, body, sign-off.

Generate your own

Cold outreach Agency Spartan

Cold first-touch email to a business owner

Get a reply, not a meeting. The meeting is the second email.

Write a cold email from [WHO YOU ARE] to [WHO THEY ARE]. They have never heard of me. Plain text only — no formatting, no bullet lists, no HTML.

The email is built on one thing: [THE OBSERVATION]. Everything else exists to hold it up.

The single action this email drives: [THE ASK].

Rules:
- 90 to 130 words. Four short paragraphs at most. No paragraph longer than two sentences.
- Open on the observation. Not on my name, not on my company, not on how I found them.
- Say who I am in one clause, buried mid-email where it belongs. Nobody opens a cold email to learn about the sender.
- Make the ask small enough to answer in one line. Ask for a reply, not for thirty minutes. Do not include a booking link.
- No compliments that could be pasted into any other email. If the praise would fit a hundred businesses, cut it.
- No questions that answer themselves. Skip "are you looking to grow" and anything shaped like it.
- Never invent a number, statistic, result or client name. If a figure would help, leave [XX] and I will fill it in or cut it.
- No exclamation marks. No emoji. Sentence case. Write a subject line of five words or fewer that reads like a human wrote it to one person.

Return the subject line, then the body, then a sign-off.

Generate your own

Event Creator Friendly

In-person workshop invite

Get the RSVP from people who will actually turn up.

Write a plain-text invitation to [THE EVENT], happening [WHERE AND WHEN]. Words only — no HTML, no layout notes.

The reader is deciding whether to give up an evening and a journey. Write for that decision.

Rules:
- 110 to 160 words.
- Say what actually happens there in the first two sentences. Not the theme, not the vibe — what people will be doing in the room.
- Include the end time as well as the start. Someone weighing up childcare or a train needs both, and leaving the end time out costs more RSVPs than any other omission.
- Name [WHO IT SUITS] in one sentence, and be willing to exclude. A room of people who came because it sounded vaguely relevant is worse than a smaller room.
- Cover [THE PRACTICALITIES] in one short paragraph. Cost, numbers, whether there is food, whether to bring anything.
- One ask, written as an ordinary sentence with the link inside it.
- Do not describe the atmosphere. Do not promise networking.
- Never invent a number, statistic, capacity or attendee count beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the event and the city or the date. Return subject, preheader, body, sign-off.

Generate your own

Follow-up Agency Professional

Follow-up after a first meeting

Get agreement on the record and the next step owned by someone.

Write a plain-text follow-up after a meeting with [WHO WAS THERE], covering [WHAT WAS AGREED]. Words only — no HTML, no layout notes.

This email becomes the record. Write it so that if someone reads it in six weeks, they know what was decided.

Rules:
- 90 to 130 words.
- Open with one sentence naming what was agreed at the highest level. Not "thanks for your time" — that can go at the end in four words or not at all.
- Then [WHO DOES WHAT], as a short list. Each line is an action, an owner and a date. Put my own actions first; leading with theirs reads as an invoice.
- Include [THE OPEN QUESTION] explicitly, with who is expected to resolve it. Unwritten open questions are the ones that surface as a disagreement two months later.
- Do not summarise the discussion. Nobody rereads a recap of a conversation they were in.
- Do not pitch, do not attach a proposal unless one was asked for, and do not suggest a next meeting unless one was agreed.
- Never invent a number, date, figure or commitment that was not in my notes. If something is unclear, write it as an open question rather than resolving it in the email.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the project. Return subject, body, sign-off.

Generate your own

Newsletter SaaS Friendly

Founder note for a small SaaS list

Get the reader to read to the end. The click is a side effect, not the point.

Write a monthly plain-text founder letter about [PRODUCT], in first person, signed by [SENDER]. Words only — no HTML, no layout notes, no section dividers.

Three beats in this order: [WHAT SHIPPED], then [WHAT BROKE], then [WHAT IS NEXT].

Rules:
- 200 to 280 words total. Three or four paragraphs. Let them get shorter as the letter goes on.
- Open on the substance. No greeting about the month, no "hope you are well", no throat-clearing.
- The shipped paragraph explains why it matters to the reader, not what the feature is called.
- The broke paragraph is the one that earns the next open. Say what went wrong plainly, without apology theatre and without making it a lesson.
- The next paragraph is one sentence. Do not promise a date I did not give you.
- At most one link, written inside a sentence. This letter is read, not clicked. Do not add a postscript full of links.
- No headers, no bullet lists, no bold. This is a letter.
- Never invent a number, statistic, growth figure or customer count. If a number belongs, leave [XX] and I will fill it in.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters that names the month's actual subject rather than "[PRODUCT] monthly update". Return subject, preheader, body, sign-off.

Generate your own

Product launch SaaS Professional

Feature launch email for existing users

Get existing users to try the feature once.

Write a plain-text feature announcement from [PRODUCT] to existing users about [THE FEATURE]. Words only — no HTML, no layout notes.

The single action this email drives: trying the feature once.

Rules:
- 110 to 160 words.
- Open on [THE OLD PAIN], not on the feature. One or two sentences naming the workaround people have been living with. A reader who does not recognise the problem has no reason to read about the solution.
- Then say what shipped, in one sentence, in the words a user would use. Not the internal name, not the version number.
- Say exactly where to find it: [WHERE TO FIND IT]. A path, not a vague location. This is the line that decides whether anyone actually tries it.
- One ask, written as an ordinary sentence with the link inside it.
- Do not tease what is coming next. Do not thank anyone for their patience. Do not describe the engineering.
- Never invent a number, statistic, time saving, adoption figure or customer count. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters describing what the user can now do, not what we built. Return subject, preheader, body, sign-off.

Generate your own

Promotional Creator Urgent

Last-chance reminder before an offer closes

Convert the people who already decided and did not get round to it.

Write the final plain-text reminder that [THE OFFER] closes at [THE DEADLINE]. Words only — no HTML, no layout notes.

Everyone receiving this has already had the full pitch. This email is a deadline, not an argument.

Rules:
- 50 to 80 words. This is the shortest email in the sequence and it should look short on a phone.
- Open with the deadline. First six words.
- Do not re-pitch. No new benefit, no new testimonial, no "in case you missed it" recap of the offer's features. Restate the offer in one clause only so they know which thing this is.
- Say [WHAT HAPPENS AFTER] in one sentence. A deadline with no consequence is not a deadline, and readers who have seen you bluff once will wait next time.
- One ask, written as an ordinary sentence with the link inside it. Nothing else clickable.
- Do not apologise for emailing again and do not say "last email, promise".
- Never invent a number, statistic, seat count or sales figure. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line of five words or fewer built around the deadline. Return subject, preheader, body, sign-off.

Generate your own

Re-engagement SaaS Professional

Email after someone cancels a subscription

Learn why they left. Winning them back is not this email's job.

Write a plain-text email from [SENDER] to someone who has just cancelled their [PRODUCT] subscription. Words only — no HTML, no layout notes.

The cancellation has already gone through. This email does not try to reverse it.

Rules:
- 80 to 120 words. Calm, short, no theatre.
- Confirm the cancellation in the first line, plainly, with no attempt to make them feel it.
- Say what happens to their data: [WHAT HAPPENS TO THEIR DATA]. This is the most useful thing in the email and most cancellation emails leave it out.
- Ask exactly one question about why they left, and make it answerable in a sentence. No survey, no rating scale, no link to a form.
- Do not offer a discount to stay. Do not offer a pause. Do not mention a feature that is coming. They have decided, and arguing with the decision is what makes people tell other people about it.
- One line saying the door is open, phrased so it costs them nothing to ignore.
- Never invent a number, statistic or customer count. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters that confirms rather than pleads. Return subject, body, sign-off.

Generate your own

Review request Ecommerce Friendly

Review request after a purchase

Get one honest review, positive or not.

Write a plain-text review request from [BRAND] to someone who bought [THE PRODUCT] about [HOW LONG THEY HAVE HAD IT] ago. Words only — no HTML, no layout notes.

The single action this email drives: writing one review.

Rules:
- 70 to 110 words.
- Name the product and roughly how long they have had it in the first line. A review request that could have been sent to anyone gets a review that could have been written about anything.
- Ask [THE SPECIFIC QUESTION] rather than "how did we do". A specific question produces a specific review, and specific reviews are the ones other buyers read.
- Do not indicate what a good answer looks like. No "we hope you love it", no five-star imagery, no "if you were happy". Steering the sentiment is how a review section becomes worthless, and on many platforms it is against the rules.
- Do not offer anything in exchange. A discount for a review buys reviews, not honesty.
- Give them a way to reply directly if something went wrong, in one line. Some of these emails should end as a support conversation instead of a review, and that is a good outcome.
- One ask, written as an ordinary sentence with the link inside it.
- Never invent a number, statistic, rating, review count or customer figure. Where a figure belongs and I have not supplied it, leave a bracketed placeholder.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters referencing the product. Return subject, preheader, body, sign-off.

Generate your own

Transactional Ecommerce Friendly

Order confirmation worth reading

Stop the where-is-my-order email before it gets written.

Write a plain-text order confirmation from [BRAND] for [THE ORDER]. Words only — no HTML, no layout notes.

This email exists to answer the three questions a buyer has the moment they finish paying: did it work, when does it come, and can I still change it.

Rules:
- 90 to 130 words on top of the order details themselves.
- Confirm in the first line, with the order number. Do not open by thanking them at length; one short thank-you can go at the end.
- Say [WHEN IT SHIPS] concretely. "Leaves us Tuesday" beats "3 to 5 business days", because the second is a range the reader has to convert into a date and will get wrong.
- Say [WHAT HAPPENS NEXT] — the next email they will get and roughly when. A buyer who knows a dispatch email is coming does not write to ask where the order is.
- Give [HOW TO CHANGE IT] its own line, including the cutoff. Address corrections are the most common support request and the cheapest to prevent.
- No cross-sell, no discount for next time, no review request. Those come later and they make this email harder to scan for the information it exists to carry.
- Never invent a number, date, tracking reference or delivery estimate beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters carrying the order number. Return subject, preheader, body, sign-off.

Generate your own

Welcome Creator Friendly

Delivery email for a lead magnet download

Get the file into their hands, then set up the next email.

Write a plain-text delivery email from [SENDER] to someone who just downloaded [THE RESOURCE]. Words only — no HTML, no layout notes.

The single action this email drives: opening the resource.

Rules:
- 90 to 130 words.
- Put the download link in the first two lines. Everything else in this email is optional to the reader and the link is not.
- Then give away [THE ONE TIP] in the body — the most useful thing inside the resource, stated plainly. A delivery email that withholds its own contents is a receipt, and receipts do not earn a second open.
- Say what the next email will be about and roughly when: [WHAT COMES NEXT]. One sentence.
- Do not pitch anything. Do not mention a product, a course or a call. They have known you for ninety seconds.
- Sign off as a person.
- Never invent a number, statistic, download count or result. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters that names the resource so it is findable in a search six weeks from now. Return subject, preheader, body, sign-off.

Generate your own

Abandoned cart Ecommerce Spartan

Last cart reminder before it clears

Recover the cart or release the reader. Both beat a third unanswered email.

Write the last plain-text cart reminder from [BRAND] about [THE ITEM]. Words only — no HTML, no layout notes.

This is the final email in the flow. Two have already gone unanswered.

Rules:
- 60 to 90 words. Two or three paragraphs. Shorter than the emails before it.
- Say plainly that this is the last one. A closing email that does not admit it is closing has no reason to exist.
- State what actually happens next: [WHAT ACTUALLY HAPPENS]. If nothing happens, say the cart will just sit there. Do not invent a countdown, an expiry or a stock level I did not give you.
- One ask, written as an ordinary sentence with the link inside it, pointing at the cart.
- End by making it easy to walk away. One line, no guilt, no "we will miss you".
- Never invent a number, statistic, discount or scarcity claim. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters that is honest about being the last email. Return subject, preheader, body, sign-off.

Generate your own

Announcement Professional

Terms or policy update notice

Have the reader understand what changed and whether it affects them.

Write a plain-text notice about a change to our terms or policy: [WHAT CHANGED], effective [WHEN]. Words only — no HTML, no layout notes.

The reader should be able to tell within ten seconds whether this affects them.

Rules:
- 100 to 150 words.
- First sentence says what changed, in ordinary language. Do not open with "we are writing to inform you" and do not quote a clause number.
- Second, say who it affects: [WHO IT AFFECTS]. If it is everyone, say everyone. If it is a subset, name it precisely so the rest can stop reading.
- Then state [WHAT THEY MUST DO]. If the answer is nothing, write "you do not need to do anything" as its own sentence. That is the most useful line in the email and it is usually missing.
- Link the full text exactly once, inside a sentence, at the end. Not three times, not as a button.
- No reassurance padding. Do not write that we take privacy seriously or that this is part of our ongoing commitment to anything.
- Never invent a number, statistic, date or legal detail beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the change. Never "Important update". Return subject, preheader, body, sign-off.

Generate your own

Cold outreach Creator Friendly

Cold pitch for a collaboration or swap

Get a yes-in-principle. The logistics are the next email.

Write a plain-text cold email to [WHO THEY ARE] proposing [WHAT YOU PROPOSE]. We have never spoken. Words only — no HTML, no layout notes.

Rules:
- 100 to 140 words. Four short paragraphs at most.
- Open with [THE SPECIFIC THING] — a real detail from their work, in one sentence. Generic praise reads as a mail merge and is worse than no opener.
- Put [WHAT THEY GET] before what I get. A collaboration email that leads with my side is a favour request wearing a partnership costume.
- State the proposal in one clear sentence. No decks, no attachments, no phases.
- Ask only for a yes in principle. The dates and the logistics belong in the next email, and asking for them now makes the reply expensive.
- Do not describe our audience with adjectives. If a size or a figure matters, leave [XX] and I will fill it in.
- Never invent a number, statistic, subscriber count or engagement rate. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters that names the proposal rather than opening with a compliment. Return subject, body, sign-off.

Generate your own

Event Spartan

Follow-up after an event or webinar

Deliver what was promised, and give the interested ones one next step.

Write a plain-text follow-up to [ATTENDED OR NOT] for [THE EVENT]. Words only — no HTML, no layout notes.

Rules:
- 90 to 130 words.
- First line delivers [WHAT WAS PROMISED], with the link. That is what the email is for, and burying it under a thank-you is why these get closed unread.
- Adjust the opening to [ATTENDED OR NOT]. Someone who came should not be told what they missed; someone who did not should not be thanked for coming. Getting this wrong is the most visible way an automated follow-up shows its seams.
- State [THE ONE IDEA] in a sentence or two — the thing worth remembering. An attendee who never opens the recording should still get value from this email.
- Give [THE NEXT STEP] once, at the end, as an ordinary sentence with the link inside it. If there is no genuine next step, leave it out rather than inventing one.
- Do not include a feedback survey and a resource link and a sales call in the same email. Pick one.
- Never invent a number, statistic, attendance figure or quote from the session. Where a figure belongs and I have not supplied it, leave a bracketed placeholder.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming what is inside. Return subject, preheader, body, sign-off.

Generate your own

Newsletter Local service Friendly

Monthly note for a local business list

Stay in the inbox as a useful sender, so the next offer email gets opened.

Write a plain-text monthly note from [SENDER] at [BUSINESS] to the customer list. Words only — no HTML, no layout notes.

Nothing is being sold in this email.

Rules:
- 150 to 220 words. Plain language, the way you would explain something to a customer standing in front of you.
- Lead with [THE USEFUL THING] and give it most of the email. Something a customer can act on without hiring anyone — the seasonal check, the common mistake, the thing people always ask.
- Cover [WHAT IS HAPPENING] in one short paragraph, at the end. Hours, a new person, a busy month. If there is nothing, leave it out rather than padding it.
- No offer, no discount, no booking push. One quiet line saying how to get in touch is enough, and it belongs last.
- Do not write a preamble about the month or the weather. Start on the useful thing.
- Never invent a number, statistic, saving or rating. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the useful thing. Never the business name plus "newsletter". Return subject, preheader, body, sign-off.

Generate your own

Product launch Ecommerce Luxury

Launch email for a single new product

Get the reader to the product page while the launch is still new.

Write a plain-text launch email from [BRAND] for [THE PRODUCT]. Words only — no HTML, no layout notes.

One product. One story. One action.

Rules:
- 100 to 150 words. Unhurried sentences, but not long ones.
- Open with [THE STORY] — why this exists — rather than with the announcement. "We made a thing" is not a reason to read; the reason it exists is.
- Include [THE DETAIL] somewhere in the middle. One concrete specific the photographs cannot carry. Concrete detail is what separates a launch from an advert.
- No superlatives. No "finally", no "we are pleased to", no adjectives doing the work a noun should do.
- Do not mention other products. A launch email that cross-sells is not a launch email.
- Do not invent scarcity, an edition size or a sell-out risk. If the run is genuinely limited I will give you the number; otherwise say nothing about quantity.
- One ask, written as an ordinary sentence with the link inside it.
- Never invent a number, statistic, price, edition size or review. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters naming the product plainly. Return subject, preheader, body, sign-off.

Generate your own

Promotional Local service Professional

Promotional email for a local service offer

Get the reader to book the offer before it ends.

Write a plain-text promotional email from [BUSINESS] about [THE OFFER]. Words only — no HTML, no layout notes.

The single action this email drives: [HOW TO BOOK]. Nothing else in the email competes with it.

Rules:
- 110 to 160 words. Short sentences. Plain language a neighbour would use.
- Lead with the offer in the first line. Not with the season, not with a greeting, not with how busy we have been.
- Say exactly what the reader gets and what it costs. If I have not given you a price, leave [XX] rather than guessing at one.
- Name who it suits: [WHO IT SUITS]. One sentence. This is what stops the rest of the list feeling sold to.
- State the deadline as [THE DEADLINE], in the body and near the ask. Write "ends [THE DEADLINE]", never "limited time" and never "act fast".
- One ask, written as an ordinary sentence. Repeat the same ask once at the end, in the same words.
- Do not stack reasons to buy. Two is plenty.
- Never invent a number, statistic, discount, review or customer count. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters that names the offer plainly. Return subject, preheader, body, sign-off.

Generate your own

Re-engagement Agency Professional

Email to a past client who went quiet

Restart the conversation. The work, if any, is two emails away.

Write a plain-text email to [CLIENT], a past client we have not worked with in [HOW LONG]. Words only — no HTML, no layout notes.

I am writing because of [THE PROMPT], not because the pipeline is thin.

Rules:
- 90 to 130 words. Three short paragraphs.
- Open on [THE PROMPT]. A reason to write that is external to my needing work is the only thing that separates this from a pipeline email, and clients can tell instantly.
- Reference the work we did in half a sentence, specifically enough that it is clearly them and not a template.
- Do not ask how they have been. Do not say "I hope this finds you well". Do not say "I was just thinking about you", which is almost always untrue.
- No proposal, no availability, no attachment, no rate card. If they want to work together they will say so, and if they do not, mentioning it makes the email awkward to answer.
- End with a question they can answer in one line, about their work rather than about a project.
- Never invent a number, statistic or result from the previous engagement. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line of five words or fewer that references the prompt, not the relationship. Return subject, body, sign-off.

Generate your own

Review request Local service Friendly

Review request after a service job

Get a review on the platform that matters, or a reply if something is wrong.

Write a plain-text review request from [SENDER] at [BUSINESS] to a customer whose [THE JOB] is finished. Words only — no HTML, no layout notes.

Rules:
- 70 to 110 words. Plain language, as if spoken.
- Reference the actual job in the first line so it is clearly about them.
- Ask for a review on [WHERE TO REVIEW] and name it. One platform. Offering a choice of three halves the completion rate, because choosing is work.
- Say roughly how long it takes. "Two minutes" removes the main objection, and it should be true.
- Do not say you would appreciate a five-star review, do not say reviews help small businesses like ours, and do not attach a prize draw. All three read as pressure and the third breaks most platforms' rules.
- Offer a direct reply if anything was not right, in one line, before the review link. A customer with a complaint should find that route first.
- One ask, written as an ordinary sentence with the link inside it.
- Never invent a number, statistic, rating or review count. Where a figure belongs and I have not supplied it, leave a bracketed placeholder.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters referencing the job. Return subject, preheader, body, sign-off.

Generate your own

Transactional SaaS Spartan

Password reset email

Get the right person to the reset link and reassure the wrong one.

Write a plain-text password reset email for a [PRODUCT] account. Words only — no HTML, no layout notes.

Two people receive this email: someone who just asked for it, and someone who did not. Serve both.

Rules:
- 50 to 80 words. Nothing in this email that is not about resetting the password.
- First line says what this is and that someone requested it. The reset link goes immediately after.
- State [HOW LONG IT LASTS]. A reader who does not know the link expires will open it tomorrow and be confused; a reader who does will act now.
- Give [IF IT WAS NOT THEM] its own line, and be calm about it. An unrequested reset email is alarming, and the correct reassurance is that the password has not changed and nothing happens unless the link is used.
- No branding paragraph, no marketing, no links to anything else. Not the blog, not the help centre, not the app. One link, one purpose.
- Never invent a number, figure or timestamp — that includes any IP address, device or location. If I have not supplied it, leave it out entirely rather than guessing.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 35 characters. Plain and unmistakable. Return subject, body, sign-off.

Generate your own

Welcome Local service Professional

Welcome email after a first booking

Reduce the no-show. Everything else is secondary.

Write a plain-text welcome email from [BUSINESS] to someone who has just made their first booking: [WHAT WAS BOOKED]. Words only — no HTML, no layout notes.

The single job of this email is to make the appointment happen.

Rules:
- 110 to 150 words. Plain language a neighbour would use.
- Repeat the booking back in the first two lines — the service, the day, the time. That readback is the reassurance, and it is why this email gets opened again the morning of.
- Say what to have ready: [WHAT TO HAVE READY]. If there is nothing, write that there is nothing. An unanswered question is what makes people cancel.
- Give a real way to reach a person: [HOW TO REACH US]. Say plainly that changing the time is fine.
- Do not sell anything. No upsell, no review request, no newsletter pitch. Those come later and this email is not where you spend the goodwill.
- Never invent a number, statistic, rating or review count. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters that repeats the booking rather than saying "welcome". Return subject, preheader, body, sign-off.

Generate your own

Abandoned cart Ecommerce Friendly

First abandoned cart nudge, no discount

Get them back to the cart. No discount on the first email.

Write a plain-text abandoned cart email from [BRAND] to someone who left [THE ITEM] behind an hour ago. Words only — no HTML, no layout notes.

Assume they got distracted, not that they hesitated. This is the first email in the flow.

Rules:
- 70 to 110 words. Three short paragraphs at most.
- Open by naming the item. Not "you left something behind" — say what it was.
- Do not offer a discount, and do not hint that one is coming. Discounting on the first touch trains the list to abandon on purpose.
- Give exactly one reason to come back that is not price: [THE REASSURANCE].
- One ask, written as an ordinary sentence with the link inside it. Send them to the cart, not the homepage.
- Do not manufacture scarcity. Write about stock or a deadline only if I gave you one.
- Never invent a number, statistic, review count or rating. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters that names the item rather than the behaviour. Return subject, preheader, body, sign-off.

Generate your own

Announcement SaaS Professional

Price increase announcement

Have the customer understand the new price and the date without contacting support.

Write a plain-text email from [SENDER] telling an existing [PRODUCT] customer that the price is changing: [THE CHANGE], from [WHEN]. Words only — no HTML, no layout notes.

The reader should finish this email knowing what they will pay, when, and what their options are, without needing to contact anyone.

Rules:
- 120 to 170 words. Neutral, precise, unhurried.
- Put the old number, the new number and the date in the first three lines. A price email that makes the reader hunt for the number reads as an attempt to hide it, and that is what generates the angry reply.
- Give the reason in one sentence: [WHY]. One. A paragraph of justification signals that we do not think the increase is defensible.
- Do not apologise, and do not thank them for their understanding before they have given any.
- State [WHAT THEY CAN DO] plainly, including the option that costs us money. Burying the downgrade path is what turns a price rise into a cancellation.
- Do not bundle this with a feature announcement. Pairing a price rise with new features reads as a justification and cheapens both.
- Never invent a number, percentage, cost figure or customer count beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters that says a price is changing. Do not soften it into "an update to your account". Return subject, preheader, body, sign-off.

Generate your own

Cold outreach Agency Spartan

Webinar invitation for a live session

Get the registration. Attendance is a different email's problem.

Write a plain-text webinar invitation for [THE SESSION], running [WHEN]. Words only — no HTML, no layout notes.

The single action this email drives: registering.

Rules:
- 100 to 150 words.
- Lead with [WHAT THEY LEAVE WITH] — what the attendee can do afterwards that they cannot now. An agenda is not a reason to attend; an outcome is.
- Put [WHEN] on its own line, with the timezone. A reader deciding whether to register is really deciding whether they are free, and making them hunt for the time loses them.
- Name [WHO IS RUNNING IT] in one clause. Credentials in a full sentence read as insecurity.
- Say [THE RECORDING] explicitly. A large share of registrations come from people who already know they cannot make it, and hiding the recording policy costs those sign-ups for nothing.
- Three bullet points maximum if you use any at all, and only for what is covered.
- One ask, written as an ordinary sentence with the link inside it.
- Never invent a number, statistic, attendance figure or testimonial. Where a figure belongs and I have not supplied it, leave a bracketed placeholder.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the outcome or the topic, not the format. Return subject, preheader, body, sign-off.

Generate your own

Follow-up Local service Professional

Follow-up after sending a quote

Get a decision. A no now is worth more than a maybe for six weeks.

Write a plain-text follow-up to someone I sent [THE QUOTE] to, who has not replied. Words only — no HTML, no layout notes.

A clear no is a good outcome here. Write it that way.

Rules:
- 60 to 100 words. Shorter than the quote email.
- Reference the quote and roughly when it went, so they do not have to go looking.
- Address [THE OPEN QUESTION] in one sentence — the thing they were probably weighing. Naming it is what turns a nudge into a useful email, and it often surfaces the real objection.
- Do not discount. Do not offer to "work with their budget". A price that drops on the first follow-up was never the price, and they will remember that on the next job.
- State [WHAT CHANGES WITH TIME] only if it is genuinely true. If nothing changes, say the quote stands and leave it there.
- Make a no easy and explicit: one line inviting them to say if they have gone another way, with no guilt attached.
- Never invent a number, statistic, price or deadline beyond what I have supplied.
- No exclamation marks. No emoji. Sentence case.

Write a subject line of five words or fewer referencing the job, not the follow-up. Return subject, body, sign-off.

Generate your own

Newsletter Creator Friendly

Weekly roundup with a point of view

Give the reader one idea they keep, whether or not they click anything.

Write a plain-text weekly roundup newsletter from [SENDER] on [THE THEME], using [THE PICKS]. Words only — no HTML, no layout notes, no horizontal rules.

The reader should get something out of this even if they click nothing.

Rules:
- 250 to 350 words.
- Open with [THE ARGUMENT] — what I actually think about the theme — in two or three sentences. Do not open with "this week I have been reading". The opinion is the issue; the links are evidence for it.
- Give each pick one or two sentences saying why it is here and what it changed. Never write a description of what the piece is about. The reader can get that from the title.
- Order the picks so they build the argument, strongest last.
- Links go inline, inside the sentence, on the words that describe the thing. Do not write bare URLs and do not write "read more here".
- Close in one line. No summary, no housekeeping, no promotion of my own work.
- Never invent a number, statistic, subscriber count or claim about how something performed. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters that names the argument rather than the format. Never "Issue [XX]" and never "Weekly roundup". Return subject, preheader, body, sign-off.

Generate your own

Product launch Creator Friendly

Waitlist or pre-order opening email

Get them onto the list. The sale is a later email.

Write a plain-text email opening the waitlist for [THE THING]. Words only — no HTML, no layout notes.

The single action this email drives: joining the list.

Rules:
- 90 to 130 words.
- Say what [THE THING] is in the first two sentences, concretely. A waitlist for something the reader cannot picture collects addresses and nothing else.
- Name [WHO IT IS FOR] in one sentence, and be willing to exclude people. A waitlist that suits everyone suits nobody, and the ones who opt out now would have refunded later.
- State [WHAT JOINING MEANS] explicitly — whether it costs anything, commits them to anything, or just puts them first. This is the sentence that decides the sign-up rate.
- Give [WHEN]. A month is enough. Do not promise a date I have not given you.
- One ask, written as an ordinary sentence with the link inside it.
- Do not hype. No "something big", no "I have been working on something". Say what it is.
- Never invent a number, statistic, price, seat count or waitlist size. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters naming the thing rather than teasing it. Return subject, preheader, body, sign-off.

Generate your own

Promotional Ecommerce Salesy

Seasonal sale email with a real deadline

Get the reader to shop the sale before it ends.

Write a plain-text sale email from [BRAND] announcing [THE OFFER]. Words only — no HTML, no layout notes.

The single action this email drives: shopping the sale.

Rules:
- 90 to 130 words. Short sentences. The offer is the message, so nothing should delay it.
- First line is the offer and the deadline, together. Not a greeting, not a season, not a story about the year we have had.
- State [THE EXCLUSIONS] plainly in the body. Burying them in a footnote is what turns a good sale into a support queue.
- Write the deadline as [THE DEADLINE], in the body and again beside the ask. "Ends Sunday at midnight", never "limited time" and never "act fast".
- One ask, written as an ordinary sentence with the link inside it, repeated once at the end in the same words.
- Do not stack urgency. One deadline is urgency; a deadline plus a stock warning plus a countdown is noise, and readers discount all three.
- Never invent a number, statistic, discount, stock level or customer count. Where a figure belongs and I have not supplied it, leave [XX].
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters carrying the offer and nothing else. Return subject, preheader, body, sign-off.

Generate your own

Re-engagement Ecommerce Friendly

Win-back email for a subscriber gone quiet

Get one signal back — an open, a click or an unsubscribe. All three are better than silence.

Write a plain-text re-engagement email from [BRAND] to a subscriber who has not opened anything in [HOW LONG]. Write the words only — no HTML, no layout notes.

The single action this email drives: [THE ASK].

Rules:
- 100 to 150 words. Short sentences.
- Name the gap in the first line. Do not open with "we miss you" and do not pretend this is an ordinary send.
- Give one honest reason to look again: [WHAT CHANGED]. One. A list of five reasons reads as a catalogue and gets skipped.
- Make leaving easy and say so in plain words. Put the unsubscribe sentence in the body where they will see it, not only in the footer. A clean list is worth more than a name that never opens.
- One ask, written as an ordinary sentence with the link inside it. No buttons, no second ask.
- Do not apologise. Do not offer a discount unless I gave you one to offer.
- Never invent a number, statistic or figure. Where a figure belongs and I have not given it, leave [XX].
- No exclamation marks. No emoji. Sentence case throughout.

Write a subject line under 40 characters that names the situation rather than baiting the open. Return subject, preheader, body, sign-off.

Generate your own

Review request Agency Professional

Testimonial request from a client

Get three usable sentences without making the client write an essay.

Write a plain-text testimonial request from [SENDER] to [CLIENT], whose project is finished. Words only — no HTML, no layout notes.

Rules:
- 100 to 140 words.
- Do not ask for a testimonial. Ask three specific questions and say you will assemble their answers into something they can approve. A blank-page request is why most of these go unanswered — the client wants to help and does not want to write copy.
- The three questions should cover the situation before, what changed, and what they would say to someone considering it. Adapt the wording to [THE RESULT], and keep each answerable in a sentence or two.
- Say [WHERE IT GOES] plainly, and ask explicitly whether their name and company can appear. Consent asked afterwards is consent asked too late.
- Offer to draft it from their answers and send it back for approval or editing. That single offer is what moves the response rate.
- Do not suggest what the answers should be, and do not attach an example testimonial for them to copy. What comes back will be your own words in their mouth, and it will read that way.
- Never invent a number, statistic, result or quote. If [THE RESULT] needs a figure I have not supplied, leave a bracketed placeholder.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 45 characters. Return subject, body, sign-off.

Generate your own

Transactional Ecommerce Friendly

Shipping notification with a real ETA

Get the tracking number in front of them and set the arrival expectation.

Write a plain-text dispatch notification from [BRAND] for [THE ORDER]. Words only — no HTML, no layout notes.

Rules:
- 70 to 110 words.
- First line: it has shipped, with [TRACKING]. The tracking number is the reason this email is opened and it should be the first thing found.
- Give [THE WINDOW] as a range across named days, not as "3 to 5 business days". A reader should not have to count weekends.
- If the order was split, say what is in this shipment and what is still to come. An unexplained partial delivery is a support ticket every time.
- Give [IF IT DOES NOT ARRIVE] in one line, with a threshold. Telling someone when to start worrying stops them worrying earlier.
- No cross-sell, no review request, no discount. The reader is tracking a parcel.
- Never invent a number, figure or date of any kind — that includes the tracking number, the carrier, the window and any delivery estimate. Use only what I have supplied.
- No exclamation marks. No emoji. Sentence case.

Write a subject line under 40 characters saying it has shipped, with the order number. Return subject, preheader, body, sign-off.

Generate your own

Welcome Ecommerce Friendly

Welcome email for a new shop subscriber

Get the new subscriber to open the next email, not to buy today.

Write a plain-text welcome email for someone who just subscribed to [BRAND], a shop selling [WHAT YOU SELL]. They gave their address at [SIGNUP PLACE] and have not bought anything yet.

Write the words only. No HTML, no layout notes, no design suggestions.

The single action this email drives: [PRIMARY ACTION]. Everything else is context.

Rules:
- 120 to 180 words in the body. Short sentences. Let them get shorter as the email goes on.
- Open with what changed for the reader, not with how pleased we are. Say what they joined and what arrives next.
- Name the sending rhythm concretely: [CADENCE]. Never write "regularly" or "from time to time".
- One ask, written as an ordinary sentence with the link inside it. No second ask. No button language. Do not write "click here".
- Put one short reassurance line directly after the ask — how to leave the list, or that the address goes nowhere else. One line, no more.
- Write a subject line under 45 characters, then a preheader that carries the subject forward instead of repeating it. The preheader is a real sentence, not a fragment.
- Sign off from [SENDER]. A person, not the shop.
- Never invent a number, statistic, figure or customer count. Where I have not given you one, leave a bracketed placeholder such as [XX] and let me fill it in.
- No exclamation marks. No emoji. Sentence case throughout.

Return it in this order, each on its own line: Subject, Preheader, Body, Sign-off.

Generate your own

Browse

Browse free email prompts by email type.

By email type

By business type

All free email prompts →

In the studio

The words are the easy half. The email is the work.

A model writes the copy. It does not write HTML that survives Outlook, dark mode and a Gmail clip. Paste your brief into the studio and get a branded campaign your ESP will import — Mailchimp, Klaviyo, ActiveCampaign or MailerLite.

Generate your own See how it works