> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/setting-up-guide/connecting-channels/whatsapp-templates/per-user-marketing-limits.md).

# Per User Marketing Limits

## Overview

**Per-user marketing limits** restrict how many **marketing template messages** a user can receive within a certain period.

These limits help:

* Prevent **spam**
* Improve **user experience**
* Ensure **relevant communication**

### How It Works

* Applied at the **individual user level**
* Checked **at the time of sending**
* Based on **overall messages received by the user (from all businesses)**

A message may be blocked even if you haven’t messaged the user before.

{% hint style="info" icon="meta" %}
Controlled entirely by **WhatsApp (Meta)** and cannot be modified.
{% endhint %}

### When Messages Get Blocked

A marketing template may fail if:

* The user already received multiple marketing messages
* User engagement is **low**
* The system detects **over-messaging**

### Common Error 

{% hint style="warning" %}
*Message not delivered to maintain healthy ecosystem*
{% endhint %}

### Conversation Behavior

* First message → Opens a **marketing conversation**
* One additional template can be sent
* Further messages require **user interaction**

### Messages Affected

| Message Type        | Affected |
| ------------------- | -------- |
| Marketing Templates | Yes      |
| Utility Templates   | No       |
| Session Messages    | No       |

### Best Practices

{% hint style="success" %}

* Target **active users**
* Encourage **user replies**
* Avoid frequent campaigns
* Send **relevant content**
  {% endhint %}


---

# 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://help.pickyassist.com/setting-up-guide/connecting-channels/whatsapp-templates/per-user-marketing-limits.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.