> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/privacy-requests/user-requests/customize-automated-end-user-request-emails.md).
# Customize automated end-user request emails
{% hint style="success" %}
**Premium Feature**: DSAR
{% endhint %}
Didomi will automatically generate an email to the end-user when a DSAR is first submitted or when the status of their user request ticket is moved to certain statuses.
{% hint style="info" %}
[Click here](/privacy-requests/user-requests/user-request-status-glossary.md) to learn more about which user requests statuses will generate an email to the end-user.
{% endhint %}
Didomi offers default email templates for these automated emails to end-users which will be used unless otherwise edited by your organization. Refer to the tabs below for examples of the default email templates.
Request verificationWork in progressRefusedAccess data request fulfillmentDelete data request fulfillmentOpt out data request fulfillment
Currently, the templates used for these automated emails to end-users can only be edited via API. Fore more information on configuring the HTML of these emails to match your branding assets please refer to our [developer documentation](https://developers.didomi.io/api-and-platform/privacy-requests/emails#work-in-progress-notification).
---
# 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://docs.didomi.io/privacy-requests/user-requests/customize-automated-end-user-request-emails.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.
