Funnels

Store Terms & Conditions acceptance on 1-step / 2-step order forms (timestamp, version, and contact/order proof)
Problem HighLevel added Terms & Conditions on 1-step and 2-step order forms so the checkbox must be checked before Complete Order. That only blocks checkout. It does not store acceptance on the contact, order, payment, or any submission record. When a buyer later disputes a no-refund or T&C policy, there is no internal paper trail that they accepted those terms at purchase. HighLevel support confirmed consent is not saved as submission data. Saying they could not pay without checking the box is not enough. The buyer can claim the checkbox or T&C text was different at the time of order, and we have nothing to show. Why this matters This creates real risk on chargebacks, refund disputes, and "I never agreed to no refunds" claims. It also creates legal and compliance exposure because there is no proof of agreement. The T&C option on the order form looks complete but cannot be used as evidence. The only workable option today is to rebuild checkout with Sites > Forms (classic forms store T&C in submission data) and embed that instead of the Funnel order form element. That undercuts the native order form. What we need When T&C is enabled on a 1-step or 2-step order form and the buyer completes payment, HighLevel should persist acceptance on the contact and/or order (for example terms_accepted = true), store a timestamp of acceptance (ideally with timezone or UTC), and keep a snapshot of what they agreed to including the T&C label/preview text, linked URL, and page/funnel step ID at time of purchase (or a version hash). This should be visible in Contact > Payments / Orders / Activity, on the order details, and exportable for disputes. Ideally it should also attach to payment/transaction metadata so it survives contact merges and support handoffs. Current behavior (confirmed by HighLevel support) The T&C checkbox is UI-only. Complete Order stays disabled until checked. There is no separate submission record for order-form consent. Classic Forms do store T&C in submission data. Funnel order forms do not. Related but different The changelog "Enable terms and conditions on 1-step and 2-step order forms" only added the UI gate. The existing idea about a Marketing/SMS consent checkbox is useful, but it does not solve storing purchase T&C acceptance as proof. Business impact (real example) We cannot prove a buyer accepted a required no-refund T&C on a Funnel order form. That alone is exposing a $1,598 refund decision on a single customer, with no auditable consent record. Without stored acceptance, native order-form T&C is a liability hole for any merchant using no-refund or similar policies. Ask Treat order-form T&C like a real consent event: store it, version it, and surface it on the contact/order so merchants can prove acceptance when disputed.
0
·
Enhancement
Native JSON Import/Export Schema for Page Builder
Problem: GHL's AI builder and page builder are... not competitive right now. They're limited, and the AI-generated designs look like every other AI-built site. Users are forced to either hand-build everything (slow) or use external tools like Lovable/Claude (which means they're thinking about leaving GHL). The real issue is when someone tries to paste clean code from an external AI tool into GHL, it breaks the visual editor and tanks the UX. It gets dropped into a "Custom HTML" block, which means it's no longer editable in GHL's native editor. You lose the whole point of having a visual builder. The Solution: Open up a JSON import/export system for the page builder. Let users paste a structured JSON object (similar to how Elementor or Bricks work) and have GHL instantly convert it into native, fully-editable elements (rows, columns, headlines, buttons, etc). When you drag a "Headline" into a "Column" in GHL, the backend saves a JSON object that looks something like this... { "type": "headline", "text": "Welcome to my Funnel", "style": { "color": "blue", "font-size": "32px" } } Problem right now... GHL keeps this structure "internal" or proprietary. If you paste code, they treat it as a "Custom HTML" block, which breaks the visual editor. By opening up an import function for that raw JSON structure, you allow external tools to inject native elements rather than "dumb" HTML code. Basically... stop trying to build the best AI designer. Just build the door. Why This Wins for GHL You Stop Chasing AI GHL doesn't need to out-engineer OpenAI or Anthropic. They're never going to. But if you expose a clean schema, external AI tools will generate GHL-compatible designs for free. Let Claude/GPT/Gemini be the designer. GHL is the delivery layer. You own the ecosystem without the R&D burden. You Solve the Blank Canvas Problem Biggest friction point for new users is starting from scratch. If someone can drop in a JSON-generated funnel and instantly get a fully-built, editable page... user onboarding gets way easier. First-time users don't bounce. They commit. Vendor Lock-In Actually Works Counterintuitive... opening up import/export makes people stay, not leave. If I can easily bring clean designs into GHL and edit them natively, I'm not looking for alternatives. I'm invested in your platform. Marketplace Opportunity Users start sharing "GHL JSON blocks" (hero sections, pricing tables, sales sequences). Agencies build migration tools that convert ClickFunnels/WordPress designs to GHL-native format. The ecosystem explodes without GHL doing the work and updating the library. Turbocharge Your AI (If You Build One) If GHL eventually builds robust internal AI, having a standardized JSON schema means the AI can reliably manipulate layouts. It's easier to train a model on structured data than on visual code. You already have the infrastructure. What This Looks Like User opens Lovable → generates a clean landing page → exports as JSON → pastes into GHL → everything appears as native GHL elements → fully editable in the visual builder. No broken custom HTML. GHL's builder isn't losing because it's too simple. It's losing because it's too limited compared to what external tools can generate in 60 seconds. Instead of fighting that battle, lean into it. Be the best destination for AI-generated designs, not the best AI designer. Expose the schema. Let the AI models do the heavy lifting. Own the platform. Win. Why Now Every major builder (Webflow, Wix, ClickFunnels) is scrambling to figure out their AI story. The ones winning aren't trying to be AI designers, they're making it stupid-easy to bring external designs in and own them natively. GHL has a window to get ahead.
3
·
New Feature
Load More