30917: Campaign rejected: All opt-in methods must include complete workflow descriptions

Your A2P 10DLC campaign registration was rejected because one or more selected opt-in methods were not fully described. If you use more than one consent path, such as a website, keyword, paper form, QR code, or verbal consent, include a complete workflow for each method so the opt-in can be reviewed and verified.

• You selected multiple opt-in methods but described only some of them.
• One or more opt-in descriptions do not explain where the opt-in happens, what the consumer sees, and what action the consumer takes to provide consent.
• The opt-in description is too generic and does not include enough detail to verify the consent flow.
• The opt-in evidence cannot be reviewed because it is behind a login or was not provided as a publicly accessible screenshot, image, or video.
• You indicated SMS keyword opt-in but did not include the related keyword flow or opt-in confirmation details.

• For each opt-in method you selected, describe the full end-user journey from the first prompt through the consent action.
• Explain where the opt-in occurs, what disclosure language the consumer sees, and what specific action confirms consent.
• If opt-in happens on a website, provide the public URL and make sure the site includes a privacy policy and terms of service.
• If opt-in happens on a paper form or behind a login, provide a public link to hosted screenshots, images, or a video that shows the consent flow.
• If opt-in happens by SMS keyword, include the opt-in keyword and the opt-in confirmation message. If you do not use SMS opt-in, leave those fields blank instead of providing partial information.
• Remove any opt-in methods you do not actually use, then resubmit the campaign after you update the registration.

Run through this list before submitting or resubmitting your campaign:

• Every opt-in method you selected has its own workflow paragraph in message_flow explaining where, what, and how consent is collected.
• Website opt-in includes the public URL, a link to the privacy policy, and a link to terms and conditions.
• Keyword opt-in includes the keyword, the phone number, and the opt_in_message confirmation text.
• Offline opt-in (paper, verbal, QR) includes a publicly accessible URL to hosted screenshots or documentation showing the full consent experience.
• No opt-in method is selected without a corresponding description. If you don't use a method, deselect it rather than leaving its description empty.
• Each workflow description includes the required disclosures: message frequency, "message and data rates may apply," and opt-out instructions.

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
• message_flow field reference
• Troubleshooting and rectifying A2P Campaigns