30909: Campaign rejected: Message Flow or Call to Action incomplete/unverified

This error appears when your A2P 10DLC campaign is rejected because the Message Flow or Call to Action does not give reviewers enough information to verify how end users consent to receive messages. Include a complete description of every opt-in path you use and the required disclosures so the campaign can be reviewed successfully.

• Your Message Flow does not clearly explain how end users opt in, especially when consent is collected outside a public website through verbal, paper, in-store, QR, or other offline flows.
• Your submission does not list every opt-in method used for the same campaign in the message_flow field.
• Your website opt-in flow is missing required information such as links to terms and conditions, a privacy policy, message frequency, or the "message and data rates may apply" disclosure.
• Your opt-in evidence cannot be verified because the website is private, behind a login, incomplete, or missing publicly accessible screenshots of the consent flow.
• Your keyword opt-in flow is incomplete because required keyword details or related opt_in_message, opt_out_message, or help_message information is missing when you manage those flows yourself.

• Rewrite the message_flow field so it explains exactly how consent is collected from start to finish. If you use more than one opt-in method, list all of them in the same submission.
• If you collect consent on a website, include the website URL, a link to your privacy policy, and a link to your terms and conditions. Make sure the privacy policy states that mobile numbers are not shared, and includes message frequency and "message and data rates may apply."
• If your opt-in flow is not publicly visible at the website you provide, add a public URL with hosted screenshots or other proof that shows the full consent experience.
• If users can opt in by texting a keyword, provide the keyword list and the required opt-in confirmation details. If you manage help and opt-out yourself instead of using default or Advanced Opt-Out behavior, provide the corresponding help_message, opt_out_message, help_keywords, and opt_out_keywords values as required.
• After you correct the CTA details, update the rejected campaign and retry review in Console or resubmit the campaign through the API with the required campaign fields.

Campaign reviewers at The Campaign Registry (TCR) verify each of the following before approving a campaign:

• Collection mechanism — the message_flow describes every way end users give consent, such as a website form, SMS keyword, paper form, or QR code.
• Required disclosures — the opt-in flow includes a privacy policy link, terms and conditions link, message frequency, and a "message and data rates may apply" statement.
• Public verifiability — reviewers can access and confirm the opt-in experience. If the flow is behind a login or offline, hosted screenshots or other publicly accessible evidence must be provided.
• All paths listed — if the campaign uses more than one opt-in method, every method is described in the same message_flow field.

Run through this list before submitting or resubmitting your campaign:

• message_flow names the URL, keyword, paper form, or other mechanism where consent is collected.
• message_flow includes a link to your privacy policy and a link to your terms and conditions.
• Your privacy policy states that mobile numbers aren't shared with third parties, includes message frequency, and includes a "message and data rates may apply" disclosure.
• If opt-in happens on a website, the URL is publicly accessible. If it isn't public, you have provided a URL with hosted screenshots of the full consent flow.
• If end users opt in by texting a keyword, opt_in_message, opt_in_keywords, help_message, help_keywords, opt_out_message, and opt_out_keywords are populated (when you manage these yourself rather than using Twilio defaults).
• If the campaign uses multiple opt-in paths, all paths are described in the same message_flow field.
• Sample messages match the declared use case, identify the Brand by name, and include opt-out language.

If your campaign uses more than one opt-in method, describe every path in the same message_flow field. Reviewers reject campaigns when the submission accounts for only one of several active opt-in paths.

Edit the rejected campaign rather than deleting and recreating it. A vetting fee is assessed only once per campaign, so resubmitting the same campaign avoids a new fee.

• Console: go to Messaging > Regulatory Compliance > Campaigns, click the failed campaign, then click Edit Campaign to correct the fields and resubmit.
• API: update the campaign resource with corrected field values. See Troubleshooting and rectifying A2P Campaigns for detailed instructions.

• A2P 10DLC - Gather the Required Business Information
• A2P 10DLC Campaign Approval Requirements
• Why Was My A2P 10DLC Campaign Registration Rejected?
• A2P 10DLC Campaign Vetting and Messaging Compliance (video)