Re-entry & enrollment
The re-entry setting decides whether a contact can enter the same workflow more than once. It's the single most important toggle to get right, because it determines whether someone can receive your sequence twice.
By default, a workflow blocks re-entry — once a contact has entered, they won't be enrolled again even if they meet the trigger a second time. Turn re-entry on only when you want the workflow to run fresh every time the trigger fires.
- Leave re-entry off for one-time sequences — Welcome sequences, new-lead follow-up, or any flow a contact should only ever go through once. This prevents someone from getting your "Thanks for signing up" texts a second time.
- Turn re-entry on for recurring actions — Things like an appointment-reminder or a "tag added" flow that should run every single time the trigger happens, no matter how many times that is.
- Re-entry only matters for active or completed contacts — A contact who is still moving through the workflow won't be re-added regardless of this setting. Re-entry decides what happens after they've finished or exited.
Execution window & time zone
The execution window controls the hours during which your workflow is allowed to send messages, and the time zone setting decides whose clock those hours are measured against. Together they keep your texts and emails from landing at 3am.
When you set an execution window, any action that would fire outside those hours is held and released at the start of the next allowed window. The contact still gets the message — just at a sensible time.
- Set your sending hours — Define a start and end time (for example, 8:00am to 8:00pm). Anything scheduled to go out before or after that window waits until the window reopens.
- Choose how the time zone is determined — You can run the workflow on your account's time zone, or on each contact's own time zone so everyone gets messaged at a reasonable local hour.
- Pick the days the workflow can run — Limit sending to specific days of the week if you don't want messages going out on weekends.
Sender & stop-on-response
The sender setting controls who your messages appear to come from, and stop-on-response decides whether the workflow keeps running after a contact replies. Both shape how personal — and how respectful — your automation feels.
Choose a default sender so every message in the workflow goes out under the right name and number. When a real conversation starts, stop-on-response lets you pull the contact out of the automation so they aren't getting scripted messages on top of a live reply.
- Set the workflow sender — Pick the user the messages come from. This sets the from-name on emails and the number on texts, so replies route back to the right person instead of a generic inbox.
- Turn on stop-on-response for conversational flows — When a contact replies, the workflow stops sending the remaining steps. This keeps an automated nurture from talking over a live conversation once the contact is engaged.
- Leave stop-on-response off for transactional reminders — Appointment confirmations or receipts should still send even after a reply, so you'd typically leave this off for those workflows.