# Campaign Scheduling

### Overview

The **Campaign Scheduling** feature allows you to **automate your campaign’s start and stop times** based on your preferred working hours.\
This ensures that your campaigns operate only during the designated time window — helping you maximize effectiveness, maintain professionalism, and prevent unnecessary usage of call minutes.

### Requirements

To enable **Campaign Scheduling**, you need to provide the following inputs:

* **Start Time:**\
  The exact time (in 24-hour format) when your campaign should begin each day.\
  \&#xNAN;*Example:* `09:00` for 9 AM
* **End Time:**\
  The exact time (in 24-hour format) when your campaign should pause each day.\
  \&#xNAN;*Example:* `17:00` for 5 PM
* **Time Zone:**\
  The time zone in which your campaign should operate.\
  This ensures that start and end times are applied accurately according to your local time.

<figure><img src="/files/dP7oognJLUEaozUVZ3VD" alt=""><figcaption></figcaption></figure>

### How It works

* Your campaign **automatically starts** at the specified **start time** each day.
* It **automatically pauses** at the specified **end time** each day.
* This routine continues daily **until the campaign is completed**.
* You can **manually stop the campaign at any time** — once stopped, it will not resume automatically unless you restart it yourself.

**Example:** If you set:

* Start Time: `10:00`
* End Time: `16:00`
* Time Zone: `Asia/Kolkata`

Then your campaign will automatically **run from 10 AM to 4 PM IST** every day.\
Outside these hours, the campaign will automatically pause and resume again at **10 AM IST** the next day.

{% hint style="danger" %}
While campaigns are scheduled to start and stop at the exact specified times, a **slight delay of a few minutes** may occur due to system processing time.\
You may notice your campaign starting or stopping a few minutes later than scheduled — this is completely normal and part of the processing behavior.
{% endhint %}

<https://app.voicegenie.ai/>


---

# Agent Instructions: 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:

```
GET https://voicegenie.gitbook.io/voicegenie-ai/product-guides/campaigns/campaign-scheduling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.