> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/forms/email-notifications-and-templates.md).
# Email notifications and templates
Choose recipients, set where replies go, edit customer and admin templates, and send test emails.
Use this when a form should send confirmation emails, admin alerts, or both.
### How form emails work
Each form has two email flows, each with its own card in the form editor:
* **Customer Confirmation Email**: sent to the person who submitted the form.
* **Admin Notification Email**: sent to your team when a submission comes in.
You manage recipients, reply-to, and template content separately for each.
### Choose who receives emails
#### Customer confirmation email
Use **Customer's Email Comes From** to choose the form field where the customer enters their email. The confirmation is sent to the address they submit there.
Only Email-type fields appear in the picker, so add an Email field to the form first. Until the form has one, the card shows *No email fields yet*.
#### Admin notification email
* **Send Notifications To**: your team's fixed addresses. Add an email and press Enter, as many as you like. These addresses receive every submission.
* **Also Send to Email Fields From This Form (Optional)**: sends a copy to whatever address is captured in the selected field(s).
{% hint style="info" %}
If the form should send a customer email every time, make the email field required.
{% endhint %}
### Choose where replies go
Both email cards have a **Reply-To Address** setting: where replies land when someone hits Reply.
* **Default sender address**: replies go back to the address the email was sent from. This is the default.
* **A specific email address**: replies go to a fixed address you type in **Reply-To Email**, for example the store's own inbox when emails are being sent for a specific store.
* **An email field from this form**: replies go to the address the customer submitted, using the Email-type field you pick in **Reply-To Field**. Set this on the admin notification and your team can hit Reply and write straight back to the customer.
{% hint style="info" %}
Keep **Default sender address** for best deliverability. A custom reply-to address on another domain can land in spam.
{% endhint %}
### Edit the templates
{% stepper %}
{% step %}
#### Open Mail Templates
From the main **Forms** list, open **Mail Templates** for the form.
{% endstep %}
{% step %}
#### Choose the audience tab
Switch between **Customer** and **Admin**.
{% endstep %}
{% step %}
#### Update the email subject
Write a subject line that makes the purpose clear.
{% endstep %}
{% step %}
#### Edit the email body
Update the HTML template with the content and variables you need.
{% endstep %}
{% step %}
#### Send a test
Use **Send test** before you publish changes.
{% endstep %}
{% endstepper %}
### Common template data
The editor supports form and shop data.
Common values shown in the template editor include:
* form column headings
* submitted values from each field
* `shop.name`
* `shop.email`
* `shop.url`
Use consistent field names in the form builder so the template stays easy to maintain.
### Practical setup rules
* Keep the customer subject short and clear.
* Include the submitted values in admin emails.
* Test after renaming a field.
* Re-test after changing required fields.
### Troubleshooting
#### Customer emails are not sending
Check these first:
* the form includes an email field
* the correct field is selected under **Customer's Email Comes From**
* the submission included a valid address
#### Admin emails are not sending
Check these first:
* at least one fixed admin address is entered, or an email field is selected
* the form was submitted successfully
* the template changes were saved
#### A template shows blank values
Check whether the field name changed after the template was created.
### Important interaction with Klaviyo
If **Trigger Klaviyo event on form submission** is enabled, Roadmap's automatic customer confirmation email is disabled for that form.
Roadmap still sends the admin notification email.
Read next: [Trigger Klaviyo on submit](/forms/trigger-klaviyo-on-submit.md)
### Related guides
* [Building with forms](/forms/building-with-forms.md)
* [Trigger Klaviyo on submit](/forms/trigger-klaviyo-on-submit.md)
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.roadmap.so/forms/email-notifications-and-templates.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
