Handling Delayed Call Initiation Within Business H...
# support
a
Hi Vapi team 👋 We schedule outbound calls using schedulePlan, distributed across the customer’s business hours. It’s critical for us that calls never start outside business hours (we already keep a 2-hour buffer before business end). Our concern is handling peak traffic or Vapi-side delays that may delay call initiation. We rely on latestAt to enforce the cutoff, but since latestAt can’t be more than ~1 hour after earliestAt, we can’t set a single hard business-hour cutoff (e.g., 9 AM–5 PM). Question: Is there any way to set latestAt beyond 1 hour, or what is the recommended Vapi best practice to ensure delayed calls never start after business hours? Thanks 🙏
v
You cannot set
latestAt
more than ~1 hour after
earliestAt
in
schedulePlan
. The recommended approach is to programmatically split your business hours into 1-hour windows and schedule each call with its own `earliestAt`/`latestAt` pair, ensuring all calls end before your business cutoff. For example:
Copy code
json
"schedulePlan": {
  "earliestAt": "2024-01-15T14:00:00Z",
  "latestAt": "2024-01-15T15:00:00Z"
}
This guarantees no call starts after business hours. See the [API reference](https://docs.vapi.ai/api-reference/calls/create?explorer=true) for details. Source: - [Vapi API Reference: Create Call](https://docs.vapi.ai/api-reference/calls/create?explorer=true)