How to add a click-to-call button to your website (the tel: link), and what to put on it

The line to copy

Here is the whole thing. Swap in your own number and paste it where you want the button. The sample number is the made-up one used in the standard itself.

<a href="tel:+12015550123">Call now</a>

That is all a click-to-call link is. The web developer reference MDN shows the same pattern under "Linking to telephone numbers", and says what a tap does depends on the device: "Cellular devices autodial the number."

There are two parts, and they do different jobs:

• The address, inside the quotation marks after href=. The phone reads this. The visitor never sees it.
• The words, between the two tags. The visitor reads this. The phone ignores it.

If you would rather show the number than a label, put the number in the words part and keep the address the same:

<a href="tel:+12015550123">(201) 555-0123</a>

If someone else looks after your website, send them this page. If you use a site builder, the idea is the same as when you add a chat window to your site: find the place that takes a line of code, or the link setting on a button.

How to write the number inside the link

The format of a tel: address comes from a public standard called RFC 3966, "The tel URI for Telephone Numbers", dated December 2004. Three of its rules matter for a small business site.

1. Start with the plus sign and the country code. The standard says: "All phone numbers MUST use the global form unless they cannot be represented as such." And: "Globally unique numbers are identified by the leading "+" character." For a United States number that means +1, then the area code, then the seven digits.
2. No spaces. The standard says tel: addresses "MUST NOT use spaces in visual separators". A number pasted from your letterhead often has spaces in it. Take them out.
3. Hyphens, dots and parentheses are allowed but do nothing. The standard says "Phone numbers MAY contain visual separators" and that they "merely aid readability and are not used for URI comparison or placing a call." Its own example is tel:+1-201-555-0123. Digits only is the simplest choice and the hardest to get wrong.

A quick check before you publish: count the digits after the plus sign. A United States number has eleven, the 1 and then ten more.

Use the same number, written the same way, everywhere a customer can find you. Google's guide to business details in search results describes the phone field as "A business phone number meant to be the primary contact method for customers" and adds: "Be sure to include the country code and area code in the phone number." More on keeping the number the same on Google is in the phone number and chat on your Google Business Profile.

What words to put on the button

MDN's rule for any link is short: "The content inside a link should indicate where the link goes, even out of context." It calls linking only the words "click here" or "here" a "sadly common mistake". For a call button, that means the words should say a call is about to start. Any of these does the job:

• "Call now"
• "Call [business name]"
• "Call for a quote"
• "Call (201) 555-0123", with your own number, if you want people at a desk to be able to read it and dial by hand

Words to avoid on a call button:

• "Contact us" or "Get in touch". The visitor expects a form and gets a dialer.
• "Click here". It says nothing about what happens next.
• "Open 24/7" or "We always pick up" unless it is true. If a call after six goes to voicemail, do not promise otherwise on the button. Put your real hours beside it and make the greeting match: what to say in a business voicemail greeting.

One more honest point. If only an icon of a handset is shown, with no words, a person using a screen reader has nothing to go on. Keep words on the button.

How big to make it, and where to put it

A call button is tapped with a thumb, often with one hand, often outdoors. Three published sizes are worth knowing. We read all three today.

• Google's web.dev guide: "A minimum recommended touch target size is around 48 device independent pixels on a site with a properly set mobile viewport." It adds that this "corresponds to around 9mm, which is about the size of a person's finger pad area."
• MDN: "A minimum size of 44×44 CSS pixels is recommended." It also says "Text-only links in prose content are exempt from this requirement".
• The web accessibility standard, WCAG 2.2: its "Target Size (Minimum)" rule, level AA, sets the floor: "The size of the target for pointer inputs is at least 24 by 24 CSS pixels", with listed exceptions.

So 24 is the floor, and 44 to 48 is what the guidance recommends. Aim for 48. Leave room around it too. The web.dev guide says "Touch targets should also be spaced about 8 pixels apart, horizontally and vertically," so a thumb aiming at "Call now" does not land on the menu beside it.

Where to put it is our own advice, not taken from a source:

1. In the top bar of every page, so it is on screen the moment the page loads.
2. Again at the end of each page, beside your form or chat, for the person who read to the bottom.
3. In the footer, with the number written out, for people at a desk.

Then test it. Open your site on your own cell phone, tap the button, and let it ring through. Do it once in working hours and once after closing, so you hear what a customer hears. The 20-minute missed-call audit shows how to count the calls that got no answer.

What happens on a computer with no phone

A tel: link does not act the same everywhere. MDN says "tel: link behavior varies with device capabilities" and lists what can happen besides a cell phone dialing: "Most operating systems have programs that can make calls," and "Other behaviors include saving the number to contacts, or sending the number to another device."

You do not control which of those a visitor gets. That is why the number should also be written out somewhere on the page, and why a person at a desk should have a second way to reach you that does not need a phone at all, such as a short form or a web chat.

Know how many people tap it

A tap on a call button is the nearest thing a website has to a ringing phone. It is worth counting. If your site has a visitor counting tool, ask whoever set it up to count taps on the tel: link as its own event. We did not read any tool's instructions for this guide, so we give no steps here. The wider picture, including asking every caller how they found you, is in how to track where your leads come from.

Keep in mind what a tap does not tell you. It says a dialer opened. It does not say the call was placed, or that anyone picked up. Your phone records answer that, and what a missed call costs shows how to put your own numbers on the ones that were not answered.

Where NewFrontDesk fits, honestly

You do not need us for any of this. A call button is one line of code on your own site, and the call goes through your own phone company. NewFrontDesk is not a phone carrier. It does not place calls, forward calls or pick up your phone. Missed-call text-back is built and tested but is not switched on yet, so no texts are being sent today.

What works today is the web chat and the lead inbox. They sit beside your call button for the visitor who would rather type than ring, or who taps "Call now" after closing and gets no answer. Their name, number and what they need go into one list with a status. What is built and what is not is on the status board. To talk it through, call (346) 913-7215 or request setup.

Sources

• MDN Web Docs: the anchor element (linking to telephone numbers, link text, size and spacing of links)
• RFC 3966: The tel URI for Telephone Numbers (December 2004), sections 5.1 and 6
• web.dev (Google): Accessible tap targets
• W3C: Understanding WCAG 2.2 success criterion 2.5.8, Target Size (Minimum)
• Google Search Central: local business structured data (the telephone property)

Sources read on October 10, 2026. Every page listed opened. The web.dev page says it was last updated on March 31, 2020, and the Google Search Central page on September 8, 2026. We did not open the help pages of any website builder or visitor counting tool, so this guide gives no builder-by-builder steps. We did not test the link on every phone and browser; what a tap does on each device is as MDN describes it. The button wording and placement advice is our own, not taken from a source. The sample number is a made-up one from the standard, not a real line.