Schedule AI campaigns with explicit timezones and retry rules
Distinguish campaign start time, recipient eligibility and retry timing before scheduling outbound calls.
Table of Contents▼
A campaign's start time and a recipient's permitted calling window are different settings. Selecting a timezone for the campaign does not prove the system knows every recipient's location or enforces all applicable calling rules.
Record the intended time precisely
Use an explicit named timezone and verify the saved schedule. A local time without a zone is ambiguous. Daylight-saving transitions can create times that occur twice or do not occur at all; inspect the date as well as the clock time.
Burki's scheduling API accepts a timezone, converts the scheduled instant to UTC and rejects ambiguous or nonexistent local times on the scheduling path. This is date handling, not automatic legal compliance or recipient-location discovery.
Separate start, eligibility and capacity
| Decision | What to verify |
|---|---|
| Scheduled start | The saved instant matches the operator's intended timezone |
| Recipient eligibility | The current contact policy permits this attempt |
| Recipient window | Location/timezone information is reliable enough for the approved policy |
| Capacity | Carrier, provider, worker and funding limits permit admission |
| Human destination | Required staff are available for a supported handoff |
A number's area code is not reliable proof of the recipient's current location. Do not silently fill missing location data with a convenient assumption.
Review retries as new attempts
Define the maximum attempts and delay for the particular use case. Recheck changed restrictions and the allowed schedule before a retry. A retry should not reactivate an opt-out or duplicate an uncertain external action.
There is no universally correct retry interval or best hour across all audiences. Use an approved policy first, then measured outcomes within that policy.
Test without a live customer list
Use controlled endpoints to verify a scheduled run, a paused run, an ineligible contact and a due retry. Inspect the actual attempt timestamps and run identity rather than relying only on a “scheduled” label. Confirm what happens when the service restarts or capacity is unavailable.
Burki's optional campaign settings do not promise automatic national/state rule updates, per-contact timezone inference or guaranteed unattended outreach. Keep the operator responsible for the policy and stop conditions.
See contact controls and campaign configuration before expanding the run.
Ready to try Burki?
Create an assistant and check your available browser practice allowance.
Create your assistantTrial eligibility and available practice are shown in your workspace.