> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/commerce-and-integrations/mimeeq-basket/basket-emails-and-pdfs.md).

# Basket Emails & PDFs

Make every Basket email and PDF match your brand and language. Learn how submission emails work and how to use variables and static labels.

Mimeeq sends an email with a PDF copy every time a Basket is submitted. You can personalise and translate the content of these emails and PDFs in **Settings** → **Basket**.

***

## How basket emails work

Mimeeq handles all email communication when a Basket is submitted.

{% hint style="warning" %}
Email confirmations are sent only when this feature is enabled in your settings. See [Configure basket settings](/commerce-and-integrations/mimeeq-basket/basket-settings.md).
{% endhint %}

* The submitter and your team receive an initial email containing the basket items, form details and a PDF copy.
* All emails include a special reply-to address for seamless communication.
* When customers reply to these emails, their responses are automatically forwarded to all team members in your send-to email list.

```mermaid
flowchart LR
    A[Basket submitted] --> B[Email and PDF sent to customer and your team]
    B --> C[Customer replies to the email]
    C --> D[Reply forwarded to your send-to email list]
```

{% hint style="warning" %}
Mimeeq does not store any email conversations; it only forwards messages.
{% endhint %}

***

## Dynamic variables and static text

Your emails and PDFs can use two types of content:

<table><thead><tr><th width="40">#</th><th width="116.21875">Type</th><th width="318.71484375">How it works</th><th>Use it for</th></tr></thead><tbody><tr><td>1</td><td><strong>Dynamic variables</strong> (placeholders in double curly brackets)</td><td>Automatically pull in information from each submission. For example, the <code>firstName</code> variable shows the customer's actual name. Variables such as <code>referenceCode</code>, <code>total</code> and <code>companyName</code> insert submission-specific details.</td><td>Personalising headers, subject lines and message content.</td></tr><tr><td>2</td><td><strong>Static text</strong></td><td>Fixed text that stays the same for every submission. It can be translated but does not change based on submission data.</td><td>Standard labels and messages.</td></tr></tbody></table>

For example, you could write 'Dear {{firstName}},' and if John submits a basket, he receives an email saying 'Dear John,'.

![Email and PDF settings data grid listing the variable fields](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FxbskDlH2TGf9zY2qZc5E%2Fbasket-image-7_pyp1cj.png?alt=media)

***

## Use a variable in a translation

1. Click the row in the data grid that contains the variable field, such as **Introduction text for submitter email**.
2. In the modal that opens, enter a translation for each language. The available variables are listed on the right.
3. Click the copy icon next to a variable, then paste it into the translation field where you need it.

![Translation modal with language fields and the list of available variables on the right](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2F5bwkrpNPL2P1ZANRIULj%2Fbasket-image-8_42dlfm.png?alt=media)

***

## Available variables

<table><thead><tr><th width="75.05078125">#</th><th width="217.5859375">Field</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td><code>firstname</code></td><td>The first name of the contact person</td></tr><tr><td>2</td><td><code>lastName</code></td><td>The last name of the contact person</td></tr><tr><td>3</td><td><code>fullName</code></td><td>The full name of the contact person</td></tr><tr><td>4</td><td><code>email</code></td><td>The email of the contact person</td></tr><tr><td>5</td><td><code>phoneNumber</code></td><td>The phone number of the contact person</td></tr><tr><td>6</td><td><code>companyName</code></td><td>The company name of the contact person</td></tr><tr><td>7</td><td><code>address</code></td><td>The address of the contact person</td></tr><tr><td>8</td><td><code>notes</code></td><td>Additional notes provided by the contact person</td></tr><tr><td>9</td><td><code>customerDisplayName</code></td><td>The display name of the customer</td></tr><tr><td>10</td><td><code>referenceCode</code></td><td>The reference code for the Basket</td></tr><tr><td>11</td><td><code>submissionDisplayName</code></td><td>The display name for the submission</td></tr><tr><td>12</td><td><code>total</code></td><td>The total price of the Basket</td></tr><tr><td>13</td><td><code>websiteUrl</code></td><td>The URL of the company's website</td></tr><tr><td>14</td><td><code>contactUrl</code></td><td>The contact URL for customer service</td></tr><tr><td>15</td><td><code>logo</code></td><td>The URL of the company logo</td></tr></tbody></table>

![Example email showing where variable content appears](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FjP65fPUHkxBb6uHblGLz%2Fbasket-image-6-new_1x3xqaq.png?alt=media)

***

## Static text labels

Non-variable fields keep text consistent in every email and PDF. Use the data grid to translate or edit these labels. Variables are not supported in these fields.

![Data grid of non-variable static text label fields](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FPMba3NgzEYMZFO0x4iHj%2Fbasket-image-9_6ej696.png?alt=media)

Click a row in the data grid to add a translation to the field. Once added, the translation appears in emails and PDFs. The screenshot below shows where each static text label is used in the email.

{% hint style="warning" %}
Manage translations for custom fields in the [Custom Fields](/platform/custom-fields/custom-fields.md) settings.
{% endhint %}

![Example email with each static text label highlighted where it is used](https://621103948-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsqWfi8ifBhTdkvf1vOlY%2Fuploads%2FtWfWig4u4FpmxnOYisCv%2Fbasket-image-10-new_l0eeo4.png?alt=media)

{% hint style="info" %}
To translate the Basket interface on your website, such as buttons and panel headings, see [Embed the basket on your website](/commerce-and-integrations/mimeeq-basket/basket-website-embed.md).
{% endhint %}

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Configure basket settings</strong></td><td>Set primary details, choose form fields and add recipient emails.</td><td><a href="/commerce-and-integrations/mimeeq-basket/basket-settings.md">Basket Settings</a></td></tr><tr><td><strong>Custom Fields</strong></td><td>Create custom fields to collect extra information on the Basket form.</td><td><a href="/platform/custom-fields/custom-fields.md">Custom Fields Overview</a></td></tr><tr><td><strong>Embed the basket on your website</strong></td><td>Add the Basket to your site and translate its interface.</td><td><a href="/commerce-and-integrations/mimeeq-basket/basket-website-embed.md">Basket Website Embed</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.mimeeq.com/commerce-and-integrations/mimeeq-basket/basket-emails-and-pdfs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.