> 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/how-do-i-make-sure-my-emails-will-get-delivered.md).

# How do I make sure my emails will get delivered?

There’s no system that can precisely tell which emails reach a lead’s inbox or go to spam, mainly due to privacy, security, and technical limitations.

Humanic improves deliverability by gradually increasing your send rate, helping you avoid spam triggers, skipping contacts who haven’t opened multiple emails, and ensuring every message includes an unsubscribe option.

Ultimately, deliverability can only be estimated based on a few key factors:

* Only emailing people who have opted in.
* Regularly cleaning your list to remove invalid or outdated addresses.
* Sending content that’s relevant to your audience.
* Avoiding purchased or scraped email lists.
* Your domain’s age and reputation.
* The sender IP’s reputation.
* Correct setup of SPF, DKIM, and DMARC.
* The presence of links, images, or tracking pixels in your emails.

**More tips to increase deliverability**

* Keep your emails relevant and valuable to your audience.
* Write honest subject lines that match your message and avoid clickbait.
* Always include an easy-to-find unsubscribe option or let people know they can reply to unsubscribe.
* Regularly clean your list to remove inactive or invalid contacts.
* Test different versions of your emails and track results to improve performance.
* Use a trusted email service provider with strong deliverability 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://humanic.gitbook.io/humanic/campaign-execution-and-monitoring/email-deliverability/how-do-i-make-sure-my-emails-will-get-delivered.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.