> For the complete documentation index, see [llms.txt](https://docs.ai.insly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.insly.com/nora/skills/email-follow-up.md).

# Email Follow Up

One of the biggest bottlenecks for underwriters is chasing brokers for missing information. When a submission arrives without all the required details, underwriters cannot proceed with creating a quote. This creates a back-and-forth “email ping-pong” that can easily waste hours and stall deals.

Nora removes this pain completely.

* If required values are missing after extraction, Nora automatically sends an email to the submitting broker.
* The email includes a clear reference to which fields are missing. The template and wording are fully customizable to match your tone and process.
* The broker simply replies to the email — either itemised or freeform — and the system re-processes the response.
* Missing values are automatically added to the submission, and the underwriter gets a notification that the case is now complete and ready to quote.

All of this happens without the underwriter lifting a finger. The email does not land in their inbox; it goes directly into Nora, where the submission is enriched and marked as complete.

**This feature eliminates:**

* repetitive manual communication,
* speeds up quoting,
* ensures brokers get a faster response.

Underwriters save valuable time, reduce errors, and focus on what really matters: assessing risk and writing more business.

{% hint style="info" %}
For information on how to set up this feature, see the [configuration guide](/nora/configuration-guide/set-up-email-follow-ups.md), or [reach out to us](/readme.md). Email follow-ups are available on the **Standard** **plan** and upwards.
{% endhint %}


---

# 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.ai.insly.com/nora/skills/email-follow-up.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.