Commercial Calling Windows

Calling windows must reflect the current regulatory requirement, the approved campaign policy, carrier rules, and the recipient’s applicable local time. The OP26X console exposes configurable guardrails; this guide describes the operating pattern.

Define one policy object

const callingPolicy = {
  timezone: 'Asia/Kolkata',
  localStart: '09:00',
  localEnd: '20:00',
  includeStart: false,
  includeEnd: false,
  blockedDates: [],
  retryWindow: 'next-approved-window'
};

Scheduling rules

• Store one authoritative IANA timezone for the policy.
• Evaluate eligibility immediately before dialing, not only when the campaign is created.
• Convert retries into the next eligible window in the recipient’s applicable timezone.
• Keep emergency and compliance suppression checks active even inside the allowed window.
• Log the policy version and calculated window used for every attempt.

Window calculation

Change management

1. 01

   Record the policy source

   Capture the requirement, effective date, owner, and affected campaigns.

2. 02

   Update the versioned policy

   Change the server-side source of truth before updating campaign schedules.

3. 03

   Test boundaries

   Verify the minute immediately before start, at start, immediately before end, and at end.

4. 04

   Observe queued campaigns

   Check that retries and existing schedules adopt the new policy without duplicate calls.