Skip to main content
Question

Routing Forms: small bug in the Phone Field?

  • January 22, 2026
  • 9 replies
  • 58 views

angeliti

Hello!

I noticed a small bug in the Phone Field in Routing Forms.

Basically, even though the field correctly detects my country, it doesn’t automatically add the country code, just the +. So when the user starts writing his phone number on it, he is forced to first write his or her country code. Otherwise, it will change the country.

I’ve recorded a quick video showing what I mean:

https://www.loom.com/share/ca2d72c96fef433c9c879912aad6c43a

The same issue happens with the Phone Field in regular scheduling forms: the user’s country is pre-selected, but the country code is not pre-filled. User needs to select a different country and then select his country again to have the country code added to the Phone Field.

Would be great if you could fix this!

Thanks,
Ángel.-

9 replies

David
Community Manager
  • Community Manager
  • January 22, 2026

Hi ​@angeliti - Thanks for all the super helpful info here.

I’ll get this passed along to our team so they can dig into it some more and see whats going on. Once I have any updates, we’ll let the community know!


  • New Community Member
  • January 30, 2026

Hello we have clients who are older and have issues with this. It should just default to adding the country code number. They go to the field, and when they type in for example [removed by moderator] it default to a different country code it should have 1 on there so they don’t have to do this.


  • New Community Member
  • January 30, 2026

@Arizona05118 - as a workaround you can prefill the “+1” in the link to ensure that it automatically shows the country code number in phone input. For example, using the link - https://calendly.com/d/cxpp-pt5-m4k?a3=+1 - will automatically show the “+1”.

You can add ?a3=+1 to your routing form url (make sure to change a3 to a1,a2, etc depending on which question number corresponds to the phone input).


angeliti
  • Author
  • Community Member
  • February 3, 2026

@David any updates about this?

I noticed another minor issue with routing forms:

I have set up a webhook to pass the routing form submission to Zapier, and even though I have Name and Last Name as separate fields, they come together in the webhook.

Here is my routing form:


And here is the payload I get in Zapier (notice how both Name and Last Name are grouped together):


Hopefully you can pass this to the developers so they can fix it 🙂

Thanks,
Ángel.-


David
Community Manager
  • Community Manager
  • February 3, 2026

No updates as of now, but I’ll get this passed along as well - Thanks ​@angeliti !


David
Community Manager
  • Community Manager
  • February 11, 2026

Hi all! We’re looking at pushing a fix for the phone number field today - So keep an eye out for any changes!


angeliti
  • Author
  • Community Member
  • February 12, 2026

Thanks ​@David!

 

Just checked and it’s not online for me yet. Will check again in a few hours 🙂


  • New Community Member
  • February 13, 2026

Any update here?


  • New Community Member
  • February 16, 2026

Guys, will you be fixing it or I should look for alternate solutions? We use the calendat with paid Ad campaigns. We loose money with poor conversion.