SaaS Mode

I recently had a SaaS client cancel their sub-account subscription - this all worked fine and rendered their account inaccessible. However, what neither of us realised was that they would continue to be billed for WhatsApp and other add-ons they had purchased. Since they had cancelled their sub-account, they could no longer log in to cancel their add-ons without restarting their subscription. Instead, I had to cancel everything on their behalf from my agency level. It would be intuitive that if someone cancels their sub-account subscription, it cuts off all other add-on payments.

Allow an agency to default Offer WordPress reselling to No, instead of having to turn it off manually on each location.

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

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.

Have a way set up for when sub accounts cancel their subscriptions to make them authorize to release all of their phone numbers and have the numbers automatically released. Currently when they cancel their phone numbers remain and still received inbound calls/texts which results in a charge - then results in us getting a complaint or a dispute.

Right now in SaaS Mode we can rebill things like emails, SMS, calls, and other usage with a simple multiplier. That’s great, but it doesn’t match how most SaaS plans are actually sold. Feature request: Add the ability to set included usage + overage pricing and optional caps for each rebillable item. Example: My SaaS plan includes: 10,000 emails / month 2,000 SMS / month After that: Emails rebill at my chosen multiplier (e.g. 1.3x cost) SMS rebill at my chosen multiplier (e.g. 1.5x cost) Optional: Set a hard or soft cap (e.g. stop sending at 25,000 emails OR notify + continue billing) Why this matters: Lets agencies sell real, modern SaaS plans (“includes X, then pay per use”) instead of only pure pass-through markup. Protects margins by charging for true heavy usage instead of eating the cost. Avoids underpricing “power users” while still letting normal users stay within plan limits. Works perfectly for: Emails SMS Calls / minutes AI usage Any other metered resource GHL supports Key controls needed: Per-resource included amount (per month / per billing cycle) Per-resource overage multiplier or per-unit price after the included amount Optional usage cap: Hard cap: stop usage Soft cap: warn + continue and bill Reporting so we can see: Included vs overage usage Overage revenue per sub-account This would make SaaS Mode far more flexible and would align GHL pricing with how agencies package and sell their own SaaS bundles.

When users choose to downgrade their SaaS plans, if the new plan doesn't include things like Conversation AI or the Chat Widget, those features should be disabled upon downgrading (especially making the chat widget inactive without manually removing the code) so that they truly have a downgraded plan. Agency users or Admins should be able to see all of the features when logged into a subaccount even if the users cannot. For example, if we do not want to give users access to Domains, but our agency wants to purchase one for them on their behalf, we cannot have it disabled in the SaaS configurator otherwise agency users cannot see it either. Having a "not visible to users" flag on certain options might help make this more obvious if this feature us rolled out, but it makes downgrades difficult. Also, having some option to turn off certain workflows or other features upon downgrading would be nice too, but might be more difficult to manage.

To reconcile the Lead Connector costs to the Agency to what is being rebilled (set by the Rebilling Settings Category Multipliers) to the sub-accounts, today it takes two reports and tons of data fixing because of bugs and inconsistencies in the reporting. Setting the bugs and inconsistencies aside (see below), adding a few more columns to the ADTR relating to the Sub-account Detailed Transaction Report (SDTR) would be a quick fix, so just the ADTR could be used. Sub-Account Data – Must have fields from the SDTR: 1. Amount 2. Rebill Settings Category (currently, it’s loosely in the description. It is needed by itself) Example data: a. Phone System Resell Settings b. LC - Premium Triggers & Actions c. LC Email Verification d. Funnel AI e. Etc. 3. Rebill Settings Category Multiplier - adding Amount in the report, we could calculate this value by “amount/originalAmount”, but having the actual multiplier used in the transaction would be preferred. Nice to have, but not needed to reconcile the data - it would be a complete combination of the ADTR and the SDTR: Sub-Account Data: • walletCredits • totalBalance • balance • creditsUsed • discountAmount Bugs and Inconsistencies 1. The “originalAmount” column has positive and negative numbers. They should all be negative. 2. Every transaction needs a ref: {ID} in the description. The “description” column is a key to the corresponding re-billing transaction in the SDRT. It uses ref: {ID} to create a unique key. However, many transactions are missing the ref: {ID}.

Currently the pause account doesn't stop workflows so if someone cancels or has a billing issue there messages will still be auto sent thus incurring more charges to the sub-account user and the agency. Seems the workflows all need to pause when there is a billing issue or cancellation. Same with domains, why would there funnel/website still work when they haven't paid or cancelled? This should be part of the pause of a sub-account, just like any other web/funnel builder has

I sell white label subscriptions of GHL and then offer services such as building smart websites, AI Agents, etc. However, I had someone purchase an AI Agent for a fee, but they were not subscribers, and I had to refund their money. Is there a way to verify they are subscribers before letting an order go through for an add-on?