C
Carole Asselin
Allow users to move a contact from one step of an automation to another, instead of duplicating entire branches.
Examples of use cases:
  • A contact doesn’t click a download link after Email 1 → send a reminder Email 1B → if they then click, return them to Email 2 and continue the series.
  • Check if a field is filled. If not, update the field → then continue the original sequence without duplicating all later steps.
Why it matters:
Currently, the only way to handle these scenarios is to duplicate the entire “Yes” branch of an automation under the “No” path. This quickly leads to very long, messy workflows that are hard to maintain or adjust later. A simple “jump to step” or “return to branch” option would avoid this duplication.
Benefit to all users:
Cleaner automations, easier maintenance, fewer errors, and more efficient customer journeys.