Twilio Error 30923: SMS Consent Cannot Be Required

Updated

Short answer: Error 30923 means your opt-in flow makes agreeing to texts a required condition for using your service, creating an account or completing a purchase. Make SMS consent a separate, optional choice, with any checkbox unchecked by default, so people can finish without it. Then correct your message flow description and resubmit the campaign.

What error 30923 means

Twilio's title for this code is "30923: Campaign rejected: Message consent cannot be required for service use". The error page explains:

"Your A2P 10DLC campaign was rejected because your opt-in flow makes consent to receive messages a required condition for using your service, creating an account, or completing a transaction. For A2P 10DLC, campaign reviewers must be able to verify that end users knowingly agree to receive messages, that the consent applies to the specific campaign, and that the opt-in experience is voluntary and clearly documented."

Common causes

Twilio lists five:

  • "Your sign-up, checkout, or account flow requires a user to agree to receive SMS or MMS messages before they can continue."
  • "Your messaging consent is bundled with general terms of service or another required agreement, so the user cannot accept the service terms without also opting in to messaging."
  • "Your web form uses a checkbox for messaging consent that is preselected, or the user cannot clearly choose to decline messaging and still complete the form."
  • "Your message_flow does not clearly explain how the user opts in, or it does not include every opt-in method used for the campaign."
  • "The website used for opt-in does not include accessible Terms and Conditions and Privacy Policy links, or the opt-in flow is not publicly verifiable."

How to fix error 30923

  1. Let people say no. "Update your opt-in flow so users can access the service, create an account, or complete a purchase without being required to consent to messaging."
  2. Separate SMS consent from your terms. "Separate messaging consent from required service terms. Use a distinct opt-in action that specifically covers the messages you plan to send." Twilio's onboarding guide adds: "A consent checkbox for privacy policy and terms of service must be separate from any messaging consent checkboxes".
  3. Fix the checkbox. "If you use a checkbox, leave it unchecked by default and label it clearly as optional."
  4. Update the call to action. "In your call to action, clearly disclose the messaging program details and make clear that consent is not a condition of purchase when that language applies to your flow."
  5. Keep records, then resubmit. "Keep records of consent for each recipient so you can show when and how the user agreed to receive messages for this specific campaign. After you correct the flow, resubmit the campaign for review."

What to change, in practice

What triggers 30923What to do instead
Sign-up, checkout or account creation cannot continue without agreeing to textsLet people finish without SMS consent
SMS consent is bundled with the terms of service or another required agreementUse a separate opt-in action that covers only your messages
The SMS checkbox is pre-selectedLeave it unchecked and label it optional
The message flow description skips an opt-in methodDescribe every opt-in method
The opt-in site has no accessible Terms and Privacy Policy linksAdd both links

Other official sources say the same. Twilio's toll-free checklist states: "Voluntary Consent: Opt-in cannot be mandatory." HighLevel's guidance says: "Do not require SMS consent in order to submit the form." CTIA's Messaging Principles say "opt-in details should not be obscured in terms and conditions (especially terms related to other services)."

CodeTwilio title
30925"Campaign rejected: Opt-in must be unchecked by default; active consent required"
30931"Campaign rejected: Opt-in process must allow consumers to decline"
30913"Campaign rejected: Marketing and informational consent must be separate"
30556"SMS consent is bundled with other communication channels"

For 30913, Twilio's onboarding guide says: "Marketing and transactional message consent must be consented to separately with two checkboxes." For 30556, Twilio says SMS consent "cannot be bundled with consent for other channels."

CTIA's Messaging Principles list the data senders should keep where applicable:

  • The time consent was given
  • How it was collected, such as a web form, a paper sign-up form or an SMS keyword
  • The wording and action used to get consent
  • The campaign the opt-in was for
  • The IP address used to give consent
  • The phone number that consented
  • Who consented, by name or another identifier such as a user name or session ID

Twilio's Messaging Policy also says you must keep proof of consent "for as long as needed to meet your legal requirements and at least until a recipient withdraws their consent."

How to avoid it next time

  • Before you submit, try your own sign-up and checkout and decline texts. You should still be able to finish.
  • Keep marketing consent, informational consent and your terms in separate controls.
  • Precheckly's Pro plan ($29 a month) includes 10 A2P registration pre-checks a month. Each one reviews the opt-in flow, website, privacy policy, campaign description and samples, with an AI review and suggested rewrites. See pricing.

Related guides: Twilio error 30909 for an incomplete message flow, Twilio error 30891 for website rejections, and the list of A2P 10DLC error codes.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.