Rejected for lead generation or affiliate marketing (Twilio 30951, DCA 708)
Short answer
Carriers ban texting programs that collect leads for others or share opt-ins with third parties. You can trigger this rejection just by having “lead generation”, “we sell leads” or “share with partners” on your website or in your privacy policy. Messaging your own leads about your own business is fine.
What you'll see
| Where | Code | Wording |
|---|---|---|
| Twilio (10DLC) | 30951 | “Campaign rejected: Third-party lead generation or MLM content detected” |
| Twilio (10DLC) | 30932 | “Campaign rejected: Privacy policy must disclose third-party data sharing” (raised when opt-in data may go to third parties or lead generators) |
| Twilio (toll-free) | 30468 | “Toll Free verification rejection - Disallowed: Third-party Lead Generation” |
| Telnyx, Bandwidth | 708 | “Lead Gen/Affiliate Marketing Prohibited” |
| Bandwidth Proxy, Infobip | 7002 | Lead generation or affiliate marketing |
Text in curly quotes is the provider's wording; the rest is our summary.
Why it happens
- The website offers “lead generation”, “SEO and lead gen” or “we connect you with partners”. Telnyx says
Any mention of lead generation or SEO on the website would lead to a decline of this nature.
- The privacy policy allows sharing or selling contact data to partners or affiliates.
- Comparison or quote sites that pass consumer details to several providers.
- Purchased contact lists, or opt-ins collected by one business and used by another.
- Marketing agencies registering their own brand while their site advertises lead generation for clients.
How to fix it
- Register the business that actually sends the messages, with its own opt-in and website.
- Remove lead-selling, “buying leads”, “affiliate lead distribution” and “purchased lists” wording from the website, as LeadConnector's website guide advises.
- Fix the privacy policy: SMS opt-in data and consent are never shared with third parties. See privacy policy rejections.
- Describe your own lead follow-up honestly. Telnyx's toll-free team notes:
Lead alerts, and lead management is allowed.
- Choose lead generation or lead nurture correctly when your platform asks (Twilio 30916).
The rule comes from the carriers: T-Mobile requires senders to collect the consumer consent yourself, and not use consent acquired from a third party
, and AT&T prohibits Lead generation campaigns that indicate the sharing of collected information with third parties
. The 11th Circuit vacated the FCC's “one-to-one consent” rule in January 2025, but that changed the law, not carrier policy.
Check before you resubmit. Every rejection costs days, and often another $15 vetting fee. Paste your description, message flow, samples and policy text into the free preflight check, or generate a consistent set with the campaign builder.
Frequently asked questions
Can a marketing agency register 10DLC at all?
Yes, for its own messages, but register the agency's real use case and keep lead-generation services off the pages reviewers see, or describe them in a way that doesn't involve selling or sharing leads. For clients, register each client as its own brand.
Can I text leads who filled out my own form?
Yes, if your form collected SMS consent for your business with the full disclosure. That is first-party consent. Shared or purchased leads are what's prohibited.
Is lead-generation rejection final?
Twilio marks 30951 as not eligible for resubmission, and the vetting partners tell you not to resubmit 708. Change the website and policy first, then register a new, accurate campaign.
Sources
- Twilio: Forbidden Message Categories in the US and Canada (updated 2026-06-03)
- Twilio error 30951 (accessed 2026-10-03)
- Twilio error 30932 (accessed 2026-10-03)
- Twilio error 30468 (accessed 2026-10-03)
- Bandwidth: DCA2 vetting rejection reasons (2026-03-17)
- Telnyx: 10DLC carrier error codes explained (accessed 2026-10-03)
- Telnyx: Toll-free messaging (verification statuses and rejection reasons) (accessed 2026-10-03)
- LeadConnector: Website compliance guide (modified 2026-08-31)
- T-Mobile Code of Conduct v2.2 (November 2020 (latest public))
- AT&T Code of Conduct for Short Code and 10-Digit A2P SMS (March 1, 2021 (latest found))
- Insurance Marketing Coalition v. FCC (11th Cir.) (decided 2025-01-24)
Rules change often and providers sometimes disagree; where they do, this page says so. This is general information, not legal advice, and no one can guarantee approval. See the disclaimer.
Related problems
- Twilio 30908, 30932, 30536, 30477, 30519, 30550 · DCA 805, 851, 852 · TF 1207, 1501-1503Privacy policy rejections: the SMS clause carriers require
- Twilio 30883, 30897, 30940-30962, 30441-30469 · DCA 701-709 · Proxy 7001-7012 · TF 1701-1806Prohibited and restricted SMS content: SHAFT, cannabis, loans, lead gen
- Twilio 30893, 30496, 30499, 30507, 30537, 30916 · DCA 602 · Proxy 2003, 2005, 8001-8004Use case mismatch: when your samples, description and opt-in disagree
- MESSAGE_FLOW · Twilio 30909, 30896, 30917, 30924 · DCA 806MESSAGE_FLOW rejection: fix an opt-in the reviewer can't verify
The Approval Kit adds industry template packs, opt-in and policy page templates, and an agency checklist.