A2P 10DLC is the US carrier registration system standing between a business and its first SMS: brand vetting, campaign review, trust scores, throughput caps and per-message fees. These guides cover what registration costs and why campaigns get rejected, and the structural point most guides skip: channels that never touch carrier SMS routes, like iMessage, sit outside the system entirely, with no A2P registration required, while consent law applies everywhere.
Most 10DLC guides stop at the approval email. Carriers and their vetting partners do not. A registered campaign can be pulled back into review at random, suspended over a flagged link or a complaint spike, or frozen because someone edited it, and while it is down you cannot send, cannot move your numbers, and keep paying the monthly registration fee. Here is what actually triggers a post-approval suspension and how to see one coming.
RCS on iPhone made "just switch to RCS" sound like the free upgrade to green-bubble outreach. Then you read the onboarding. Business RCS needs a verified sender approved by Google and the carriers, a review measured in weeks, and an SMS fallback that still runs on your A2P 10DLC registration. Here is the part the channel's marketing leaves out.
A2P 10DLC registration governs one thing: sending on US SMS carrier rails. Channels that do not ride those rails require no registration, and iMessage is the one built for conversations. What registration actually demands, the path that requires none, and the compliance that applies either way.
The piece that ranks for this comparison argues registered A2P SMS beats iMessage for business messaging. Some of its case is genuinely right, and three of its claims don't survive contact with how the law and the platforms actually work. Both halves, laid out.