> 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

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