How to create an SMS QR Code on AI Two

What an SMS QR code does

You enter the phone number and message body, generate a QR image, and download a scan verified PNG that opens the default messaging app when scanned.

When I tested a booth keyword on a trade show tent card, the scan landed in compose with the number and body prefilled so staff did not repeat instructions aloud in a noisy hall.

Credits apply per generation. I lock the number and body text first, then pick print size and styling if the form offers it.

Stay in QR Studio for phone, email, and other contact generators when the job is messaging instead of a website URL.

I treat SMS codes as staff facing shortcuts on signage. If the number or keyword changes, I regenerate and reproof before reprint.

Scan verification catches broken patterns before download. I still proof on paper at final size under venue lights.

In my experience, a short call to action beside the code helps guests know the scan starts a text thread, not a voice call or email compose screen.

For seasonal campaigns I date the filename so old tent cards are not mixed with a new keyword after operations updates routing.

I keep a printed proof in the front desk binder so weekend staff scan the same code visitors see on the counter card.

How to run it step by step

Step one: confirm the published number including country code and the exact body text legal approved. Step two: open SMS QR Code in QR Studio. Step three: enter number and message, generate, wait for scan verification, download. Step four: print or embed at the size you need. Step five: scan with two phones before a large print run.

I keep a screenshot of the live messaging policy in the project folder beside the PNG.

Store the file with the department name in the filename notes.

If operations changes the line or keyword, regenerate. Do not edit modules in a layout app.

When I proofed a window cling, afternoon sun glare was the real test, not the monitor preview.

I note print width in millimeters beside the filename for vendor reorders.

If one phone struggles, I enlarge the art ten percent and regenerate.

I add the keyword in plain text under the code for visitors who prefer typing on slow networks.

I proof once on iOS and once on Android before I approve a signage run. One platform can fail while the monitor looks fine.

Credits apply per generation, so I lock the number and body text before I explore color styling options.

When the same counter also needs a voice line, I keep a separate Phone QR in the same folder instead of forcing one generic link.

Print and placement tips

Use high contrast modules on a light field for counter cards, truck panels, and window stickers.

Matte stock reduces glare. Glossy cards can mirror pendant lights into the camera.

Size for the real viewing distance. Guests often scan from arm length at a reception desk.

Leave a quiet zone free of logos and headshots.

Place the code where thumbs naturally reach on a folded tent card. Corner placement on folded stock fails in the wild.

Test under the lighting that matches the install site, including bright storefront sun and warm office bulbs.

Avoid printing over busy photography backgrounds without a white sticker island.

For outdoor service trucks, bump module size and quiet zone because phone cameras struggle under mixed daylight and shade.

Older cameras need bigger quiet zones than new flagships, so I size for the weakest phone I expect at the counter.

Mistakes I avoid

Using a personal mobile number on public signage. I publish a shared operations line first.

Skipping the phone proof because the PNG verified on screen.

Printing five hundred inserts before a two phone test.

Saving a low resolution PNG and upscaling in the layout app.

Mixing QR art with heavy dither textures that eat module edges on press.

Pointing the code at a website URL when the brief needs a click to text flow.

When to use another QR tool

Need a click to call flow instead of text? Open Phone QR Code. Need pre addressed email? Email QR Code. Need WiFi, menu, or PDF payloads? Essential types in QR Studio. Need scan counts by campaign? Dynamic codes in My QR Codes rather than a static SMS PNG alone.

The contact and messaging cluster guide maps sibling pages. The QR Studio pillar maps social and essential tools when the job is not SMS.

Business cards that promote several contact paths sometimes need separate codes per channel instead of one generic link.

If legal asks for analytics on print campaigns, I pair a dynamic tracking code with the creative brief while keeping the SMS payload tested on paper.

After the download

I attach the verified PNG to the print vendor ticket with quiet zone notes so prepress does not crop modules.

For front desk installs I schedule a scan test after mount when lighting matches peak visitor hours.

If operations rotates numbers seasonally, I date the filename and retire old counter cards so staff do not post outdated text targets.

I keep a screenshot of the published number and body text beside the PNG in the project folder for quick audits when a guest reports a failed scan.

Weekend staff sometimes swap counter creative without telling marketing, so the binder proof is the source of truth for which code is live today.

I store the payload strings in a text file beside the image so future teammates know which line the card texts without opening design files.