Claude Code Prompts for Email: 20 Messages to Copy
20 Claude Code prompts for email you can copy: set up your SaaS emails, brief each one, fix the design and test it all, written in plain English.
Quick answer
The best Claude Code prompts for email read like a brief to a person: say which email you want, who gets it and when, what it should say, and ask to see a preview first. Below are 20 copy-ready messages covering setup, each common SaaS email, design and wording, and testing, each with what to expect.
Last checked: October 2026
On this page
These are Claude Code prompts for email you can copy and send as they are. Each one reads like a brief to a designer or developer, with what Claude Code does next shown underneath.
They cover transactional emails: the ones your SaaS, site or tool sends because someone did something, like signing up, forgetting a password or paying you.
The messages assume SimpleSends is connected; the four steps to do that come first. For the full picture, read how to send emails from Claude Code.
Before you start: connect SimpleSends to Claude Code
You connect once, then everything else happens in the chat. A connector lets Claude Code talk to another service while you build, using a standard called MCP (Model Context Protocol).
- Sign up on the SimpleSends website and follow the steps there to set up the email address you'll send from. To send from your own domain, this includes adding a few DNS records where your domain is registered. DNS records are short settings that tell the internet your emails really come from you.
- In Claude Code, open Customize, then Connectors, choose Add, then Add custom connector. Fill in these two fields:
| Field | What to enter |
|---|---|
| Name | SimpleSends |
| MCP server URL | https://mcp.simplesends.com/mcp |
- When Claude prompts you to connect, log in to SimpleSends.
- Back in the Claude Code chat, tell Claude Code: "I've connected SimpleSends for all transactional email." It takes it from there, including adding what your project needs to send email.
Once live, your SaaS sends real emails through SimpleSends on its own, using a secret key (an API key, a password one service uses with another) and a little sending code. Claude Code doesn't need to be open for that.
How to write Claude Code prompts for email
A good brief answers four questions in normal sentences. No special wording needed.
| Part of the brief | Example |
|---|---|
| What you want | A welcome email |
| Who gets it, and when | Every new user, right after they sign up |
| What good looks like | Short and friendly, with one button to their dashboard |
| How you want to review it | Show me a preview before you build it |
It also helps to mention your users and say what to leave out. Reply as you would to a person: "shorter, and move the button up" is enough. For more, see how to get Claude Code to write your SaaS emails.
Setup messages
Send these first. They give Claude Code the context for every email after.
1. Check what's in place
Check that SimpleSends is connected, then tell me in plain English what's already set up for email in this project and what's still missing.
What happens: Claude Code confirms the connection and lists what's done and what's left.
2. Plan which emails you need
Look at how my SaaS works and list every transactional email it should send. For each one, tell me when it goes out and who gets it. Don't build anything yet.
What happens: You get a list, usually including a welcome email, password reset and receipts, plus emails specific to your product. Edit it as you like. More in which emails your SaaS needs.
3. Set your sender details
All my emails should come from "Yourcompany" at hello@yourcompany.com. When people reply, the replies should go to support@yourcompany.com.
What happens: Every email uses these details. Use an address on the domain you set up on the SimpleSends website.
4. Set up everything in one go
Set up all my transactional emails from the list we agreed. Work through them one at a time, show me each one before you build it, and send me a test of each when it's done.
What happens: Claude Code drafts, previews and builds each email in turn, and you approve or ask for changes as you go. For what each should include, see these 12 transactional emails every SaaS needs.
Messages for each common email
Use these to set up or redo one email at a time, with your own details.
5. Welcome email
When someone signs up, send them a short, friendly welcome email. Thank them, tell them the one thing to do first, and add a button to their dashboard. Show me a preview first.
What happens: You get a draft with a subject line. Once you approve it, Claude Code connects it to your sign-up.
6. Confirm their email address
After someone signs up, send an email asking them to confirm their address with one button. If they haven't confirmed after a day, send one reminder.
What happens: Claude Code builds the email, the confirm step and the reminder.
7. Password reset
Add a "forgot password" email. The reset link should only work once and expire after a short time. On the site, show the same message whether or not that email address has an account.
What happens: Claude Code builds the reset flow and the email. These rules come from OWASP's widely used password reset guidance.
8. Receipt after a payment
When a payment goes through in Stripe, send the customer a receipt with what they bought, the amount, the date and a link to their billing page.
What happens: A receipt goes out after each successful payment. Stripe is a payment service; name yours if it's different.
9. Payment failed
If a renewal payment fails, send a calm email telling the customer, with a button to update their card. Don't make it sound like a warning.
What happens: You approve a draft, then it goes out on every failed payment. Ask for a follow-up a few days later if you want one.
10. Trial ending
Three days before a free trial ends, email a reminder with the end date and a button to pick a plan.
What happens: Claude Code sets up a timed email based on each user's trial end date.
11. Team invite
When someone invites a teammate, email the teammate saying who invited them, with a button to accept. Invites expire after seven days.
What happens: Claude Code builds the email and the accept step, with the expiry.
12. Tell me when someone signs up
Every time someone new signs up, send me an email at hello@yourcompany.com with their name, email address and which plan they chose.
What happens: You get a short note per sign-up. When that's too many, ask for a daily summary instead.
Design and writing messages
These shape how every email looks and sounds.
13. Match your brand
Design all my emails to match my site: same colors, logo at the top, lots of white space. Show me the welcome email in the new design first.
What happens: Claude Code designs one email for you to approve, then uses that design for the rest. More in this guide to designing your SaaS emails with Claude Code.
14. Set your tone of voice
Our tone is warm and plain-spoken, like a helpful colleague. Short sentences, no jargon. Rewrite all my emails in that voice and show me before and after.
What happens: You see old and new wording side by side and approve the voice once.
15. Tighten one email
The welcome email feels too long. Cut it to about half, keep the button, and give me three subject line options to choose from.
What happens: You get a shorter version and three subject lines to choose from.
16. Make them work everywhere
Make sure every email looks right on phones and in dark mode, and that each one has a plain-text version for inboxes that don't show designs.
What happens: Claude Code checks and fixes each email. Dark mode shows emails on a dark background; a plain-text version is a text-only copy.
Testing and fixing messages
Use these before launch and whenever something looks off.
17. Test every email
Send me a test of every email to hello@yourcompany.com, filled in with realistic example details, and list which ones you sent.
What happens: Test emails arrive in your inbox, so you see what your users will. Our guide to testing your emails before users see them has a full checklist.
18. Try awkward details
Test my emails with awkward details, like a very long name or no first name. Tell me if anything breaks or looks odd, and fix it.
What happens: Claude Code fixes gaps, for example falling back to "Hi there" when there's no name.
19. Find out why an email didn't arrive
A user at jo@yourcompany.com says they never got their password reset email this morning. Check what happened and explain it to me.
What happens: Claude Code reads the send logs and delivery status in SimpleSends and tells you whether it went out, and if not, why. More in how to check whether your emails actually sent.
20. Change an email later
Change the trial ending email to go out five days before the trial ends instead of three, and update the wording to match. Show me before and after.
What happens: You see the change before it goes live. Any email can be changed this way.
Frequently asked questions
Do I have to use these messages in order?
No. The setup messages work best first, because they give Claude Code your list of emails and your sender details. After that, use any message whenever you need it. You can also send message 4 alone and come back to the others to adjust single emails later.
Can I use custom connectors on the free Claude plan?
Yes. Anthropic’s help center says custom connectors are available on Free, Pro, Max, Team and Enterprise plans. Free plans are limited to one custom connector, so if you already use one, you’d need to remove it before adding SimpleSends.
I’m on a Team or Enterprise plan. Can I add SimpleSends myself?
On Team and Enterprise plans, an Owner adds custom connectors for the organization from Organization settings. Once they’ve added SimpleSends, you open Customize, then Connectors, find it in the list and choose Connect to log in with your own SimpleSends account.
Why can’t Claude Code see SimpleSends in a new chat?
Connectors can be switched on and off for each conversation. In the chat, choose the + button at the bottom left, open Connectors, and check that SimpleSends is turned on. If it still doesn’t appear, remove the connector and add it again.
Do my emails go out from the chat once my SaaS is live?
No. The chat is where you build, preview and send tests. Once your SaaS is live, real emails go out from your project through SimpleSends on their own, even when Claude Code isn’t open. A password reset at 3am still arrives.
Sources (2)
- Get started with custom connectors using remote MCP(checked October 4, 2026)
- Forgot Password Cheat Sheet (OWASP Cheat Sheet Series)(checked October 4, 2026)
Keep reading
More on Claude Code + email →Claude Code HTML Email That Looks Good in Every Inbox
A Claude Code HTML email brief that covers old Outlook, phone screens, dark mode, blocked images and a plain-text version gets you emails that hold up anywhere.
6 min read
Check If Email Was Sent: How to Find Out What Happened
A user says they never got your email? Here’s how to check if an email was sent, read your send logs, find the cause and fix it, with Claude Code’s help.
6 min read
Claude Code Email Testing: Check Emails Before Users Do
Claude Code email testing in plain English: send test emails to yourself, check links, names and layout on mobile, then run a pre-launch email checklist.
6 min read