Phone number QR code generator

The tel: payload

The code contains a tel URI — the scheme plus the number. Formatting characters people type for readability (spaces, parentheses, dots, hyphens) are stripped out; a leading + is kept because it carries meaning.

The whole payload for a US number:

That brevity is a real advantage: a tel: code is one of the smallest payloads on this site, which makes it coarse, forgiving, and scannable from further away than almost anything else you can print.

tel:+12025550123

Use the full international number

Encode the number in international form: plus sign, country code, then the national number without its trunk prefix — the format phones themselves use when roaming. +1 202 555 0123 dials correctly from anywhere; a local 0202 form works only inside one country and breaks the moment a visitor scans it.

There is no downside to the international form for domestic callers, and it future-proofs the print. If your material will never leave one building, you can get away with less — but 'never' is a long time for a sticker.

What actually happens after the scan

iOS and Android show the number and wait for a tap before opening the dialler; the call itself needs one more confirmation. No mainstream camera dials silently — a scan cannot ring your phone bill on its own.

Third-party scanner apps present their own confirmation screens, and a few only display the raw tel: string. The number is always recoverable either way, which is the point of the format.

Nothing is saved unless the person chooses to: after the call, your number sits in their call history like any dialled number, not in their contacts. If being saved is the goal, that is the vCard's job, not this code's.

Extensions and phone menus

The tel URI has syntax for extensions, but phones interpret it inconsistently — some pause and dial, some ignore it, some show it as junk. Encode the main number only.

Put routing instructions in the visible print next to the code: 'scan to call, then press 3 for service'. Words on paper are more reliable than dialling tricks inside the payload.

Where scan-to-call earns its place

The format shines wherever a call is the natural next step and typing is awkward: service stickers on machines and lifts, van doors and shopfronts, emergency and facilities contacts in stairwells, 'call for entry' signs at gates. The person is standing there with a phone in hand; the code removes the transcription step.

It works for any diallable number — mobiles, landlines, toll-free lines. The scanning phone just dials; nothing about the format assumes a mobile on the receiving end.

Because the payload is tiny, this is also the code to choose when print space is hostile: it stays readable at sizes where a vCard would already be failing.

One number, or something more?

A phone code carries a single call target — nothing is saved to contacts, and there is no name attached. If people should keep your details, a vCard code saves name, company, number and email in one tap.

If the conversation should start in writing, an SMS code opens a message draft, and a WhatsApp code opens a chat. Pick the code by the action you want the scan to trigger, not by the data you happen to have.

Frequently asked questions

A service-desk call route needs a canonical number

For a public service sign, encode `tel:+12025550123`, then show `+1 202 555 0123` in ordinary print beside it. RFC 3966 defines the `tel` URI scheme and distinguishes a telephone number identifier from a dial string: https://datatracker.ietf.org/doc/html/rfc3966 . That distinction matters when a local extension such as 417 works only from an office PBX. The QR generator can normalize spaces, parentheses and hyphens, but it cannot decide whether an extension, country code, call restriction, or account routing policy is correct. Test the final code on a phone that is not already in the organisation's calling context; the acceptance result is that the dialler presents +12025550123 for confirmation, not that a call was silently placed.

Do not turn a dialler shortcut into a contact directory

A call QR carries one destination only. In a clinic lobby, a number for reception can be useful, while a contact card with several departments, email addresses and website fields is a different task and a much denser payload. If the sign covers three countries, use a number whose international form is actually monitored and state the service hours beside the symbol. Review the route after any phone-system migration: a static code keeps its old number even after a new extension is published. For a proof set, scan the exported image, inspect every digit in the dialler, cancel the call, and compare it with the approved telecommunications record. If a handset inserts a country-specific prefix or rejects the URI, retain the visible number as the fallback. The QR code cannot prove that the call will connect, identify the person who answers, or bypass roaming, parental controls, or a device's confirmation screen.

Put the fallback where a caller can use it

Print the number with spacing that helps people read it, but keep the QR payload in its canonical international form. A sign that says only “scan to call” excludes someone whose camera is unavailable or whose phone policy blocks URI handling. For a roadside support board, add the service name and number, then scan from the installed height and distance. Check after a number port, IVR redesign, or change in opening hours: the URI may remain syntactically correct while the operational route has changed. The code saves typing; it must never be the only evidence of who will receive the call or when.

Keep number ownership reviewable

Record the responsible service, number, test date, and artwork revision together. That small record makes a later migration visible before an old sign becomes a dead or misrouted call shortcut.