Skip to main content
The Schedule tab controls when the campaign dials. You set a timezone and one calling window per weekday; the platform overlays legal dialing-hours rules on top and enforces both automatically.

Configure the Schedule

  1. Select a Timezone. The list opens on US and Canadian timezones; search by name or abbreviation (for example PST or ET), or choose Show all to pick any other timezone.
  2. In the Calling Hours table, toggle each weekday Active and set its Start and End times (24-hour format). Click a time to open the Select time popover, then choose an Hour and a Minute.
Until a timezone is chosen, the day rows stay locked. When you enable a day it fills the full legal window for that timezone (08:00–21:00 for US timezones), and the time pickers only offer legally allowed times. If a row has a problem, such as a start time that isn’t before the end time, a short message appears under it explaining what to fix.
The end time is exclusive — a 09:00–17:00 window places its last dial before 17:00. Changing the timezone clears the day rows so you can re-confirm each window under the new timezone’s legal calendar.
Legal dialing hours are only built in for some countries. If a timezone has no legal rule on file, such as the Canadian timezones, enabling a day fills 00:00–23:59 and the pickers aren’t restricted, so set the window you actually want to call in. A timezone the platform can’t match to a country, such as UTC, is treated as a US timezone, so enabling a day fills 08:00–21:00. Contacts in a country with no rule on file are blocked when the campaign tries to dial them; see Legal Dialing Hours.
Regulations restrict when automated calls may be placed. The scheduler enforces them at two levels:
  • Campaign level — the Schedule tab restricts the pickers to the legal times for your chosen timezone, and clamps saved times back into legal bounds if rules change. A weekday that isn’t in the legal calling calendar for the timezone stays in the table but is greyed out, marked Not in legal calendar, and can’t be switched on. The tab uses the timezone’s country-wide window; limits that apply to a single state (for example Florida’s 8 PM end) are applied per contact, not here.
  • Contact level — before every dial, the platform resolves each contact’s local timezone (from their ZIP code, falling back to their phone number’s area code) and only dials inside the calling window that applies to them. Contacts outside their window are queued, not skipped. The postal-code reference data behind this lookup is refreshed automatically every week.
A contact is Blocked instead of queued when no window can be worked out for them. If their timezone can’t be found from the ZIP code or the phone number, the Reason reads “Timezone could not be resolved — no postal code match and no recognizable area code”, so a correct ZIP code helps where the number gives no clue. If no legal dialing-hours rule applies to their country or state, it reads “No dialing rules apply for …” followed by the place. See the Block Reasons Reference. Some jurisdictions also impose frequency caps (for example, Florida’s limit of 3 calls per 24 hours). Contacts held by a frequency cap show as “Frequency capped” in monitoring and are retried automatically when the window expires.
Not sure whether it’s legal to call right now? Ask the Squawk Co-pilot for a timezone (and, for the US, a state). It answers yes or no against today’s legal dialing window for that place, with no campaign needed, and says so if it can’t confirm.

What Happens at the Window Edges

  • Launching outside the window — the launch succeeds and the campaign is queued with a “Campaign queued — dialing starts …” message. Dialing begins automatically when the window opens.
  • Window closes mid-run — the run moves to Window Closed; calls already in progress finish naturally, and no new dials are placed.
  • Window opens — the run resumes automatically. No manual action is ever needed for schedule pauses (the Resume button is intentionally hidden for them).

Callbacks and the Schedule

When a contact asks to be called back at a specific time, the AI agent schedules exactly one callback attempt at the requested time, interpreted in the contact’s timezone:
  • Callbacks must be within 30 days.
  • Requests sooner than 5 minutes out are scheduled at the earliest allowed time rather than dropped.
  • The agent knows your calling hours and steers contacts toward times inside the window.

Requirements to Save

The schedule autosaves once it is valid: a timezone is selected, at least one day is active, and every active day has a valid start-before-end range. If you edit the schedule so that it has no timezone or no active day (for example, by switching off the last active day), a banner reads “Select a timezone and at least one day to save your schedule.” and that change isn’t saved. A new campaign’s untouched, empty Schedule tab shows no banner. The launch checklist flags it instead, because Schedule configured is one of its gates.

Where to go next

Launching & Live Monitoring

The launch checklist and real-time run dashboard.

Compliance & DNC

How per-contact legal windows and consent checks gate each dial.