Designed email to plain-text rewrite
Use when a template-heavy email needs a plain-text version that reads like a person sent it.
Fill in before running
Replace each placeholder with your own detail. The more specific you are, the less the model invents.
- {{ORIGINAL_EMAIL}}
- {{SENDER_PERSON}}
- {{GOAL}}
- {{MAX_WORDS}}
Getting a better result
- Plain text often wins on reply rate for sales and lifecycle mail, and loses for merchandising. Decide which job the email has first.
- Keep the unsubscribe link even in a plain-text send. Removing it is both a legal and a deliverability problem.
- One link. Multiple links in a plain-text email make it read like a template again.
Questions about this prompt
When should I convert rather than send the designed version?
When the email has a conversational job, such as sales, onboarding or lifecycle mail where a reply is a good outcome. Plain text tends to win on reply rate there and to lose for merchandising, where the product grid is the message. Settle which job the email has before converting it.
What should I paste in besides the body copy?
Button labels and image alt text, the person it appears to come from, one goal, and a word ceiling. Include the alt text specifically. If the design was carrying a chart or a product grid, the rewrite will say so rather than inventing content it cannot see.
What does the rewrite return?
The plain-text version within your word limit with a single link, a table of every element removed and how the text covers it or why it was dropped, and a note on what must stay for legal or operational reasons. The removed-element table is where you catch a vanished postal address.
What is the mistake when stripping a template?
Dropping the unsubscribe link because it looks wrong in something written to read like a personal note. It is a legal requirement and a deliverability one, and hiding it raises complaints. The other slip is adding a second link, which makes the email read like a template again.