What Changed
The Wait Until Contact automation step gained a second way to react when
an agent contacts the lead:
- Restart the cycle. Choose an earlier step (a delay, a task, any action
above the wait) and, on contact, the workflow rewinds there and runs it
again — so a “nudge, then wait” pattern can repeat itself every time the
agent reaches out, instead of the wait only resetting its own clock. - Extend the wait is still there, unchanged, and is still the default.
Reset cap changes
- A blank Maximum resets field now means the wait never stops resetting —
it used to silently cap at 100. - Setting an explicit cap now stops the automation once it’s reached,
rather than letting the timeout run and moving the lead on to the steps
below. Those are usually leads the agent has just been in touch with
repeatedly, and moving them on (into a pond, say) was the wrong call.
Good to know
- Restart is opt-in per step; existing Wait Until Contact nodes keep working
exactly as before. - Restarting needs at least one eligible step above the wait (not the
trigger) — the builder will tell you if there isn’t one yet. - Each restarted cycle opens its own follow-up task, numbered by cycle, so
earlier ones stay visible rather than being replaced.