Before you send, QuickText reads your message the way your recipients would and points out things that often go wrong. You see it as the Message check card on the Send page, and it updates while you type.
The message check never blocks you. It only points things out, and you decide what to fix. You can turn it off under Settings > Sending > Check my message for common problems while I write.
How to read it #
Each item has one of three levels:
- Problem Something that will likely go wrong. Worth fixing before you send.
- Warning Worth a second look.
- Tip A suggestion to help your messages arrive and get replies.
When nothing applies, you see a green Your message looks good instead.
Your message is empty problem #
There is nothing to send yet. Write your message before you send.
Some details are missing warning #
You used a personalization tag like {{first_name}}, but some people have no value for it, so their message would have a blank spot.
How to fix it. Give the tag a fallback after the | sign. {{first_name|there}} writes the first name when it exists, and the word “there” when it does not. A tag with a fallback is always safe. Use See who on the finding to see who is affected.
Some people share the same number warning #
Two or more of your selected contacts have the same phone number, so that phone would get your message several times.
How to fix it. This is usually a duplicate contact. Check your Contacts for repeats and remove the extra one.
Everyone gets the exact same text warning #
You are sending an identical message to a lot of people. Identical bulk texts look like spam, both to carriers and to the people reading them.
How to fix it. Make each message a little different. Add a detail like Hi {{first_name|there}}, or a wording variation like [[Hi|Hey|Hello]], where each person gets one option at random.
Shortened link spotted warning #
Your message contains a link shortener like bit.ly or tinyurl. These hide where a link really goes, so carriers often block texts that use them.
How to fix it. Use the full web address instead, for example pythonandvba.com/your-page rather than bit.ly/abc123.
Longer than one text tip #
A single text holds about 160 characters. Emoji and special symbols shrink that a lot. Longer messages are split into several parts, and your phone plan may charge for each part.
How to fix it. Shorten the message if you want to keep it to one text. QuickText counts using your longest personalized version, so the count is realistic.
Words in all capitals tip #
ALL CAPS reads as shouting and is a classic spam signal, whether the whole message shouts or just one part like “CALL ME NOW”.
How to fix it. Use normal sentence case. A single short word like STOP or ASAP is fine.
No question in the message tip #
Carriers notice replies. When people answer, the thread looks like a real two way conversation instead of a one way blast, and your future messages arrive more reliably.
How to fix it. End with a question that invites a reply, like “What do you think?”. Skip this if the message is purely informational.
Starts with a link tip #
Messages that open with a link are treated with suspicion by spam filters and by people.
How to fix it. Say who you are first, then share the link.
Words that spam filters dislike tip #
Phrases like “act now”, “click here” or “call me now” are classic spam wording. Carriers filter on them, and readers have learned to distrust them.
How to fix it. Use friendlier, everyday wording. Instead of “Act now for a FREE consultation!”, try “Would you like to book a quick chat this week?”.
Very short pause for this many people tip #
Many messages fired off in rapid succession look automated to carriers. This shows up when you text a larger group with only a second or two between each one.
How to fix it. Give it a pause of about 5 seconds or more. On the Send page, click Change pace and set the pause between messages.
That is a lot of messages in one go tip #
You are about to text a large number of people at once. Even with pauses, carriers sometimes flag heavy texting from a normal SIM.
How to fix it. On the Send page, tick Send in batches. QuickText sends a portion now and continues when you run it again, skipping anyone who already got the message.
