# AI powered Email Templates in Sure Send
# AI-Powered Email Templates in Sure Send
Your complete guide to building clean, branded email templates in Sure Send using AI. Download the skill, customize it for your brand, install it once, and start generating paste-ready email HTML from plain-language descriptions.
---
## 1. The free skill
The Sure Send Email Template HTML Skill is a single file you install in your AI of choice. Once installed, you describe the email you want in plain language and the AI returns clean, Sure Send-compatible HTML you can paste directly into a template.
**Download:**
[suresend-email-html.zip 8390](https://outline-production-attachments.s3-accelerate.amazonaws.com/uploads/357c6223-4512-4dd2-81ef-8cf15c138bad/9b577b13-db36-4779-9d5f-ffae0162f6b4/suresend-email-html.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA4EOUDTOVUICLPZ4P%2F20261113%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20261113T000000Z&X-Amz-Expires=86400&X-Amz-Signature=f1c1c05dc54c6c9394d961009e6affb644b2b1f39326697b877ba18ac2d28a5f&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)
The skill is free. Use it, customize it, share it with your team. The base version uses Sure Send brand colors by default. Run the customization prompt in the next section to swap them for your own brand before you install.
> **Important:** Do not install the skill yet. Customize it first (Section 2), then install the final version (Section 3). That way you only install once and your brand is baked in from the start.
---
## 2. Customize the skill for your brand
The default skill uses Sure Send brand colors (Dark Blue and Golden Yellow). If you want your AI to generate emails in your own brand colors with your logo and your sign-off, run this customization prompt before installing.
**You will need:**
* The downloaded skill zip from Section 1
* Your two primary brand colors (hex codes or descriptions)
* Your logo URL (optional, but recommended)
* Your standard email sign-off
**How to use it:**
1. Open the downloaded zip file and find the file called `SKILL.md` inside.
2. Open a fresh chat in Claude (or your AI tool of choice).
3. Copy the entire contents of `SKILL.md` and paste it as your first message.
4. Copy the customization prompt below and paste it as your second message.
5. Answer the five questions when the AI asks them.
6. The AI will return a complete updated `SKILL.md` with your brand baked in.
### Paste this prompt
```
I want to customize this skill to match my brand instead of the Sure Send
defaults. Please ask me the following five questions one at a time. After
I answer all of them, return a complete updated version of the SKILL.md
file with my answers baked in as the new defaults. Update the brand
defaults table in the skill and update the example HTML in the skill to
use my colors instead of the Sure Send colors. Do not change any of the
technical rules.
Here are the five questions to ask me:
1. What are your two primary brand colors? Give me hex codes if you have
them (like #1A2B3C), or describe them (like "deep navy blue and warm
gold"). The first color will be used for primary buttons and section
banners. The second color will be used for accent buttons and
highlights.
2. What is your brand's text color for headings and body? If you have
specific hex codes, share them. If not, the safe defaults are dark
gray (#2A2A2A) for headings and near-black (#08090D) for body.
3. Do you have a hosted logo URL you want to include in your emails? If
yes, paste the URL. If you do not have a hosted logo URL yet, you can
upload your logo to Sure Send's Media Manager (Settings > Media
Manager), then copy the hosted URL it generates. That URL is permanent
and works everywhere. If you do not have a logo to use right now, just
say "skip" and the skill will leave logo placement out of the
templates. You can always add it later.
4. What is the general tone of your communications? Pick one or describe
your own: warm and conversational, professional and direct, polished
and luxury, casual and friendly, formal and corporate.
5. What is your standard email sign-off? Examples: "Talk soon," "Best
regards," "Looking forward to connecting." This will be used by
default in the closing of every email the skill generates.
Once I have answered all five, return the complete updated SKILL.md as a
single fenced code block. Make sure the YAML frontmatter stays intact,
the brand defaults table reflects my answers, the example emails use my
colors, and the technical rules are unchanged.
```
### After the AI returns your customized skill
1. Copy the [SKILL.md](http://SKILL.md) content from the code block.
2. Save it as a file named exactly `SKILL.md` on your computer.
3. Create a folder named something like `my-brand-email-skill`.
4. Move the [SKILL.md](http://SKILL.md) file inside that folder.
5. Compress the folder into a zip (right-click > Compress on Mac, Send to > Compressed folder on Windows).
6. Keep this zip file handy. You will use it in the next section.
> **Skipping customization?** If you want to use the default Sure Send brand colors and customize later, go straight to Section 3 and install the original zip from Section 1.
---
## 3. Install the skill
Anthropic Skills only work in [Claude.ai](http://Claude.ai). If you use ChatGPT or another tool, see the alternative installation note at the bottom of this section.
### Claude installation
1. In [Claude.ai](http://Claude.ai), look in the left sidebar near the top. You will see a **Customize** option.
2. Click **Customize**, then click **Skills**.
3. Click the **+** button next to the Skills heading, then choose **Create skill > Upload a skill**.
4. Select your zip file. If you customized the skill in Section 2, use the zip you created there. If you skipped customization, use the original zip from Section 1.
5. Done. The skill activates automatically whenever you describe an email template.
### Test it
Open a fresh Claude chat and send this:
```
Build me a welcome email for a new buyer lead. Thank them, mention I
will send personalized listings within 24 hours, and end with a CTA
button to save my number.
```
Claude should return three things: a subject line, the email HTML in a code block, and a short explanation. Copy the HTML and paste into a new Sure Send email template (switch the editor to HTML view first).
### Alternative: ChatGPT and other AI tools
ChatGPT and similar tools do not support installable skills, but the same content can be used as a system prompt or custom instruction. Open the zip file, copy the contents of `SKILL.md`, and paste it as your first message in a new chat. The AI will follow the same rules from that point on.
---
## 4. The MCP bonus prompt (Claude only)
If you have the Sure Send MCP connector set up in Claude, the AI can push templates directly into your Sure Send account, skipping the copy-paste step entirely.
### Prerequisites
* You use [Claude.ai](http://Claude.ai) (the MCP connector is Claude-specific)
* The skill is installed
* The Sure Send MCP connector is connected
### How to connect the Sure Send MCP
1. In [Claude.ai](http://Claude.ai), go to **Settings > Connectors**.
2. Click **Add Connector** or **Browse Connectors**.
3. Search for "Sure Send CRM".
4. Click Connect and authenticate with your Sure Send account.
### How to use the bonus
After the connector is set up, just describe your email and add a sentence at the end telling Claude to save it.
### Example
```
Build me a welcome email for a new buyer lead. Thank them, set
expectations for personalized listings within 24 hours, and end with
a CTA button to save my number.
After generating it, save it as a template in my Sure Send account
named "Welcome Email - New Buyer Lead" in the Welcome category. Keep
it personal, not shared with the team.
```
Claude will generate the HTML, then call the Sure Send MCP to save the template directly. You skip the copy-paste step entirely. The template appears in your `Settings > Email Templates` list, ready to use.
### Optional: standing instruction for auto-save
If you want every email going forward to be auto-saved as a template (instead of asking each time), paste this once in your Claude chat:
```
Going forward, whenever you generate an email template for me using the
Sure Send email skill, also save it directly to my Sure Send account
using the create_email_template MCP tool. Use the email's subject line
as the template name unless I specify otherwise. Default category to
"AI Generated" and keep templates personal (not shared) unless I say
to share them.
```
---
## 5. Best practices for email in Sure Send
These apply whether you are generating with AI or building by hand.
### The big three
1. **Email strips formatting.** True across every email tool, not just Sure Send. Pasting from Word or Google Docs loses colors, fonts, and spacing. Structure (paragraphs, headings, links) survives.
2. **No paste-as-plain-text shortcut exists.** Cmd+Shift+V does nothing in the Sure Send editor. The workaround: paste normally, select what you pasted, then press **Cmd+Shift+M** (Ctrl+Shift+M on Windows) to strip inline formatting.
3. **Preview is an approximation.** The in-app preview is close to what gets delivered but not identical. Always send a test to yourself before any important campaign.
### Top 10 best practices
1. Use the editor's built-in tools, do not paste designed content from Word or Google Docs.
2. Always preview AND test-send before campaigning.
3. Use the Button tool for CTAs, not styled links.
4. Set custom button colors via the style panel, not by pasting CSS.
5. Put merge fields in text content or link hrefs, never inside `style=""` or `![]()
`.
6. Use the editor's column tool for multi-column layouts (do not paste tables).
7. Skip width and height attributes on images, use inline style instead.
8. Stick to Arial for email body text and headings (custom web fonts get stripped).
9. Use Cmd+Shift+M after a messy paste to clean up inline formatting.
10. Proofread merge fields carefully (misspellings silently become empty strings).
### Keep it simple
* One-off emails (responding to a contact): just type. Skip the templates and AI.
* Templates (reusable structures for automations or one-off sends): use the AI skill.
* Newsletters: use the AI skill, but build the sign-off block INTO the template body. Newsletters do not auto-append your email signature from Settings.
---
## 6. Sample prompts to try
Copy any of these into Claude (with the skill installed) and tune them to your business.
### Welcome email for a new buyer lead
```
Build me a welcome email for a new buyer lead who just submitted an
inquiry on my website. Thank them, set expectations that I will send
personalized listings within 24 hours, mention they can text or call
anytime, and end with a CTA button to save my number.
Three short paragraphs, warm tone.
```
### New seller lead intro
```
Build me an intro email for a new seller lead. Acknowledge that
selling is a big decision, position me as their guide who handles
strategy and logistics, and end with a CTA to schedule a 15-minute
home valuation call.
Keep it confident but not pushy. Three paragraphs.
```
### Monthly market update newsletter
```
Build me a monthly market update newsletter template.
Header: my logo on a Dark Blue background. Logo URL: [your logo URL]
Two short sections:
1. "Local market snapshot" - one paragraph that local markets vary
block by block, invite them to reply with the area they are watching.
2. "Featured listing this month" - one paragraph teasing a property
worth a closer look.
End with a CTA button "See all my listings" and a sign-off block with
my name, team name, and clickable phone.
```
### Open house invitation
```
Build me an open house invitation email. Include:
- The address of the property
- The date and time of the open house
- One short paragraph describing the property's best features
- A CTA button "Get directions" linking to Google Maps
- A note that they can text or call me with questions
Keep it short and punchy.
```
### Just listed announcement
```
Build me a "just listed" announcement email. Include:
- Property photo at the top
- Address, price, beds/baths
- One paragraph describing what makes this property special
- A CTA button to schedule a private showing
- My signature block
Visual but not over-designed.
```
### Closing day celebration
```
Build me a closing day congratulations email for a client whose
transaction just closed. Warm tone, celebratory but professional.
Thank them for trusting me, offer ongoing support for anything they
need post-close, and invite them to refer friends and family.
End with my sign-off, no CTA button.
```
---
## 7. Common merge fields
Use these inside your templates. They get replaced with real values at send time.
### Contact fields (for the recipient)
| Merge field | What it pulls |
|-------------|---------------|
| `{{person.first_name}}` | First name |
| `{{person.last_name}}` | Last name |
| `{{person.full_name}}` | Full name |
| `{{person.email}}` | Email address |
### Sender fields (for you, the agent)
| Merge field | What it pulls |
|-------------|---------------|
| `{{sender.first_name}}` | Your first name |
| `{{sender.full_name}}` | Your full name |
| `{{sender.email}}` | Your email address |
| `{{sender.phone}}` | Your phone number |
### Team fields
| Merge field | What it pulls |
|-------------|---------------|
| `{{team.name}}` | Your team name |
### Custom fields
| Merge field | What it pulls |
|-------------|---------------|
| `{{custom.field_name}}` | Any custom field on your account (use the field's exact lowercase, underscored name) |
### Where to use merge fields
**Safe:** text content, link hrefs, button text, subject line. **Unsafe:** inside `style=""` attributes, inside `![]()
`, inside CSS class names.
**Important:** unknown or misspelled merge fields silently become empty strings. Proofread.
---
## 8. Troubleshooting
### My email looks different in preview than the editor
The editor preview uses a slightly different rendering path than the actual delivered email. Some elements (especially buttons) can look different. Always send a test to yourself before any important campaign.
### My merge fields show as `{{person.first_name}}` in the email I received
You sent the template as a plain test send rather than to a real contact. Test merge fields by sending the template to yourself as if you were a real contact (or testing with a real contact record). Templates only resolve merge fields when sent through the normal send pipeline.
### My pasted formatting looks ugly after pasting from Word or Google Docs
This is expected. Press **Cmd+Shift+M** (Ctrl+Shift+M on Windows) after pasting to strip inline formatting. Then re-format with the toolbar.
### My button color is different in the preview vs the delivered email
Known limitation. If you do not explicitly set a button color, the preview can show black while the delivered email shows the default Sure Send Dark Blue. To force consistency, set the button color explicitly using the style panel (or generate via the AI skill, which always sets the color explicitly).
### My custom font does not show up in delivered emails
Email clients strip custom web fonts. Stick to Arial (the email-safe default) or one of the system fonts (Helvetica, Georgia, Verdana, Times New Roman). The AI skill uses Arial by default.
### My logo image is not loading
Make sure the logo URL is absolute (starts with `https://`), publicly accessible (not behind a login), and reliable (not a temporary or expiring link). The most reliable path is to upload your logo to Sure Send's Media Manager (Settings > Media Manager) and use the hosted URL it generates.
### The skill is not activating in my Claude account
Make sure you uploaded the .zip file (not the [SKILL.md](http://SKILL.md) file directly). Anthropic Skills require the zip format. If you customized the skill, make sure your [SKILL.md](http://SKILL.md) is inside a folder, and the folder is what you zipped.
---
## 9. The skill file (full reference)
Below is the complete contents of the `SKILL.md` file included in the download. This is provided for reference so you can see exactly what the skill does, review the technical rules, and copy it directly if you prefer not to download the zip.
### Full SKILL.md contents
Copy the code block below if you prefer not to download the zip. In the Outline sidebar, click the arrow next to this heading to collapse this section.
```none
---
name: suresend-email-html
description: Use this skill when the user is building an EMAIL TEMPLATE for Sure Send CRM (not a one-off email). Fire on requests for templates, newsletters, automation emails, welcome emails, buyer/seller lead emails, market updates, open house invitations, just listed announcements, or any reusable email content. Also fire on explicit mentions of Sure Send, "my CRM," "my templates," merge fields like `{{person.first_name}}`, or requests for email HTML output. Also fire when iterating on a previously generated template. DO NOT fire for one-off email replies to specific people, personal emails, cold outreach, internal communications, or plain prose email requests. If ambiguous, ask once whether the user wants a reusable template or a one-off email, and only fire if they confirm template. Returns subject line, Sure Send-compatible HTML in a code block, and a brief explanation.
---
# Sure Send Email Template HTML Generator
Generates Sure Send-compatible email template HTML from plain-language descriptions. Output is paste-ready for the Sure Send template editor at `/settings/email_templates`. The skill enforces the technical rules that the Sure Send editor and its sanitization pipeline require, so the HTML you generate will render reliably across email clients and survive Sure Send's save and send-time transforms.
## What this skill does
1. Reads the user's plain-language description of an email they want to build.
2. Asks up to two clarifying questions if essential information is missing (subject line, CTA target, sender details).
3. Generates Sure Send-compatible HTML using the brand colors and conventions defined below.
4. Returns the email in a three-part output format: subject line, HTML in a fenced code block, plain-language explanation of choices.
5. Handles follow-up adjustment requests by regenerating the full email (not snippets).
## Brand defaults
Use these defaults unless the user explicitly requests something different.
| Element | Default value |
|---|---|
| Body background | White #FFFFFF |
| Body text color | Soft Black #08090D |
| Body font | Arial, sans-serif |
| Heading color | Dark Blue #055980 |
| Primary button background | Dark Blue #055980 |
| Primary button text | White #FFFFFF |
| Accent / secondary button background | Golden Yellow #EEBD6B |
| Accent button text | Soft Black #08090D |
| Section banner background | Dark Blue #055980 |
| Section banner text | White #FFFFFF |
| Light accent background (callouts) | Light Blue #8CB1C4 |
| Standard body line-height | 1.6 |
| Standard body font-size | 16px |
| Standard heading font-size (H1) | 22px |
| Standard heading font-size (H2) | 18px |
| Max width | 600px |
Do not use custom web fonts like Fjalla One, Google Fonts via @import, or @font-face declarations. They get stripped in email and break in Outlook. Stick to Arial for both body text and headings.
## Sure Send brand logos (pre-loaded URLs)
These Sure Send brand logos are pre-loaded and ready to use. When the user asks for "the Sure Send logo" or refers to one of these variants by name, use the corresponding URL automatically. The user does not need to provide the URL.
| Variant | When to use it |
|---|---|
| Horizontal White | On Dark Blue backgrounds, banner headers, primary newsletter headers |
| Horizontal Blue | On white or light backgrounds |
| Horizontal Blue + Yellow | Full color logo on white backgrounds, premium feel |
| Symbol White | Compact spaces (footer corners, small headers) on Dark Blue backgrounds |
| Symbol Blue | Compact spaces on white/light backgrounds |
| Symbol Yellow | Accent placement, on Dark Blue backgrounds for contrast |
Default behavior: if the user asks for "a Sure Send logo" or "the Sure Send logo" without specifying a variant, use Horizontal White on a Dark Blue banner background. This is the most common pattern for newsletter and template headers.
Recommended sizing for headers: style="max-width: 240px; height: auto; display: block; margin: 0 auto;" for horizontal variants, max-width: 80px for symbol variants.
## Output format (always use this structure)
Every generated email returns three parts in this order:
### 1. Subject line
Subject: [the subject line]
Rules:
- Under 60 characters
- No all caps
- No excessive punctuation
- Avoid known spam triggers (free, guarantee, act now, limited time)
### 2. HTML body
In a fenced code block marked html, containing the email HTML.
The HTML must follow every rule in the technical spec below.
### 3. Plain-language explanation
Two to four short sentences telling the user what was built and any choices that were made. Specifically mention:
- Any non-default colors used
- Any sections added that the user did not explicitly request
- Any suggested CTA when the user did not specify one
- Any structural choice (single-column vs two-column, banner vs no banner, etc.)
## Workflow
### Step 1: Parse the request
Read the user's input. Identify:
- Email purpose (welcome, follow-up, market update, listing alert, newsletter, transactional)
- Audience (buyer lead, seller lead, past client, prospect)
- Required content elements (subject, body topics, CTA, signature style)
- Tone (warm, professional, celebratory, informative)
### Step 2: Ask clarifying questions if needed
If essential information is missing, ask up to two clarifying questions in a single message and wait for the answer. Common gaps:
- Subject line not specified
- CTA target URL or action not specified
- Sender or team name when context implies they should appear
If the request has enough to proceed, skip this step and generate.
### Step 3: Generate the HTML
Apply the technical spec below. Use brand defaults. Use the standard email shell.
### Step 4: Return the three-part output
Subject line, HTML code block, explanation.
### Step 5: Handle adjustments
When the user asks for changes after delivery, regenerate the complete email in the same three-part format. Do not respond with just a snippet of the change.
Common adjustment requests:
- Color changes (swap to brand-customized colors)
- Length changes (shorten or expand)
- CTA changes (change text or destination)
- Section changes (add or remove banner, signature, P.S. line)
## Technical spec
### Allowed HTML tags
Block: p, h1, h2, h3, h4, h5, h6, blockquote, pre, hr, ul, ol, li, dl, dt, dd, div
Tables: table, thead, tbody, tfoot, tr, th, td
Inline: a, b, strong, i, em, u, br, span, sub, sup, small, abbr, cite, code
Images: img
Never emit: figure, figcaption, iframe, mark, var, ins, kbd, samp, address, font, script, style, link, meta, html, head, body, title, form, input, button, embed, object, video, audio
### Allowed attributes
- Universal: class, id, style, title
- Links (a): href, target, rel
- Images (img): src, alt
- Tables: only style and class in attribute form
Do not emit width or height HTML attributes on img tags. Use inline style="max-width:100%; height:auto;" instead.
### CSS properties safe in style=""
color, background-color, background (single color value), font-family, font-size, font-weight, font-style, line-height, text-align, text-decoration, margin, margin-top, margin-bottom, margin-left, margin-right, padding, padding-top, padding-bottom, padding-left, padding-right, border, border-top, border-bottom, border-left, border-right, border-radius, width, height, max-width, min-width, display (block, inline-block, none only), vertical-align, list-style-type
### CSS properties to avoid
float, position, transform, transition, animation, flex-* (except flex-basis inside layout columns), grid-*, @import, @font-face, :hover, :focus, :active states
### Standard email shell (use for every email)
Wrap every email in a div with: font-family: Arial, sans-serif; color: #08090D; line-height: 1.6; max-width: 600px; margin: 0 auto; background: #FFFFFF;
For emails with a header banner, add a nested div with: background: #055980; padding: 28px 24px; text-align: center; containing the heading in white.
### Button syntax (critical)
Every button MUST use class="email-button" on the anchor tag. The Sure Send sanitizer keys off this class and converts the anchor into an email-safe table at send time. Buttons not in this shape do not get converted properly.
Primary CTA: background-color: #055980; color: #FFFFFF; padding: 14px 28px; border-radius: 4px; font-size: 16px; font-weight: 600; text-decoration: none; display: inline-block;
Accent CTA: background-color: #EEBD6B; color: #08090D; same padding and sizing.
Rules:
- The anchor must have class="email-button"
- The button must be inside a block-level element (p or div)
- Always specify the background color explicitly
- Center by setting text-align: center on the parent p
- Do not put a button inside a span or another a
### Link syntax (non-button links)
Use color: #055980; text-decoration: underline; on anchors. Always use absolute URLs (https://, mailto:, tel:). Do not add target="_blank" (the sanitizer adds it automatically).
### Image syntax
src must be an absolute https URL. alt is required. No width or height HTML attributes. Use style="max-width: 100%; height: auto; display: block; margin: 0 auto;"
### Layout / multi-column
Single-column layouts render best across every email client. Only use multi-column when the content genuinely calls for it. When used, use class="rx-layout-grid" with data-rx-type="layout" and flex children with data-rx-type="column".
## Merge fields
Sure Send merge fields use the format {{namespace.field}}.
Common ones:
- {{person.first_name}} - contact's first name
- {{person.last_name}} - contact's last name
- {{person.full_name}} - contact's full name
- {{sender.first_name}} - sending user's first name
- {{sender.full_name}} - sending user's full name
- {{sender.email}} - sending user's email
- {{sender.phone}} - sending user's phone
- {{team.name}} - team name
- {{custom.field_name}} - any custom field
Safe positions: text content, link href attributes, button anchor text, subject line.
Unsafe positions: inside img src, inside style attributes, inside CSS class names.
Unknown or misspelled merge fields silently become empty strings.
## Content guidelines
- Keep it short. Three short paragraphs and a clear CTA beat five long ones.
- One CTA per email unless the user explicitly asks for more.
- Use the contact's first name. Default to {{person.first_name}} in greetings.
- Match tone to context.
- Avoid spam triggers (act now, limited time, 100% free, click here now).
- End with a clear sign-off using {{sender.full_name}}, team name, optional phone or email link.
## Hard rules (consolidated)
1. Sure Send is two words. Never SureSend.
2. No em dashes anywhere. Use period, comma, or rewrite.
3. Button anchor must have class="email-button".
4. Button must be inside a block-level parent (p or div).
5. No width or height HTML attributes on images. Use inline style instead.
6. No custom web fonts. Arial only.
7. No merge fields inside style="", src="", or style blocks.
8. Default to single-column layouts.
9. One CTA per email unless the user explicitly asks for more.
10. Always wrap in the standard shell with max-width: 600px.
11. Always return the three-part output format: subject, HTML, explanation.
12. For adjustments, regenerate the complete email, not snippets.
```
---
**Sure Send**