SaaS Mode

Yay for supporting sales and VAT tax for rebilling, reselling, etc. at the agency level. But it needs to be implemented at the subaccount level as well since all v2 SaaS is through the agency subaccount and recent push has been to configure SaaS using the v2 SaaS in the agency subaccount.

I attached a free trial while prospects wait for their complimentary discovery call. Would be great to simply end the trial and take first payment so they get access to premium offers attached.

Ability to pull a report showing revenue generated from rebilling, such as twilio, mailgun, yext, wordpress etc.

The current Agency Announcement tool is a "broadcast" system—it’s all or nothing. If I want to send a specific technical update to my "Real Estate" niche sub-accounts, or a "Low Usage" warning to accounts with a low health score, I can't do it. This leads to notification fatigue for users who receive irrelevant messages. Update the Agency-level Announcement feature to include Targeting Filters. This would allow admins to push specific dashboard pop-ups, banners, or sidebar notifications to specific sub-accounts based on predefined criteria.

I think it would be great to offer specials/coupons for Saas plans in order to attract more users. I do believe this is something High Level is currently working on, but I'm not sure.

It would be great to be able to have the Company Name as the Location name since it currently uses a person's name and my team doesn't always know which company an account is associated with.

We are offering GHL in SaaS-mode to our German clients. The translation is very bad. We need to be able to customize the translation. We suggest offering your SaaS-clients the option to edit a data-base. The data-base should include all text-fields and we could edit the translation, then upload the correct translation. Especially Germans are very picky and in the end, it is bad reputation for us. For example, the word "back" is translated in a way, that it means the body-part. However, the translation in German is very different and cannot be translated in that way. Instrad of "Zum Rücken" it needs to be "Zurück". We hope to receive a solution for this soon. Thanks.

What we're trying to accomplish: As a SaaS Agency with multiple recurring subscription products, we need the ability to offer additional recurring products as order bumps at checkout or as one-click post-purchase upsells — without requiring a separate funnel build or manual intervention. Specific capabilities needed: Order Bump for Recurring Products at SaaS Checkout Allow a secondary recurring product to be offered as a checkbox bump directly on the SaaS product checkout page — presented before the buyer completes purchase. Currently, only one recurring product can be processed per checkout, blocking this entirely. Post-Purchase One-Click Upsell for Recurring Products After a SaaS product purchase is complete, automatically redirect the buyer to a native upsell page offering an additional recurring subscription with a single click — without requiring a custom funnel built around the SaaS checkout. Native Upsell Configuration Inside SaaS Product Settings Add an Upsell / Bump tab directly inside SaaS product settings where a secondary product can be selected, copy can be written, and redirect logic can be configured — without leaving the product builder. Multi-Recurring Product Checkout Support Enable the checkout system to process two recurring subscriptions simultaneously when a buyer selects both a primary product and a bump/upsell — billed separately but captured in a single seamless checkout experience. Skip Option on Upsell Allow the buyer to skip the upsell offer and proceed to the Thank You page without being forced to purchase the secondary product. Current workaround: Verbal pitch through Voice AI and sales team scripts during strategy calls. The checkout experience is missing the bump entirely, requiring manual follow-up to offer the add-on product post-sale. Business impact: Without native bump/upsell support for recurring SaaS products, the average order value at checkout cannot be maximized. Every missed bump requires a manual follow-up touchpoint — increasing operational overhead and reducing conversion rates on add-on products.

As a white-label agency building custom SaaS plans for clients, the current SaaS Mode configuration is too limited and creates unnecessary complexity. Here's what we're dealing with: Problem 1: Not enough granularity in the Plan Builder Right now, the Features tab only lets you toggle broad top-level categories (e.g. "Funnels", "Websites", "Workflows"). But within each of those categories, there are many sub-features — and we have no control over which specific sub-features are included or excluded in a plan. This makes it impossible to build truly tailored packages for different client tiers. What I'd love to see: A hierarchical feature control system in the Plan Builder: Level 1: Main categories (as they exist today) Level 2: Sub-categories per main category that can be toggled independently Level 3 (bonus): Specific actions or views within sub-categories (e.g. "view only" vs "edit") This would allow agencies to build precise packages — for example, giving a client access to Funnels but only the basic builder, without A/B testing or advanced settings. Problem 2: Unintended side effects at the User Permissions level When configuring permissions at the individual user level, disabling one permission often unintentionally disables other features that the agency wants the client to see and use. These hidden dependencies are not documented or visible anywhere, making it very frustrating to configure correctly. What I'd love to see: A clear dependency map or warning system: "Turning this off will also affect X and Y" The ability to override individual dependencies, so disabling one thing doesn't silently break something else Better alignment between SaaS plan-level settings and user permission-level settings, so there are no unexpected conflicts The bigger picture: Right now, configuring SaaS plans requires working across two separate layers (plan builder + user permissions) that don't always talk to each other logically. A unified, simplified configuration flow — with full granular control — would make GoHighLevel significantly more powerful for serious white-label agencies.

We’re requesting a feature that lets our admin and support teams view client accounts without having the ability to make changes. This will help them understand how clients are using our system and provide more proactive support while keeping account security intact. The goal is to enable certain team members to see important information in client accounts—like contact lists, workflows, message status, and integrations—without the risk of altering any settings or data. This visibility would allow our support team to catch issues early, such as incomplete SMS setups, and guide clients through solutions to improve their experience and retention. To make this effective, agency owners would need a simple way to assign view-only access to specific team members. By limiting access for non-technical staff, we can avoid accidental changes while still giving the team the insights they need to assist clients effectively. We recently faced an issue where an admin unintentionally made changes, which highlights the importance of view-only permissions. This feature would improve client support and reduce risk, allowing our team to handle accounts more securely and efficiently. Also if this granular permission allows us to remove certain parts of the software from agency users, such as them not being able to see contact data, or even workflows, pipeline, etc. Right Now we can enable "View & Manage" or disable it. I would like to be able to enable "View" only.