> For the complete documentation index, see [llms.txt](https://docs.rh-webdesign.com/cms-bundle/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rh-webdesign.com/cms-bundle/en/elemente/formulare/contact-form.md).

# Contact - Form

With the **Contact form** you build individual forms directly in the shopping experience – completely without an additional plugin. You create any fields you like, set their order, width and required state, and define which address the messages are sent to.

Typical use cases are contact, inquiry or callback forms. The transmission runs via the Shopware standard, so no additional cookie consent is needed.

<figure><img src="/files/lhYpKBORHM992pagsLme" alt=""><figcaption><p>Example in the storefront: a contact form with salutation, name, email, phone and message</p></figcaption></figure>

### General

On the **General** tab you build the form field by field. Expand an entry to edit it; using the icons on the right you can duplicate, move or delete fields. With **"Add form field"** you add another one.

<figure><img src="/files/KHM1R0qptHa1QzbkSG3Z" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="287">Function</th><th>Description</th></tr></thead><tbody><tr><td>Field - Type (1)</td><td>Type of the field: <strong>Salutation, Text, Number, Phone, Email, Textarea</strong> or <strong>Line break</strong>.</td></tr><tr><td>Field - Title (2)</td><td>Label of the field. It also serves as the technical name.</td></tr><tr><td>Field - Placeholder (3)</td><td>Hint text shown in the empty field.</td></tr><tr><td>Required? (4)</td><td>If enabled, the field must be filled in before the form can be submitted.</td></tr><tr><td>Field - Size (5)</td><td>Width of the field (25/50/75/100 %). Per row, 100 % must be reached to force a line break.</td></tr></tbody></table>

{% hint style="info" %}
The field type **Salutation** uses the globally maintained salutations. **Line break** creates a new row without outputting an input field.
{% endhint %}

### Form

Here you define the general settings of the form.

<figure><img src="/files/tgJILPUviczVHyj8b63z" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="287">Function</th><th>Description</th></tr></thead><tbody><tr><td>Form title (1)</td><td>Heading above the form. Leave the field empty to output no title.</td></tr><tr><td>Text after form submission (2)</td><td>Confirmation text shown after a successful submission instead of the Shopware standard message.</td></tr><tr><td>Show hint for required fields (3)</td><td>Shows the note below the form that fields marked with an asterisk are required.</td></tr></tbody></table>

The styling of the submit button is done via the shared building block:

{% content-ref url="/pages/IDCzxbLczQ60ESEzaHLK" %}
[Button](/cms-bundle/en/elemente/konfigurationsbausteine/button.md)
{% endcontent-ref %}

### Email

On the **Email** tab you determine how the incoming messages are delivered.

<figure><img src="/files/TtcfOPz6deajGzxbd0RC" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="287">Function</th><th>Description</th></tr></thead><tbody><tr><td>Email subject (1)</td><td>Subject with which the message arrives in the mailbox.</td></tr><tr><td>Receiver addresses (2)</td><td>One or more addresses the form is sent to. Without your own entry, the shop's default email address is used.</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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rh-webdesign.com/cms-bundle/en/elemente/formulare/contact-form.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.