Organizations need the ability to define and maintain their own phone number formatting standards, including the option to leave formatting set to “none.”

Currently, formatting set at the database level can be overridden in Web View, which introduces inconsistencies. This impacts:

• Record matching and lookup reliability

• Overall data consistency

• Reporting, especially when additional system-driven phone types (e.g., international variants) are introduced

• For organizations managing both domestic and international constituents, a single, internally defined format is often preferred over multiple system-imposed formats.
  
  Request:

• Respect database-level formatting choices in all interfaces, including Web View

• Allow formatting rules to be independent of phone type

• Ensure formatting consistency supports matching, lookup, and reporting functions