SMS QR Code Generator – text with the number and message ready

The code stores an sms: link with the phone number and, optionally, a pre-written body — for example sms:+15551234567?body=I%27d%20like%20to%20join%20the%20waitlist. Scanning it opens the phone's built-in messaging app (Messages on iPhone, Messages or Google Messages on Android) with the recipient and text already entered. The phones apply slightly different formatting internally, so this tool builds the link both ways and tests which one each platform accepts, rather than assuming one format works everywhere.

Like email, nothing sends automatically — the person still taps send. That keeps the code from being used to fire off unwanted texts and lets the sender review the message first.

A storefront sign that texts a keyword to join a waitlist or loyalty list. A real-estate yard sign where a text gets a faster reply than a call. A gym or class flyer collecting RSVPs by text. An event badge offering “text me” with a pre-written introduction line so networking follow-up takes one scan instead of typing a new contact from scratch.

A QR code that opens a chat app like KakaoTalk only works if the person scanning already has that app installed and the sender has set up a channel or open chat link inside it — useful for an established business account, but a dependency the scanner has no control over. An SMS QR code uses the messaging app built into every phone, with no app to install and no account to set up on either side, which makes it the more reliable choice for a first point of contact with someone whose apps you can't assume.

Always include the country code with a leading + (+1 for the US, +82 for South Korea) rather than a local format. A number typed as a domestic format works when scanned on a phone from the same country but fails or opens the wrong contact when scanned abroad — always test the code on a phone with a different home country if it will travel.

A standard SMS is limited to 160 characters (fewer if it contains emoji or non-Latin characters like Korean, since those use a different encoding that fits about 70 characters per segment); longer text auto-splits into multiple linked messages on most carriers. Keep the pre-filled body short — a greeting and one clear instruction — and let the recipient add the rest.

Because the person scanning has to tap send themselves, an SMS QR code is inherently opt-in — nobody receives a text they didn't personally choose to send. That's worth stating on signage that runs a keyword campaign (“text JOIN to sign up”), since it reassures scanners the business isn't collecting numbers without consent. Test the finished code on both an iPhone and an Android phone before printing signage at scale — the two platforms occasionally differ in how they parse a pre-filled body with line breaks or emoji, and it's cheaper to catch that on a screen than after a print run.

Leaving off the country code, which breaks the code for any scanner outside the local area code. Writing a body over 160 Latin characters (or roughly 70 with Korean or emoji) and assuming it arrives as one message — some carriers split it in a way that garbles the pre-filled text. And assuming the recipient's texting app opens automatically before scanning — the phone needs a default messaging app set, which is true for almost every phone but not tablets without a SIM.

It's also worth deciding up front whether the pre-filled body should even carry the whole request, or just enough to start a real conversation. A body that reads “Hi, I'd like to book a table for Friday” gives the business context immediately; a body that just says “Hi” makes the QR code pointless, since the recipient could have typed that from scratch. Aim for the shortest sentence that removes the need for the sender to explain why they're texting.

One more thing worth checking: on some Android phones, an sms: link opens a chooser asking which messaging app to use if more than one is installed, adding an extra tap the iPhone flow doesn't need. That's a platform quirk, not a bug in the code — mention it in your own testing notes so nobody assumes the code is broken when the extra prompt appears.