SMS links—URIs that begin with the sms: scheme—tell phones and tablets to open the default messaging app with a destination number ready in the “To” field and, when you add parameters correctly, a draft already sitting in the composer. They are the lightweight cousin of click-to-call tel: links: perfect for “Text us” buttons on mobile landing pages, appointment reminders that deep-link straight into a reply thread, QR codes on posters, and email signatures where some readers are on phones and want to bypass copying a number manually. SynthQuery’s SMS Link Generator is a free, English-language utility that runs entirely in your browser. You pick a country calling code from a dropdown illustrated with regional flag emoji, enter the rest of the number using the same normalization rules as our WhatsApp builder, optionally type a pre-filled message body, and immediately see two fully encoded sms: variants side by side. One follows the Android-friendly pattern that starts query parameters with a question mark before body=. The other follows the classic iOS-oriented pattern that joins body= with an ampersand immediately after the subscriber portion. When there is no body text, both collapse to the same short link, because there is nothing to separate. You can copy either string independently, set which variant powers the HTML button snippet and the QR code, open a test link that hands off to the OS messaging UI, and export a compact anchor tag for pasting into static HTML or CMS blocks. Nothing is uploaded to SynthQuery for this workflow: the page only concatenates digits, applies encodeURIComponent to the draft text, draws a QR bitmap with the qrcode package after lazy loading, and updates the DOM. Carrier routing, segment counts, and whether a desktop browser can open Messages at all remain under the control of the user’s device and network—not this page.

The interface mirrors other SynthQuery link utilities so marketing and support teams can switch between SMS, WhatsApp, and QR workflows without relearning field names. The country selector lists common markets alphabetically, shows a Unicode regional indicator pair for quick visual scanning, and displays the numeric dial prefix in parentheses so you can confirm +44 versus +1 before typing the national portion. The national field accepts spaces, dashes, and parentheses; we strip everything down to digits and, when helpful, remove a single leading trunk zero that would otherwise duplicate what the country code already encodes. Optional message bodies support emoji, line breaks, marketing copy, and merge placeholders you plan to replace upstream—up to the same generous character ceiling used on the WhatsApp page, with an explicit validation message if you exceed it. Because SMS transports bytes differently than WhatsApp once the message leaves the composer, we surface a reminder that long drafts may split into multiple segments on the carrier side even though the URI itself is valid. Outputs always show both sms: spellings whenever a body is present so engineers can ship the Android default while support staff copy the iOS string into knowledge-base articles that skew toward iPhone readers. The HTML snippet uses a high-contrast inline-styled button with system fonts for maximum paste survival inside email clients and hosted CMS editors that strip external stylesheets. The QR preview encodes whichever variant you designate as primary—handy when print collateral targets a single platform family. Clipboard actions reuse the same toast confirmations as the WhatsApp generator, and image copy attempts use the async ClipboardItem path when the browser allows it, falling back to PNG download when not. Keyboard focus order walks through country, phone, message, style selector, test buttons, copy targets, and QR actions without traps.

RFC 5724 defines the sms: scheme at a high level: the path carries an optional subscriber (your number) and parsers may accept query parameters such as body=. Real-world implementations diverge: Android’s Telephony stack historically maps ?body= into the SMS intent extras, while iOS URL handling examples in Apple’s archives show sms:number&body=message without an intervening question mark before body. SynthQuery therefore emits both literals whenever message text exists so integrators can choose per audience. We normalize the subscriber to a plus sign followed by international digits only, then percent-encode the UTF-8 body via encodeURIComponent so spaces become %20, ampersands become %26, and emoji become percent sequences. Extremely long bodies can exceed practical URI limits on some browsers even though the spec is silent—treat two thousand characters as a soft ceiling and test on physical hardware. The generator does not validate carrier routes, short-code availability, or whether the destination accepts SMS at all; those checks belong to operations and compliance teams. QR codes embed whichever primary string you select; error correction defaults suit typical print sizes. The page never dials numbers itself—it only assigns window.location.href during tests—so telephony billing remains unchanged until the user presses send inside their messaging client.

Marketing teams embed SMS CTAs beside WhatsApp and voice options so regional audiences can pick the channel their carrier plan favors. Retailers print QR codes on receipts that pre-fill “RETURNS ” plus a store code, accelerating customer support chats without forcing consumers through a login wall first. Healthcare and appointment-driven services pair reminder emails with sms: links that open a reschedule keyword already typed, reducing thumb work on small screens. Event organizers place dual QR codes—one for iOS-heavy guest lists and one for Android-heavy volunteer teams—when analytics show platform skew, or they standardize on the Android variant when testing proves iOS accepts it in their geography. Field-service businesses add “Text dispatch” buttons to lightweight PWA dashboards where technicians wear gloves and need fewer taps than a tel: call. Nonprofits running pledge drives combine short codes with web links but still publish sms: anchors for donors who prefer native messaging logs for their records. Customer-support leaders link from knowledge bases directly into SMS when chat volume spikes and asynchronous texting beats waiting on hold. Product teams prototyping two-way SMS integrations use these links to exercise handset behavior before Twilio or carrier APIs enter the picture—knowing that the generator only creates the URI, not the server-side webhook. Whenever you also run WhatsApp Business entry points, generate parallel wa.me URLs from the WhatsApp Link Generator and keep messaging policies aligned across channels.

Follow this sequence whenever you are wiring a new “Text us” call to action, refreshing QR artwork, or documenting support paths for mixed Android and iOS user bases.