SMS Emoji QR

A message-starting action

An SMS code can describe a recipient and, where supported, a draft message. It is not a bulk messaging platform and it should not be described as automatically sending a request. The SMS URI specification calls for user confirmation before sending. Keep the printed promise focused on opening or starting a conversation.

Approve the number and draft

Use a recipient the organization controls and has approved for the purpose. Keep a concise draft in ordinary language, even when an emoji reinforces the tone. Avoid including sensitive information or agreement language. Check the number and text displayed in the actual messaging application after scanning the final asset.

Plan for different devices

The application handoff depends on the device and its messaging setup. Test the intended platforms and document whether the result opens a draft, displays text, or requires another choice. A functioning SMS link in one application is not evidence of identical behavior everywhere. Provide an ordinary contact route for unsupported situations.

Connect the invitation to real operations

Tell the receiving team what inquiries to expect and where the invitation will appear. Do not invent instant-response promises. Decide what happens if the number or campaign changes. A friendly speech bubble is useful only when it leads to an appropriate, maintained conversation.

Use the full guide before production

The accompanying article covers recipient review, short draft copy, testing, alternate routes, and retiring old materials. It is planning guidance rather than an SMS tool. The site does not accept phone numbers, send messages, or connect a messaging service.

Reference: IETF: the SMS URI scheme. Reviewed for this guide on October 13, 2026. Product behavior and guidance may change.