---
title: Email scenarios for forms
related:
  - https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/automation-customization.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

## Email scenarios for forms

A common scenario involves setting up a more complex email follow-up sequence after a [form submission](https://docs.kentico.com/modules/contact-management/properties-and-after-submission-behavior.md#actions-after-form-submission), beyond a simple email response. For simple email scenarios, the standard form autoresponder can be used without designing a process in the Automation Builder.

With automation, you can send multiple emails as a follow-up to form submission, but the entire sequence must be predefined from the beginning, with each email sent by a separate step. You can also include wait steps or conditions between the email steps.

To comply with personal data protection regulations, you may need to implement conditions that check for some form of opt-in from the contact, such as a [consent](https://docs.kentico.com/documentation/developers-and-admins/data-protection/consent-management.md) or whether the contact is subscribed to a [recipient list](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/send-regular-emails-to-subscribers.md#create-recipient-lists).

- **Consent** – Can be obtained directly through the submitted form by including a _Consent agreement_ field, or more broadly (e.g., through a tracking/cookie consent banner implemented across a website).
- **Recipient list** – The first email set by the process must use the _Form autoresponder_ [purpose](https://docs.kentico.com/documentation/business-users/digital-marketing/emails.md#email-purposes) and include a double opt-in link for the recipient list. A wait step should follow to give recipients time to complete the double opt-in process, after which conditions related to the recipient list can be used to control how the process sends further emails.

> **Note:** **Regular newsletter scenarios**
>
> Automation is **not intended** for long-term newsletter distribution or regular email sending to a recipient list. In these cases, it's difficult to predict how many email issues will be sent in the future. Currently, if an automation process is triggered by a subscription form submission for a recipient list, it can only contain a fixed number of email steps. Once a subscribed contact reaches the end of the process, there is no way to extend the process or add additional email issues.
>
> You can [send regular emails to subscribers](https://docs.kentico.com/documentation/business-users/digital-marketing/emails/send-regular-emails-to-subscribers.md) manually.

### Multilingual emails

If you wish to send emails in multiple [languages](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md) from an automation process, you need to prepare a separate form for each of the language variants. Each form requires its own automation process, which then sends emails from the corresponding language-specific [email channel](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-channel-management.md).