Skip to main content
New Idea

Feature Request: Option to Customize or Disable Phone Number Format Validation

Related products:Freshdesk
  • November 7, 2025
  • 2 replies
  • 80 views

Forum|alt.badge.img+2
You have ## contacts that need your attention.

We’ve started receiving the warning message:

“You have X contacts that need your attention.”

After investigation, we learned that this appears to be caused by the specific phone number formatting we use for our contacts. It seems that the system recently began enforcing a stricter format, possibly to align with phone integration or third-party telephony standards.

Current Behavior:
Our team does not use any phone integration features. We typically reference the phone number visually from the Contact Information section and dial it manually. The previous formatting was easier to read and understand at a glance.

  • Example of easy-to-read format:
    (603) 123-4567 Ext. 123

  • Example of required (system-compliant) format:
    +6031234567123

While the latter is technically correct for integrations, it is much less human-friendly and harder to read.

Proposed Solutions:

  1. Allow custom or multiple acceptable number formats — for instance, permit both human-readable and E.164-compliant versions.

  2. Provide an admin or user-level setting to disable or suppress this warning when phone integration is not in use.

  3. Optionally detect when phone integration is disabled and automatically relax the validation rules.

Benefits:

  • Improves readability for teams that manually dial numbers.

  • Reduces unnecessary alerts or warnings.

  • Provides flexibility for different use cases (integrated vs. non-integrated environments).

2 replies

Paco43
Community Debut
  • Community Debut
  • January 27, 2026

Forum|alt.badge.img+2
  • Author
  • Active Contributor
  • January 27, 2026

 

Thank you for sharing! Support explained this workaround, which involves exporting a CSV of the improperly formatted numbers, manually correcting them, and re-uploading the file. Since we don’t use any phone integration, this was a bit frustrating for our team.

We use the Contacts section purely to visually reference phone numbers and dial them manually. For that use case, seeing a number formatted as (123)-456-7890 is much easier to read than 1234567890.

I’m hoping an accessibility or configuration option could be added to disable this requirement for customers who aren’t using phone integration. Alternatively, enforcing strict formatting only when a phone integration is enabled would make a lot of sense.