> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/accountmanagement/account-and-users/agency-notifications-for-all-your-clients.md).

# Agency: Notifications for all your clients

Set up email alerts once for every client of your agency: a daily health check, and an email as soon as something new goes wrong.

With **Meldingen voor al je klanten** (Notifications for all your clients) you set up email alerts once for your whole agency, instead of per container. Every container of every client takes part, including clients you add later.

There are two emails:

* **Dagelijkse gezondheidscheck** (Daily health check): every morning, the health score of all your clients, with the ones that need attention at the top.
* **Direct bij een nieuw probleem** (Right away on a new problem): an email as soon as a check finds something new at one of your clients.

{% hint style="info" %}
This feature is in pilot. Don't see **Meldingen** (Notifications) in the menu? Ask <support@adpage.io> to switch it on for your agency.
{% endhint %}

## Who can use it

* Members of the agency can open the page and see the settings.
* Only an owner or admin of the agency can change them. Other members see the page read-only.

## Open the page

Log in to [AdPage](https://data.adpage.io/auth/login). In the menu, under **Tracking**, click **Meldingen** (Notifications).

The page shows the two emails as tiles. Below them, under **Klanten** (Clients), you see all containers of your clients with their health score.

## The two emails

### Dagelijkse gezondheidscheck (Daily health check)

Sent every morning around 7:00 (Amsterdam time), after the nightly check of all containers.

* Containers that need attention come first, with what failed and what is new since yesterday.
* Healthy containers are listed by name below that.

Choose when it goes out:

* **Elke ochtend** (Every morning): also when everything is healthy, so you know the check ran.
* **Alleen als er iets is** (Only when there is something): no email when all your clients are healthy.

### Direct bij een nieuw probleem (Right away on a new problem)

Sent after every check (each night, or when someone starts one), once per finding. Whatever was already wrong when you switched the email on does not count as new.

Choose when we email:

* **Bij elke nieuwe bevinding** (On every new finding): also a warning, as soon as a score drops below 100.
* **Kritiek, of een score onder 80** (Critical, or a score below 80): a new critical finding, or a score that drops below 80. This is the recommended setting.
* **Alleen kritiek** (Only critical): only a new critical finding.

## Set up an email

{% stepper %}
{% step %}

### Open the email

Click the tile of the email. On the left you see an example with your own clients; on the right, the settings.
{% endstep %}

{% step %}

### Switch it on

Turn on **Deze mail aan** (This email on).
{% endstep %}

{% step %}

### Choose when it goes out

Pick one of the options described above.
{% endstep %}

{% step %}

### Add the recipients

Under **Wie krijgt de mails** (Who gets the emails), enter an email address and click **Toevoegen** (Add). You can add up to 10 addresses. Both emails go to the same list. Without a recipient, no email goes out.
{% endstep %}

{% step %}

### Send a test email

Click **Stuur een testmail** (Send a test email). The email goes to your own address, with \[Test] in the subject. Close the window with **Klaar** (Done).
{% endstep %}
{% endstepper %}

Every change is saved right away. The emails are written in the language you use AdPage in when you save.

## Choose which containers take part

Under **Klanten** (Clients), each container has a switch. A new client takes part automatically. Switch a container off for a test container or a client that is on hold.

## How the health score works

The score is the same as on the containers overview: it starts at 100, minus 15 for every critical finding and minus 5 for every warning. A container without a check yet shows **Nog geen score** (No score yet).

## Trial mode

During the pilot, the emails can still be in trial mode. The page then says **De mails staan nog in de proefstand: we meten al, maar sturen nog geen mail.** (The emails are still in trial mode: we're already measuring, but not sending email yet.)

Your settings, the example and the test email already work in trial mode. As soon as AdPage switches your agency to live, the emails go out with the settings you chose. You don't need to change anything.

## Troubleshooting

* **I don't see Meldingen in the menu.** The feature is in pilot and is switched on per agency. Ask <support@adpage.io>.
* **"Meldingen voor al je klanten staat nog niet aan voor je bureau"** (Notifications for all your clients is not switched on for your agency yet). Same as above.
* **"Alleen de eigenaar of een beheerder van het bureau kan dit wijzigen"** (Only the owner or an admin of the agency can change this). Ask an owner or admin of your agency. See [Agency: Add a user to your agency](https://docs.adpage.io/accountmanagement/account-and-users/agency-add-a-user-to-your-agency.md).
* **I don't receive the emails.** Check that the page doesn't say trial mode, that your address is under **Wie krijgt de mails**, and your spam folder. Send a test email to check delivery.
* **A client is missing.** Only clients linked to your agency take part. See [Link your company to an agency](https://docs.adpage.io/accountmanagement/account-and-users/link-your-company-to-an-agency.md).


---

# 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.adpage.io/accountmanagement/account-and-users/agency-notifications-for-all-your-clients.md?ask=<question>&goal=<user_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.
