Match the international display and the link target

RFC 3966 defines global telephone numbers as beginning with a plus sign and including a country code, and specifies using global form when it is available. Using that form in a tel link reduces dependence on a number that only makes sense within a local context. RFC 3966.

Two Way Medya’s public primary number can be displayed as +90 537 397 34 34 with tel:+905373973434 as its target. In this Turkish example, the domestic leading 0 is not added again after +90. Use the business’s verified international number rather than applying this example blindly to every country. Keep the number available as selectable text instead of placing it only inside an image.

Explain who answers the call

If several numbers are available, distinguish sales, technical support and the switchboard visibly. A visitor should not have to call each to discover the right team. If support in another language is genuinely available, explain which channel provides it. Publishing an English page does not by itself establish English-language phone support.

Where an extension is needed, show the switchboard number and extension separately and clearly. Appending extension digits directly to the main number can create a different destination. If automated extension handling is required, test it with the phone applications you support. A readable extension instruction may be the clearest first implementation.

Give business hours a time-zone context

“Call between 09:00 and 18:00” leaves an international reader with an unanswered question: whose time? State the confirmed working days and time zone together. “Weekdays, 09:00–18:00, Istanbul time” is only appropriate if it describes your actual operation; here it is an illustrative wording example.

Keep holiday hours, emergency support and normal support separate if they differ. A form or email outside phone hours should be a genuine alternative. Publish a response-time commitment only when the team has approved it and can sustain it. Do not invent a deadline to make the interface sound more reassuring.

Consider the desktop ending as well as mobile

On a phone, a tel link may hand the task to a calling application. A desktop may have no suitable application or may ask the visitor to choose one. Keep the visible number alongside the action so the visitor can copy it and call from another device.

  • Compare the button label with the destination number.
  • Give the number a meaningful context for screen-reader users.
  • Check that the link is reachable by keyboard.
  • Offer an alternative through the contact page for visitors unable to call.

Do not assume that the same number supports WhatsApp or another messaging service unless the business has confirmed it.

Separate link testing from a real call

First compare the HTML destination with the visible text. Then, on an authorised test device, check that the correct number reaches the calling screen without accidentally initiating a call. Connection and a staff response can be a separate test agreed with the business.

Review every occurrence if the number also appears in the footer, service pages and campaigns. Where practical, generate them from one verified content record. Defining the contact component this way during website design helps avoid overlooked copies when the number changes. It does not guarantee the availability of the telephone service.

Frequently asked questions

Is a spaced display number different from an unspaced link?

Spacing can improve readability. The country code and digit sequence must match. Check the display text and tel destination separately before publishing.

Is opening the call screen sufficient proof?

It demonstrates that the link opens the intended destination. It does not establish that the number is active, the call connects or somebody answers. Those require separate checks.

Sources & further reading

RFC 3966 — The tel URI for Telephone Numbers ↗
Web design & developmentLet’s discuss this service ↗