Courses

Currently, we have to upload a video every time we want to add it to a course or membership. We need to be able to add a video by adding the Media Folder Hyperlink or be able to select it from the Media folder.

Instead of just drip using days, have categories/posts on memebership sites locked until the user has completed the ones prior. This makes more logical sense for Membership Sites that are for Training courses. HIGHLVL-I-3121

Currently, when a student comments on a course lesson, the instructor only receives a single in-app notification. If this notification is missed or cleared, there’s no way to view comment history or know where the comment was made. Requested enhancements: Persistent Comment Activity Feed – a central area (within Memberships or Conversations) showing all recent course comments with links to the specific lessons. Email Notifications for New Comments – ability for instructors to receive email alerts whenever a student leaves a comment, ideally with comment text and a direct link to the lesson. (Optional) Workflow Trigger: “New Course Comment” – allowing automation of custom notifications (email, Slack, etc.) when a comment is posted. Reason: Improves engagement tracking and instructor responsiveness by ensuring comments aren’t missed once the initial in-app notification disappears.

We need to have video watching analytics that tell us: If a video was played at all by a student How long it was played by a student Where the video was stopped by a student How many times it was played by a student (i.e. repeat watching) Not having any analytics data on videos in a course is a major oversight and needs correcting asap.

Give course owners the flexibility to allow course students to download course videos straight from the course portal player.

Allow the ability to display all courses for sale inside a membership. If someone clicks on a product thumbnail and they've already purchased, they get access. If they haven't purchased, the order form pops up so they can buy and then unlocks the product. This is especially important for Bump Offers.

I would like the ability to host podcasts directly inside GoHighLevel and publish episodes across all major podcast platforms — similar to RSS.com and Kajabi. Key Needs: • Host and manage multiple podcasts inside GHL • Upload or record audio, add show notes, episode titles, and artwork • Auto-generate an RSS feed and distribute with one click to: Spotify, Apple Podcasts, Google/YouTube Podcasts, Amazon, and more • Embed a customizable podcast player on funnels, websites, and memberships • Allow public or private podcasts (great for paid programs) • Basic analytics: downloads, listeners, platforms, retention

I notice when building a website, colour palettes and image library are available for each new page. But when creating a funnel for the same account, the colour palettes and images don't cross over so need to find to recreate for each page. Same goes for membership site and products and offers. Could we have a function in each client account where brand colours and fonts and images are always available once created in once place and made available in all places. HIGHLVL-I-6032

PROBLEM: When a contact sends a file attachment (image, PDF, document) via WhatsApp during a Conversation AI interaction, there is currently no way to automatically store that file in a File Upload custom field on the contact record. The only available method is manual: staff must click the three-dot menu on each message and select "Add to Documents." This is not scalable for businesses processing high volumes of document-based workflows such as recruitment, insurance, lending, real estate, or healthcare. USE CASE: We run an overseas recruitment agency. Candidates send their passport photo via WhatsApp to our Conversation AI bot. The bot can already read the image and extract data from it using Image Response. However, we cannot automatically save the actual file to the contact record for compliance, audit, and document management purposes. Our current workaround requires staff to manually download and re-upload every passport image, which defeats the purpose of automation. PROPOSED SOLUTION: Option A — Bot Action: Add a new Bot Action type called "Save Attachment" that allows the Conversation AI bot to automatically save incoming file attachments to a specified File Upload custom field on the contact record. Option B — Workflow Action: Add a new Workflow Action called "Save Incoming Attachment to Custom Field" that triggers when a Customer Reply contains a file attachment, and automatically uploads it to a designated File Upload custom field. Option C — Workflow Trigger Filter: Enhance the existing "Customer Reply" trigger with a filter for "Message contains attachment: Yes/No" and provide the attachment URL as a usable custom value that can be passed to a File Upload custom field via an Update Contact action. Any of these options would close the gap between receiving documents via WhatsApp and storing them in the CRM without manual intervention. WHO BENEFITS: Any business that collects documents from contacts via WhatsApp: recruitment agencies, insurance companies, real estate agents, healthcare providers, legal firms, lending companies, and service businesses requiring signed documents or ID verification. ADDITIONAL CONTEXT: The GHL API already supports uploading files to File Upload custom fields (POST endpoint with buffer). The infrastructure exists — it just needs to be exposed as a native Workflow Action or Bot Action so users can automate the process without relying on external tools like Make or Zapier.

Please create an affiliate notification webhook feature whereby the affiliate can be programmatically notified about new leads and sales via a webhook. Please also allow affiliates to add additional tracking IDs (&tid=[whatever] to the end of their affiliate links to be able to track their individual traffic sources or media. This way, affiliates can immediately and programmatically see which of their marketing efforts are working and which are not. Perhaps allow the sub-account owner to decide whether to include personal customer data in the payload that's included in the (or not).