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

# Confirmation Email

Part of our automated is also checking confirmation emails that the user should receive after submitting a form. This step is optional and can simply be skipped if it is not needed.

When testing your form, we generate a new unique email address each time, which we enter into the email field of your form. We then wait 15 minutes after sending for an incoming email to that address. If an email is expected but none arrives contrary to expectations, we trigger an alert.

Just choose "Email received" in the section "Define successful test" and we will check our inbox for incoming emails.

![Screenshot Formspector: Set "Email received" as success test](/files/MproJIsIsFPqOrsbVFtC)


---

# 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.formspector.com/fundamentals/confirmation-email.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.