Every sequence has waits in it, and most of them were copied from a template. This lesson is about choosing them on purpose.
A person who has just filled in a form still has your tab open and still remembers why they came. Two days later they have forgotten, and your message arrives as an interruption rather than a continuation. The same words perform completely differently depending on when they land.
A calendar sequence sends on day one, day three and day seven regardless of what the person did. An event sequence waits for a signal and reacts to it. Calendar is easier to build and it is why so many people receive a nudge to finish something they finished yesterday.
Many stacks process automation once a night. That turns every twenty minute intention into an up to twenty four hour wait, and nobody notices because the report still says the mail went out. It is the most common gap between a designed sequence and a running one.
A sequence that never ends is a machine for generating complaints. Decide up front how many messages someone gets before you stop, and treat silence as an answer rather than a reason to try harder.
Run the free domain check first, then tell us what it found. We come back with what we would fix first, at no cost.