Forms

It's absolutely awful that embedded forms have no ability for us to remove the padding which can cause issues with how the forms render in other sites causing unwanted gaps in the content before and after the form, not to mention how it appears in mobile etc. Ideally we'd have a fully HTML form embed option but for some reason even that basic feature of most platforms with form building capability hasnt existed...

When using sticky contact and the name, email, and phone number is different it should create a new contact or find THAT existing contact. Instead, sticky contact feature is updating the contact information for the contact who is sticky on the browser with the new submission's information. This is a MAJOR issue as this creates a scenerio where the CRM is incorrect and it does not inform the subaccount users that this has happened. You would have to constantly monitor every conversation to be able to tell if this occurs.

This is all Y'all need to totally replace JOTFORM and the likes!

Allow forms to have multiple pages to step through. Each step can have multiple fields/questions. Allow forms to have icons as select options. See screenshot. Add a progress bar so the user can visually see how much completed and how much left to complete.

Currently, if we want to tag people who complete a certain form, we need to set up a new automation workflow. It would be great to have the ability to apply a tag right in the form options, without having to set up a whole new workflow.

It would be great to see in the custom fields settings area, where the custom field is currently integrated in a form/survey or "Update contact workflow action". This way we can check what automations would be affected when adjusting or deleting a custom field

A multi-step form similar to getleadforms.com with conditional logic and customization, like the attachments to this post, would be ideal.

Right now, we can do almost every file extension, but no videos. IMO we need this Use case: Video Review collecting.

Hi Go High Level Team, I'd love to suggest a feature that I think would bring tremendous value to users working with forms inside GHL—form abandonment tracking. Currently, there's no built-in way to see where users drop off while filling out a form. It would be incredibly helpful if the platform could offer insights into: -Which specific fields users reach before exiting the form -At what step or field most users abandon the form -The overall completion rate per form This could be integrated into the existing form analytics dashboard or introduced as a standalone feature. Even a basic version showing partial completions or drop-off rates per field would make a big difference in optimizing forms for better conversion. Thank you for constantly improving the platform and listening to user feedback. I really appreciate the work you all do and hope this suggestion can be considered for future updates!

We’ve repeatedly seen a major performance issue caused by embedded HighLevel forms — especially on mobile. After extensive testing, we identified that forms in the footer or hero section can reduce mobile Lighthouse scores by 20–30 points. Example: Our homepage consistently scored below 70 on mobile. After removing just the embedded newsletter form, the score jumped into the 90s. This aligns with issues we also had 3 years ago on a WordPress site using the same forms. The core problems include: Delay in First Contentful Paint (FCP) and Largest Contentful Paint (LCP) Render-blocking form-related CSS/JS Unnecessary third-party scripts loaded even when forms are not visible ~4–5 seconds added to visual rendering This affects not only UX but also SEO and conversion rates. The desktop performance remains high, so this is clearly a mobile-specific bottleneck. 🟠 Suggested Improvements: Lazy load forms only after interaction (e.g., click or scroll) Defer all form-related JavaScript (e.g., libphonenumber, intlTelInput) Avoid loading hidden forms during initial paint Reduce bundle size by loading only necessary input types Please prioritise this — we’re seeing this across multiple websites and it’s harming performance out of the box.