Import of phone numbers | Voters

Import of phone numbers

test test

Extremely difficult to import numbers when we have phone numbers in a google sheets/excel in different columns. We would think we could just select additional phone in the import for each column and it would merge them all for us (especially since the column would be labeled mobile or landline or work). Vs. us or clients having to try to figure out how to put all their phone numbers into one column and then you can't even label what they are. If it's landlines, mobile, work, etc.. So then they have to go contact by contact to edit that??

October 22, 2023

Sales & Marketing

Merged in a post:

LC phone additonal numbers

test test

April 14, 2026

Digiking Admin

Would it make sense to have a set of mapping-only custom fields that are:
•	Hidden from the standard contact card UI (or at least not cluttering the main view), and
•	Mapped into a single interactive phone field that the dialer uses.
For example, we would use pairs of custom fields like:
•	{{ contact.contact_1 }} + {{ contact.contact_1_phone_number_1 }}
•	{{ contact.contact_1 }} + {{ contact.contact_1_phone_number_2 }}
•	(And potentially contact_2, contact_3, etc.)
Instead of the phone field showing “mobile / home / work”, the dropdown or options would show:
•	The contact name from contact_1 as the label
•	The phone number options from contact_1_phone_number_1, contact_1_phone_number_2, etc., as dialable choices 
So the UI might look like:
•	Contact 1 – Main - (213)456-7890
•	Contact 1 – Alternate
•	Contact 2 – Main
This would probably mean replacing the dropdown description for typing it in, when creating a contact manually. or a mix of options. This would make it work with phone leads managing few phone numbers and cold calling at volume.

Brian Del Terzo

This is definitely needed. We were so confused when we couldn’t select the alternative numbers from a contact record while trying to send texts or make calls—until it was brought to our attention that only the numbers added to the built-in phone number field (which can store up to four numbers) are recognized for those functions.
The issue is that there’s currently no way to populate those additional phone number slots during a bulk import. Even though we can create a custom field for secondary numbers, those fields aren’t treated as valid phone numbers for calling, texting, or automation.
This creates a major manual bottleneck for users who manage contacts with more than one number.
Suggested Improvement:
Enable the bulk import process to support mapping multiple phone number columns directly into the built-in phone number field (e.g., Phone 1, Phone 2, Phone 3, Phone 4). Even allowing delimited numbers in a single column to auto-assign across the available slots would be a big help.
This would save significant time, reduce confusion, and make the platform much more intuitive for teams handling high-volume imports or clients with multiple contact numbers.

Max Ghezzi

And while we're at it, could we please add another selection on the dropdown that reads 'Other' ?
Now have to choose from Home, Work, Mobile and Landline.
Let's add 'Other' as well.

Digiking Admin

Max Ghezzi Or option to type in also!

Max Ghezzi

Digiking Admin Yes, even better!

TJ Garland

Now that GHL has the ability to have up to 11 phone numbers, there should be a way to have a CSV file of 2+ phone numbers (2+ columns) that can be imported into GHL. Currently, the only method is to create a custom field for the 2nd phone number and bypass the built-in "multiple phone numbers" function. Really frustrating as my client wants everything in the one field, not the main PHONE field plus a custom field that sits beneath it.

Photo Viewer