Setting Call Schedules and Time Zones

Schedule settings protect both customer experience and compliance. They determine when Callaro can call, whose local time matters, and whether your team can review activity confidently during launch.

For most operators, this is one of the highest-risk settings in campaign setup. If the schedule is wrong, even a strong script and clean contact list can create poor outcomes quickly.

Before you start

• Audience geography is known.
• Local calling policy windows are documented.
• Campaign owner and reviewer are assigned.
• You know whether the campaign targets one timezone or multiple.

Who should own this

• Sales Ops: schedule design and policy compliance.
• SDR Lead: confirms schedule supports follow-up capacity.
• QA reviewer: validates first-day execution timing.
• Compliance owner or manager: confirms any restricted calling windows or holidays.

Set the schedule step by step

1. Open campaign schedule settings.
2. Set the campaign timezone to the primary contact region or the operating rule your team has agreed to use.
3. Add allowed day and time windows for calling.
4. Exclude weekends, holidays, or edge hours where your policy or customer experience standard says not to call.
5. Save the schedule and read the summary carefully to confirm it matches the intended local time.
6. Launch in supervised mode for the first schedule cycle so someone can verify calls start and stop when expected.

What the important schedule settings mean

1. Campaign timezone: This is the anchor for how the campaign schedule is interpreted. Choose it deliberately and document the reason.
2. Local contact timezone: If your audience spans multiple regions, using local contact time can protect customer experience and reduce bad call timing.
3. Allowed calling windows: These define when the campaign can actively dial. Narrower windows are often safer for a first launch.
4. Weekend and holiday exclusions: These help prevent avoidable complaints and misaligned outreach.
5. Separate campaign by geography: When timezones vary widely, separate campaigns usually give you better control and reporting than one broad schedule.

What good looks like

• Calls happen only when your team expects them to happen.
• The campaign schedule matches the audience's local experience, not just the operator's calendar.
• Follow-up teams are available while the campaign is active.
• No one is surprised by when the campaign starts, stops, or resumes.

Common mistakes and troubleshooting

1. If calls run at wrong local time, pause campaign immediately.
2. Correct timezone and verify next run window.
3. Resume with reduced volume for one cycle so you can confirm the fix safely.
4. If answer rates fall at edge hours, narrow the schedule before changing other variables.
5. If your audience spans distant regions, split the campaign by timezone instead of stretching one schedule to fit all.
6. Escalate to an admin if scheduling behavior remains inconsistent after settings are corrected.

Final checklist

• Timezone matches campaign audience.
• Allowed windows are policy-compliant.
• First-day run times match expected schedule.
• Team signs off before full-scale operation.

Related articles

• Creating a campaign
• Assigning phone numbers to a campaign
• Pausing and resuming campaigns
• Campaign settings reference