> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/messages/sending-mailouts/schedule-delivery.md).

# Schedule Delivery

In the Notification, Newsletter or Invitation, click on the Message Setup tab and click the Schedule Mailout to schedule the mailout.

In the Notification, Newsletter or Invitation, click on the **Message Setup** tab and click the **Schedule Mailout** to schedule the mailout.

Select the **Date and Time** you want your **Invitation/Newsletter/Notification** to be sent out.

Click the **Add to Schedule** button.

Pending messages are sent every fifteen minutes, so if you schedule this mailout now then you might still need to wait several minutes before delivery is complete.

Limit the number of recipients to 10,000. Mailouts larger than this tend to trigger spam filters. To help prevent this, Messages are released from the system in batches to lower the chance of being flagged by a spam filter. Large mailouts may be released over several hours. If you need to send to more than 10,000 recipients, consider sending in multiple batches.


---

# 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://docs.shiftiq.com/help/messages/sending-mailouts/schedule-delivery.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.