> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/campaign-execution-and-monitoring/email-deliverability/email-thresholds.md).

# Email Thresholds

These are put in place to ensure maximum deliverability of emails

Spam: Warning at 0.025%, suspension at 0.05%\
Bounce: Warning at 2%, suspension at 5%

If these rates continue to exceed our thresholds, email sending will be automatically suspended to protect deliverability for all Humanic users.

To improve your email performance:

* Only email people who have explicitly opted in to receive emails from you
* Remove invalid or old email addresses from your lists
* Ensure your content is relevant to your audience
* Do not import purchased email lists or use sourcing tools


---

# 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://humanic.gitbook.io/humanic/campaign-execution-and-monitoring/email-deliverability/email-thresholds.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.