CRM

It would be fantastic to have the capability to add attachments (such as photos or doc files) to the notes and make this section more feature rich.

If someone came from Instagram, where does it link me to view their profile? Support Ticket# 6152089 confirmed that it does not: > When a contact comes from Instagram Lead Ads, their source is tracked in HighLevel, but we don't store or link directly to their Instagram profile URL. Here's where you'll find the Instagram connection info: > Open the contact's detail page (like the one you linked) and scroll down to the Contact Information or Source section — you'll see "Instagram Lead Ads" listed as their source. This tells you they came through that channel, but HighLevel doesn't pull in a clickable Instagram profile link automatically. > If you need to reach out to them on Instagram, you'd typically use the phone number or email captured in the lead form to search for them manually on Instagram, or reference any Instagram handle they may have provided in the form fields.

Just an idea that could really speed up workflow for people who like working with CSS (aka me lol)... Right now if we want to apply global CSS across all funnel pages, we either have to: Use the Custom CSS block inside the builder - but that only affects one page at a time. So if I have 10–15 pages... I gotta go back and forth, copy-paste, repeat. Not super fun Or paste CSS in the Body tracking code box - which works, but it’s just a plain text area. No syntax highlighting, no structure... not super friendly to edit/manage if have long codes. What would be awesome: Add a “Global CSS” section under Funnel Settings (right below the “GDPR Compliant Fonts” toggle maybe?) (Check screenshot below) This would be a dedicated code editor like the one inside the builder (dark theme, syntax highlighting, etc.) Plus, add an “expand” icon (like in the screenshot) inside the Global CSS editor. When clicked, it should open a popup editor — dark mode, syntax highlighting, full-screen mode, same experience as the page-level Custom CSS. Cuz' editing 100+ lines of CSS inside a small textbox? Not fun Styles should apply across all pages in that funnel And support CSS variables in the builder like fonts, padding, colors, background, margin, height, width and all CSS properties, so we can write stuff in Global CSS like: Code Syntax Ex: :root { --primary: #f8ff00; --secondary: #3ad59f; --cta-gradient: linear-gradient(90deg, #f8ff00, #3ad59f); --width: clamp(3rem, 3.824vw + 1.776rem, 7rem); --font-family: 'Outfit'; } Then, reuse those anywhere with var(--primary) or even clamp() properties in the builder. It would apply styles across all funnel pages automatically. We will have one source of truth to edit anything. This will save a ton of time, reduce duplicate work, and make global design changes so much easier. Way more scalable than managing styles per-page. Would love to see this added! 🙏

I'd like for notes to show up in the conversation thread the same as internal comments do, as well as have them customisable like sticky notes, colours, styled, etc. Additionally, have the ability to do so via API

Imagine if Opportunities view and Conversations view had a baby. Then their baby had a baby. Merge Conversations and Pipelines into One Unified Workspace Conversations and Opportunities often represent the same customer interaction, but HighLevel currently treats them as separate systems with independent statuses. Users recreate the Conversations inbox inside pipelines because they need visible stages, drag-and-drop organization and additional opportunity information. Pipelines, however, lack the simplicity and familiarity of an inbox. Could HighLevel treat Conversations and Pipelines as two views of the same workspace? Proposed views: Inbox: Optimized for reading and replying, with Unread, Recent, All and Starred filters. Pipeline: The same contacts and conversations organized into customizable stages. Split: Pipeline stages and the selected conversation visible together. Shared functionality: • Conversation status and opportunity stage become one shared, customizable status. • Moving a pipeline card changes the stage shown in Conversations. • Changing the stage from a conversation moves the pipeline card. • Inbox cards display opportunity value, stage, source, assignment and other pipeline information. • Pipeline cards display unread status, starred status and the latest message. • Opening a record from either view displays the same conversation, contact and opportunity information. • Unread and Starred remain message indicators, not separate workflow stages. • Starred conversations remain visible in the inbox until manually unstarred. • Global Unread and Starred counters remain visible in the navigation or header throughout HighLevel. The recently added conversation slide-in within Opportunities is a strong first step. Combining these areas into one workspace would eliminate duplicate statuses and reduce the workflows currently required to keep Conversations and Opportunities synchronized. The attached UI concept shows how the Inbox and Pipeline views could share the same records, stages and conversation information while preserving the important functionality of both areas.

Debriefing and reusing emails are made unnecessarily difficult: Allow changing email name after it was sent. Show subject line AND subheader in stats. Allow clone email and turn it to A/B test easily. Allow changing the order in past email view. Allow Save email as template (in one click)

I am loving GHL - but it is painfully slow to navigate around. Is there anything we can do to get it to speed up?

Ability to Customize Additional Phone Number Names (I.e. Work, Home, Mobile, etc.)

We miss the ability to have multi line support for custom values. Maybe let us choose between a couple of different formats when creating the custom value?

What we're asking for: Bold/italic and background color options at the individual field level, set once in the field editor (Settings → Custom Fields), similar to conditional formatting in a spreadsheet. This reuses infrastructure you already have. Bold/Italic/color-picker controls already exist in your text editor toolbar and the unified color palette shipped for the funnel/website builder — this is applying that same, already-built control set to field labels, not building a new formatting engine. What this is NOT asking for: Not a rich-text/WYSIWYG editor per field, and not conditional/rule-based formatting logic — just a manual bold/italic/color toggle set once per field. Impact: a visual cue lets a rep spot the field that matters at a glance, without breaking eye contact or conversation flow to read every label.