Smarter Outbound AI Call Scheduling

We've overhauled how queued outbound AI calls are scheduled and placed from your journeys.

. The "only call if the contact doesn't respond to text" delay used to max out at 15 minutes. You can now set it anywhere from 2 minutes to 2 days, with a new minutes/hours/days picker in the journey builder. Give your leads a full day to reply by text before the AI picks up the phone.

. Previously, if a call came due outside your allowed calling hours (say, a lead entered your journey at 3 AM), it was skipped entirely. Now the call simply waits and is placed when your calling window next opens — in the contact's own timezone if that's how you've configured the stage.

. Right before a queued call is placed — including calls that waited overnight for your calling window — we re-verify that it still makes sense:

If the contact replied by text after the call was queued, the call is cancelled.

If the opportunity was closed or already advanced to the next goal stage in your journey (for example, they booked on their own), the call is skipped.

Do Not Call and Voice AI preferences on the contact are respected as always.

Better visibility on the contact . When a call is cancelled because the contact texted back, that now shows up on the contact's activity history — just like skips from Do Not Call and Voice AI settings do. You'll always be able to see why the AI didn't call.

. We also shipped under-the-hood improvements to how queued calls are dispatched, so calls waiting on your account's concurrency limit are picked up promptly as soon as a line frees up.