Twilio Error 30909: Message Flow or CTA Incomplete

Updated

Short answer: Error 30909 means the Message Flow or Call to Action in your A2P 10DLC campaign does not give reviewers enough information to verify how people agree to receive your texts. Describe every opt-in path from start to finish, show the consent wording people actually see, and give public evidence for any opt-in reviewers cannot visit. Then resubmit the same campaign.

What error 30909 means

Twilio's title for this code is "30909: Campaign rejected: Message Flow or Call to Action incomplete/unverified". The error page says: "This error occurs when an A2P 10DLC campaign's Message Flow or Call to Action does not provide enough information to verify how users consent to receive messages."

The Message Flow field is where you describe how people opt in. Twilio calls it "the heart of your registration, and it's also where most rejections happen." It must be 40 to 2,048 characters long, and "At each point of opt-in, the consent language shown to users must identify the brand and state the types of messages users agree to receive."

A call to action is "the language that invites someone to sign up for your messaging program". Twilio checks "that the call-to-action and the right disclosures are displayed at the time of phone number collection".

Common causes

Twilio lists four:

  • "The message_flow does not clearly describe how users opt in, or does not describe every opt-in method the campaign uses."
  • "A keyword flow omits the keyword, destination number, or where users encounter the opt-in instructions."
  • "A paper, verbal, QR-code, in-store, or non-public opt-in flow lacks publicly accessible supporting evidence."
  • "A verbal opt-in is described with a one-line summary instead of the full script."

How to fix error 30909

  1. Describe every opt-in path. "Provide a complete, end-to-end description of each opt-in path in 40 to 2048 characters." If people can opt in more than one way, list every method.
  2. Show the consent wording. "Make sure the consent language users see at opt-in names your brand and states what messages they'll receive, and describe it in message_flow."
  3. For a website form, the consent must clearly request permission to send SMS messages. Any checkbox must be "optional and unchecked by default". The wording must include message frequency, a "message and data rates may apply" disclosure, opt-out instructions such as "Reply STOP to unsubscribe" and help instructions such as "Reply HELP for help".
  4. For keyword opt-in, "include the exact keyword, destination number, and where the instructions appear."
  5. For verbal opt-in, "provide the full script that staff read to users, not a one-line summary."
  6. For paper, QR-code, in-store or login-only opt-in, give reviewers a public link to an image or screenshot of it.
  7. Check the privacy policy. "The Privacy Policy must state that mobile numbers aren't shared with third parties and include the messaging disclosures."

Twilio's error page gives this example of a website opt-in description for the Message Flow field:

"Customers visit www.acmecoffee.example/sms, enter their phone number, and select an optional checkbox that is unchecked by default to agree to recurring promotional messages from Acme Coffee. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe. Reply HELP for help. Terms: www.acmecoffee.example/terms. Privacy Policy: www.acmecoffee.example/privacy."

Put the disclosures where people consent, not only in your terms. Twilio's rejection guide says: "A required disclosure in the CTA must appear where consent is collected; putting it only in Terms of Service may not resolve the CTA error."

More specific codes you may see

Twilio notes: "Your campaign rejection may also return a more specific error code." Some of them:

CodeWhat it means
30543A required live opt-in page link is missing
30544The call to action does not say what the messages are for
30545The call to action does not state how often messages are sent
30547The call to action has no opt-out instructions
30549There is no Terms of Service link in the opt-in flow
30550There is no Privacy Policy link in the opt-in flow
30551The consent wording does not say the messages are SMS or text messages
30556SMS consent is bundled with email, phone or other channels
30568The call to action does not name the business or brand
30569The call to action lacks the message and data rates disclosure
30570The call to action lacks customer support (HELP) instructions
30896The opt-in details do not show how people consent
30917Not every selected opt-in method is fully described
30924The opt-in lacks the required consent language
30925The consent checkbox is missing or pre-selected

Resubmitting

Twilio says: "Resubmitting retains the campaign and avoids a second vetting fee, but it starts a new review that takes up to 5 business days for standard use cases." It adds that these changes "make the consent flow easier to verify", but they do not make approval certain.

How to avoid it next time

  • Write the Message Flow in the order a new subscriber sees things: where they find the opt-in, what they enter and the consent wording on screen, as in Twilio's example.
  • Keep proof. Twilio's 30923 page asks you to keep "records of consent for each recipient".
  • 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 30923 covers consent that is required to use a service, Twilio error 30891 covers website rejections, and the list of A2P 10DLC error codes has the rest.

Sources

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