> ## Documentation Index
> Fetch the complete documentation index at: https://codebeans-customer-cart-manager.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Email templates

> Edit the subject and HTML of each notification email, use variables, add your logo, preview, and send a test.

There are two templates:

| Template | Found under | Sent to |
| - | - | - |
| **Ticket Confirmation** | **Customer Alerts** | The shopper, after they submit a support request. |
| **New Support Request** | **Merchant Alerts** | You, when a shopper submits a support request. |

Click a template to open the **Email Template Editor**.

## Edit the subject and content

* **Subject** — the email's subject line. Variables work here too, for example `New Support Request from {{shop_domain}} 🎫`.
* **Content** — the full HTML of the email, in a code editor with syntax highlighting.

The editor shows **Unsaved changes** until you click **Save** (top right). **Discard** throws your changes away.

## Variables

Click a variable in the **Liquid variables** panel to copy it, then paste it into the subject or content.

**\{\{submission\_details}}** `HTML block`

Everything the shopper typed into your support form — each field as a labelled box.

**\{\{shop\_domain}}** `text`

Your store's name from its myshopify address — for example `acme-outdoor` for `acme-outdoor.myshopify.com`.

**\{\{cart\_id}}** `text`

The shopper's [Cart ID](https://codebeans-customer-cart-manager.mintlify.site/carts/cart-ids.md), in the format you've chosen, e.g. `#1024` or `v_yna3sj0b2`. It's listed only for the **New Support Request** template, but it works in **Ticket Confirmation** too — handy for *"Your reference is {{cart_id}}"*.

> [!TIP]
>
> Include `{{cart_id}}` in the customer confirmation. Shoppers can then quote it when they reply or call, and your team can find the cart in seconds.

## Preview

Click **Preview** to see the email rendered with sample data (a name, email and message, the store `mystore.myshopify.com` and Cart ID `#1024`). Click **Close** to return to the editor.

## Email Branding (logo)

Add your logo to the top of the email:

1. Tick **Include branding (logo) in this email**.
2. Choose **Upload File** (click or drag & drop a PNG, JPG, GIF or WebP up to 2 MB) or **Paste URL** (the full web address of your logo).
3. The logo appears centred at the top of the email.

Each template has its own branding switch, so you can show the logo to customers but not in your internal alerts, or the other way round. Click **🗑 Remove logo** to remove it.

## Send a test email

Under **Test Email**, enter a **Recipient Email** and click **Send Test Email**. The test uses your template, branding and [SMTP settings](https://codebeans-customer-cart-manager.mintlify.site/notifications/smtp.md), filled with sample data. You'll see *Test email sent!* when it's on its way.

> [!WARNING]
>
> **Send Test Email saves your template first**, so the test shows exactly what you're editing. Don't use it to try out changes you might not want to keep — use **Preview** for that.

If the test fails with *"This address previously bounced or complained, so email to it is suppressed"*, that address is on the suppression list — try a different address.

## Reset to default

Click **Reset to default** in the **Content** panel and confirm with **Reset** to restore the original subject and content. This can't be undone.

## Writing tips

> [accordion] Keep the layout table-based
>
> The default templates use HTML tables and inline styles because that's what email apps display most reliably. If you rewrite the HTML, keep that approach rather than using modern CSS layouts.

> [accordion] Always send yourself a test
>
> Different email apps render HTML differently. Send a test to a Gmail and an Outlook address before going live.

> [accordion] Mention your support hours
>
> Set expectations in the confirmation, e.g. *"We reply within one business day, Monday to Friday."*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.