> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/cappings.md).
# Cappings
Frequency capping allows you to limit the number of messages a profile can receive in a certain time frame.
{% hint style="info" %}
The feature is restricted to users with **App** or **Administrate** rights.
{% endhint %}
## Label-based Capping
You can create a frequency capping for all the orchestrations attached to a specific label. It works for orchestrations created via the Dashboard or Batch's APIs.
Batch dynamically checks the number of messages across all channels (email, SMS, push) that have been sent in the last X hours/days to see if the message has to be sent or not.
If you send a multiplatform push message, it counts as one sending even if the person might receive the push on several devices.
> **Important notes**: \
> \
> Messages sent very closely or at the same time may not be taken into account by the capping feature.\
> \
> Labels added to a completed orchestration have no effect on capping — since the orchestration is no longer running, no sends occur.
## Capping analytics
You can see the number of messages that were not delivered because users already reached the limit defined in your dashboard settings. The corresponding metric is called "Skipped".
---
# 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://doc.batch.com/getting-started/features/customer-engagement-platform/settings/cappings.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.
