Prompts · Review request

Review request email prompts that get a specific answer.

Copy/paste review request email prompts for any model. Each one asks one specific question, never steers the sentiment and never offers anything in exchange. Then bring the copy to the studio and ship the campaign.

Every review request email prompt, in one place.

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

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

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

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.