Error from Macro Form Populating a Phone Number

Smart CRM & Sales Hub
1

To the audience we leverage macro call to action forms all the time. Populate Name: First/Last, email… no issues. The challenge we are having defaulting to the US Phone number is when someone tries to auto populate the phone number it adds the 1 for the US under auto populate. When that happens it glitchs’, because Hubspot has already put in the US 1+ in the filed. So it shows an error and then we get clients that bounce due to that friction. Can you not put in a simple “if then” that says if a 1 is auto input to the US long distance please remove it and have just 10 digits auto populate. Seems pretty simple to me … thanks

2

Any help here appreciated.

4

Hey @Froth,

Thanks for posting in the Community!

To clarify - are you referencing a customer auto-populating their phone number in your HubSpot form with their personal device, or another way (i.e. multiple form submissions)? I ask, because I’m reading through our knowledge base article on setting up your phone number property validation, and there’s a section dedicated to understanding phone number validation. I’m wondering if any of this context is helpful to your current inquiry?

Shane, Senior Community Moderator

5

You have defined the problem properly … but the response does not solve the problem on the macro form with the phone number is auto populated from your computer, cell or iPad, etc. The cell already have the 1 designation and when we just click away to auto populate with our names, addresses, etc. it’s fine. Then bam it hits your phone number and pushes the 1 long distance designation that already has been prepopulated by the HubSpot macro form.

Conflict and an error occurs. Hope this helps … the macro form in my opinion needs to remove the 1 long distance designation when it attempts to load the phone number. Just allow it to enter the final 10 digits of the phone. Remove the 1.

Frank Roth
Adjunct Professor, Marketing
Advisor & CoFounder Boxer Marketing Group
College of Undergraduate Studies | Pacific University
2043 College Way | Forest Grove, OR 97116
(c) 503.360.3724 | froth@pacificu.edu

6

@Froth Yes, this is absolutely possible. I can add logic to detect and remove a leading 1 from auto populated US phone numbers before HubSpot validates the field, ensuring only the 10 digit number is submitted. This will eliminate the duplicate +1 issue and reduce form abandonment. Happy to get this fixed for you.

7

That is fantastic … so impressed! So what do you need from me? How long will this update take?

Thanks so much.

Frank Roth
Adjunct Professor, Marketing
Advisor & CoFounder Boxer Marketing Group
College of Undergraduate Studies | Pacific University
2043 College Way | Forest Grove, OR 97116
(c) 503.360.3724 | froth@pacificu.edu

8

Hey @Froth,

Thanks so much for confirming this!

I’d like to tag in a few Community experts to see what insight they might have here. @karstenkoehler, @danmoyle, and @TomM2 - do any of you have suggestions for how @Froth here?

Shane, Senior Community Moderator

9

This is the response I got from @ElixahMeraki … “Yes, this is absolutely possible. I can add logic to detect and remove a leading 1 from auto populated US phone numbers before HubSpot validates the field, ensuring only the 10 digit number is submitted. This will eliminate the duplicate +1 issue and reduce form abandonment. Happy to get this fixed for you.”

10

Hope this posts: This is what @ElixahMeraki said … Yes, this is absolutely possible. I can add logic to detect and remove a leading 1 from auto populated US phone numbers before HubSpot validates the field, ensuring only the 10 digit number is submitted. This will eliminate the duplicate +1 issue and reduce form abandonment. Happy to get this fixed for you.

11

Hi @Froth,

This is a known issue when browser autofill kicks in on a phone number field, it can take the first digit of the entered number and treat it as the country code, which produces a duplicate/invalid number, exactly what you’re describing.

Two workarounds people are using while this stays unresolved on HubSpot’s end:

  1. Turn off the country code dropdown on the form field if you’re US-only — disable “Show country code dropdown menu” in the form editor so it just shows a plain phone field without the +1 selector (note: only available on legacy forms currently, not new forms).
  2. Workaround via hidden field + workflow — create a separate single-line text property (e.g. “Form Phone”), use that on the form instead of the native phone field, then run a workflow that copies it into the real Phone Number property bypasses the autofill/country code collision entirely.

Your “if 1 is detected as country code, strip it” idea is a reasonable ask worth posting as a formal request in the HubSpot Ideas forum if it’s not already there, since this is a recurring pain point for others too.