SaaS Mode

The current billing behavior for Agency SaaS subscriptions halts all subsequent invoicing and payment attempts immediately following a single failed or missed monthly payment. When a client resolves the single outstanding missed invoice (e.g., paying November's invoice on December 9th), the system recognizes the account as "current" but fails to generate or process invoices for any intervening missed months (e.g., December's payment, which was already due). Example: * November 1: Payment failed (Card expired). * December 1: The system DID NOT generate an invoice or attempt payment for the December subscription fee. * December 9: The user paid the outstanding November invoice. * Result: The system marks November as paid, but December's invoice is permanently skipped. The system then reverts to the original schedule, sending the next invoice on January 1st. This behavior results in immediate revenue loss for the Agency and requires manual reconciliation and invoicing for every missed month, undermining the core function of automated SaaS billing. Intended Behavior: The system must operate with a cumulative billing logic standard for all subscription platforms: Maintain Schedule: All future scheduled subscription invoices must continue to be generated and added to the client's ledger, regardless of the status of previous invoices. Cumulative Payment Attempts: Once the client resolves any single past-due invoice, the system should immediately generate and/or process all subsequently due, but unpaid, monthly invoices. Correct Status: If a client is one month behind, the system should show two invoices due: the immediate past month (e.g., November) and the current month (e.g., December).

This new feature seems pointless at the moment. It says you can manage Saas products & subscriptions but you cant. I followed this setup process and created the new saas product inside the agency sub-account. But the following issues/improvements need to be in place asap for this feature to be worth it. When inside the agency sub-account and applying the saas subscription to the contact (inside payments tab)... The "saas" subscription does not apply any saas settings or saas plan to the sub account that the contact is related to. Therefore any rebilling settings is also not being applied. When applying the saas subscription from the sub account level it should automatically active saas mode and update the sub account information the exact same way it does when applying from the agency level. Also if you apply the saas plan from the agency level, you cannot schedule this for a future date and only option is to charge immediately. This also would be a great fix and better improvement to the feature. As we dont charge upon account creation and only charge on a certain day of the month. Being able to schedule saas mode plans for a future date will be a game changer for us. Also separately i great improvement to the subscriptions would be to enable pro-rate charges the same way Stripe does. This will allow us to chose a specific recuring billing date but charge a pro-rate amount for any usage before the billing date comes. Hopefully this makes sense.

It would have been nice for the team to prioritize Sub-Account Self Upgrade FIRST for v2 SaaS plans - as opposed to prioritizing Sub-Account Self Cancellations. This needs to be realized and priortized first prior to other non-Agency (Premium) features as Agency owners we pay a premium of $497+ per month.

In the last 2 months, the app has been completely inaccessible for both us and all our subaccount clients, for 15-30 minutes. In the current downtime (just fixed as I was writing this), even forms on clients' pages weren't loading. Needless to say, this is extremely problematic because with tens of subaccounts, our support inboxes get overcrowded and we lose several clients if this happens frequently. Making the app run without hiccups is more important than any feature. Please prioritize this so that it doesn't happen.

When our clients order our SaaS product, they are required to do 2FA to login. Then they get this GHL-branded email, in spite of use being white label agency. Please make this system email generic, or enable us to edit it......READS.....Hi, Thank you for choosing HighLevel. Use the following verification code to verify your email address. 940932 Thanks HighLevel Team

Right now if a user in SAAS mode has an LC Number and the auto recharge activated, it will keep paying monthly fee also if the subscription has been cancelled and the account has been paused. This is huge, people get mad at us

I cannot currently change my account to saas mode because I have to charge each user/subaccount fees. I already roll into the clients monthly service fee the cost of software(GHL). I don't want to stop this option and I don't want to charge certain clients their saas fee. We should have more control over what we can charge clients if at all. I have plans for saas but can't do it because each of my clients would have to be billed for the software they are already on. This is a huge oversite and needs to be fixed up asap. Asking a customer to pay for a service and then pay separately for the software leads to a huge can of worms - "I want to switch this for this", "Can we use click funnels instead GHL", "can we use something cheaper". This is not the kind of customer service I promote.

When a new SAAS client signs up, the Stripe client name is auto generated using the First and Last name instead of the company name. We should be able to use the Company name.

Please add an "other" category on this site since we are forced to choose a category of where to place our feedback, and there was no place for me to put this comment since you need an "other" category since there wasn't a "canny feedback" category, so you are forcing me to put it in the wrong one.

Deleting cookies and clearing site data SOMETIMES fixes the issue but often it does not and we have to wait a few days and try again before we can access sub-accounts. Tech support is aware of this but we unable to tell us if a fix was in the works. We've replicated the issues in 3 browsers - Edge, Brave and Chrome