> For the complete documentation index, see [llms.txt](https://docs.momocode.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.momocode.de/en/shopware-6/confirmation-mails-for-forms/1.-description.md).

# 1. Description

Since the current Shopware 6 version does not yet have individual forms, but only the contact and newsletter form, this app is, in contrast to the Shopware 5 version, only limited to the contact form. For the newsletter form there is already a mail to the sender of the form by default. As soon as individual forms are possible in Shopware 6, the app will be extended and the restriction to the contact form will be removed.

If a visitor sends the contact form, only the shop owner receives an e-mail with the summary by default. With this app you get the possibility to send automatic confirmation mails to the sender, if he has filled out and sent the contact form.

You can create any e-mail templates via the Shopware Administration and link them to your contact form via the form configuration. In the e-mail templates, you can access the values filled in by the sender if you want to refer to them in the e-mail. In contrast to the Shopware 5 version of the app, in this version unfortunately the labels of the form fields in the e-mail are not available as variables, but only the filled in values. The e-mail to the sender is sent to the address that he/she entered in the e-mail field of the contact form.

If you do not select an e-mail template for your contact form, no e-mail will be sent to the sender.

The app is also compatible with sub- and language shops. If the appropriate translation is available for the email template, the sender will receive the confirmation email in the language that is configured for the shop in which he is currently located.


---

# 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.momocode.de/en/shopware-6/confirmation-mails-for-forms/1.-description.md?ask=<question>&goal=<endgoal>
```

`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.