> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/account/notifications-and-email.md).

# Notifications & Email

## Notifications in the portal

The bell icon in the header shows important events: new bookings, cancellations, incoming payments, and withdrawal status. This inbox keeps its history, so you can look back through it.

## Email for you

**Automatic summaries** are sent daily, weekly, and monthly, containing key numbers for your business — so you don't need to log in to know how the day went.

## Email for customers

Sent automatically at the right moment:

* **Booking created** — contains the details and a button to pay.
* **Payment received** — confirmation with the invoice.
* **Schedule reminder** — before the appointment day.
* **Reschedule and cancellation** — confirmation of the change.
* **Password reset** — for customer accounts.

Every email uses your business's logo and colors.


---

# 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.diro.app/en/account/notifications-and-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.
