> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/setup-guidepro/admin/images-and-media.md).
# Configuration of Customer-side E-Mail notifications
In the "Customer-side notifications" section, you can customize the email templates for automated customer communication. You can create individual templates for individual customers/customer groups.
**Customizable Notifications**
* **Open Order Approvals**: Daily notifications list all pending approvals from your company. This way, you stay informed about the status of orders and can act promptly. You can designate specific roles to receive these notifications and add additional email recipients.
* **Order Confirmation**: As soon as an order is placed, a notification is sent. The responsible employee always receives a copy of this email, ensuring direct documentation of the order. Here too, you can define specific roles and additional recipients.
* **Expiring Services**: This notification informs you when active services are set to expire within a specified number of days. You can use it as a reminder to request renewal services from your provider in a timely manner or take other necessary actions. You can also set a reminder for the day the service expires to be notified again.
**Benefits of Configuration**
By configuring these notifications correctly, you ensure that your team is always informed and no important deadlines or tasks are missed. This guarantees that all services are optimally managed, preventing any gaps in service.
---
# 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://hub.equipme.io/setup-guidepro/admin/images-and-media.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.
