An SMS frequency statement is the disclosure that tells subscribers how often they can expect to receive text messages from a business’s SMS program. It is a required element under CTIA’s Messaging Principles and Best Practices, enforced through TCR campaign vetting and carrier review of opt-in workflows. Every 10DLC campaign registration that submits a message flow — the description of how subscribers opt into the SMS program — must demonstrate that the frequency disclosure is present in the opt-in mechanism and consistent with the sample messages submitted for review. Missing, buried, or vague SMS frequency statements are among the most consistent reasons campaign registrations fail the message flow inspection. Understanding exactly what an SMS frequency statement requires, what forms it takes, where it must appear, and what wording satisfies carrier standards determines whether your opt-in documentation passes or returns a vetting rejection. The SMS Consent Language Validator at MyTCRPlus evaluates frequency disclosures against CTIA and carrier standards before submission.
What an SMS Frequency Statement Is and Why CTIA Requires It
The SMS frequency statement is one element within the required disclosure stack that CTIA’s Messaging Principles mandate for all opt-in mechanisms. That stack includes the sending brand name, a program description, the frequency statement, “Message and data rates may apply” language, HELP and STOP instructions, and links to the SMS Terms and Conditions and Privacy Policy. The frequency statement sits within that stack specifically to set accurate subscriber expectations about message volume before consent is given.
The requirement exists because a subscriber who consents to receiving one message per month and then receives four messages per week has not genuinely consented to the program as it operates. High opt-out and complaint rates driven by unexpected message volume are a carrier filtering signal. Carrier systems interpret unusually high unsubscribe rates and spam complaints as evidence of a non-compliant messaging program, and that signal feeds into the trust score evaluation that determines whether messages are delivered or filtered. The frequency statement is not a formality — it is the mechanism by which subscriber expectations are calibrated at the moment of consent, and accurate calibration is what prevents post-approval filtering.
TCR 101 provides the registration baseline: brand registration, campaign registration, and the message flow submission that documents the opt-in workflow — including frequency disclosure — to the carrier vetting system.
The Two Forms of SMS Frequency Statement and When Each Applies
CTIA-compliant SMS frequency statements take two forms: specific frequency disclosures and variable frequency disclosures. The choice between them is not aesthetic — it creates distinct compliance obligations in each direction.
A specific frequency disclosure states a defined message limit: “Up to 4 messages per month,” “2 messages per week,” “1 message per week.” This form is appropriate for programs with a predictable, consistent send cadence — a weekly promotional newsletter, a bi-weekly appointment reminder program, or a fixed-cycle marketing campaign. The specific frequency disclosure creates a compliance obligation to remain within the stated limit. A program that discloses “up to 4 messages per month” and consistently sends six is in violation of the consent given at opt-in. If the send frequency exceeds the disclosed limit, the opt-in language must be updated before the next enrollment cycle.
A variable frequency disclosure — “Message frequency varies” — is appropriate for triggered or transactional messaging programs where message volume depends on subscriber behavior or operational events rather than a fixed schedule. Abandoned cart reminders, appointment confirmation responses, shipping notification sequences, and two-factor authentication programs all fit this model because the number of messages a subscriber receives depends on their interactions with the business. “Message frequency varies” is an accepted CTIA formulation for these programs and does not require updating when send volume fluctuates.
The practical error businesses make is using “Message frequency varies” for programs that actually have a fixed promotional cadence — because it’s simpler than committing to a specific number. This inversion creates a different compliance exposure: if the program sends predictable promotional messages on a fixed schedule, “message frequency varies” misrepresents the program structure and can be challenged as an inaccurate disclosure at the point of consent.
Where an SMS Frequency Statement Must Appear
The CTIA requirement is that the frequency disclosure appears in three locations: the opt-in mechanism, the opt-in confirmation message, and the SMS Terms and Conditions page on the business’s website.
The opt-in mechanism — typically a web form collecting the subscriber’s phone number — must include the frequency statement as part of an adjacent disclosure block positioned immediately near the phone number field or the form submission button. “Adjacent” is a specific requirement: the disclosure must be visually near the opt-in action, not buried in a linked terms document, not placed in a footer, not accessible only after the form is submitted. A form that places the frequency disclosure three scrolls below the phone number field, or that requires the user to click through to a linked page to find it, does not satisfy the adjacency requirement.
The full adjacent disclosure block on the opt-in form should follow this order: brand name, program description, consent statement (with acknowledgment that consent is not a condition of purchase where applicable), message frequency statement, “Msg & data rates may apply,” HELP instruction and contact, STOP instruction, and links to SMS Terms and Conditions and Privacy Policy. The frequency statement is typically the fourth element in this sequence, placed after the program description and before the data rates disclosure.
The opt-in confirmation message — the SMS sent immediately after a subscriber opts in — must also include the frequency disclosure. A compliant confirmation message format looks like: “[Brand Name]: You’re confirmed for [program name]. Msg frequency: up to 4/mo. Msg & data rates may apply. Reply HELP for help, STOP to cancel.” This message serves as the subscriber’s receipt of the consent terms and must be consistent with the disclosure on the opt-in form.
The SMS Terms and Conditions page on the business’s website is the third location. The Terms page should specify the frequency in the same terms used on the form — if the form says “up to 4 messages per month,” the Terms page must say the same. Inconsistency between the form disclosure, the confirmation message, and the Terms page creates a vetting flag when TCR campaign reviewers compare the submitted message flow against the website URL provided during brand registration. The Platform Microsite Service provides pre-formatted Terms and Conditions pages that align frequency disclosures across all three required locations.
The fourth location is TCR’s campaign registration message flow field. The Message Flow is the description businesses submit during campaign registration that explains how subscribers opt in to receive messages. The message flow description must include a reference to frequency disclosure as part of the opt-in process, and the sample messages submitted alongside the registration must contain opt-out instructions — typically confirming the frequency in the confirmation message sample. The TCR Registration Mastery Guide covers the message flow submission requirements, including frequency disclosure, in detail.
What Wording Passes TCR Vetting and What Fails
The wording standard for an SMS frequency statement is functional rather than stylistic. The disclosure must communicate message volume clearly and be positioned for subscriber visibility at the moment of consent. The following examples meet the standard:
“Msg frequency: up to 4/mo.” — concise, specific, commonly used in confirmation messages. “Message frequency varies.” — accepted CTIA variable-frequency formulation. “You’ll receive up to 2 messages per week from [Brand Name].” — plain-language form disclosure that states frequency in full sentences. “Recurring msgs, freq varies.” — abbreviated version acceptable in character-constrained environments when paired with full disclosure on the opt-in form.
Wordings that fail vetting include phrases that are vague without being technically “varies” — “We’ll text you occasionally,” “You may receive messages from time to time,” “Periodic updates will be sent.” These fail because they communicate no usable information about message volume and cannot be evaluated against subscriber expectations.
Burying the frequency disclosure in a terms block that requires a scroll to reach fails the adjacency requirement, even if the language itself is technically correct. A frequency statement that says “4 messages per month” on the form and “up to 8 messages per month” in the Terms and Conditions fails the consistency requirement. A confirmation message that omits the frequency while the form includes it creates a documentation gap that vetting reviewers can identify.
When the SMS Frequency Statement Is Missing or Insufficient
Campaign rejections for opt-in documentation failures concentrate around the message flow submission. When a TCR campaign reviewer inspects the submitted message flow and determines that the opt-in mechanism described doesn’t include a frequency disclosure — or that the frequency disclosure doesn’t appear in the sample confirmation message — the campaign receives a rejection on insufficient message flow grounds. The full list of opt-in-related rejection codes is documented in the TCR Error Codes & Rejections Hub.
Beyond TCR rejection, a missing SMS frequency statement creates downstream exposure. A subscriber who was not accurately informed of message frequency at opt-in has a stronger basis to challenge whether valid TCPA consent was given for the messages they received. TCPA litigation has turned on consent documentation quality, and the frequency statement is a documented element of that consent. Carrier filtering triggered by elevated complaint rates from subscribers who received more messages than they understood they were consenting to creates deliverability problems that persist after the original consent documentation issue is corrected.
Resubmitting a campaign after a message flow rejection requires correcting the opt-in mechanism on the website, updating the confirmation message template, resubmitting the campaign with a corrected message flow description, and waiting for the carrier re-vetting cycle to complete — typically three to four weeks with carrier fees applied per resubmission.
An SMS frequency statement is a small disclosure element with outsized compliance consequences. It appears in three mandatory locations — the opt-in form, the confirmation message, and the SMS Terms and Conditions — and must be internally consistent across all three. It takes one of two forms: a specific numeric limit or “Message frequency varies,” and the choice between them creates distinct obligations that run for the life of the messaging program. Getting it right before campaign submission is measurably faster than correcting it after rejection.
Validate your SMS frequency statement and the full adjacent disclosure stack with the SMS Consent Language Validator on MyTCRPlus — built to verify opt-in language against CTIA guidelines and the carrier standards applied during TCR campaign vetting.
