Numbering, rates, routes, and translation methodology

How Localcall verifies international numbering facts, public prices, route availability, masked examples, and machine-assisted translations.

Numbering facts

We record calling codes, domestic and international prefixes, national-number length ranges, line-type patterns, and trunk-prefix transformations in a version-controlled evidence registry. Country regulators are preferred; ITU E.164 and ITU national numbering-plan records are the baseline. Each record includes its source links, source version, verification date, and correction notes.

Examples and validation

Published examples are deliberately masked with X characters, such as +61 4XX XXX XXX. They illustrate structure without publishing a number that could belong to a person or business. The interactive validator normalizes user input and checks it against currently supported Localcall route patterns; it does not prove that a number is assigned or reachable.

Rates and route health

Public per-minute prices come from the same rate snapshot used by the product. A route is described as available only when both a public price and a supported provider route exist. Pages expose the supported line types plus the public rate-update and route-verification times, but never provider identifiers, margins, customer activity, or private telemetry.

Translations

Localized editorial pages may be machine-assisted. Before search activation they must pass language detection, untranslated-text checks, controlled telecom terminology, numerical and URL preservation, required-section validation, factual back-translation, and RTL rendering checks. A locale is promoted independently; publishing English does not automatically publish all translations.

Public data

The non-proprietary evidence records are available as JSON.