Why pause windows matter
Calling at the wrong time:- Annoys recipients
- Reduces answer rates
- May violate regulations
- Wastes resources
How they work
During a pause window:- No new calls are initiated
- Contacts wait in the pending queue
- When the window ends, calling resumes
- No contacts are skipped—just delayed
Configuration
Pause windows are defined on programs:Weekly windows
Define recurring windows for each day of the week:Advanced windows (specific dates)
For holidays and special events, use advanced windows with specific dates:Common patterns
Business hours only
Only call 9 AM to 6 PM on weekdays:Lunch breaks
Pause during typical lunch times (apply to each weekday):Weekend only
Only call on weekends (for B2C):Timezone considerations
Pause windows use the organization’s timezone. If your organization is set toAfrica/Casablanca:
{ "hour": 12, "minute": 0 }means 12:00 PM in Casablanca- This adjusts automatically for DST if applicable
- Setting windows based on recipient timezones (if you segment by region)
- Using broader windows to cover multiple zones
Pause windows vs program stop time
| Feature | Purpose |
|---|---|
| Pause windows | Temporary pauses, calling resumes |
stopAt | Permanent end, remaining contacts skipped |
stopAt to set a hard deadline.
Best practices
- Respect local customs - Lunch times vary by culture
- Consider your audience - B2B: business hours, B2C: evenings/weekends
- Account for holidays - Use advanced windows for local holidays
- Test your windows - Verify they work as expected
- Document your reasoning - So future you understands the choices
Limitations
- Windows are based on organization timezone
- Granularity is to the minute
- Cannot set different windows per contact (segment into different programs)
Related topics
Programs
Setting pause windows.
Retry Strategies
Retries respect pause windows.