> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/campaigns/ongoing-vs-one-time.md).
# Ongoing vs One Time
When setting up your campaigns, you have several timing options: ASAP, later, or automated / ongoing.
**Send ASAP**: If selected, the campaign will begin sending right away. Keep in mind, if this selected during quiet hours, the campaign will begin sending once your quiet hours have ended.
**Send Later**: If selected, the campaign will begin sending at the time specified.
**Automated / Ongoing**: If selected, the campaign will send once confirmed to the current audience + anyone added to the audience moving forward.
For example, if I make an audience of people on the 'Intro' membership plan, each time a new person signs up for the 'Intro' membership plan, this email will send.
When selecting an 'Automated / Ongoing' campaign' you have 2 options: at a specified time or at any time.
'At a specified time' will send the campaign each day to new audience members at the same time every day. You can specify that in the 'At a specified time' section.
'Anytime' will send the campaign as soon as the new information is added to the audience, outside of your quiet hours.
Intelligent Sending (AI): This option may override the above preferences, based on the user's most engaged time. For example, if the recipient has historically opened their emails around 2:00 pm, their campaign will send at that time.
---
# 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://help.gleantap.com/campaigns/ongoing-vs-one-time.md?ask=&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.
