Contacts

Currently you can delete unused custom fields one at a time. However, there is a select option, but when you select multiple custom fields to delete, the delete function disappears and the only option is to move them into another folder (Contact Info, General Info or Additional Info) Surveys can get extremely cluttered when there are a lot of unnecessary custom fields (use case: loading a snapshot that has a lot of custom fields) It is time consuming to have to delete unused custom fields one at a time instead of a Bulk Delete.

At least when importing I see here that Monetary is spelled incorrectly

URGENT!! No way to make any bulk actions based on calendar. I cannot even add tags or process any workflows for existing contacts based on which calendar they used!!!! URGENTTTT

Africa/Dakar, Africa/Accra, Asia/Katmandu, Africa/Addis_Ababa, Africa/Mbabane, Asia/Manila are just a few of the timezones that were in contact accounts within our system from spam bot traffic. The timezones are added to the customer account automatically should adhere to strictly the timezones available in the search list or provide a text search option for the Timezone search so I can delete the harmful bots en masse

Currently, GoHighLevel displays a warning for emails with no subject in the email campaign checklist and template settings. However, this validation is not applied to emails sent individually to contacts, which allows messages to be sent without a subject. This inconsistency may compromise the professionalism of communications and potentially impact email deliverability. Proposed Enhancement: Universal Validation: Implement the same subject validation for individual email sends as is in place for campaign checklists and template settings. Handling Emails Without a Subject: Option 1: Prevent the email from being sent if the subject field is empty. Option 2: Display a clear alert (e.g., "Are you sure you want to send an email without a subject?") before proceeding with the send action. Expected Benefits: Ensures consistent behavior across all sending scenarios. Enhances the professionalism of outgoing emails. Helps prevent potential deliverability issues related to missing subject lines.

When dealing with numeric custom fields within the CRM, I'm finding that I can only update these fields with static, pre-defined numerical values. However, my workflow requires these fields to be updated dynamically based on calculations that occur outside the CRM—in this case, on a Google Sheet where an automated formula calculates a value post-form submission. To provide a clearer picture: imagine a scenario where each form submission results in a unique calculation on Google Sheets. That resulting number needs to be fed back into the CRM to update a custom field for each contact record. The system, however, doesn't seem to support the dynamic injection of these values back into the CRM fields; it only accepts a number that I manually input as a static value during the setup. This is quite limiting, especially since the whole point of automation is to streamline the process without manual intervention. I'm sure I'm not the only one who would benefit from a more flexible system that accommodates dynamic updates.

When creating/updating an opportunity in a workflow, it's not currently possible to update a numerical or monetary field using a bracketed value. You have to type a number. This is actually a workaround for not being able to update Opportunity fields via a LeadConnector zap action (have to update contact fields via Zap, then update the opportunity in a workflow). But cannot update the opportunity properly in the workflow without being able to dynamically populate numbers like {{contact.30_margin}} (see image attached).

After trial and error, I found out that the filters are case dependent. For example I work in the Automotive Niche. I added custom fields to capture vehicle make. Now I'm trying to filter by it. I used it as "is" and then put in Ram. But some of the data shows for example RAM as all caps, and other with just the R capitalized Ram. when I did it this way, I only got 8 records. When I changed it to "is" RAM I got 2700 records. If I change it from "is" to "contains" then it is not case sensitive. I really can't think of a use case that would dictate the need for the "is" to be Case Sensitive. Given the ongoing issue of any company with quality of data, inconsistencies will be high. Which if there is a use case that calls for this, then we need to add a note such as under the contains that indicates that the "is" field is case sensitive. Which brings up the issue that you can duplicate the filter box. The ability to clone the entire box or delete the entire box is needed. Also as others have noted, there needs to be alot more options for the selections. Benchmark Hubspot as they did a release about 2 years ago to greatly improve their filter selections and it was really robust and helpful.

This is disappointing.... I wanted to download names and addresses as a CSV file to mail-merge onto postcards and there is no option to separate the address field from the city, state zip. There should be a single ADDRESS line (just the number and street address) and not just ADDRESS (Full)

The new example data is an interesting idea. I understand and appreciate how it can help explain the functions. Please add sample conversations, notes, tasks, and calendar with appointments. But the samples create chaos in the account. Need an easy button to immediately remove all test data from the account including workflows, pipelines, social templates, etc once the demonstration/orientation is complete.