Salesforce phone number validation
NumberForge is a managed package that ports Google libphonenumber to Apex so you can validate, format, and enrich phone numbers inside Salesforce. Processing stays in the org: there are no runtime callouts to an external phone-validation service.
What it checks
Like libphonenumber, NumberForge tests whether a number is possible and valid for a region (length, prefix, pattern) and can format it for storage or display (E.164, national, international). Optional enrichment returns carrier name, geographic description, and time zones from packaged offline metadata.
It does not query a carrier to see if the number is assigned or reachable. Salesforce validation rules alone also cannot parse international numbers or apply per-field format rules.
Bulk and save-time processing
In NumberForge Configuration you attach field rules to standard or custom objects. When automation is deployed, those fields are processed on record insert and update. That is the path for keeping Contact, Lead, Account, and custom object phones consistent as users save. Preview a rule with sample input before you enable it.
Flow and Apex
Use NF Process Phone in Flow to validate and format a single value, or NF Find Phone Numbers to extract numbers from notes and other text. For custom batch, triggers, or REST, call the global NF class (parse, isValid, format, findNumbers, and enrichment helpers).
-
Save-time rules
Validate and format phone fields on insert and update from NumberForge Configuration.
-
Phone Assistant
Triage existing numbers on the record page, including region when a number needs it.
-
Flow actions
NF Process Phone for one value; NF Find Phone Numbers to extract numbers from text.
-
NF Apex API
Global libphonenumber-style API for triggers, batch, and custom integrations.
One plan: €29,99 per org / month or €299 per year. Sandbox orgs are free. Pricing · FAQ · Install