Schedule and retry
Set the hours your org may call, how many times a shopper is tried, and how long to wait between tries.
At the end: calls go out only in your calling hours, and each flow tries a shopper who doesn't answer as often, and as far apart, as you chose.
Set your calling hours
Open Settings → General
You need the Admin or Owner role.Set Calling hours
Under Calling hours, pick the Days and the time From and to. Times are in the org's Timezone, set when the org was created.
RowCall places calls only inside these hours, and never before 9:00 or after 21:00 whatever you set. See Calling hours.
A run started outside your hours waits for them to open, as long as it's still allowed then (consent can lapse meanwhile). From the API, send whenClosed: "refuse" to start a run only if it can go out now; it's refused with OUTSIDE_CALLING_HOURS otherwise.
Set a flow's tries
Open the flow's Settings tab
Under Limits.Set Tries per shopper
How many calls a run may place in all. 1 means no retry.Set Minutes between tries
How long to wait after an unanswered call before the next one.Set Longest call (seconds)
The call ends politely after this.Publish
Limits are part of the flow, so they take effect when you publish.
The library flows start with tries that fit their moment:
| Flow | Tries per shopper | Minutes between tries |
|---|---|---|
| Live checkout help | 1 | — |
| Order verification | 2 | 60 |
| Checkout recovery | 2 | 240 |
| Failed delivery rescue | 2 | 90 |
| Return-intent save | 2 | 120 |
| Delivery scheduling | 3 | 120 |
When a run stops trying
A run ends as soon as the shopper answers, and then has their answers and an outcome. It also stops when every try went unanswered, the shopper opts out, or their consent no longer allows the call. The run's lastError says why, and a run.failed event goes out. Retries always stay inside calling hours.
See calls as they happen.