Putting a keyword at the front of outgoing and incoming messages might be able to help as well if a users phone number was tied to more than one service.
That said, if you look up the best practices and use the very specific language / processes that the DCAs are looking for, you should be able to get approved with little effort.
Some things I’ve learned, in no particular order:
— If your provider (e.g. Twilio) has specific language they advise you include on a form / website / etc., use that exact language verbatim.
— For forms where you collect a phone number, have the compliance text very visible, perhaps even sacrificing UI/UX. After your campaign is approved, you can clean it up.
— Make sure you include your business / project name & opt-out instructions (reply STOP) in every sample message you submit for the campaign.
— Stick to the use case you selected & do not deviate. Make sure your campaign details align with the campaign description.
— Marketing-related campaigns — avoid if at all possible.
There may be a wrapper opportunity here.
You do need to have a “reason” that fits into a tree of business-like-things but you don’t need an EIN or anything. Mine was “technology industry” I think.
I wrote about my experience on reddit: https://old.reddit.com/r/twilio/comments/z9q3i1/10dlc_confus...
For very small audience or personal projects, PushOver or similar push notifications API app/services are decent very low friction options.
P.S. on Azure, not Twilio
I did basic RCS research a couple months ago & was pretty elsurprised how much RCS Business Messaging motivation there was, about retaining sms in the face of apps & notifications eroding the channel. Offering branding & other business features. It was eye opening context, new framing to me for why RCS is happening, far deeper than Android/everyone vs iPhone vs whatsapp. https://en.wikipedia.org/wiki/Rich_Communication_Services#RC...
TL;DR: Use a gateway independent service provider, or register with another carrier that lets you work around the restrictions for small use-cases at the cost of slightly higher technical complexity.
In seriousness, though, what those regulations boil down to is carriers self-regulating so that congress doesn't step in and regulate for them in ways that they won't like. It is _backed_ by congress, though, so the penalties are very real and potentially disastrous; up to $10k fine per offending message, not offending company or organization. Amounts that even for hobby projects can add up to very large amounts, very quickly.
Wild over-simplification incoming: Essentially all the hoops that twilio and others make you jump through are part cover-your-butt, and part cover-their-butt. All of it is dictated to them by The Campaign Registry (TCR) and the various Direct Carrier Aggregators (DCA's. Twilio is kind of a DCA unto themselves, and kind of not... it gets a little confusing in their case). Basically TCR makes the rules, and the DCA's interpret and implement them. Some of them don't leave a lot of room for interpretation (clear opt-out language, requiring positive confirmation of opt-ins for marketing traffic, etc.) and some of them are really fuzzy around the edges (your website needs contact information that matches EXACTLY your business registration information for some DCA's and not others. Some DCA's require very specific language on contact forms and privacy policies, some don't. Some need some language that covers the rules, but not specific language dictated to you by them. It turns into a minefield). Because the DCA's interpret the rules themselves, you get the wait-times. Almost all DCA's do manual verification of the campaign applications, and most of the time they sit in very deep queues.
Some providers, like Telgorithm and Bandwidth, allow you to act as your own campaign holder, whereas Twilio is actually the registered campaign contact. Twilio does that to lock you into their service - it makes it a pain to move your number because you have to re-apply to TCR for all new brands and campaigns. The other providers make that "easier", but you have to do more work on your end to capture and handle TCR webhooks, so there are plusses and minuses. However, one big plus of going with one of those other guys is that you don't _have_ to use the API's, you can do it all on the TCR and provider dashboards, and that lets you register special-case campaigns and brands such as conversational-only (doesn't require all the crazy opt-out language restrictions, etc.), and personal brands (can use DBA's and other low-touch business styles registered to your house address for a dollar). If you are only ever making a bot that only ever texts you personally, that can be a good way to go. However, the second it goes to someone else's phone there is a chance (low, mostly, slightly higher for Tmobile phone numbers for a big list of other reasons) that it will be auto-flagged as potentially invalid traffic. At low trust-scores that will result in not getting messages. If your trust scores continue to fall, they can turn you over to the FTC, and then... well probably best to fake your own death at that point. And before you ask, no, they don't tell you what your trust score is. You have to infer it from average delivery rates, which is just... super.
Your last option is a gateway provider. These are companies that give you a number (AWS has one with 800 numbers, for example), or have very limited behavior such as push-notifications only. Generally these work by registering as a brand of their own with TCR and creating for you an on-the-fly campaign that is configured in such a way that they are essentially sending traffic on your behalf. You'll pay a higher price per message to cover their risk, and if something looks wonky, they will cut you off way faster than anyone else, so expect weird errors and spotty delivery (especially to Tmobile numbers). They sit in a bit of a gray-area, and generally limit the kinds of traffic you can send, in some cases requiring that you pre-define the content of all messages you intend to send. So if you are doing a lot of dynamic message content generation, it might not work for you.
If you're still reading, well, congrats! I know that is a wall of text, and honestly I'm just scratching the surface and leaving a lot out. The goal of services like Twilio is to make it as simple for you as is technically possible, and honestly they do a pretty good job of it. My advice would be 1) if you are only ever sending a small number of messages, just to yourself, and of a fixed content, just use a gateway. 2) if you are generating dynamic content in the message bodies, or if you intend to send to a small number of phones, register a DBA and sign up with Twilio with your DBA (or LLC if you don't mind the extra tax work) as the business and do the wait-and-check dance. Expect that to take a month or more. 3) In any other case, or if you have a very limited use case, talk with the folks at Telgorithm and they can hook you up (I'm not affiliated with them - I just have used them in the past and really like them).
