10 min read

Funnel AI Built Your Page in Five Minutes. Here's Why It Captured Zero Leads (HighLevel Funnel & Website AI and Workflow AI, Fixed)

HighLevel Funnel AI builds a complete page from one prompt, and the form on it can be a Custom Code block that captures nothing. Here is the fake form problem, the Workflow AI phantom reference problem and the exact fix order that ships a funnel that creates contacts.

TLDR

  • HighLevel Funnel AI generates page structure, copy, visuals and SEO suggestions from a single prompt, per the official Funnel & Website AI documentation.
  • In a documented July 2026 field test, the lead form the AI rendered was a Custom Code element. It looked finished. It submitted nowhere. Zero contacts were created.
  • The fix is always the same: build a real form in Sites > Forms first, then swap it into the AI page as a Forms And Surveys element.
  • Workflow AI Builder writes correct structure but invents references to forms and tags that do not exist. The error panel catches them. Merge fields it invents fail silently.
  • Prompt Funnel AI in one flat paragraph. A multi-line numbered prompt hung the builder for 20 minutes in the same test.
  • Build order that works: form, then funnel, then form test, then workflow, then end-to-end test, then publish.
  • An agency that ships this order in a fresh GoHighLevel account can do it inside the 30-day free trial.

Who This Is For

  • Agencies using HighLevel Funnel AI to build client landing pages at volume.
  • Business owners who built a page with "Build with AI", ran ads to it and saw no leads in Contacts.
  • Anyone whose Workflow AI automation looks perfect on the canvas and never fires.
  • Freelancers evaluating GoHighLevel because the AI builders promise a funnel and follow-up in an afternoon.

The Page That Looks Done and Isn't

Funnel AI is good. That is the problem.

The Funnel & Website AI documentation describes it as "an AI-powered page creation experience for building funnel and website pages from prompts, guided inputs, URLs, and images". It produces "page structure, copy, visuals, and layout direction" plus suggested titles and descriptions for SEO.

It does all of that. In a July 2026 field test documented in a HighLevel agency's internal SOP, one prose prompt produced a complete ten-section HVAC and plumbing lead page in about five minutes. Hero, trust bar, services grid, testimonials tied to real local towns, a branded service van in the client's palette, risk reversal copy nobody asked for.

And a lead form that captured nothing.

Here is the cost chain.

  • The AI renders the form as a Custom Code element. Raw HTML. No submit handler.
  • The page is previewed. The form looks right. Nobody clicks submit on the preview.
  • The page is published. Ads go live.
  • A visitor fills the form and clicks. No success message. No contact. No workflow.
  • The visitor assumes the business is broken and moves on.
  • The client sees ad spend and zero leads and blames the platform, or the agency.

The documentation does not mention form generation at all. That silence is the tell. The AI builds what a form looks like. It does not build a form.

How the Fake Form Was Proven

The field test did this in order.

  • Filled the AI's form on the live preview and clicked submit. No success message.
  • Checked Contacts twice, in the UI and through the HighLevel MCP server. Zero contacts.
  • Opened Sites > Forms. The form was not listed.
  • Clicked the form element in the builder. The settings panel read "Custom Code".

A real GoHighLevel form does two visible things a Custom Code block never does. It auto-formats the phone number as you type. It shows a success message on submit. If you do not see both, the form is decorative.

Workflow AI Has the Same Failure Class

The Workflow AI Builder documentation says it "converts natural-language prompts into end-to-end workflows". It also says, in plain words, that the AI cannot test workflows and that manual review is required before publishing.

The structure it writes is reliable. The references are not. In the same field test the generated workflow contained:

What Workflow AI wrote What the error panel said What was actually true
Trigger filter "Form is: [form name]" Form not found The chip showed the right name but held no valid form ID
Action "Add tag: keystone-lead" Referenced Tag does not exist or does not belong to this location The tag had never been created
Merge fields {{form.service_needed}} Nothing. Silent. Form fields become contact custom fields. The real tag is {{contact.service_needed}}

Two of three were caught by the error panel. The third would have shipped an email with raw merge tags in it.

What GoHighLevel Sets Up

The AI builders are worth using. They are just not the last step. Six components make them safe.

  1. A real form, built first. Sites > Forms > Create form > Start from Scratch pre-loads First Name, Last Name, Phone, Email and two A2P consent checkboxes. Why it matters: a form that exists in Sites > Forms has a real ID, creates contacts and appears in the workflow trigger picker. Example: a "Roof Inspection Request" form with a Single Dropdown for urgency built in four minutes. Impact: every later step has something real to bind to.
  2. Funnel AI in Build mode, prompted as one paragraph. Sites > Funnels > Build with AI opens the Ask AI panel. The documentation describes Assist mode as structured inputs (niche, goal, audience, tone, layout) and Build mode as free description. Why it matters: Build mode with a single flat prose prompt generated a full page in about five minutes in the field test, while the same content as a numbered list hung the pipeline in an "Analyzing website, Reproducing sections" loop. Example prompt shape: business, audience, headline, offer, sections, form fields, copy style, colours, all in one paragraph. Impact: first-generation pages that need copy tweaks, not rebuilds.
  3. The form swap. Click the AI's form, confirm the panel says Custom Code, delete it, click the empty column's Add button, choose Forms And Surveys, Add Existing Form, pick yours. Why it matters: this is the single step that turns a brochure into a lead capture page. Example: the swapped form loses the AI's card styling and gets restyled from the element's Styles tab. Impact: function first, then looks. Leads land in Contacts.
  4. Workflow AI, then the error panel. Automation > Workflows > Build using AI takes a prompt that names the exact form in quotes and describes trigger, channels, timing and actions with verbs (Send, Notify, Create, Update, Wait). Why it matters: the generated structure is correct on the first pass for the standard local-business recipe: add a tag, email the lead, email the owner. Example: "When 'Roof Inspection Request' is submitted, add the tag storm-lead, send the lead a confirmation email, send the owner an internal email with name, phone and urgency." Impact: a three-action workflow in under a minute. Then open the circled-check icon in the left rail and work the list until it reads Zero errors.
  5. Reference repair. For a phantom form: open the trigger, remove the chip, re-pick the form from the dropdown, close the dropdown before clicking Save. For a phantom tag: remove the chip, retype it, click "Add New tag" so it is actually created. For merge fields: never trust AI-written ones, insert them from the custom values picker, which only offers fields that exist. Why it matters: fixing one error often reveals the next. Impact: a workflow that fires and renders real values.
  6. The end-to-end test with a test contact. Submit the real form on the preview. Confirm the contact. Open Enrollment history and confirm the workflow fired. Open the sent email and confirm names, not {{merge.tags}}. Why it matters: the documentation is explicit that the AI cannot test. Impact: nothing goes live on hope.

Niche Starting Point

HighLevel's own Funnel AI page and no-code website builder page show what the builders produce. Start the account from the 30-day link at the end of this post rather than those pages' own trial buttons. The trial is longer and the builders are the same.

Step-by-Step Setup

The order matters. Form first means the AI's fake form is the only thing you throw away.

  1. Confirm the sub-account. Agencies run many. The URL pattern is app.gohighlevel.com/v2/location/{locationId}/dashboard or your white-label domain. Check the name in the top-left switcher before building anything.
  2. Collect brand inputs. Primary colour, accent colour, font, any rules. Do not let the AI invent a brand.
  3. Sites > Forms > Create form > Start from Scratch. Keep the pre-loaded name, phone, email and A2P consent checkboxes. Add fields from the left rail. Dropdowns are under Choice Elements > Single Dropdown. Set Label, options and Required in the right-hand panel.
  4. Edit the submit button text in the right panel's Text box. Typing on the canvas button does nothing. Use action copy: "Book My Inspection", never "Submit".
  5. Save and confirm the form appears in Sites > Forms with today's timestamp.
  6. Sites > Funnels > Build with AI. The panel opens on Assist. Click Build.
  7. Write the prompt as one continuous paragraph. No numbered lists, no line breaks. Include business, area, audience and pain, headline, offer, CTA label, sections in order, form fields, FAQ count, copy style, colours and mobile-first. Click the purple send button. Confirm the prompt became a sent bubble with parsed chips.
  8. Watch the pipeline. Healthy signals: design tokens, per-section build cards, content writing, image specs, final checks, canvas render, page auto-renames, autosave on. Hung signal: "Analyzing website" cycling with an empty canvas. If hung for ten minutes, refresh the URL and resubmit as prose. Nothing is lost if the canvas never rendered.
  9. Review top to bottom. Iterate copy in the same Build box. Open the SEO panel in the top-left toolbar and review the auto-generated title and description. The documentation says AI SEO suggestions "should still be reviewed before publishing".
  10. Swap the form (component 3 above). Retest on the preview: phone auto-formats, success message shows.
  11. Test the form for real. Submit a test entry. Confirm the contact exists in Contacts. Do this before the workflow. A workflow triggered by a dead form can never fire.
  12. Automation > Workflows > Build using AI. Prompt with the exact form name in quotes. Answer the clarifying questions if the AI asks up to three. A fully specified prompt skips them.
  13. Open the error panel (circled-check icon, left rail). Fix every phantom form, tag and merge field. Re-check until Zero errors.
  14. If the client needs a real email, not an in-app notification: in the Internal notification action set Type to Email first, then To User Type to Custom email, then the address, then write Subject and Message. Switching the type wipes the content, so set the type before writing.
  15. Test workflow with a test contact. Check Enrollment history and the rendered email.
  16. Stop before Publish. Both the funnel and the workflow stay in draft until the client confirms. A published workflow sends real messages to real contacts.

Compliance notes. The A2P consent checkboxes on the default form exist for a reason. US SMS follow-up needs A2P 10DLC registration in Settings > Phone Numbers > Trust Center before any workflow texts a lead. Email follow-up needs SPF, DKIM and DMARC on the sending domain or the confirmation lands in spam and the client reports the funnel as broken.

AI Studio note. AI Studio builds quizzes, custom booking flows and interactive apps from a chat. Its projects cannot move into standard Funnels or Websites and forms are not auto-connected there. Use Funnel & Website AI for lead pages unless the client specifically needs an interactive app.

Revenue Model

Illustrative numbers. The point is the time saved per build and what that time is worth when it is repeated.

Build step Manual, per client page With AI builders and this fix order
Page layout, copy, images Half a day to a day About five minutes generation plus 30 minutes review
Lead form 15 minutes 15 minutes (built first, same either way)
Form swap and restyle Not needed 10 minutes
Three-action workflow 30 to 45 minutes Under a minute generation plus 15 minutes reference repair
Testing 15 minutes 15 minutes

For a business owner. One page and one follow-up sequence in an afternoon, on the Starter plan at $97 per month, with a form that creates contacts.

For an agency in SaaS Mode. Say a landing page plus follow-up automation is a $500 to $1,500 setup fee on top of a $297 to $497 per month sub-account. If the AI builders cut build time from a day to two hours, the same team can onboard several times as many clients per week. Ten sub-accounts at $297 is $2,970 per month before setup fees. The setup fee stays the same. The delivery cost drops.

The margin killer. Every client page shipped with a Custom Code form is a refund, a churned client and a bad review. The fix order above costs about 25 minutes per build. That is the whole insurance policy.

FAQ

Why is my GoHighLevel Funnel AI form not creating contacts? Because the AI rendered it as a Custom Code element, not a GoHighLevel form. Click the form in the builder and check the settings panel. If it says Custom Code, delete it and add a real form from Sites > Forms through the Forms And Surveys element.

How do I know a HighLevel form on my page is real? It auto-formats the phone number as you type and shows a success message on submit. It also appears in Sites > Forms. A Custom Code form does none of these.

Why does my Workflow AI automation never fire? Usually a phantom reference. The trigger names a form that was never bound to a real ID, or an action adds a tag that was never created. Open the error panel (circled-check icon in the left rail) and fix each item until it reads Zero errors.

Can Workflow AI test the workflow for me? No. The official documentation states the AI cannot test workflows and manual review is required. Use the Test workflow button with a test contact and check Enrollment history.

Should I use Assist mode or Build mode in Funnel AI? Build mode for lead pages. Assist mode uses structured inputs, Build mode takes a free description. Write the Build prompt as one paragraph with no line breaks.

Does Funnel AI cost extra on a GoHighLevel plan? Funnel & Website AI and Workflow AI Builder are part of the platform. AI Studio has usage pricing. Check the pricing page for current plan inclusions before you build client offers around it.

Which GoHighLevel plan do I need to resell AI-built funnels to clients? SaaS Mode with marked-up rebilling of SMS, email and AI usage needs the Agency Pro plan at $497 per month. Unlimited at $297 gives you unlimited sub-accounts without the markup rebilling.

Can I try Funnel AI and Workflow AI on the free trial? Yes. The 30-day free trial through the link below gives full access to the builders, forms and workflows, which is enough time to ship one client funnel end to end and test it.

Ship the Funnel That Actually Captures Leads

Read the automation setup guide first if workflows are new to you. Then build the form, build the page, swap the form, fix the references and test.

You can do all of it in 30 days free.

✅ HighLevel 30-Day Free Trial

Claim Your Free Month

What's New in GoHighLevel

  • Sept 4, 2026, Phone System. Missed call text-back now automatically selects an eligible sending number when the originally called number cannot send SMS. If your AI-built funnel routes calls to a voice-only number, the text-back still goes out from a number that can send.
  • Sept 3, 2026, Client Portal. The user login workflow trigger now fires for logins from the new Client Portal. Agencies giving clients portal access to their funnel stats can trigger a check-in on first login.