> 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/quiet-hours.md). # Quiet Hours These can be set for both email and SMS. The way they work is that during the hours you set, no automated messages will be sent from your account So if you have a campaign set up to go out at 5:30am, but your quiet hours go until 7am, the campaign won't actually be sent until after 7. **Email Quiet Hours**: During the hours that you set here, no automatic emails will be sent. By default we have the hours as 12am-4am, but you can edit them as needed for your business. **SMS Quiet Hours**: During these hours, no automated SMS campaigns will be sent. By default we have the hours as 7:30pm-9am, but you can edit them as needed for your business. We recommend making sure they are set at least from 10pm-4am to be compliant, but it is up to you what hours you set. --- # 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/quiet-hours.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.