NEW! Expanded phone number entry support for forms

October, 02, 2025

Hey Community!

Smartsheet forms now support a wider range of global country codes, making phone number entry more intuitive and reliable worldwide. We’ve also added smarter validation with clearer error messages to make form submissions easier.

What’s new:

Expanded global country code support (40+ new countries)
Fixes for top community-reported issues and escalations
Real-time formatting as users type
Smarter validations and error messages
Localization upgrades

Please note, this release focuses solely on the submission experience. Forms builder work regarding this feature, like setting new countries as defaults, is coming in a future iteration. Additionally, country flag icons have been removed for scalability reasons.

Environment Availability: Commercial US, Commercial EU, Gov, AU

Plan Availability: All plans

Subscription Model Availability: Both Legacy Collaborator Model and User Subscription Model

Stay informed by subscribing to receive product release updates for curated news of recently released product capabilities and enhancements for the platform of your choosing, delivered to your inbox. As new releases occur, you will receive a weekly email with news of what's released every Tuesday.

Find more posts tagged with

Forms

Comments

cooperl

I really appreciate that you are consistently trying to improve your forms, however, the inability for people to enter all zeros in a phone number field has created a headache for us. This has been our default for individuals that don't have a phone number to enter (in a required field)…and now they're being forced to enter various numbers. Hence, we don't know which phone numbers are real in our SmartSheet…and which are just numbers entered in as dummy variables.

Selin Esener

Thank you for calling attention to this! There are two paths that solve for this. You can either remove the “required” setting from the phone number field, or set 000-000-0000 as the default to bypass the validation. Please let us know if neither of those approaches resolve your issue. Thanks!

chandurh

Hi!

Appreciate improvements always being made in the platform.

However this new update has caused quite a few headaches for our business related to tracking for inbound call operations, from not accepting phone numbers from Puerto Rico as being valid, to not allowing us to use previously accepted set dummy numbers like "000-000-0000" for anonymous calls, "555-555-5555" for technical disconnects, "999-999-9999" for unavailable or have the ability to enter invalid numbers when we receive calls with spoofed information, that we still need data collected on.

Previous to this update, we were still able to have number validation on which protected the data set, and ensured 10 digit numbers, or alternative expectations for different country codes, without actually validating the number as legitimate, and this worked well. Is there a way to have the new updated number validation as optional, or add in ways to build multiple exceptions, rather than just a singled one using the default as advised in the previous response?

Thanks !

Selin Esener

@chandurh thank you for letting us know. I am going to create a separate message so we can discuss further.

AliceVBH

Hi @Jason DelValle,

Thank you for the update, we are still encountering various issues with phone number validation across various countries.

Some issue were pre-existing the form update that took place in the spring, others have started occurring since that update (for example for some countries no matter how many digit you input you get an error).

Is there a timeline for resolution of the post-update bugs please?

Thank you

Selin Esener

@AliceVBH have you filed an escalation for this with our support team? If not, please do and elaborate on which validations need to be fixed.

AliceVBH

@Selin Esener yes I created a support ticket towards the end of June providing all the necessary information. My team has also tested a number of country codes; I shared a brief summary of the findings in this thread https://community.smartsheet.com/discussion/comment/493749?utm_source=community-share#Comment_493749

Selin Esener

Ah ok great! I believe your escalation is the one we have been working on. There are some fixes going out today. Please contact your escalator or send me an individual message and I will check on the status if it is not resolved by tomorrow.

AliceVBH

Amazing! Thank you @Selin Esener

Sign in to join the conversation!

Quick Links

Trending discussions

Refine your AI-generated charts with suggested prompts
October 22, 2025 Analyze data now includes suggested prompts to help you further refine and explore your data through AI-generated charts. After creating a chart using the analyze data AI tool, you’ll automatically see three contextual suggestions in the analyze data panel, sharing ideas to help you adjust visuals, surface…
Nested Sharing Modal now generally available!
October 10, 2025 Introducing our new nested sharing modal with a more intuitive and streamlined sharing experience. This will make it easier for our users to control access to their documents, invite collaborators, and manage sharing settings more efficiently. Specifically for managing collaborators, admins can sort and…
Plan level visibility in Workspaces now available
October 15, 2025 Users will now know which plan their workspaces belong to with a new plan identification chip located at the top of the Workspace panel. Learn More Environment Availability: Commercial US, Commercial EU, Commercial AU Plan Availability: All Subscription Model Availability: Legacy and USM Stay informed by…