CRM

Dear GHL Development Team, I am writing as a partner with significant business experience and a vertical focus in the B2B sales sector. Our community of professionals and agencies agrees that, while GHL is an exceptional platform, its current CRM implementation represents a critical bottleneck for managing complex and professional sales processes. The current structure seems more geared towards mass acquisition and is not optimized for the Consultative Selling typical of B2B. 💡 The Need: HubSpot-aligned CRM Architecture for Professional Selling To transform the GHL CRM into a truly professional and high-performing tool for B2B, we strongly recommend adopting a data and management architecture similar to that offered by industry-leading platforms such as HubSpot. 🎯 Key Proposed Improvements: Simplified and Interconnected Data Management (Contact ↔ Company ↔ Opportunity): Contact (Lead/Person): The individual. Company: The legal entity. Opportunity (Deal/Affair): The object of the sale. Fast and Bi-directional Association: The ability to quickly create and associate a Contact with a Company and simultaneously with one or more Opportunities (and vice-versa), with a clear and immediate view of all relationships. Benefit: Allows B2B sales teams to track the complex decision-making journey within a company (multiple stakeholders). Complete Data Customization (Custom Fields): Mass Customization: All data fields (Contact, Company, and Opportunity) must be fully customizable (Custom Fields) and not constrained by predefined lists, to adapt to any market vertical (e.g., company size, industry sector, estimated budget). Benefit: Transforms the CRM into a flexible system, capable of modeling data exactly as required by each company's unique sales process. Optimization of View and Speed of Use: The User Interface (UI) and User Experience (UX) must be optimized for speed and clarity. Information entry, modification, and consultation must be frictionless, allowing the salesperson to dedicate more time to selling and less to data entry.

Custom fields in GHL only support static text options. We need the ability to create dynamic dropdowns populated from CRM data — such as contacts, companies, or tagged records. This would allow Opportunities to reference vendors, partners, staff, or any other CRM record without manually updating lists. Dynamic custom fields would massively expand CRM functionality and reduce the need for middleware or manual maintenance.

HIGHLVL-I-2827

Currently the date format is set to MM/DD/YYY automatically and can't be changed, so it is annoying looking at the American format within sub accounts that are not American businesses and there's nothing we can do to change it but it is a simple fix.

I would like to see if we can get at least 3 months of logs in the workflows, audit logs, activity timeline, quiz/form/survey submissions, web logs, etc. since we have recurring bookings sometimes and there's a lot of customer activity. It is difficult to troubleshoot errors, booking failures without accessing logs beyond a month. For an issue that came out a few days ago, we needed workflow logs for October the 18th and they were only available from November the 16th (i.e. the last 30 days). Some customers book their workshops well in advance, not just less than a month, and it's important that we have the required info to understand what happened back then and troubleshoot issues along their journey to provide a better service.

Currently, CSV exports seem to be in the ANSI format which is outdated and doesn't support other languages or special characters. This causes any CRM data in other languages or special characters to show up as complete gibberish in the CSV. The modern standard is UTF-8, which supports other languages and special characters. There's no reason CSV's should be using the old ANSI standard.

I’m actively building systems using Custom Objects and Object-Based Workflows (Beta) and wanted to submit a feature request related to number fields. Current behavior: In object-based workflows, when updating a Number custom field (including on associated records), the workflow action only allows setting a static value or inserting a variable. There is currently no option to: increment decrement perform basic arithmetic (e.g. +1 / −1) This applies even when updating number fields on associated custom object records. Impact: This limitation makes it impossible to support common real-world use cases such as: Tracking counts of associated records (e.g. active enrollments per student) Maintaining balances or totals without external systems Enforcing “ANY / ALL” logic patterns when aggregation is not available As a result, builders are forced to choose between: unsafe temporary state changes, or manual processes that reduce automation value Requested enhancement: Allow object-based workflow actions to support basic arithmetic operations on Number fields, such as: Increase by X Decrease by X Set value using simple expressions This could be scoped initially to: Number fields only Object-based workflows (Beta) Same-record or associated-record updates Even limited support (e.g. increment/decrement by 1) would unlock many important automation patterns and significantly improve the viability of Custom Objects for production use.

Hi HighLevel Team, I’m currently building production templates using Custom Objects and Object-Based Workflows (Beta) and have run into a limitation that affects real-world usability. Current behavior: In object-based workflows (e.g. Enrollment-based workflows), the custom variable picker only exposes fields on the triggering object. Fields from associated custom objects (e.g. Student, Program) are not available in the variable picker, even though the associations are properly configured and usable elsewhere in the UI. Impact: This prevents common, expected use cases such as: Auto-naming records using associated object fields (e.g. Student Name – Program Name) Building dynamic notifications that reference related object data Creating clean, automated workflows without brittle workarounds or manual steps Requested enhancement: Expose associated custom object fields in the workflow variable picker for object-based workflows, similar to how related Contact / Opportunity fields are accessible in legacy workflows. Ideally: Associated objects appear in the variable picker Fields are scoped to valid associations This would significantly improve adoption of Custom Objects and allow builders to ship cleaner, safer automation without relying on manual naming or external systems.

It would be nice to be able to attach a photo or document to the notes. for example, upload a screenshot

We have Mailgun selected as the primary email provider for our sub-account. When we connect two-way sync to our Gmail accounts, emails sent to clients are delivered through LeadConnector instead, and this causes issues with responses not reflecting in the conversation/email thread.