How to Create a QR Code for Email, SMS, or a Phone Call

CreationCreate by Type

Published

Share
Illustration for How to Create a QR Code for Email, SMS, or a Phone Call

Overview

To create an email, SMS, or phone call QR code, encode a link beginning with mailto:, sms:, or tel:. These schemes identify an email destination, a text-message recipient, or a telephone number. Whether a scan opens the intended app depends on the scanning software and the available handler—not just the QR image. The URI standards define the formats. Support after scanning depends on the device and reader. [1][2][3]

The biggest caveat is SMS prefilled text: the standard defines a body parameter, but that does not establish support across iPhone and Android scan paths. Treat it as a feature to validate, not a guaranteed result. [2]

The examples below are templates. Replace the sample address or number with a destination you control before generating or testing a code.

Email QR code: use mailto:

For a recipient only:

mailto:hello@example.com

For a subject and short message:

mailto:hello@example.com?subject=Pricing%20question&body=Please%20send%20details.

RFC 6068 defines these fields. The intended result is an editable email draft, not automatic delivery; the user can change it or cancel. [1]

SMS QR code: start with the recipient

For a recipient-only link:

sms:+12125550123

RFC 5724 also defines this syntax for a prefilled body:

sms:+12125550123?body=Please%20send%20details.

Apple’s archived SMS link reference describes a number-only link. Try a recipient-only link first on iPhone and Android. [4] For a mixed-device audience, start with recipient-only SMS and add a body only after testing your intended paths. [2]

Do not present scanning as sending a text. RFC 5724 says activating an SMS URI should not send a message without prior user confirmation. [2]

Phone call QR code: use tel:

tel:+12125550123

Use the international number with a leading + and country code when the number can be represented that way. RFC 3966 requires global form in that case; local numbers require a phone context. [3]

A tel: link identifies a number; it does not guarantee one identical screen everywhere. Apple documents a confirmation prompt for telephone links, while Android distinguishes opening a dialer from placing a call through native app actions. Test what the scanner offers before sharing. [5][6]

Create the QR code in five steps

These are generator-independent instructions, not verified steps for a particular product.

  1. Choose one action. Start with the simplest link above that meets your goal.
  2. Replace the example destination. Check the complete email address or phone number, including the country code.
  3. Use a generator that accepts the complete URI. If its website field requires HTTPS, look for a raw-text input or an appropriate contact-action input. Do not add https:// before mailto:, sms:, or tel: merely to satisfy the field.
  4. Generate and inspect the output. Compare the decoded payload with your intended string. For this direct-URI workflow, confirm that the code contains your action link rather than an unexpected web redirect.
  5. Test the exported image. Verify both the decoded destination and the action offered by the scanner. Stop before sending or calling unless you are deliberately testing a destination you control.

Keep prefilled text short. DENSO WAVE explains that increasing the data amount requires more QR modules; shortening the payload can reduce that requirement. This is not a substitute for testing the final artwork. [7]

For email subject and body values, use %20 for spaces, %26 for a literal ampersand, and %23 for a literal hash sign. Email body line breaks use %0D%0A. Preserve the ? and & characters that separate parameters. [1]

For example, the subject “Pricing & availability” becomes:

subject=Pricing%20%26%20availability

QR payloads are not HTML source. The separator between email parameters is a literal & in the encoded URI. Use & when writing that separator inside an HTML attribute—not when pasting the raw payload into a QR generator. Avoid double-encoding an already encoded value. [1]

For the RFC-defined SMS body parameter, reserved characters are also percent-encoded using UTF-8. Correct encoding does not remove the platform limitation described above. [2]

Test the scan path your audience will use

Use this as a validation plan, not as a claim that these tests have already been performed:

Check Record before publication
Native camera scanning Device, OS version, scanner, and offered action
Email Recipient, decoded subject/body, and ability to cancel
SMS Recipient; whether the body appears, disappears, or changes
Phone Complete number and confirmation/dialer behavior
Relevant in-app browser or scanner App/version, handoff result, warning, or failure
Final artwork Exported image and, if applicable, a physical print at its intended size

If the scanner reads the string but does not offer the action, do not assume the QR image is unreadable. Android’s documentation, for example, distinguishes URI data from the app action and requires an available handler. That supports investigating the scan-to-app handoff separately from decoding. [6]

Recommended fallback: print the address or number next to the code and label the action clearly—“Scan to email,” “Scan to text,” or “Scan to call.” If you need multiple contact choices or explanatory instructions, consider an HTTPS contact page instead of one direct action.

Before you publish

  • Replace every example destination and remove accidental whitespace.
  • Compare the decoded payload with the intended URI.
  • Verify email fields and any proposed SMS prefill on target devices.
  • Record scanner and in-app-browser results rather than assuming compatibility.
  • Test the final image or print and provide a readable contact fallback.

The practical workflow is: build the URI, encode it, inspect it, and validate the complete scan path. A standards-compliant string is the starting point—not proof that every device will handle it the same way.

References

[1] RFC 6068, The ‘mailto’ URI Scheme — https://www.rfc-editor.org/rfc/rfc6068.html

[2] RFC 5724, URI Scheme for GSM Short Message Service (SMS) — https://www.rfc-editor.org/rfc/rfc5724.html

[3] RFC 3966, The tel URI for Telephone Numbers — https://www.rfc-editor.org/rfc/rfc3966.html

[4] Apple Developer Documentation Archive. SMS Links. https://developer.apple.com/library/archive/featuredarticles/iPhoneURLScheme_Reference/SMSLinks/SMSLinks.html

[5] Apple, Phone Links (archived documentation) — https://developer.apple.com/library/archive/featuredarticles/iPhoneURLScheme_Reference/PhoneLinks/PhoneLinks.html

[6] Android Developers, Common intents — https://developer.android.com/guide/components/intents-common

[7] DENSO WAVE, Information capacity and versions of the QR Code — https://www.qrcode.com/en/about/version.html

Ready to create your QR code?

Create QR Code