Opportunities & Pipelines

Description Within Opportunities, it is possible to book calendar appointments. However, not all calendar types work correctly. When using the calendar type “Service Booking,” it is not possible to select the dedicated service person during appointment creation. Problem: For Service Booking calendars, the service person selection dropdown is missing The assigned service person is selected randomly by the system Users have no control over which service person is booked Expected Behavior: When booking a Service Booking appointment from within an Opportunity: A dropdown to select the service person should be available The selected service person should be explicitly assigned to the appointment Behavior should be consistent with other supported calendar types Actual Behavior: No service person dropdown is shown Assignment happens automatically and unpredictably This makes Service Booking calendars unusable within Opportunities (if the service person wants to book the appointment for him/herself) Impact / Use Case: Service Booking calendars cannot be reliably used in Opportunities Users must leave the Opportunity view to book appointments correctly This significantly degrades the user experience and breaks sales workflows Adds friction, context switching, and increases the risk of booking errors Proposed Solution: Add a service person selection dropdown when using Service Booking calendars inside Opportunities Ensure consistent behavior across all calendar types Alternatively, allow configuring a required service person or a deterministic assignment rule it would be also beneficial to show the appointment owner for any kind of appointment at that place (there is enough room) Quick Fix (pragmatic part fix): Apply convention over configuration: only service team members should book meetings intended for themselves. If no service person is explicitly selected, default to the booking user if they are part of the service booking team; otherwise, fall back to a random assignment.

Use case: I have contact fields named Connection Date, Connection Date 1, and Connection Date 2, which also exist as fields in the opportunity record. When a date is added to a contact, I want it to automatically reflect in the corresponding opportunity fields through the “Update Opportunity” automation. However, the update is not occurring as expected.

No way to create the reason for the lost lead... (missing)

When adding dynamic text to a trigger link URL (name, booking notes, another custom field, etc.), any "&" in the appended text breaks the query string and cuts off everything after it. It would be very helpful if GoHighLevel automatically encoded ampersands as %26 so parameters are passed correctly to the browser. This would prevent broken links and make trigger links more reliable when handling user-generated text. Right now we have to create a second custom field just to convert and store the encoded text for this query string. PS: Every other symbol is getting encoded correctly right now.

I’ve identified a permission inconsistency between the GHL web version and the LeadConnector mobile app. 1) When “View & Manage Tags” is turned off in user permissions, agents correctly cannot edit or remove tags inside the LeadConnector app, but they are still able to edit or delete tags when logging in through the GHL web platform on a laptop inside the Opportunities section. This behavior should be consistent across both platforms, and disabling tag management should prevent tag editing everywhere. 2) There is also a second inconsistency involving ownership changes. When an agent is the owner of a lead, the web version correctly prevents them from changing the owner based on the role’s permissions, but in the LeadConnector app the same agent is still able to change the owner of the lead. The permission enforcement should match on both platforms. Please help investigate these discrepancies.

"Opportunity Update" - Aesthetics expand the overall window height 1 line so the opportunity change can be displayed without having to hit "view more" EVERY single time....

In any workflow or SMS templated message, put {{opportunity.lead_value}} and notice that it renders as plain text (if you enter "3000" in the Opportunity, it'll output as "3000") Since Opportunity Lead Value is a monetary value, it should output as such, just like a custom monetary field would output as currency: $3,000.00 I understand a workflow could use Number Formatter, but SMS/Email Templates cannot. And simply adding a dollar sign in front in the SMS Template would output as $3000 without commas or decimals - inconsistent from a monetary custom field on Opportunities. Here's a video: https://share.zight.com/xQuQY62e Ticket# 1883544

When you close the left sidebar, the opportunities window doesn't expand to include the whole screen.

My client is a wellness clinic with parent/child and husband/wife sharing the same email address and phone numbers. Unfortunately, I cannot add two different opportunities with these same fields... it merges them. If i choose duplicate contacts, instead of create a cohesive customer journey in our pipeline view, it continually adds new leads along the journey. This is obviously no good as well. I need this addressed immediately as I will have to take my client off and build on another platform if we cannot have this feature. too many people are under the same email and phone number in the system. I've been working on this system for 4 months now and am pretty worried about this finding in the last moments before we fully launch.

Currently, invoices, transactions, and estimates only appear in the Opportunity Card if they were created from the Opportunity Card itself. However, when payments are processed from other areas like the Payments or Contacts tabs, they don't sync back to the associated Opportunity Card — even when the contact and opportunity are clearly linked. Can we ensure all related payment activity, regardless of where it's initiated, is automatically reflected in the Contact's Opportunity Card?