Skip to contentSkip to navigationSkip to topbar
Page toolsOn this pageProducts used
Looking for more inspiration?Visit the

30852: Verification rejection - Disallowed: Fraud


ERROR: 30852

error-30852 page anchor
MESSAGING
ERROR

Your verification submission was rejected because the business or messaging program was associated with fraud or deceptive messaging. Messaging traffic on the phone number is blocked until the number is successfully verified for messaging to the United States and Canada.

Possible causes

possible-causes page anchor
  • The business, messaging program, or sample content in the submission was identified as associated with fraud, scams, or deceptive messaging.
  • The review raised compliance concerns after evaluating your business, stated use case, sample messages, web presence, opt-in or consent flow, and associated terms or privacy information.
  • The submission included a use case or message content that is not allowed for messaging under Twilio's messaging compliance requirements.
  • The details in the verification request didn't accurately represent how the phone number will be used.
  • If you believe this rejection is incorrect, contact Twilio Support and provide additional information that clearly explains your business and messaging use case.
  • Review the rejected verification in Console under the number's Regulatory Information tab so you can confirm the rejection details and whether the request can be corrected and resubmitted.
  • Verify that your submission accurately reflects your business and messaging program, including fields such as BusinessWebsite, UseCaseSummary, ProductionMessageSample, OptInType, and any supporting opt-in evidence or additional information.
  • Remove any content, workflows, or sample messages that could appear deceptive, misleading, or inconsistent with your stated use case before you resubmit, if resubmission is allowed.
  • Make sure your messaging program complies with the Messaging Policy and the prohibited use case guidance for messaging.