GoHighLevel Schedule Visibility: Form and Survey Expiry Setup

HighLevel shipped a new setting today called Schedule Visibility, and it fixes something agencies have been working around with workflows and manual toggles for years: there was no native way to make a Form, Survey, or Quiz open on one date and stop accepting entries on another. If you run event registrations, flash-sale opt-ins, or evergreen webinar funnels for clients, this replaces a chunk of duct-taped automation with one setting.

Because this landed in HighLevel’s changelog only hours before this article was written, there is no support article on it yet, and the coverage that exists elsewhere on GoHighLevel forms and surveys predates the feature entirely. This walks through what the setting actually does, where to find it, and the questions HighLevel’s own announcement leaves open that you should check in your own account before you rely on it for a client launch.

What Schedule Visibility Actually Does

Schedule Visibility is an opt-in toggle inside a Form, Survey, or Quiz’s own settings panel – it is not a global account setting, and it is not turned on by default. Leave it off and the object behaves exactly as it always has: always open, always accepting submissions.

Turn it on and you get two independent controls: an opening rule and a closing rule. Before the opening time and after the closing time, HighLevel automatically swaps in a replacement experience for visitors instead of the live form. Enforcement is automatic in both directions – submissions start accepting the moment the open time hits, and new submissions are blocked the moment the close time hits, with no one needing to log in and flip a switch on either end.

Where to Find It

The setting lives inside the builder for the specific Form, Survey, or Quiz you want to schedule – open the object, go to its settings panel, and look for Schedule Visibility alongside the object’s other display and submission settings. It applies per-object, so a Form used across three different funnel pages is scheduled once, at the Form level, not once per page it happens to be embedded on.

Setting the Open and Close Windows

Each edge of the window has two options:

You can mix these: a form that opens right away but closes on a fixed date is the flash-sale pattern. A form that opens on a future date and never closes is the pre-launch teaser pattern. Both edges are optional independently of each other.

The Pre-Launch and Post-Expiry Experience

This is the part that separates Schedule Visibility from just hiding a page. For each edge – before opening, and after closing – you choose one of two replacement experiences:

• Show a page – a fully custom page with your own rich content, built inside the same interface, shown in place of the live form.
• Open a link – redirect the visitor to a different URL entirely, which can be a waitlist page, a different offer, or an external site.

A preview mode lets you see the unavailable-state page before it ever goes live, which matters because you will not get a second look at it once real traffic is hitting the link during the actual closed window.

Practically, this means a webinar funnel can show a “doors open on the 14th” teaser page before the registration form unlocks, then automatically swap to a “see you at the replay” redirect the moment the event starts – without a workflow, a manual page swap, or anyone touching the account on either date.

The Time Zone Question

HighLevel’s announcement includes a time zone selector as part of the setup, described as configuring the zone used for the opening and closing schedule. The wording in the changelog does not spell out whether the opening date and the closing date can each carry a different time zone, or whether one zone selection governs both edges of the same schedule. Since a US-based agency running a launch for an East Coast client list and a West Coast client list would care about this distinction, verify it directly in your account before assuming either behavior – do not schedule a hard deadline like a coupon cutoff around an assumption here.

What the Changelog Doesn’t Answer Yet

Because this is a same-day feature with no support article behind it yet, treat the following as open questions to test in your own account rather than settled behavior:

• Multi-page embeds. A Form embedded on more than one funnel or website page is almost certainly scheduled once, everywhere, given how HighLevel treats Forms as shared objects elsewhere in the platform – but this isn’t stated outright, so confirm it before assuming a closed form disappears from every page it’s placed on.
• Workflow trigger behavior. If a closed window blocks the submission itself, the Form Submitted or Survey Submitted workflow trigger logically never fires during that window – no submission, nothing to trigger on. That’s an inference from how the trigger works generally, not a documented statement, so if you have automation depending on submissions arriving in a specific window, test it rather than assume it.
• Saved Progress interaction. HighLevel separately offers a Save Progress feature for Forms, Surveys, and Quizzes. What happens to a visitor’s partially completed, saved session if the closing time passes before they come back to finish it is not addressed in the Schedule Visibility announcement.
• Embedding outside GoHighLevel. Whether the scheduled open/close behavior works the same way when a Form is embedded via iframe on a non-GoHighLevel website, versus only on GHL-hosted funnel and website pages, is not confirmed.
• Rollout stage. The changelog entry is tagged as a standard release rather than a beta, which suggests general availability – but staged rollouts across accounts are common for HighLevel, so confirm the toggle is actually present in your account’s Form, Survey, or Quiz settings before you promise a client this is ready to use.

Where This Actually Saves Work

The use cases HighLevel names directly in the announcement line up with the kind of client requests that used to require a workflow-and-workaround approach:

HighLevel’s own changelog credits two named customer feature requests behind this release – one asking for coupon-expiration enforcement, the other for evergreen webinar funnels that could self-expire without manual intervention. Both are exactly the kind of recurring client ask that agencies have historically solved with a patchwork of workflows, manual reminders, or a developer-built redirect script.

What This Replaces in an Existing Build

Before today, closing a form on a schedule meant building the date logic yourself. A common pattern was a workflow watching for the close date, then swapping the funnel step’s destination or manually unpublishing the page – which works, but depends on someone remembering to build it correctly for every launch, and depends on the workflow actually firing on time rather than sitting in a queue. A pre-launch teaser page had the same problem in reverse: someone had to remember to swap the placeholder for the live form on launch morning, or build a second workflow to do it.

Schedule Visibility moves both of those from “a workflow you have to design and test” to “two dropdowns and a date picker” on the object itself. That matters most for agencies running the same launch pattern repeatedly for different clients – a recurring webinar funnel, a monthly flash sale, a rotating quiz contest – where rebuilding or copying a workaround workflow for every new instance is the actual time sink, not the concept of scheduling itself.

It also removes a failure mode that workaround workflows share: if the workflow that was supposed to close the form doesn’t fire – a delay, a misconfigured trigger, an account-level pause – the form stays open past its deadline with nobody noticing until a customer complains about a coupon that should have expired. Because the new setting is enforced by the object itself rather than by a separate automation watching the clock, there’s one fewer moving part that can silently fail.

If you run either the launch-teaser or the hard-deadline pattern for clients now, this is worth testing on a low-stakes form first, confirming the open questions above in your own account, and then rolling it into the standard build for the next launch rather than the workflow-based version you may already have documented in your SOPs.

Frequently Asked Questions

What is GoHighLevel's Schedule Visibility setting?

It's a per-object setting on Forms, Surveys, and Quizzes that lets you set an opening date and time and a closing date and time. Before the opening time or after the closing time, HighLevel automatically shows a custom page or redirects to a URL instead of the live form, and submissions are blocked outside the open window with no manual steps required.

Is Schedule Visibility turned on by default?

No. It's an opt-in toggle inside each Form, Survey, or Quiz's own settings panel. Anything you don't enable it on keeps behaving exactly as before – always live, always accepting submissions.

Can I show a custom page instead of just hiding the form before or after the window?

Yes. For both the pre-launch and post-expiry states you can choose either 'Show a page' with fully custom content, or 'Open a link' to redirect visitors somewhere else entirely, and you can preview that replacement experience before it goes live.

Does closing a form stop its workflow trigger from firing?

HighLevel's announcement doesn't state this directly, but since a closed window blocks the submission itself, it follows that the Form Submitted or Survey Submitted trigger has nothing to fire on during that window. If your automation depends on this, test it in your own account rather than assume it.

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

Get my free setup quote

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.