# 30884: Campaign vetting rejection - Spam/Phishing

Log Type: APPLICATION

Log Level: ERROR

## Description

This error means your A2P 10DLC campaign was rejected during manual vetting because it was identified as a known spam or phishing campaign. A2P 10DLC vetting is required for US long code messaging to help prevent spam, fraud, and unwanted messaging.

### Possible causes

* The campaign appears to send spam, phishing, or messages that request confidential information from recipients.
* The campaign sends unsolicited messages or does not demonstrate a clear, consent-based opt-in flow.
* The submission misrepresents the sender or does not clearly match the registered brand, website, links, or sample messages, which can increase spam or phishing risk during review.

### Possible solutions

* Do not resubmit the same campaign. This rejection reason is ineligible for resubmission as submitted.
* If you believe the rejection was made in error, contact Twilio Support to request an appeal.
* Before you register a new campaign, materially change the campaign content, message flow, or associated brand details so the use case is legitimate, consent-based, and clearly identifies the sender.
* Review your opt-in flow, sample messages, links, and campaign details to make sure they comply with Twilio Messaging Policy and A2P 10DLC approval requirements.

#### Additional resources

* [Troubleshooting and rectifying A2P Campaigns](/docs/messaging/compliance/a2p-10dlc/troubleshooting-a2p-brands/troubleshooting-and-rectifying-a2p-campaigns)
* [Programmable Messaging and A2P 10DLC](/docs/messaging/compliance/a2p-10dlc)
* [A2P 10DLC Campaign Approval Best Practices](https://help.twilio.com/hc/en-us/articles/11847054539547-A2P-10DLC-Campaign-Approval-Best-Practices)