Ad Reporting and Attribution

Like an API for LLMs, model context protocol servers ARE the future of software. Can we at least have API endpoints converted? If not even further control? MCP servers would allow us to ask a chatbot, “read my unread notifications”, “here is my email reply: …” imagine AI powered HighLevel. Already setup for Hubspot, Salesforce, Zapier, and thousands of other tech companies. Let’s go HighLevel! https://docs.anthropic.com/en/docs/agents-and-tools/mcp

way to ensure that a student watches a video. I know that I can lock a lesson until the previous lesson is completed, but currently, as student can click on "Mark as Completed" without actually watching the video.

Objective: Improve metric tracking, lead distribution, and internal communication among user groups within the platform. Current Problem: Currently, GHL only allows the addition of individual users without the ability to organize them into teams. This limitation impacts: Group Metrics: It’s impossible to analyze conversion rates, performance, or productivity by team (e.g., sales team vs. support team). Uneven Lead Distribution: Leads are assigned to individuals, not teams, which can overload some users while leaving others underutilized. Fragmented Communication: There’s no way to send targeted notifications to specific groups (e.g., alerts to the sales team about hot leads). Proposed Solution: Introduce a "Teams" feature within GHL, with the following functionalities: Team Creation Hierarchical Organization: Allow admins to create teams (e.g., "Sales SP", "24/7 Support") and assign users to multiple teams if needed. Customizable Permissions: Define access levels by team (e.g., sales team can edit pipelines, marketing team can only view reports). Team Metrics Custom Dashboard: View total conversion by team (e.g., how many leads from Team X became customers). Compare performance between teams (close rates, response times, etc.). Filter reports by team for strategic analysis. Automatic KPIs: Generate metrics like "Team Conversion Rate" or "Leads Assigned per Team" in charts and tables. Lead Distribution to Teams Automated Rules: Distribute leads evenly among team members (e.g., round-robin). Prioritize teams with lighter workloads or higher conversion rates. Assign leads based on tags or specific criteria (e.g., SP leads → SP sales team). Workload Balancing: Prevent overload by monitoring how many leads each team is handling. Internal Notifications by Team Targeted Alerts: Send real-time notifications to entire teams (e.g., "New urgent lead for the sales team"). Integrate with channels like Slack, email, or push notifications within GHL. Automated Reminders: Notify teams about pending tasks (e.g., follow-ups for unattended leads). Strategic Importance for GHL: Scalability: Larger businesses need to manage multiple teams without losing the big-picture view. Decision-Making: Team metrics help leaders identify gaps and reallocate resources effectively. Customer Experience: Evenly distributed leads are attended to faster, boosting satisfaction. Competitiveness: Platforms like HubSpot and Salesforce already offer this feature – GHL needs to keep up. Example Use Case: A marketing agency with 3 teams (Sales, Onboarding, Support) would use GHL to: Measure which team converts the most leads into meetings. Distribute 100 leads/day evenly among 10 sales reps. Send an automatic alert to the support team when a client opens a critical ticket. Technical Implementation Suggestion: Simple UI: Add a "Teams" section in the settings menu, with drag-and-drop user assignment. APIs for Automation: Allow teams to be used in workflows (e.g., "Send lead to Team X if tag is Y"). Integration with Existing Features: Link teams to pipelines, calendars, and campaigns. Why This is Urgent: Businesses are migrating to GHL for its flexibility, but the lack of team management limits its use for medium/large organizations. This feature would transform GHL into a truly competitive all-in-one platform.

When deleting a user, please add a checkbox option to reassign their leads, opportunities, appointments, etc., to another user selected from a dropdown menu. This feature is common in other CRMs and helps streamline transitions during staff turnover. You've implemented a similar approach when pausing or deleting sub-accounts (e.g., removing A2P settings), so this functionality seems feasible within the current framework. This enhancement would make user management much more efficient.

I've recorded a video that expresses an issue when it comes to booking two Users on a single apt. This would apply to physical location or Zoom. "Collective Bookings" would work for this except when I remove a one User from the appointment on the collective booking, it still references that User(s) calendar when it should only reference the User(s) that remain on the appointment. This results in unavailable time slots even though the unavailable User was removed. https://www.loom.com/share/0c2b62915dd3459bb2a7abcfe18de4be?sid=5b892894-a6f9-4400-8440-85a3eeea67db

Currently, we have only 1 true email field that allows for additional emails to be listed in it manually. There is no way to automatically put additional emails in that list, and to also automatically send workflow emails to those additional emails. To try and solve this, we created a text field that we call email 2. This way we are getting our contacts work and personal emails. (we need both because work is a government email and we deal with a lot of fire wall issues) We then use the email 2 field in workflow emails in the cc option. This creates a few problems. It creates another contact record that is no longer associated to the original contact record when an email is sent out (using the cc option). When unsubscribing there is no native way to update email 2, we have to just delete it and build a whole workflow to find the other original contact record to unsubscribe that contact record as well. There is no way to merge these contact records natively, or if they come in with another email 2 from another form, it is just going to create another contact record. You see the problem- lots of duplicate contact records and no way to easily unsubscribe these emails. Is there a way we can have another true email field, an email 2 option that isn't just a text field, and a way to compare all email fields to find duplicate contacts. This way if we have another true email field - the unsubscribe process will be easier to build.

Hello, could you implement more variety in the community points system. Right now the only way to "earn points" is through comments or likes on a post. Would it be possible to add more ways of earning points? Some ideas are; commenting on other's posts (2 points) writing a post (3 points) attending live calls or events of the community creator within GHL (5 points) This would encourage more overall engagement within communities!

The ability to send out the quiz results via email so users can keep a copy of their results

Like an API for LLMs, model context protocol servers ARE the future of software. Can we at least have API endpoints converted? If not even further control? MCP servers would allow us to ask a chatbot, “read my unread notifications”, “here is my email reply: …” imagine AI powered HighLevel. Already setup for Hubspot, Salesforce, Zapier, and thousands of other tech companies. Let’s go HighLevel! https://docs.anthropic.com/en/docs/agents-and-tools/mcp

When we create a service menu, regardless of whether our users have access to all folders or access only to the folders that concern them, they see and can modify all the service menus that exist, even those of their colleagues. It should be ensured that employees only see the menus of services to which they are assigned.