How to Make a Phone Number Clickable in an Email Signature

To make a phone number clickable in an email signature, wrap the visible number in a link whose href begins with tel::

<a href="tel:+1-212-555-0101">+1 212 555 0101</a>

Use the complete international number in the link target. The recipient's device then decides which available calling application, if any, can handle that link. A tel: link identifies a telephone number; it does not guarantee that every email client will preserve the link or that every device will place a call in the same way.

Visible Number and Link Target Are Different Jobs

The text between the opening and closing <a> tags is what the recipient sees. The value after href="tel: is the telephone URI the device receives.

Keeping those jobs separate lets you make the displayed number easy to scan while keeping the URI predictable. It also makes testing easier: do not stop after checking that the number looks right. Inspect the actual link target too.

The IANA URI scheme registry lists tel as a permanent scheme. RFC 3966 defines its syntax and explains that a telephone URI is an identifier rather than a complete set of dialing instructions.

Use a Global Number in a Public Email Signature

For a signature sent across locations and time zones, use the global form: a leading +, country code, and subscriber number.

tel:+1-212-555-0101

RFC 3966 permits the visual separators -, ., (, and ) inside a telephone URI. Spaces are not listed as visual separators, so a compact or hyphenated target is the safer standards-based choice. The displayed text can still use spaces when your signature editor lets the visible label and target differ.

Avoid a public link such as tel:212-555-0101. A local number lacks the information needed to identify it globally. RFC 3966 requires a local telephone URI to include a phone-context parameter, but a complete global number is usually clearer for an externally shared signature.

The global format follows the international numbering-plan model documented in ITU-T Recommendation E.164. That recommendation defines numbering structure; it does not establish compatibility with a particular email application.

What About Phone Extensions?

RFC 3966 defines an ext parameter:

<a href="tel:+1-212-555-0101;ext=204">+1 212 555 0101, extension 204</a>

This identifies an extension, but it does not prove that a recipient's email client and calling application will dial it automatically. Test the exact combination your audience uses. If extension behavior is important, keep the extension visible so a person can enter it manually.

What MySigMail Actually Generates

MySigMail treats the phone field as text and uses the entered value to build a tel: target. For example, entering:

+1-212-555-0101

produces this target in the signature markup:

tel:+1-212-555-0101

MySigMail does not currently normalize the number into another format or validate it against RFC 3966 before creating that link. Enter a standards-friendly global value instead of relying on the editor to repair spaces, remove a domestic trunk prefix, or add a country code.

If you are deciding which details deserve space, start with the client-facing professional signature baseline. A phone link is useful only when someone owns the number and recipients have a reason to call it.

Reproducible Phone-to-Link Matrix

We checked how the current MySigMail generator maps the phone field on August 7, 2026. Its operation is literal: phone value → tel:phone value. The RFC column below is an editorial syntax check against the global-number rules; it is not an email-client compatibility test.

We also loaded a minimal anchor in a Chromium browser and inspected its DOM. The visible +1 212 555 0101 remained human-readable while both the href attribute and resolved property remained tel:+1-212-555-0101. That confirms the HTML distinction, not what Gmail, Outlook, Apple Mail, or a particular calling application will do after delivery.

Add a Clickable Number in MySigMail

1. Add or edit the phone field in your signature.
2. Enter a complete global number such as +1-212-555-0101.
3. Preview the signature and confirm the visible number is correct.
4. Install the rendered signature using the instructions for your email client.
5. Send a real message to an external inbox and inspect the received link before relying on it.

The editor's phone input is not a reachability check. Confirm that the number belongs to the right person or team and that someone can answer it.

Test the Received Signature, Not Just the Editor Preview

A useful test has four layers:

1. Source: confirm that the final anchor contains the intended href="tel:..." value.
2. Delivery: send the signature through the actual mail system and inspect the received message. A client or security layer may transform markup.
3. Interaction: tap or click the received number only on a device with an appropriate handler configured.
4. Outcome: verify the proposed destination before approving any call, especially for international or paid numbers.

Repeat the delivery and interaction steps for the few client-and-device combinations that matter to your organization. A browser DOM check alone cannot substitute for received-message testing. Our mobile signature guide covers the broader layout and content checks that should accompany this link test.

Troubleshooting Clickable Phone Numbers

The number is visible but not clickable

Inspect the received markup. Plain text that merely resembles a number may be auto-linked by one client and left untouched by another. An explicit anchor with a tel: target is more intentional, but delivery systems can still alter HTML.

The link opens no calling application

The device may not have a handler assigned to the tel scheme. This does not necessarily mean the HTML is malformed. Check the target first, then the device configuration.

The wrong number appears in the calling application

Compare the visible text with the actual href. A mismatch is easy to miss and can send the recipient somewhere unexpected. RFC 3966 specifically recommends making the telephone URI's number visible so the action is predictable.

The number works locally but fails for international recipients

Replace the domestic-only target with a complete global number beginning with + and the country code. Do not assume a recipient shares your local dialing context.

An extension does not dial automatically

Keep the extension in the visible label and test it with the intended calling application. Treat ;ext= as structured identification, not a universal promise of automated keypad behavior.

The Practical Rule

Use a readable global number, make the target explicit, and test the installed signature after delivery. The reliable pattern is:

<a href="tel:+1-212-555-0101">+1 212 555 0101</a>

Build the signature in MySigMail, enter the phone field in a standards-friendly global form, then verify the received link in the environments that matter to you.