Bulk Edit Phone Number Validation

[michaeljay201]

The new auto-formatting and validation feature for phone numbers is a step in the right direction.

However, the current integration seems to be missing the mark with regard to user experience. I was unable to find any articles or posts in the Help Center announcing the new auto-formatting feature. The only Knowlege Base article that pops up when searching "phone number validation" is a detailed breakdown of editing default contact properties, and then there is only a reference to the validation and formatting being applied "automatically by Hubspot based on the country code."

This feature is certainly a step in the right direction, but several improvements are needed to improve the user experience and make the feature more functional overall (noting that recent comments on an "old" idea thread are already being discussed here; skip to page 7).

Suggested improvements include:

1. Global Setting to Enable/Disable auto-formatting at the account level - currently, the feature is enabled by default with no disable setting available
2. Global Setting to assign a default Country Code - currently, the Country Code must be selected manually for every new contact (see screenshot below)
3. Bulk edit phone numbers to apply Country Code format & validation -- currently, only able to apply formatting & validation when editing one individual contact at a time OR when adding to new contacts manually added (not via web forms -- this is needed, too)
4. Retain "number only" format for export and/or sync to other apps or integrations to remove non-number characters (parentheses, plus sign, spaces)

Default behavior of phone number formatting & validation when creating a new contact:

There are likely other enhancements that other users, especially those not based in the US, would appreciate.

[michaeljay201]

Hi everyone!

This idea's status has changed from ‘Being Reviewed’ to ‘Idea Submitted’. This change is due to our improvement project to update our Ideas Forum statuses in order to provide better transparency into how we are listening to your feedback.

“Idea Submitted” means that our product teams are aware of this feedback and are monitoring the need for this feature alongside other inputs that determine their priorities & roadmap.

For this request, the information in Rachel's comment from April 2025 still applies. We aren't moving it to 'delivered' yet because not all asks in the original post have been addressed, but there is still the feature for phone number validation which is live. 

For more details about the statuses we use on the Ideas Forum & what they mean, you can read this community post here.

[michaeljay201]

👋Hi everyone, Rachel from the Product team here. I wanted to share a relevant beta update: Phone number property validations.

• You’ll now be able to set validation rules for custom and default phone number properties. If you turn on phone number validation, the property value must match E.164 format. Once you apply the validation rule, users cannot remove phone number formatting when manually editing phone number property values.
• Additionally, you will be able to set a default country code for phone number properties that will automatically be applied to updates to phone numbers via Import. If a value is missing a country code but is valid based on the other requirements, the selected country code is added automatically before the value is saved.

Opt into the beta here. Thanks in advance for your feedback! 

[michaeljay201]

Hi folks,

I’m Ian, the Product Manager for HubSpot’s Forms tool.

Thank you all for taking the time to submit, upvote, and comment on this Idea. I'm happy to report that we are now enforcing phone number validation on all phone number properties as part of the new Hubspot Forms Editor. You can opt-in to the public beta here. 

Ian

[CSic]

This is helpful Thank you.

Can we get phone number validation for chatflow phone number entries too? 

[rwebb1]

👋Hi everyone, Rachel from the Product team here. I wanted to share a relevant beta update: Phone number property validations.

• You’ll now be able to set validation rules for custom and default phone number properties. If you turn on phone number validation, the property value must match E.164 format. Once you apply the validation rule, users cannot remove phone number formatting when manually editing phone number property values.
• Additionally, you will be able to set a default country code for phone number properties that will automatically be applied to updates to phone numbers via Import. If a value is missing a country code but is valid based on the other requirements, the selected country code is added automatically before the value is saved.

Opt into the beta here. Thanks in advance for your feedback! 

[hhiggins]

Hi everyone!

This idea's status has changed from ‘Being Reviewed’ to ‘Idea Submitted’. This change is due to our improvement project to update our Ideas Forum statuses in order to provide better transparency into how we are listening to your feedback.

“Idea Submitted” means that our product teams are aware of this feedback and are monitoring the need for this feature alongside other inputs that determine their priorities & roadmap.

For this request, the information in Rachel's comment from April 2025 still applies. We aren't moving it to 'delivered' yet because not all asks in the original post have been addressed, but there is still the feature for phone number validation which is live. 

For more details about the statuses we use on the Ideas Forum & what they mean, you can read this community post here.

[KGoethals]

Having a default country code https://knowledge.hubspot.com/workflows/format-phone-numbers-using-workflows is useless for international companies using HubSpot. Would be great if you can use your Country property to define the Country Code and then format the phone number with this information.

[CDelas]

Hello

Thanks so much for these updates.

It looks like it doesn't for for "06" in France. Could you help me?

Camille - Sonio

[AMaier44]

I enrolled into the beta for Phone Number validation. I do not see this working on phone numbers that aren't formatting and have the extension written as ###########x### in the workflow. When I go to the contact record and hit validate, it does move the digits after x to the extension property. 

For example: I enrolled the two selected contacts into the workflow and it did not validate them. 

[hkfreem]

This beta is helpful but it is still not "validation" it is simply formatting. 

We need real validation options upon intake especially public facing forms.

It would be awesome if we could just put in a API key or login to integrate Twilio to be able to actually validate phone numbers and prevent junk/spam in the first place

https://www.twilio.com/en-us/blog/validate-phone-number-input

[EmilyT]

Hi all. With the new phone number validation workflow step in beta, has anyone found a way to clear the property if the step finds the phone number to be invalid? I currently have the workflow steps shown in this article, but if a phone number is invalid it just causes an error in the workflow. This seems like an issue because if I have 20,000 invalid phone numbers I shouldn't have to manually remove them all. 

Has anyone found a good way to go through this process? Invalid phone numbers are a big issue for me since we have an SMS integration as well, so I want to be able to clean up those errors as well as just clean up the phone numbers overall. TIA!

[keshukeshvala]

Thank you Hubspot team to share this important update with workflow option.  A few questions: 

Q1: Is there a way where if we are using third party apps to import data into hubspot at that time we can check Phone number is in current formate or not? and if not update them using worfklow or formate phone number rule? 

We tries enabling Formate Phone Number rule but it was not allowing third party app to send data - throwing error. 

Q2: How to update alreay existing phone numbers which have invalid formate? How can we find those? --> After filtering them we will run workflow to update phone number. 

Q3: As many requested it would be nice to have rather default country option to choose as code --> allowing to use Country Property --> chosoe coutnry code and udpate records. For companies working internationally its must as we have records from morem than 20 countries and can not choose one default country.