SaaS Mode

The Courses/Memberships API has two distinct but equally critical problems: missing functionality and missing documentation. Both need to be addressed — ideally as part of API v2. 📋 Problem 1: Existing endpoints are undocumented Through direct API testing, we confirmed that several course endpoints actually exist and respond correctly — but are completely absent from the public API documentation. Developers relying on the official docs have no way of knowing these endpoints exist: PUT /membership/locations/{locationId}/products/{productId} — Updates a course ✅ works, ❌ undocumented POST /membership/locations/{locationId}/assessments/quiz — Creates a quiz ✅ exists, ❌ undocumented POST /membership/locations/{locationId}/assessments/assignment — Creates an assignment ✅ exists, ❌ undocumented GET /membership/locations/{locationId}/assessments/quiz/assessmentStatus/location/submission — Lists submissions ✅ works, ❌ undocumented Undocumented endpoints are functionally invisible to external developers. A complete, accurate, and up-to-date API reference for all Courses/Memberships endpoints is urgently needed. 🐛 Problem 2: Bug — Video URLs not imported when creating lessons When creating a lesson via API and passing a video URL, the video is frequently not loaded and the field remains empty. This is a confirmed bug that makes automated course creation unreliable and largely unusable in production. 🚫 Problem 3: Missing — Student progress & completion endpoints There are no API endpoints to retrieve a contact's learning progress. This is the single biggest gap for marketing automation use cases: GET completed lessons per contact & course GET completed categories/modules per contact & course GET overall course completion percentage per contact POST/PUT to manually set lesson or module completion (e.g. for retroactive data migration) Without these, it is impossible to build automations based on actual student learning behavior, trigger personalized email sequences, or retroactively tag contacts based on completed lessons. 🚫 Problem 4: Missing — Analytics export in Member Analytics The Memberships Analytics UI shows per-student progress (completed lessons, categories, products) but offers no export functionality whatsoever — no CSV, no download, nothing. This forces manual data collection and makes Smartlist-based automation impossible for existing students. 🚫 Problem 5: Missing — Course progress as native Smartlist filter Contacts cannot be filtered by course progress in Smart Lists. Required filters: "Has completed lesson X" "Has completed module/category Y" "Course completion ≥ N%" 💥 Business Impact For businesses running multiple courses (e.g. health academies, coaching programs), these gaps make it impossible to: Build course content programmatically via API Trigger personalized follow-up sequences based on actual lesson completion Segment students into meaningful Smart Lists Integrate the CRM with external LMS systems or content pipelines Migrate or retroactively set student progress data The most critical use case — and the one that directly drives platform revenue: A course priced at just €1 is designed as a high-quality entry point to build trust and demonstrate value. The strategy is simple and proven: guide students through every lesson → use completion-based triggers to send personalized encouragement and follow-up emails → convert engaged, satisfied students into buyers of the next, higher-priced course. This funnel cannot be built without lesson-level progress tracking and automation. The result is lost upsell revenue — not just for individual businesses, but across every agency and sub-account on the platform. Delivering these features would directly strengthen the platform's reputation as a serious, full-featured course and membership solution — making it significantly more attractive to new agencies and their clients. Courses that are consumed fully, and students who naturally progress to the next offer, are the most powerful proof of platform quality. ✅ Our Request Publish complete API documentation for all existing Courses/Memberships endpoints immediately — this costs nothing and unblocks developers today Fix the video URL import bug in lesson creation Add student progress endpoints (read + write) in API v2 Add CSV export to the Member Analytics UI Add course progress as a native Smartlist filter Please treat this as a combined Feature Request + Bug Report and prioritize items 1 and 2 as quick wins that can be delivered independently of API v2.

The Problem: Currently, the Agency AI Suite Usage dashboard provides an incomplete picture of platform activity. The top-level summary cards only aggregate "pay-per-use" data, completely ignoring free usage (e.g., Summer of AI transactions). While this free usage is visible row-by-row in the table below, it is not calculated in the totals. Furthermore, agency owners are effectively locked out of analyzing their own data because: ❌ There is no "Export to CSV" button for the transaction list. ❌ The UI prevents selecting and copy/pasting all rows beyond the visible viewport. ❌ Custom date range selections have an active bug (selecting a date offsets to the day prior). The Business Impact: As agency owners scaling AI, we cannot manage what we cannot measure. Being blind to our actual total token usage and transaction volume across all sub-accounts prevents us from forecasting future costs, managing client capacity, or building our own internal analytics. If the dashboard cannot calculate the combined total of free + paid usage, we at least need the ability to export the raw data to calculate it ourselves. The Solution (Actionable Feature Requests): ✅ Comprehensive Summary Cards: Update the top-level metric cards to display Total Usage (calculating both Paid + Free combined), or provide a simple toggle/filter so we can easily switch between them... like the ones in the bottom half where the table is. ✅ Universal Export Functionality: Add an "Export All" button to download the full transaction log (including all metadata and sub-account details) so we can utilize our data externally. ✅ Global Filtering Alignment: Ensure the filters (Mode, Status, etc.) apply uniformly to both the summary cards at the top and the transaction list at the bottom. ✅ Fix Date Range Bug: Resolve the UI timestamp parsing bug where selecting a specific custom date automatically marks the day before. Summary: The AI Suite Usage tab is currently a half-baked feature. We need full data visibility and data ownership to properly operate and scale our SaaS businesses. Please prioritize giving us access to our complete numbers.

We are not able to change the payment cycle on our SaaS subscriptions anymore. Please fix this bug. The only way to change the payment cycle now is to take the account off of SaaS mode and creating a new subscription in Stripe that is connected to nothing. Or. Cancel the current subscription, suspending the account. Let the client make a completely new subscription through SaaS, which automatically creates a new account. What the Actual Fuck.

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.

If a user is upgrading to annual billing the system will still only charge monthly VAT amount in Stripe! (not sending correct VAT amount/parameter). Same problem when users upgrades/downgrades to another plan - GHL still sends the original (first) VAT amount even if plan is changed!

Once these are switched on you can't turn them off. As an agency we need to be able to turn these off as default. Having to go and do them individually is extremely unprofessional. As agencies we should be able to choose what work for our clients and not have GHL choose for us. The only assumption I can see, is that GHL makes money from these features. At the moment we have to go into every trial and disable the features which is crazy considering the platform is supposed to automated for our clients yet we have to do things manually??

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.

When using the Voicemail Detect feature on a Call action, if the customer phone's voicemail answers, the call is considered complete even when Voicemail Detect is turned on. This seems to be happening specifically for numbers where the voicemail has an "announce" feature or may be a VOIP system. Either way, my client has more dropped leads than successful workflow completions due to this feature not working as documented. in the Help. https://help.gohighlevel.com/support/solutions/articles/155000003274-workflow-action-call Please fix asap!

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).

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