Skip to main content
A configuration is an org-level, reusable bundle that a campaign points at. It defines when contacts may be called (calling windows per timezone), how aggressively to retry, how to normalize uploaded phone numbers, and which agent version does the dialing. Create a configuration once and reuse it across many campaigns. A configuration has three parts:
  • Schedule — when calls are allowed, by timezone.
  • Dialing policy — retry limit and the default country code for normalizing numbers.
  • Agent — which agent (and version) to dial with.

Schedule

The schedule controls which timezones are inside their calling window at a given moment. Calls are only placed to contacts whose timezone is currently in a window.

TimeWindow

A TimeWindow is a set of weekdays plus a daily start and end time. If start is earlier than end, the window is a normal same-day range (for example 09:00-17:00). If start is later than end, the window crosses midnight (for example 22:30-03:30), and the early-morning portion is attributed to the previous day’s days entry.
If default_windows is empty and no override matches a contact’s timezone, no calls are placed to that contact. Set at least one window before launching a campaign.

ScheduleOverride

A ScheduleOverride attaches a list of windows to one or more timezones. For any contact in a listed timezone, these windows replace default_windows entirely.

Regular vs scheduled windows

There are two parallel sets of windows. Use scheduled windows when you want first-time scheduled contacts to be dialed on a different schedule than everyone else. To list every valid IANA timezone identifier accepted by these fields, call:

Dialing policy

When contacts are uploaded against a campaign, numbers without an explicit country code are parsed using default_country_code and formatted to E.164 (for example, +44). Numbers that cannot be parsed are reported as invalid. See Contacts for upload behavior and Dialing and retries for how attempts are spent.

Agent

Default configuration

A configuration can be marked as the organization’s default with is_default. Only one default may exist per organization.
Creating or updating a configuration with is_default: true while a default already exists returns 409 Conflict. Un-default or delete the existing default first.

Endpoints

All endpoints require the campaigns:read scope to read and campaigns:manage to create, update, or delete.
Deleting a configuration that is referenced by one or more campaigns returns 409 Conflict. Reassign or delete those campaigns first.

Create a configuration

Contacts

Upload contacts and how numbers are normalized to E.164.

Dialing and retries

How attempts and calling windows govern when calls go out.