TL;DR: CTIA guidelines are voluntary, and the document says so about itself. The May 2023 Messaging Principles and Best Practices states that it does not impose, prescribe, or require contractual or technical implementation on anyone in the messaging ecosystem, including the carriers. It still runs your texting program, because CTIA’s October 2025 Messaging Security Best Practices lists a pattern of abuse of industry best practices, including the Messaging Principles, as something a carrier risk assessment may act on, and says that for email-to-SMS traffic a sender who ignores the consent principles may see messages blocked. No demand letter, no cure period, just throughput. The May 2023 revision retired the P2P and A2P labels for Consumer and Non-Consumer, and the test is who sends, not how many: a rep texting one prospect from a work number is Non-Consumer traffic. Content sets the consent tier, with conversational at implied consent, informational at express consent, and promotional at express written consent. The document asks for a call to action that discloses five specific things, seven fields of evidence behind every opt-in, a confirmation message carrying five elements on any recurring campaign, opt-out accepted by phone, email or text and in natural language rather than only the word STOP, deactivation files processed daily, and no rented, sold, or shared lists. It rules out snowshoe sending across many numbers, grey routes, and any URL shortener whose web address and IP addresses are not dedicated to your exclusive use. Carriers have this much room because of FCC 18-178, the December 2018 declaratory ruling in WT Docket No. 08-7 that classified SMS and MMS as information services rather than Title II telecommunications, which is the protection text messaging never got and voice calling did.
Your texts stopped landing. The campaign is registered, the copy did not change, nobody sent a demand letter, and reply rates fell off a cliff about ten days ago. So who made that decision, and under what rule?
Probably a carrier. Probably under a document nobody can sue you for breaking.
What the CTIA guidelines actually are
CTIA is the trade association for the United States wireless industry. Its messaging rulebook is a document called Messaging Principles and Best Practices, last revised in May 2023. The scope section tells you plainly what it is not: as a set of voluntary best practices, it does not impose, prescribe, or require contractual or technical implementation on messaging ecosystem stakeholders, including Service Providers.
That sentence does a lot of work. The CTIA guidelines bind no carrier, no aggregator, and no sender. Stakeholders may choose to implement modified and additional requirements through their own guidelines, policies, and contracts, which is the polite way of saying your real rules live in your messaging provider’s terms and your carrier’s filtering policy. The CTIA text is the shared description everyone writes those from.
One change in the May 2023 revision still trips teams up. The labels P2P and A2P are gone. Traffic is now Consumer or Non-Consumer, and the test is the sender rather than the volume. If a business, organization, or anyone acting on its behalf sends the message, it is Non-Consumer. A rep texting one prospect from a work number is Non-Consumer traffic. There is no low-volume exemption to sit in.
Why CTIA guidelines bite faster than the law does
A TCPA claim is slow, expensive, and arrives with a docket number. Carrier filtering is fast, quiet, and arrives as nothing at all.
CTIA’s Messaging Security Best Practices, published October 2025, is the document that joins the two. Section 3.1 says a Service Provider may block a message where a risk assessment reasonably suggests the message is an Unwanted Message, then lists what that assessment may consider. One of the four listed items is a pattern of abuse of industry best practices, including the Messaging Principles and Best Practices. Section 4.2 says the same thing out loud for email-to-SMS traffic: a sender’s failure to abide by the consent principles may increase the risk that its messages are blocked.
So the CTIA guidelines become operative through filtering rather than litigation. You are not served. You are throttled, and the first signal you get is a reply rate.
Why carriers get to block business texting
Why does a carrier get to make that call at all? Because of how texting is classified.
In December 2018 the Federal Communications Commission ruled that SMS and MMS are information services, not telecommunications services, and not commercial mobile services. That is FCC 18-178, in WT Docket No. 08-7. Twilio and a coalition led by Public Knowledge had petitioned for the opposite outcome, specifically so that wireless providers could not block messages at will, and the Commission denied both petitions. It observed that in the voice context under Title II it has generally found call blocking by providers to be unlawful and typically permits it only in specific, well-defined circumstances. Texting never got that treatment.
That is the whole structure, bottom to top. Statute underneath, carrier discretion on top, and the CTIA guidelines in the middle telling everyone what acceptable behavior looks like.
The three consent tiers in the CTIA guidelines
The CTIA guidelines sort business messages into three kinds of content and attach a different level of consent to each.

- Conversational. The consumer texts you first and you answer quickly with a single relevant message. Implied consent, and the document expects no additional permission.
- Informational. Someone gives you a number and asks to be contacted: appointment reminders, welcome texts, alerts. Express consent, agreed for that specific informational purpose.
- Promotional. Anything that promotes a brand, product, or service, or prompts the recipient to buy something, go somewhere, or take action. Express written consent, through a signed form, a checked box, or equivalent.
The tier follows the content, not your intent. CTIA says adding a call to action such as a coupon code to an informational text may place that message in the promotional category. The consent you collected for appointment reminders does not stretch to cover it, and that single sentence is the most common way a clean program quietly becomes a dirty one.
What a business texting call to action must disclose
The CTIA guidelines define a call to action as the invitation to opt in, and want five things visible before anyone agrees to anything:
- The program or product description.
- The telephone numbers or short codes the messages will originate from.
- The specific identity of the organization or individual represented in the initial message.
- Clear and conspicuous language about opt-in and any associated fees or charges.
- Other applicable terms, including how to opt out, customer care contact information, and the privacy policy.
The document also says calls to action and the messaging that follows should not contain deceptive language, and that opt-in details should not be obscured in terms and conditions, especially terms about other services. If the only place your form mentions texting is paragraph nine of the terms, that is the exact failure that sentence was written for.
The seven consent fields behind every business texting opt-in
Consent you cannot produce later is consent you did not collect. The CTIA guidelines list the record they expect behind every opt-in:
- Timestamp of consent acquisition.
- The acquisition medium, such as a web form, a physical sign-up form, or an SMS keyword.
- A capture of the experience, meaning the language and action used to secure consent.
- The specific campaign the opt-in was provided for.
- The IP address used to grant consent.
- The phone number consent was granted for.
- The identity of the individual who consented.
Look at the third one. Not a checkbox value, the screen. If your signup page changes wording in March, you need to know which version produced an opt-in that draws a complaint in May. Most CRMs store a boolean. A boolean is not evidence.
CTIA also treats an opt-in as non-transferable and non-assignable, applying only to the campaign and the specific sender it was obtained for. On the floor that means marketing’s newsletter consent does not cover the sales team’s outbound cadence, and a list that arrived through an acquisition carries no consent at all.
How CTIA guidelines handle opt-outs
Opt-out is where the CTIA guidelines stop describing policy and start describing software. They ask senders to:

- Let a consumer opt out at any time.
- Support multiple mechanisms of opt-out, including phone call, email, or text.
- Send exactly one final confirmation message per campaign, after which no further messages go out.
- Use STOP as the standard wording, while still reading and acting on natural language such as stop, end, unsubscribe, cancel, quit, or please opt me out.
- Honor an opt-out despite de minimis variance in the reply, including capitalization, punctuation, and letter case.
Two of those break most sales stacks. Multiple mechanisms means the rep who hears stop texting me on a voicemail has to reach the same suppression list as the keyword handler. Natural language means your platform cannot only match the literal string STOP.
That is a systems requirement rather than a policy requirement. When calls, texts, and CRM updates live in separate tools, suppression gets synchronized by hand, and by hand means eventually. A business texting setup that writes every message and call outcome back to the same CRM record is what makes a voicemail opt-out visible to the rep who is about to send the next text.
Practices that end a business texting program outright
Some items in the document are tuning. These are not. Each one is a practice the CTIA guidelines tell senders to stop doing, and each is the kind of pattern section 3.1 of the security document describes as abuse.
- Rented, sold, or shared opt-in lists. CTIA says do not use them and build and vet your own.
- Stale numbers. Process telephone deactivation files regularly, which the document illustrates as daily, and remove deactivated numbers from opt-in lists.
- Snowshoe messaging. Spreading the same traffic across many sending phone numbers or short codes.
- Grey routes. Any path a Service Provider has not authorized for Non-Consumer messages.
- Public URL shorteners. CTIA wants a shortener whose web address and IP addresses are dedicated to your exclusive use, which a public shortener is not by definition.
- Anonymous links and numbers. Links and the sites they redirect to should identify the owner and carry contact information such as a postal address, and a message should not carry a phone number that forwards to an unpublished number unless the owner is named in the text.
- Borrowed numbers. Only text-enable a number your telecom or interconnected VoIP provider assigned to you.
The shortener rule catches honest teams more than bad actors. A rep pastes a public short link into a template, the template goes into a cadence, and now the program’s link reputation is shared with every other user of that service. Dedicated link domains are the cheap fix, and most text delivery problems get traced back to something this ordinary.
Where CTIA guidelines stop and the law starts
None of the above is a legal standard, and the CTIA guidelines repeat that twice in their own scope section. The legal layer is separate and it is the one with damages attached: the TCPA, the CAN-SPAM Act, the Communications Act of 1934 as amended, the Federal Trade Commission Act, and the rules the FCC and FTC adopt under them. CTIA names all of them and tells readers to get counsel before acting.
Keep the three layers separate when you audit a program, because they fail in different places and on different clocks.
- A legal problem shows up as a demand letter months later. Start with the statutes that govern marketing texts and with what counts as consent before the first message.
- A CTIA problem shows up as a falling delivery rate with no notice attached.
- A 10DLC registration problem shows up before you send anything, as a rejected or throttled campaign.
Teams that treat those as one compliance project usually fix the slowest one first and keep wondering why delivery never recovered.
CTIA guidelines FAQ
Are CTIA guidelines legally binding?
No. The Messaging Principles and Best Practices describes itself as voluntary and states that it does not impose, prescribe, or require contractual or technical implementation on anyone, including Service Providers. The practical weight comes from carrier and provider contracts, which may adopt modified or additional requirements, and from the filtering decisions described in the Messaging Security Best Practices.
Where can I find the CTIA short code directory?
CTIA does not run the directory itself. The US short code registry at usshortcodes.com is administered by the Common Short Code Administration, an LLC governed by CTIA on behalf of the wireless providers, with the technical side supported by CTIA’s partner GCH. What CTIA publishes is the Short Code Monitoring Handbook, and that document sets guidelines for short code programs rather than requirements. Each wireless provider still decides its own short code program rules.
Do CTIA guidelines apply to one rep texting one prospect?
Yes. The May 2023 classification turns on the sender, not the volume. A message sent by a business, an organization, or anyone acting on its behalf is Non-Consumer traffic, so the consent, disclosure, and opt-out expectations apply to a single outbound text from a sales rep.
What happens if a business ignores the CTIA guidelines?
Usually nothing visible, then filtering. The Messaging Security Best Practices names a pattern of abuse of industry best practices as an input to the risk assessment behind a blocking decision, and says failing to follow the consent principles may increase the chance of messages being blocked. Separate legal exposure under the TCPA and other statutes runs on its own track.
Audit your business texting program in one pass
Run it as an inventory rather than a policy review. Pull every enrollment path that produces a phone number and check which of the three content tiers the resulting messages fall into. Open the consent record for ten numbers at random and see how many of the seven fields you can actually produce, including the wording of the page they agreed on. Text STOP to your own program from a number that opted in through a non-keyword path, then check whether the rep’s next cadence step was suppressed. Look at what your templates link to and who owns that domain.
Four checks, and every one of them is answered by a record you either have or do not. That is the useful part of a voluntary document: it tells you what a carrier is looking at before the carrier looks.
Sources
- CTIA, Messaging Principles and Best Practices, May 2023. Primary document for the Consumer and Non-Consumer classification, the three consent tiers in Exhibit II, the five call-to-action disclosures, the seven opt-in record fields, the opt-out guidelines, and the rules on rented lists, snowshoe messaging, grey routes, shorteners, and text-enabling. api.ctia.org. Reviewed November 21, 2026.
- CTIA, Messaging Security Best Practices, October 2025. Section 3.1 on when a Service Provider may block a message and what a risk assessment may consider, and Section 4.2 on consent failures increasing blocking risk for email-to-SMS traffic. api.ctia.org. Reviewed November 21, 2026.
- Federal Communications Commission, Petitions for Declaratory Ruling on Regulatory Status of Wireless Messaging Service, FCC 18-178, WT Docket No. 08-7, adopted December 12, 2018 and released December 13, 2018. Classifies SMS and MMS as information services rather than telecommunications or commercial mobile services, and denies the Twilio and Public Knowledge petitions. docs.fcc.gov. Reviewed November 21, 2026.
- US Short Code Registry, Short Codes 101. States that short codes are administered by the Common Short Code Administration (CSCA), an LLC governed by CTIA on behalf of US wireless carriers, and that technical aspects of the registry are supported by CTIA’s partner GCH. usshortcodes.com. Reviewed November 21, 2026.
- CTIA, Short Code Monitoring Program Handbook, Version 1.9, effective August 2, 2023. Section 1.1 establishes guidelines for SMS, MMS and free-to-end-user programs that use a short code, and records that each wireless provider makes the ultimate decision about its own short code program requirements. api.ctia.org. Reviewed November 21, 2026.
Sources verified by the Kixie Research Team on November 21, 2026.
Ready to close more deals with Kixie?
See how Kixie's AI-powered tools can transform your sales and support operations.
Start Free Trial