Ask users for…
Phone numbersUse: Deployed
When to use this pattern
- When you need to collect a phone number. For example, for contact information.
How to design and build
How this pattern works
- If possible, tell users why you want their phone number. An example message is: Please enter your contact information so we can get in touch with you if we have questions about your application. This message can be at the top of the page if asking for any other contact information.
- Validate phone numbers. Users must provide at least a 10 digit phone number with or without dashes. Example of acceptable formats: 703-123-4567, 7031234567, 1+703-123-4567. A validation message for when a user forgets to enter the phone number: Please enter your phone number. A validation message for when a user’s phone number is too short: This field should be at least 10 character(s).
- If a user chooses a home or mobile phone number as their method of contact, phone numbers are required fields. If a user chooses email or mail as their preferred method then a phone number field won’t be validated. (Note: Method of contact field is form dependent)
- “Mobile phone number” is a required field if the user checks (I would like to receive text messages from VA about my [ ] benefits). An example of this is on the VA Form 22-10203 (Application for Edith Nourse Rogers STEM Scholarship)
- Do not use primary or secondary phone numbers as field labels. Home and mobile phone numbers are more plain language-focused.
- If you need to display a phone number after it has been collected, then follow content style guidelines on phone numbers.
Error message templates for phone numbers
When a user doesn’t enter a phone number:
Say ‘Enter a phone number’
If the telephone number is not in the correct format:
Say ‘Enter a 10-digit phone number’