> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/notifications.md).
# Notifications
Customize the emails sent to customers, admins, companies and drivers.
CodiCo Dispatch sends emails when something happens to a booking or an account. Under **Notifications** you change the content of each email. The templates are grouped by who receives them.
## Edit a template
Open a template from the menu, for example **Notifications → Customer Notifications → Notification booking reminder**.
A notification template.
A template is made of blocks. Each block has a **Show … block** checkbox. Inside a block, more checkboxes choose which details are included, for example **Show pickup date**, **Show flight number** or **Show vehicle class**.
Text blocks such as **Notification header**, **Notice content**, **Policy content** and **Footer content** have one field per language (14 languages). Fill in each language you use.
Some templates, such as **Company Invoice Request**, also have **Enabled**, an **Email subject** and a **Body content** per language.
* **Preview** shows how the email looks.
* **Send test email** sends a test message.
* **Save** stores your changes.
{% hint style="warning" %}
Emails are sent through your mail server. Set it up in **Integrations → SMTP** before you go live.
{% endhint %}
## Customer Notifications
| Template | Sent when |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
| User credentials | A customer account is created. |
| Notification booking created | A booking is made. |
| Notification booking cancelled | A booking is cancelled. |
| Notification booking reminder | Before the trip. |
| Notification booking changed | A booking is changed. |
| Notification driver changed | A different driver is assigned. |
| Notification booking processed | The booking is accepted for processing. |
| Notification booking finalized | The trip is finished. |
| Notification companions found / successfully joined sharing / sharing cancelled (user) / companion joined (owner) / companion cancelled (user) / sharing cancelled after update (user) | Shared taxi events. |
| Notification review replied | You reply to the customer's review. |
| Booking quote | A quote is sent to the customer. |
| Notification new price offer | A new price offer is made for the booking. |
## Admin Notifications
| Template | Sent when |
| ------------------------------------------ | ------------------------------ |
| Notification company application submitted | A company applies to join. |
| Company Invoice Request | A company requests an invoice. |
| Notification review created | A customer leaves a review. |
## Company Notifications
| Template | Sent when |
| ------------------------------------------------------------------------------------------------------------------ | -------------------------------------- |
| Notification company created | A company account is created. |
| Notification booking assigned | A booking is assigned to the company. |
| Notification sharing cancelled / companion cancelled / companion joined / sharing cancelled after update (company) | Shared taxi events. |
| Notification booking reminder (company) | Before the trip. |
| Company Acceptation Mail | The company's application is accepted. |
| Notification price request | A price is requested from the company. |
| Notification price offer accepted | The company's price offer is accepted. |
## Driver Notifications
| Template | Sent when |
| ----------------------------- | ---------------------------------------- |
| Driver credentials | A driver account is created. |
| Notification driver new order | A new booking is assigned to the driver. |
| Driver invoice request | An invoice is requested from the driver. |
{% hint style="info" %}
The *Sent when* column describes each template from its name. Customers can switch individual emails on or off in their profile (see [Customers](/documentation/people-and-companies/customers.md)).
{% endhint %}
Read more about [automation](https://codico.io/taxi-dispatch-software/automation/) on the CodiCo website.
---
# 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://codico-dispatch.gitbook.io/documentation/notifications.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.
