Frequently asked questions
Quick answers for admins and developers. For Salesforce phone validation with libphonenumber, Flow, and Apex, see the validation guide. Install steps are in the documentation.
What is NumberForge?
NumberForge is a managed Salesforce package for phone number validation, formatting, and enrichment. It includes a setup UI (Config Manager), record-page Phone Assistant, Flow actions, and a global NF Apex API for custom code.
Is NumberForge based on Google libphonenumber?
Yes. NumberForge ports Google libphonenumber (currently v9.0.39) to Apex. We track upstream libphonenumber releases and ship updates for the significant ones. Parsing, validation, formatting, and enrichment run inside your org using packaged static resources.
Does NumberForge make outbound API calls?
No. Phone processing runs entirely in Salesforce. There are no callouts to external phone-validation services at runtime. Phone numbers are not sent to a third-party lookup API, so that processing stays in the org you already operate for GDPR.
How do I install and configure NumberForge?
Install the managed package from numberforge.net, assign the NumberForge admin permission set, and open Config Manager to define field rules per object. See the getting started guide for install, permissions, and optional metadata auth for automation deploy.
Is NumberForge listed on AppExchange?
No. You install the managed package from this site, not from a Salesforce marketplace listing. Phone processing runs entirely in Salesforce: there are no callouts to external phone-validation services at runtime. Sandbox orgs on test.salesforce.com are free with no time limit, so you can try the package there before production. A marketplace listing is not the current distribution path.
How much does NumberForge cost?
One plan with all features: €29,99 per org per month or €299 per org per year (~17% savings). Sandbox orgs on test.salesforce.com are free. Production orgs on login.salesforce.com require a subscription; eligible orgs get a 7-day trial (card required), one trial per org. See the pricing page for what is included.
How do I subscribe or manage billing?
Open NumberForge Configuration → License in your Salesforce org. Use Subscribe monthly or Subscribe annual to open Stripe Checkout. Pay with Visa, Mastercard, American Express, or wallets Stripe enables for your billing country (Apple Pay, Google Pay, Link). Use Manage subscription to cancel, update payment method, or download invoices. See the licensing guide.
How do I get support?
Start with the documentation and this FAQ. At launch, support is self-service; email [email protected] for licensing, install, and configuration questions.
How do I see what changed in a release?
Public package versions are listed on the changelog, with dates and the bundled libphonenumber version. We track upstream libphonenumber releases and ship updates for the significant ones. Detailed notes live in release notes.
How is NumberForge different from validation rules alone?
Validation rules only block bad saves. NumberForge parses international numbers, applies per-field format and region rules, can enrich with carrier or location metadata, exposes Flow actions for automation, and offers a triage UI on record pages for existing data cleanup.
Can NumberForge validate phone numbers on every Salesforce record save?
Yes. In NumberForge Configuration you define field rules per object. When save-time automation is deployed, NumberForge validates, formats, and optionally enriches those fields on insert and update. That is bulk processing in the Salesforce save path; for other paths use Flow or the NF Apex API. See the Salesforce phone validation guide.
Can I validate or format phone numbers in a Salesforce Flow?
Yes. NumberForge ships two invocable actions: NF Process Phone (one value) and NF Find Phone Numbers (extract numbers from text). See the Flow actions guide.
Is there a libphonenumber API for Apex?
Yes. NumberForge exposes Google libphonenumber through the global NF Apex class: parse, validate, format, findNumbers, short numbers, carrier, geocoder, and time zones. See the NF API Reference.
Does NumberForge check whether a phone number is in service?
No. Like libphonenumber, NumberForge checks whether a number is possible and valid for its region (length, prefix, pattern). It does not query carriers to see if the number is assigned or reachable. Carrier name, place, and time zone enrichment use offline metadata packaged in the org.
How were NumberForge performance claims measured?
We ran Apex benchmarks in a Salesforce org with NumberForge and another managed libphonenumber-based package installed together. Each scenario used the same inputs; we verified matching results before comparing CPU time and peak memory. The figures on our homepage are conservative roundings from three-run averages (parse workloads and validate-and-format loops).