What you are seeing
This fix makes the SMS code address the right number with the right message. You will decode the payload, compare the number and the message with the intended values, and rebuild the code with the SMS generator. Verify the fix by scanning and reading the drafted message on two phones, without sending it.
Likely causes
1.
Wrong number in the payload — Quick test: decode the payload and compare the number digit by digit with the intended number.
2.
Missing or wrong country code — Quick test: check the country code in the payload.
3.
Formatting characters breaking the number — Quick test: compare a plain-digit version with the formatted version.
4.
Non-standard SMS payload format — Quick test: compare the payload with the standard SMS format.
5.
Message text lost or garbled — Quick test: try a short message with plain characters and compare.
Step-by-step fix
Step 1: Decode the payload and write down the exact number and message it carries.
Step 2: Compare the number digit by digit with the intended number, including the country code.
Step 3: Remove formatting characters from the number and use plain digits.
Step 4: Rebuild the SMS with the SMS generator, using the verified number and a short, plain message.
Step 5: Scan the rebuilt code on two phones and read the drafted message without sending it.
Step 6: If the number is still wrong, check the source record the code was built from and correct it there.
Step 7: Retest the final code on two phones and confirm the number and message are correct before printing.
Putting this into practice
In practice, keep the intended number in one record and build the code from it, then check the proof against the same record. Two people checking the digits independently catches the typo that one person keeps missing. Record the before-and-after behaviour with the job file, so the fix is provable rather than anecdotal. When the same failure appears again, that record tells you whether the old fix held or a new cause appeared.
Common mistakes to avoid
- Letting a wrong-number SMS code stay in circulation while investigating the cause.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that scans but the SMS goes to the wrong number will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that scans but the SMS goes to the wrong number.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The decoded number matches the intended number digit by digit
- The country code is correct
- Scanning drafts the right message on two phones
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [SMS QR code generator](/sms-qr-code-generator)
- [QR payload inspector](/qr-payload-inspector)
- [QR offline verifier](/qr-offline-verifier)
- [QR scan log](/qr-scan-log)
- [QR safety checker](/qr-safety-checker)
- [blog](/blog)
