> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/email/email-onboarding/email-delivery-onboarding.md).

# Email delivery onboarding

Warm up a new sending IP with email delivery onboarding: start with engaged recipients, then scale volume gradually to protect sender reputation.

Email delivery onboarding helps you scale sending volume while protecting your sender reputation. Start with engaged recipients, then expand to larger audiences.

### Understand IP warming

**IP warming** gradually increases email volume from a new sending IP address. Start with small, highly engaged segments. Then expand to larger audiences.

IP warming helps you:

* Build sender reputation
* Build trust with ISPs and recipients
* Improve inbox placement

### Complete onboarding

1. Share your sending requirements with Netmera. We’ll create an IP warming plan that increases volume over time.
2. Segment your audience, starting with your most engaged recipients. Early positive engagement supports sender reputation.
3. Review campaign performance with Netmera. We may recommend changes to sending volume, targeting, or content.
4. Increase your sending volume as your sender reputation improves. Expand to larger audiences without harming delivery.


---

# 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://user.netmera.com/netmera-user-guide/omnichannel-engagement/email/email-onboarding/email-delivery-onboarding.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.