> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/get-notified-about-new-intake-form-submissions.md).

# Get notified about new intake form submissions

Every intake form submission lands as a task in your Service Requests folder, but nobody has to sit and watch that folder. The Notifications tab on the Intake Form settings page turns on an email, an in-app notification, or both, so a new lead reaches your team the moment it arrives.

Open Settings -> Intake Form and switch to the **Notifications** tab. The Form tab still holds the drag-and-drop editor, and the two tabs save separately, so changing who gets notified never publishes a new version of your form.

## Email a copy of each submission

Turn on **Email a copy of each submission** and add the people who should receive it. Start typing to pick a teammate, or type any address and press Enter to add one that is not an Essential user - a shared inbox like office@ or dispatch@ works well here. Remove a recipient with the x on their chip. You can add up to 25 addresses, and Save stays disabled until the switch has at least one recipient to deliver to.

Each email arrives with the submitted answers laid out field by field, plus a link straight to the request, so whoever reads it can act without hunting for the record.

These emails send from your business notification email, so make sure one is set under Settings -> Business Profile - the page warns you if it is missing, and emails are skipped until it is configured.

Email copies are also rate-limited (roughly 20 per hour) to keep a scripted flood of fake submissions from burying your inbox. Past that, submissions still land in the Service Requests folder and still raise in-app notifications - only the extra email copies are skipped for the rest of the hour.

## Create a notification in Essential

Turn on **Create a notification in Essential** and the submission also rings the notification bell in the top bar. Choose who gets it:

* **All back office users** notifies everyone on your team with web access. This is resolved fresh on every submission, so someone you hire next month is covered without you coming back to this page.
* **Only specific users** notifies just the people you pick - choose at least one before saving.

Clicking the notification opens the service request itself, with the client's answers already on screen.

Both switches are independent, so you can email a shared inbox without notifying anyone in the app, or the reverse. Nothing applies until you click **Save**.

> **Where to find it:** Settings -> Intake Form -> Notifications

## Related guides

* [Where intake form submissions go after a client submits](/administration/settings/where-intake-form-submissions-go-after-a-client-submits.md)
* [Build your intake form](/administration/settings/build-your-intake-form.md)
* [Add the intake form to your website](/administration/settings/add-the-intake-form-to-your-website.md)
* [Review users and their roles](/administration/settings/review-users-and-their-roles.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://learn.withessential.com/administration/settings/get-notified-about-new-intake-form-submissions.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.