As you know public URL shorteners are at high risk of being identified as spam quickly, thus they should never be used on 10DLC. Sinch recommends you use a customer owned domain/ULR shortener. Read below for best practices to ensure your custom URL shortener doesn’t get blocked by carrier network filtering.
If you have customers sending out unwanted messages to a list of contacts that did not provide proper consent and the messages include your custom URL shortener, it is at risk of being reported as spam by the end users and getting blocked by the carriers. This will affect delivery of all messaging for customers utilizing your URL shortener.
It's important to make sure your customers are gaining proper consent from their clients, especially if you allow the ability for your customers to freely upload contacts into your CRM/messaging platform.
Some key items to review with your customers before they start sending messages:
If you are not reviewing these with your customers when you onboard them, especially when it comes to uploading contacts, it may be best to advise your customers to utilize their full URL in their messaging until their opt in methods are properly vetted by your team and confirmed fully compliant. This will reduce the chance of your custom URL shortener getting blocked by the carriers, which will affect any customer utilizing your shortened link in their messaging. Don’t let your URL shortener get blocked. Follow these best practice to help prevent your domain from being blocked.