Ad Reporting and Attribution

🛑 If you're using LC Phone and relying on it for business calls, this affects you. Right now, if your SMS gets flagged (like during compliance reviews or registration issues), your entire phone number, including voice calls, can be shut down. That means you could lose the ability to call or be called by clients, even if only the texting side has a problem. This doesn’t happen with a direct Twilio integration, only with LC Phone because of how it’s built. We’re asking GHL to separate Voice and SMS, so a problem with one doesn’t take down the other. Until that’s fixed, this is a major risk for anyone using LC Phone as their main number. 📣 Please upvote if you think LC Phone should offer more protection and flexibility for businesses! Description: We encountered a serious issue that exposes a major risk for businesses relying on LC Phone as their primary phone system. One of our sub-accounts faced an SMS compliance issue, resulting in SMS functionality being disabled. However, due to the way LC Phone is currently integrated, this also disabled all voice calling features, cutting off the ability to make or receive calls entirely. After reaching out to support, we learned this is a known limitation of LC Phone, which is built as a managed solution on top of Twilio. Because of this structure, any SMS-related suspension affects the entire phone number, including voice, which creates an all-or-nothing outage. Why this matters: Business Continuity is at risk: If a company is relying solely on LC Phone for VOIP and runs into any SMS compliance issues, their phone line becomes completely unusable. This could shut down client communications unexpectedly and result in major loss of trust and revenue. Direct Twilio Integration avoids this: With direct Twilio setup, SMS and Voice services are separated, allowing one to remain active even if the other is impacted. This safeguard does not exist in LC Phone today. This forces users to abandon LC Phone: We would prefer to use LC Phone for simplicity and integrated management, but this limitation forced us to shift back to direct Twilio in order to ensure reliability for high-priority accounts. Suggested Solution: Please enable a separation of SMS and Voice services within LC Phone, or introduce safeguards that prevent total communication suspension when only one channel is affected. This could involve architectural adjustments or a feature that allows users to retain voice functionality even when SMS is disabled due to compliance review or registration delays. #LCPhone #TwilioIntegration #BusinessContinuity #TelephonyRisk #SMSCompliance #FeatureRequest #SeparationOfServices #HighImpactBug #VoiceAndSMS

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

If the SEO Meta Data hasn't changed. Then it is confusing to have that panel pop up every time you hit Publish. It feels like its been doing this at least 12 months now. Also the whole UI with the Zeros and Ones and the orange and the warnings the labels is confusing.

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.

With SaaS mode becoming a bigger part of high level, it would be helpful to have the date that populates in reporting to be based off of the date won. I don't know of many businesses that count a deal/income on the date it was created. A majority mark a sale and income on the actual day it closes. HIGHLVL-I-3371

Need to be able to show and sort subscriptions in order of date of next processed payment, and/or by customer name, not just by date created.

Every time I train a bot with a different source of information, all of the other bots in that account get the same information... It would be great to have the ability of having multiple bots each of them fed with different information not just different prompts

Currently, GHL assigns the CSS Selector, which are random characters and therefore are not good user-facing pretty URLs. Example: Original css-selector https://domain.com/#section-Y_GYP7UUA I want to change it to... https://domain.com/#about

We need to be able to edit the agency's logo and favicon independently. https://www.loom.com/share/14ca7abf7e8a414db281449ee1382966

Currently, duplicate opportunities are all or nothing. It would be great to have the flexibility to allow duplicate opportunities in chosen pipelines. This way we can have duplicate opportunities in some pipelines and not others. Or, at least allow duplicate won opportunities and not open opportunities.