What Is SMS Consent and Who Has to Prove It

Updated 13 min read How we research

TL;DR: SMS consent is a documented permission that ties one phone number to one named business and one category of message, and the reason it matters operationally is that you are the party who has to produce it. The FCC’s 2003 order put text messages inside the phone rules, stating that the prohibition covers both voice calls and text calls to wireless numbers including short message service calls. The 2012 order that created prior express written consent is blunter about who carries the weight, saying that should any question about the consent arise, the seller will bear the burden of demonstrating that a clear and conspicuous disclosure was provided and that unambiguous consent was obtained. Written does not mean paper, because consent collected by email, website form, text message, telephone keypress or voice recording counts under the E-SIGN Act. The federal definition names most of the fields a usable record needs, which are the signature, the specific telephone number the signer authorized, the named seller, the message type, and the disclosure that signing is not required as a condition of purchase. Store the version of that disclosure as well, which the rule does not ask for and which is the field teams most often wish they had kept. Revocation rules change on November 25, 2026, when callers may read a revocation as applying only to the category of informational messages it was aimed at, and may designate an exclusive means of revoking from a short list of automated methods. Neither one helps a marketing list, where a single opt-out still ends all marketing from that sender. The failures are predictable. A consent captured by marketing that sales then uses for a different message type, an opt-out processed in one system while another keeps sending, a purchased list whose disclosure named someone else, and a rep texting from a personal phone where no record exists at all. Store SMS consent as a record with a timestamp, a source, a scope and a disclosure version, because a checkbox cannot answer the only question anyone will ever ask about it.

SMS consent is a recipient’s documented permission for one named business to send one kind of text message to one specific phone number. Most teams store that as a single checkbox on the contact record. The checkbox is not the thing anyone will ask you for.

What gets asked for is the record behind it. Who gave permission, which number they gave it for, what they were told at the moment they gave it, what they actually did to give it, and which messages that permission covers. A field that says opted in answers the first question and none of the rest.

That gap is the whole subject. SMS consent is not a state your CRM holds. It is a fact you have to be able to show later, and the showing is on you.

Texting feels like its own channel. Legally it is not a separate one.

When the FCC built the national do-not-call rules in 2003, it stated that the prohibition on automated calls to wireless numbers encompasses both voice calls and text calls to wireless numbers, including short message service calls, provided the message goes to a number assigned to that service. That one sentence is why a texting program inherits the consent machinery built for the phone, and why the definitions you have to work with talk about calls when what you are sending is text.

So when someone asks whether SMS has its own consent standard, the answer is no. It runs on the phone standard. Which channel to use for a given prospect is a different question, and we have covered when to text prospects instead of calling separately.

Here is the sentence that should shape how you build the record. In the 2012 order that created prior express written consent, the FCC wrote that should any question about the consent arise, the seller will bear the burden of demonstrating that a clear and conspicuous disclosure was provided and that unambiguous consent was obtained.

Read it twice. The burden does not sit with the person who received the text. It sits with the business that sent it, and it covers two separate things, which are what you showed the person and what the person did in response. You can lose on either one. A complete audit trail of button clicks proves nothing if you cannot produce the words that sat next to the button.

So the design question is not whether you collected SMS consent. It is whether, long after the form has been redesigned and the vendor swapped, you can reconstruct what a specific person saw on a specific day. Most consent systems fail that test, and not because anyone cut a corner. They fail because nobody ever stored the disclosure itself.

The federal definition of prior express written consent is unusually specific about structure, which makes it a decent template even for messages that do not require that standard. It describes an agreement in writing, bearing the signature of the person called, that clearly authorizes the named seller to deliver advertisements or telemarketing messages, and that names the telephone number to which the signer authorizes those messages. The agreement has to disclose, clearly and conspicuously, that signing authorizes those messages and that the person is not required to sign as a condition of buying anything.

A column of six irregular frosted glass discs stacked on a base, with the third disc from the top slid out and floating beside the stack, leaving an open gap in the column.

Pull the fields out of that and you have the record your system should hold.

  • The phone number the person authorized, not every number on the account.
  • The business named in the disclosure, which is the business allowed to send.
  • The categories of message the permission covers.
  • The exact disclosure text shown, stored as a version rather than a pointer to whatever the page says today.
  • The affirmative action taken, with a timestamp and the page, form, keyword or document it came from.
  • Whether consent was presented as a condition of purchase, which this standard does not allow.
  • Every later change, including preference edits, opt-outs and revocations, each with its own timestamp.

How long to keep all that is a question for your counsel and your privacy policy, not for a blog post. The structure is not. If any one of those fields lives only inside a vendor’s interface, you do not control your own evidence.

Three labels come up constantly, and they are not three points on one scale.

Implied consent is permission inferred from the situation rather than stated. Someone hands over a mobile number to get a quote and expects a reply about the quote. That expectation is narrow, and it is not an invitation to a promotional campaign.

Express consent is the person affirmatively agreeing to receive texts. An unchecked box they check, a keyword they text, a form they submit.

Express written consent is the documented version with the disclosures attached, and it is the standard the rules point to for automated marketing messages. There is a full write-up of prior express written consent and what it buys you, so this section stays short.

The practical mistake is not picking the wrong label. It is letting the message drift past the label you collected. A service notification with a discount stapled to the bottom is not a service notification anymore, and the consent you hold may only cover the version without the discount.

Written does not mean paper, and it has not for a long time. The FCC’s 2012 order pointed at the FTC’s finding that consent obtained by email, website form, text message, telephone keypress or voice recording complies under the E-SIGN Act. So the collection method is mostly an operations choice. What changes between methods is how much of the record you keep by default.

  • Web form. Strong, as long as you store the disclosure version and not just the submission.
  • Checkout or booking flow. Strong, as long as order updates and promotions are separate options rather than one box.
  • Keyword opt-in. Strong on the action and weak on the disclosure, because the invitation lived somewhere else. Capture the invitation too.
  • Paper form. Strong, and usually the slowest to retrieve. Scan it into the same record as everything else.
  • Verbal on a call. The agreement can happen, the evidence often does not. If a recording and a CRM note are the only trace, decide now which one is the record.

Then there is the one that keeps showing up. A purchased, rented or inherited list is not SMS consent. The disclosure behind it named somebody else, which is exactly the field the standard requires you to get right. Treat an imported list as a list of numbers you may not text until you have your own basis for texting them.

SMS consent is revocable, and the mechanics are mostly settled. The clocks are covered in detail under text message marketing laws, so here is only what is new.

A rule published on October 26, 2026 takes effect on November 25, 2026. Two parts of it change how a sending team should think about scope. The first is narrower than it sounds. Callers may read a revocation request as applying only to the specific category of informational messages it was directed at, rather than to everything they send. That stops at informational traffic. The rule states plainly that a revocation made in response to a message carrying an advertisement, or constituting telemarketing, revokes consent to all future advertising and telemarketing from that caller, and that a consumer needs to make only one request to do it. If you run outbound sequences, that is your rule. One opt-out ends marketing. There is no category to slice.

The second part is conditional. Callers may designate an exclusive means of revoking consent, but only one of three automated methods the rule lists, which are an interactive voice or key-press opt-out in response to the call, specific standardized words in reply to a text, or a website or telephone number you provide to process opt-outs. You also have to disclose the designated method clearly and conspicuously on the call or in the text. Designate anything outside that list and you are back to honoring a revocation made in any reasonable manner. For texting there is one practical allowance worth knowing. You can disclose a single standardized word, and the rule’s own example is telling recipients they can reply stop, but you still have to honor every standardized word a recipient actually uses.

Category-level preference data is still the right shape for the record above, because informational programs are where the new flexibility lives. If your suppression list is one true or false value per contact, you cannot express a category-level revocation even where the rule now allows one. What you cannot do is read that flexibility back onto your marketing list.

The same rule amends the exemption that lets financial institutions alert customers to fraudulent activity on an account. If you send that kind of message, read the rule rather than a summary of it.

None of this breaks at the policy layer. It breaks in the handoff.

Two frosted glass tubes merging into a faceted junction block, with small glass spheres travelling on through a lower tube while one sphere falls out through a gap in the junction's underside.

Marketing collects SMS consent on a landing page for a newsletter. Six weeks later a rep pulls the same list into an outbound sequence and sends a pitch. The contact record says opted in. The disclosure said newsletter.

A prospect replies STOP to a campaign and the campaign tool suppresses them. The CRM never hears about it. The next rep who opens that record sees a mobile number with no warning on it, and texts them.

A rep texts from a personal phone because it is faster. There is no record at all, which means no disclosure, no timestamp and no suppression check. As far as your evidence is concerned, that message did not come from a system you control.

A vendor migration moves contacts and preference flags but not the disclosure history, and nobody notices, because nothing visibly breaks. The gap only shows up when someone asks what a specific person agreed to in a specific month.

The fix for all four is the same and it is boring. Keep SMS consent in one place, write every message-sending tool against that place, and run the suppression check at send time rather than at list build time. Kixie’s Business SMS sends business texts from the same platform the rep uses to call, so the message is not happening in a tool nobody else can see.

That is the standard to hold a tool to. Not whether it can send a text. Whether, after it sends one, you can still show why you were allowed to.

Yes, as a collection method. The FCC’s 2012 order relied on the FTC’s finding that consent obtained by email, website form, text message, telephone keypress or voice recording complies under the E-SIGN Act. Capturing the agreement by text is acceptable. It does not remove the disclosure requirement, so the invitation the person replied to still has to carry the required language, and you still have to keep a copy of it.

Not on its own. The standard asks what the person was told and what they agreed to, not whether they typed a number into a field. A number collected for a delivery update or an identity check does not carry a marketing campaign along with it.

Not automatically. The SMS consent you hold has a scope, and a customer relationship does not widen it on its own. The test is whether the message you want to send falls inside what the original disclosure described, and whether you can still produce that disclosure.

The sender. The FCC’s 2012 order states that should any question about the consent arise, the seller will bear the burden of demonstrating that a clear and conspicuous disclosure was provided and that unambiguous consent was obtained. That is two things to show, not one.

At minimum the number authorized, the business named in the disclosure, the message categories covered, the exact disclosure shown, the affirmative action with its timestamp and source, and every later change including opt-outs. If one of those fields lives only in a single vendor’s interface, it is not really in your record.

One thing worth saying plainly. This is operational guidance about building an SMS consent record, not legal advice. The rules differ by jurisdiction, by message purpose and by the technology doing the sending, and they move. Have qualified counsel review your messaging program against the current rules before you launch it or change it.

Then go open one contact in your CRM. Can you name the number they authorized, the business named in the disclosure, the words they saw, what they did, and when? If any one of those is missing, that is the first thing to fix, and it is a data problem before it is a policy problem.

Sources

Sources verified and content reviewed 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

Kixie Research Team is the organizational byline for content created and maintained by Kixie’s staff writers and editors through a shared research and editorial process. The team covers sales technology, outbound calling workflows, CRM integrations, and revenue operations. This shared byline reflects organizational accountability; it does not mean every article reflects hands-on testing. Individual pages identify their sources, methods, and limitations.

How we research, source, and update this article

How Kixie researches, sources, and updates articles like this one is described in our editorial standards.

If you spot an error or an outdated detail, request a correction.

Third-party sources linked in this article

This list is generated automatically from the third-party links referenced in the article above.