- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
Every GoHighLevel workflow ships with a Settings tab that almost nobody opens after the first build. That’s a problem, because two of the settings on it — Allow Re-Entry and Stop on Response — decide whether a contact gets followed up with once, twice, or never again. Get them wrong and you either double-text a lead who already replied, or you build a workflow that quietly stops re-firing after its first run and nobody notices until a client asks why a hot lead went cold.
This is a walkthrough of what each setting actually does, the one exception that overrides Allow Re-Entry no matter how you’ve configured it, and which combination to use for the workflow types agencies build most: nurture sequences, missed-call text-back, and invoice reminders.
Where the settings live
Open any workflow in the builder and click the Settings tab at the top, next to Triggers and the canvas. You’ll find three groups of controls: contact settings (Allow Re-Entry, Stop on Response), communication settings (timezone, Time Window, sender defaults), and conversation settings (mark as read). This article focuses on the two that determine whether and how often a contact runs through the workflow — the ones with real revenue consequences if they’re set wrong.
Allow Re-Entry: what it actually controls
Allow Re-Entry decides whether a contact who has already been through a workflow — and either finished it or was manually removed — is allowed to enter it again. For new workflows this toggle is enabled by default; HighLevel changed the default from off to on for newly created workflows, so an older workflow you cloned or built months ago may still have it switched off. Don’t assume — check it.
The behavior has one constraint that trips people up: a contact cannot re-enter while they are still active in the workflow. If the trigger event fires again while that contact hasn’t finished their current run, GoHighLevel skips the re-entry attempt entirely rather than queueing a second parallel run or restarting them at step one. That’s usually what you want — it’s what stops a contact who submits the same form three times in an hour from getting three overlapping SMS sequences — but it also means a workflow that looks broken (“the contact submitted again and nothing happened”) is often working exactly as designed.
The exception: appointments and invoices ignore the toggle
This is the part that isn’t documented clearly anywhere and causes the most confusion. Workflows built on an appointment-based trigger or an invoice-based trigger will always allow a contact back in for each new appointment or each new invoice, regardless of what Allow Re-Entry is set to. Turning the toggle off on an “Appointment Booked” or “Invoice Created” workflow does not stop repeat entries the way it would on a form-submission or tag-based workflow — the platform treats each appointment and each invoice as its own qualifying event, independent of the contact’s prior history in that workflow.
Practically: if you’re building a reminder sequence off an appointment trigger and a client reschedules three times in a month, that contact runs the reminder workflow three separate times whether Allow Re-Entry is on or off. Design the workflow assuming that will happen — don’t rely on the toggle to throttle it.
When to turn Allow Re-Entry on vs. off
| Workflow type | Allow Re-Entry | Why |
|---|---|---|
| Missed call text-back | On | Every missed call is a new event worth a reply, even from the same contact calling twice in one day |
| Lead nurture / drip sequence | Off | You want one contact running through the sequence once, not restarting every time a stray tag or field update matches the trigger |
| Form-submitted lead capture | Off, with a filter | Prevents a contact who fat-fingers the submit button from entering twice; pair with a condition on the trigger if you specifically need repeat submissions handled |
| Appointment reminder / no-show follow-up | Doesn’t matter | The appointment-trigger exception overrides the setting either way — plan for repeat entries regardless |
| Invoice reminder / dunning sequence | Doesn’t matter | Same exception applies to invoice triggers |
Stop on Response: the other half of the equation
Stop on Response is the setting that ends a workflow early if the contact replies. When it’s enabled, a contact who responds to any SMS, email, or call sent from that specific workflow is pulled out of the remaining steps automatically — they don’t get the next three scheduled follow-ups after they’ve already answered.
On call actions specifically, GoHighLevel’s voicemail detection is enabled by default so that a voicemail box picking up doesn’t get misread as the contact “responding” and prematurely stopping the sequence. That distinction matters if you’re running a call-then-SMS cadence: a call that goes to voicemail should let the workflow continue to the next step, not silently exit because the platform mistook the beep for an answer.
Turn Stop on Response on for anything conversational — nurture sequences, sales follow-up, appointment confirmations. Leave it off for pure notification workflows (internal task creation, tagging, reporting) where a reply from the contact isn’t a signal that the workflow’s job is done.
Multiple opportunities: a related but separate control
If your agency runs pipeline-heavy sub-accounts — real estate, high-ticket sales, anything where one contact can have several open deals at once — there’s a related setting that controls whether each opportunity gets its own workflow execution or whether the contact only ever runs through once regardless of how many open opportunities they have. HighLevel documents this as a toggle under the account’s Objects → Opportunities settings, separate from the per-workflow Allow Re-Entry control covered above.
Because HighLevel’s own documentation doesn’t state a consistent default for this one, don’t assume either way — open Settings → Objects → Opportunities in the sub-account and check the toggle’s current state before you build a pipeline-stage workflow that depends on it. If it’s off and a contact has three open deals, only one of them is driving the workflow; if a client asks why a second property listing or second quote never triggered its own sequence, this is the first place to look.
Time Window and timezone: the scope people get wrong
Time Window restricts when a workflow’s communication actions are allowed to fire — useful for keeping SMS and calls out of a contact’s late night. What catches agencies off guard is the scope: the window applies to emails, SMS, and calls only. Tag additions, custom field updates, and opportunity-stage changes inside the same workflow are not held back by the window — they execute immediately, even if the comms actions around them are queued for the next available slot. If a downstream automation depends on a tag being set at a specific time relative to a message going out, don’t assume the Time Window is holding the tag action back too — it isn’t.
Timezone has two modes: Account Timezone, which uses the sub-account’s single configured timezone for every contact regardless of where they are, and Contact Timezone, which uses each individual contact’s own timezone and falls back to the account timezone if that contact record doesn’t have one set. For anything scheduled around business hours or send windows, Contact Timezone is almost always the right choice for a client with a geographically spread list; Account Timezone is fine for a single-location local business where every contact is in the same zone anyway.
A build checklist before you publish a workflow
- Confirm Allow Re-Entry matches the trigger type — and remember it’s irrelevant on appointment or invoice triggers
- Enable Stop on Response for anything conversational; leave it off for silent backend actions
- If the workflow touches contacts with multiple open opportunities, check the account-level multiple-opportunities toggle rather than assuming
- Set Time Window if you’re sending SMS or making calls, and don’t rely on it to delay tags or field updates
- Pick Contact Timezone unless every contact in the sub-account is genuinely in the same zone
None of these settings show up in the workflow canvas itself — they’re easy to skip because the builder doesn’t prompt you to check them. But they’re the difference between a workflow that behaves the way you designed it and one that quietly duplicates messages or goes silent after the first run. Five minutes in the Settings tab before you publish catches both.
Frequently Asked Questions
Why did a contact not re-enter my GoHighLevel workflow even though Allow Re-Entry is on?
Allow Re-Entry only permits re-entry once a contact has fully completed the workflow or been manually removed from it. If the contact is still active in the workflow when the trigger fires again, GoHighLevel skips the re-entry attempt rather than starting a second parallel run. Check the contact's execution history for that workflow to see if they're still mid-sequence.
Does Allow Re-Entry apply to appointment and invoice-based workflows?
No. Workflows built on an appointment-based or invoice-based trigger always allow a contact back in for each new appointment or invoice, regardless of how the Allow Re-Entry toggle is set. Design these workflows assuming repeat entries will happen rather than relying on the toggle to prevent them.
What's the difference between Stop on Response and Allow Re-Entry?
Allow Re-Entry controls whether a contact can start the workflow again after finishing it. Stop on Response controls what happens mid-run: if enabled, a contact who replies to a message sent from that workflow is pulled out of the remaining steps immediately, rather than continuing to receive the rest of the scheduled sequence.
Does GoHighLevel's Time Window setting delay tag and custom field actions too?
No. Time Window only restricts email, SMS, and call actions to the configured hours. Tag additions, custom field updates, and opportunity-stage changes in the same workflow execute immediately and are not held back by the window.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.