Mobile carriers may reject the text messages sent via PastorsLine. There are known and unknown reasons why this happens.
Sprint and T-Mobile have simultaneously begun doing more aggressive filtering. As our vendor continues to work with carriers to allow for sending mass texts via a local, 10-digit number, we have decided to add more redundancies.
One of the known reasons carriers block messages is when mass text messages include URLs. The carriers’ machine learning software decides this activity is unusual, that it looks like a spammer’s phishing attempt. The chances of being blocked increase if the message includes specific known URL shorteners and things such as ‘bit.ly’ or ‘goo.gl’. Even worse is if it includes ‘http/https’.
Our main recommendation is to use our short code to send these messages that are being filtered. When using short code, we do not automatically convert your link into a shortened link. It will send the link as-is. You will see this message flash on the screen for a few seconds when sending links from the short code:
Short codes at the moment...
NOTE: Only owners / admins can view the short code keyword page. Users and restricted users cannot.
The mobile carriers have approved our short code: 77411. We have tested and implemented it in our system.
Note: The use of the short code requires a signature. A signature lets recipients know who the message is from, and allows them the chance to “opt out” of receiving future messages from you. This signature cannot be removed. The characters for this signature are also included in the total character count for your message.
Here’s how you can use our short code:
- Send bulk messages in both the legacy inbox and the new HUB—MMS or SMS.
- Select a signature (required) when sending messages.
- Reprocess failed messages to increase the deliverability.
- Use the short code as the “from” number in Automated Message Campaigns
- Use this with keywords (coming soon!).
- Apply it to campaigns except for Automated Message Campaigns.
- Use it outside of US marketing.
Why a short code?
- We were responding to the rapid and sporadic changes with carriers in the US about filtering.
- It’s the best option (speed and deliverability) when sending large bulk messages—though we do offer secondary numbers for a less spammy feel.
- Also read about the pros and cons of using a shortcode: SMS text messaging, short and long codes explored
Other solutions that can help:
Another recommendation, if you do not want to use a short code, is to use secondary numbers to spread the load. We also suggest avoiding the known keywords that trigger blocking. Another help is to use the Rebrandly URL shortening service.
We have now integrated Rebrandly for you. We have used custom new domain names to attempt to bypass the carrier algorithms. These new names will more successfully deliver your messages across several domain names.
[NOTE: For full details about your Rebrandly options, check out this article:
Custom PastorsLine domain names we are using.
Previously Used (retired)
We are removing the www. in front of all links sent to a group message as the WWW, though it ensures it appeared as a link, it casing your messages to being filtered. This is why we retired the short domain names that don't appear as links when sent.
When sending these links in group messages, the version that is shortened looks like chch.nl/123 which has been tested to our best ability to work on mobile OS SMS apps. The ones retired doesn't. In either case, if you just send the short domain alone, it may not be recognized as a URL at all but that should never be the case for your app.
Hopefully, our workarounds and fixes will give you the best of both worlds: the power of a shortcode and the personal friendly touch of a local number. You shouldn't have anything to do now, but let us know if you are still seeing issues.