> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/overview.md). # Overview On Batch, you can create and manage three types of Orchestrations: * **Campaigns**: they allow you to send one-shot messages to your users. * **Now**: Send your campaign as soon as you run it. * **Scheduled**: Send your campaign whenever you want in the future, based on each Profile's local time or on Universal time (UTC). * **Recurring Automations**: Send messages in a recurring way, on specific intervals over time.\ Recurring Automations are great to onboard your new users for instance. You can schedule several automations that will be sent throughout their first week after installing your app, to help them discover all the features and benefits it has to offer. They are also a good way to announce special offers that last over a certain period, encourage them to upgrade to a newer version and more. * **Trigger Automations**: Send one or a serie of messages, following a user action, via different channels and with decisioning logics.\ Trigger Automations are useful to manage a wide variety of use cases, from simple welcome notifications sent shortly after users install the app to advanced abandoned cart alerts or user journeys. On each Orchestration, you have access to a wide range of feature to be able to organize them, set marketing pressure rules, specify your targeting and personalize your message. The following sections will walk you through the different types of Orchestrations and their capabilities. --- # 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://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/overview.md?ask=&goal= ``` `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.