> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/settings/submitted-email-settings/incident-autoresponder.md).
# Incident Autoresponder
{% hint style="info" %}
Navigate to **Settings > Submitted Email Settings > Autoresponder**
{% endhint %}
### Introduction
The Incident Autoresponder feature in LUCY allows administrators to automatically respond to emails submitted via the reporting plugin. The response can include the risk score calculated by LUCY and you can define separate responses for real incidents and simulations.
***
### Autoresponse Detection
{% hint style="info" %}
Navigate to **Settings > Submitted Email Settings > Auto Response Detection**
{% endhint %}
Sometimes the reply that LUCY receives is not a report but an out-of-office message or some other automatic reply. In order to avoid a situation where two autoresponders are talking to each other, you can define various phrases that LUCY can check for in its messages to determine if the response came from an autoresponder.
You can create a list of phrases by separating each phrase with a comma.
**Timeout** - Any reply within this number of seconds will be considered an autoresponse and LUCY will treat it accordingly.
**Out of Office Delay** - Time (in days) before LUCY re-sends the message that triggered the autoresponse.
**Out of Office Phrases** - Provide a list of text patterns here and LUCY will scan incoming messages for these phrases. If any are found, LUCY will treat the message as an autoresponse.
**Bounced Phrases** - Similar to Out of Office, any message that contains a phrase from this list will be treated as a bounced message. LUCY will attempt to re-send bounced messages until the message returns a different status.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.lucysecurity.com/application-reference/settings/submitted-email-settings/incident-autoresponder.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
