A phone link can display the correct local number yet open a different number in the dialler. Treat visible copy and the tel destination as a pair. For international visitors, an agreed global-number representation avoids silently relying on the visitor’s country context.
Who should use this acceptance brief
Trades, mobile services and local enquiry websites. Use this as a scoped commissioning task for a website supplier. Where system evidence is required, a teaching file is not a substitute.
Source-bound platform fact
RFC 3966 defines tel identifiers, including global numbers and local numbers with context. Handling a tel link still depends on the device and installed applications. RFC 3966: telephone URIs · Checked 16 October 2026.
Filled teaching example
Synthetic example, not a client case. Inputs, expected decisions and counterexamples follow; no live platform integration is claimed.
On narrow screens, scroll to read the complete table.
| Input / case | Check basis | Expected decision |
|---|---|---|
| display +61 3 0000 0000 | tel:+61300000000 | same digits |
| same display | tel:+61300000001 | mismatch |
| display 03 0000 0000 | no approved global mapping | manual verification |
Run the acceptance exercise
- Confirm the destination with the number owner, using a non-customer test record.
- Compare normalised global digits, including any deliberate extension separately.
- Open the dialler without placing a call and record what the device displays.
Interpret the result and retain evidence
The example uses a synthetic fixed-line placeholder, not an instruction to call it. It removes ordinary display separators but refuses to infer a missing country code. A matched URI proves neither that the line is staffed nor that a call converted; those require separate operational evidence.
Limits before implementation
No automatic number verification, outbound call or telecom-routing claim. Preserve accessible link text and provide copyable contact details.
Replay the finite example
Save both files in one folder and run with Node22.13 or newer. These finite checks are not a live service or certification. Filled inputs and expected outputs · Inspectable functions
node decision-check.mjs click-to-call-number-match.json