Phone number validation helps you catch formatting issues before a Resource Profile is saved. Consistent validation across Resource Profiles, Security User Profiles, and Web Import templates helps improve data quality and reduce phone number errors.
Why it matters
Improve phone number data quality across Beeline Enterprise.
Support downstream processes that rely on accurate contact information.
Help prevent delays caused by incorrect phone number data.
Create more consistent worker contact information across your organization.
Who it's for
Client administrators.
MSP administrators.
How it helps
Validates phone numbers when Resource Profiles are saved.
Checks country-specific phone number formatting requirements.
Checks that phone numbers meet required length requirements.
Displays clear error messages when validation fails.
Prevents unsupported special characters and incorrect formatting.
Applies validation to Resource Profiles, Security User Profiles, and supported Web Import templates.
Helps ensure new and updated phone numbers follow the same format standards.
Availability and setup
Client Administrator and MSP Administrator access with appropriate permissions.
Feature enablement through Preferences > VMS Settings > Data Management > Phone Type Format Validation.
Validation support for Resource Profiles, Security User Profiles and supported Web Import templates.
Default validation formats provided by Beeline.
Changes to the default validation format require a Service Request.
Where validation applies
Area
Validation behavior
Resource Profiles
Validates Business, Mobile, Fax, and Home phone numbers when saved.
Security User Profiles
Applies the same phone number validation rules.
Web Import templates:
Resource Phone
Resource
Resource User Contact Information
Validates phone numbers during import processing.
Before you begin
Verify that you have access to VMS Settings.
Verify that any required updates to phone type validation formats have been requested through Beeline.
Information in this article reflects a standard Enterprise configuration. Your Enterprise platform is based on your organization’s configuration. Settings and/or data visibility rules may vary slightly from what is described.
To accomplish your task, complete these steps from your Enterprise dashboard.
Select Preferences > VMS Settings > Data Management. A Data Management page displays.
Select Phone Type Format Validation.
A Phone Type Format Validation page displays.
Select Edit.
For Enable Phone Type Format Validation, select Yes from the Override list.
What this does: Enables phone number validation for your organization.
Why this matters: Phone numbers are validated before they can be saved, helping prevent incorrectly formatted data from being stored.
Select OK. The configuration is saved.
Phone number requirements
Phone numbers must meet the configured requirements for the selected country and phone type.
Requirement
Description
Country code
Use a recognized country code.
Number length
Enter the required number of digits for the selected country.
Format
Use dashes (-) where required.
Special characters
Do not enter unsupported special characters, spaces, or punctuation.
Example phone number formats
Phone numbers must match the format configured for the selected country and phone type.
Examples
Business phone number format is invalid.
Mobile phone number format is invalid.
Fax phone number format is invalid.
Home phone number format is invalid.
The following examples show valid phone number formats for Chile.
Phone type
Example
Business
+56 0-12345678
Mobile
+56 9-01234567
Fax
+56 0-12345678
Home
+56 0-12345678
Format requirements vary by country and phone type. If you need to update your organization's phone number validation formats, open a Service Request.
What users experience
Phone number validation helps you identify and correct formatting issues before a Resource Profile is saved.
Step
What you experience
Benefit
Select a country code
Choose the appropriate country code for the phone number.
Apply validation requirements that match the selected country.
Save the profile
Validation checks the phone number against the configured format requirements.
Validate the phone number before it is stored and used elsewhere in Enterprise.
Enter a valid phone number
The profile saves successfully when the phone number meets the configured format requirements.
Maintain accurate, consistent phone number data.
Enter an invalid phone number
An error message identifies the formatting issue and prevents the profile from being saved until it is corrected.
Correct problems immediately instead of finding them later in downstream processes.
Example valid phone numbers in a Resource Profile
Validation messages
If a phone number doesn't meet the configured format requirements, validation messages identify the affected phone number field.
Examples include:
Business phone number format is invalid.
Mobile phone number format is invalid.
Fax phone number format is invalid.
Home phone number format is invalid.
When imported data contains invalid phone numbers, the import results identify the affected records and validation errors so you can correct and reimport the data.
Web Import validation
Phone number validation applies to supported Web Import templates using the same rules enforced elsewhere in Enterprise.
If imported phone numbers don't meet the configured format requirements, import results identify the affected records and validation errors.
Example validation results for imported Resource Template dataExample import results showing phone number validation errors
Reporting behavior
Validated phone numbers are available in reporting, helping improve the consistency and quality of phone number data throughout Enterprise.
Please complete the following fields as part of your Beeline Community registration. Unless noted as private, this information will be displayed on your user profile within the community.
