Contacts

Inline Editing of Contact Fields in Smartlist & Contact List Views
Summary: Enable inline editing of contact fields directly within the Contact List and Smartlist table views, allowing users to update field values without navigating into individual contact records. Current Behavior: When using Smartlists with customized column views (via Manage Fields), all displayed data is read-only within the list. To update any field — whether a standard contact field or a custom field — users must open each contact record individually, locate the field, make the edit, and return to the list. When managing large lists with many contacts, this creates significant friction and inefficiency. Requested Behavior: Allow users to click directly on a field value within the Smartlist or Contact List table view to edit it inline — similar to how spreadsheet applications handle cell editing. This could be triggered by: A single or double-click on a cell value A small edit icon appearing on hover Supported field types should include: text, number, date, dropdown, radio select, checkbox, and other applicable custom field types. Use Case / Business Value: Users who build operational Smartlists (e.g., scheduling views, financial tracking, route management) often need to make quick, high-volume updates to custom fields across multiple contacts at once. Inline editing would eliminate the repetitive open-edit-save-back cycle, dramatically reducing time spent on routine data updates and improving overall workflow efficiency. Priority / Impact: High — particularly valuable for users leveraging Smartlists as operational dashboards with custom fields. [created by Ask Ai :-)]
1
·
New Feature
Add Phone Number Mapping for Contacts with Multiple Phone Numbers
Idea / Feature Request: I would like to request an improvement for contacts that have multiple phone numbers saved under one lead/contact record. Currently, when a lead has more than one phone number, the system can treat secondary numbers differently from the primary phone number. In some cases, when a user calls or receives activity from a secondary number, the CRM may create a new blank contact instead of linking the call, SMS, recording, or activity back to the original contact. This causes confusion because the new contact may only show the phone number, with no name, email, address, opportunity, notes, tags, or previous conversation history. The team then has to manually search, merge, or verify which contact the activity belongs to. Requested Feature: Please add better phone number mapping so that all phone numbers attached to a contact are recognized as part of the same contact record. For example, if a contact has: Primary phone number Secondary phone number Home number Work number The CRM should automatically recognize all of those numbers as belonging to the same contact. Any call, SMS, voicemail, recording, or activity connected to any of those numbers should be logged under the original contact, not create a new blank contact. Why This Is Important: This would help teams avoid duplicate contacts, missing call recordings, split conversation history, and confusion when managing leads with multiple phone numbers. It is especially important for industries like real estate, medical offices, home services, and sales teams where one lead may have multiple valid phone numbers. Suggested Functionality: Add mapping for all contact phone numbers, not only the primary phone field. Allow users to choose which saved number to call or text directly from the contact profile. Keep all call recordings, SMS conversations, voicemails, and call logs under the original contact. Prevent the system from creating a blank duplicate contact when the phone number already exists as a secondary number on another contact. Show a clear label for each number, such as Mobile, Home, Work, Spouse, Office, or Other. Allow workflows, triggers, and reporting to recognize secondary phone numbers as part of the same contact identity. Expected Result: If any phone number saved under a contact is used, the activity should stay connected to that same contact and opportunity. This will keep the CRM cleaner, reduce duplicate records, and help teams maintain accurate communication history.
1
·
New Feature
Contact Data Protection Mode (Masked or Action-Only View)
We need a secure way to hide or fully mask client phone numbers and email addresses from sales agents inside GoHighLevel, to prevent internal data leakage, unauthorized copying, and lead theft. Problem: Currently, sales agents can directly view: Full phone numbers Email addresses Copy contact data freely This creates a serious issue: Risk of lead theft Data leakage to competitors No control over sensitive patient/client information Compliance risks (especially for healthcare / medical businesses) 🎯 Requested Solution: We need a new permission-based feature that allows account admins to: Mask Contact Data (Basic Mode) Phone numbers shown as: +90 ** 42 Emails shown as: j***@gmail.com Copying disabled Agents can still: Click to call Click to email Use WhatsApp / SMS buttons Action-Only Mode (Preferred) Agents DO NOT see any raw contact data at all. Instead they see: 📞 “Call Client” button 📩 “Send Email” button 💬 “Send SMS / WhatsApp” System executes communication without revealing data. Permission-Based Reveal (Admin Controlled) “Reveal Contact Info” button Requires admin permission or password/OTP Every reveal action is logged: User who accessed it Time Reason Audit Logging (Required) Track: Calls initiated Emails sent Attempts to copy data Contact reveal events 🔐 Why This Is Important: This feature is critical for: Medical clinics & healthcare agencies High-value lead businesses Agencies with distributed sales teams GDPR / privacy compliance environments Preventing internal lead theft 🏥 Use Case: We run healthcare and medical tourism campaigns where each lead is extremely valuable. Agents should be able to work the lead without ever seeing raw personal contact data. 💡 Expected Outcome: Stronger data security Reduced internal fraud risk Better compliance Increased trust for enterprise clients using GHL
0
·
New Feature
Load More