30836: Verification rejection - Opt-in URL not accessible

Your verification request was rejected because the opt-in URL in the submission couldn't be accessed for review. Messaging traffic on the phone number remains blocked until the number is verified. Reviewers use the opt-in example to confirm how you collect consent for the messaging use case, along with the related website, privacy policy, and terms information in the submission.

• The opt-in URL requires a login, password, or other credentials, so reviewers can't access it.
• The link is broken, returns an error, no longer resolves, or the page was changed after you submitted it.
• The URL doesn't lead directly to the opt-in content or doesn't clearly show how the consumer opts in to receive messages.

• Replace the URL with a public link that is reachable, resolvable, and accessible without authentication.
• Make sure the link goes directly to the web form or other proof of consent that tells the full opt-in story for the submitted use case. A valid example can be a web form, a hosted image, or a document such as a verbal opt-in script.
• If the opt-in flow is inside an authenticated app or portal, host screenshots at public URLs and submit them as your opt-in evidence. If you submit verification through the API, use optInImageUrls for those publicly hosted images.
• If you use screenshots, include the complete opt-in experience and visible business branding so the consent flow is easy to review.
• If the rejected request is eligible for resubmission, correct the URL and resubmit within seven days to enter priority review. After that window, the phone number remains Restricted until you resubmit verification.