How to fix Twilio error 30932: SMS consent shared with third parties
By Paul Cranmer, Founder · Last verified November 2026 · Twilio · A2P 10DLC campaign registration
Error 30932 means a reviewer found wording that lets mobile numbers, SMS consent or opt-in data be shared, sold or transferred to someone else: a third party, an affiliate or a lead generator. It hits lead-generation businesses most, because their policies rightly say leads go to partners. You can keep sharing other lead data; the fix is to say plainly that the mobile number and the consent to text are never part of it, and to make your opt-in name only your brand.
Who this is for
- Lead-generation businesses that pass leads to lenders, brokers or contractors
- Businesses whose policy template says data may be shared with affiliates
- Anyone whose A2P 10DLC campaign was rejected with error 30932
Not for
- Businesses that sell or hand phone numbers to others for their texting (that is not allowed; there is no wording fix)
- Toll-free or short code verification
What the platform requires
- Twilio 30932: no wording that mobile data, SMS consent or opt-in data may be shared, sold or transferred to third parties, affiliates or lead generators.
- Consent belongs to one sender: it cannot pass from one business to another.
- Marketing and non-marketing consent are asked separately, never pre-ticked, never required to submit the form (Twilio 30924, HighLevel).
- The policy states the non-sharing rule (Twilio 30908's passing sentence).
Get a live URL first
Our SMS consent kit asks you to confirm that mobile numbers and SMS consent are never shared, and only then writes the privacy section, SMS terms and opt-in page. For a lead sharer, it adds the carve-out sentence to the sharing section.
Get the SMS consent kitStep-by-step: paste your privacy policy URL
- Find every sharing sentence. Search your privacy policy and terms for "share", "sell", "partners", "affiliates", "third parties" and "lead generators". List each sentence that could cover phone numbers.
- Carve out mobile numbers and consent. Next to each sharing sentence, say that your customers' mobile numbers and their consent to receive text messages are never part of what you share, and never shared for anyone's marketing. Add Twilio's passing sentence to a text message section.
- Make the opt-in name only you. The consent box must name your business, not "our partners" or a list of companies. One box for your service texts, a separate optional box for promotions, neither pre-ticked, and neither required to submit the form.
- Keep the pages consistent. The privacy policy, the SMS terms, the opt-in page and the message flow you register must say the same thing. A carve-out in one place and "may share" in another still fails.
- Check, then resubmit. Run the three links through the A2P 10DLC checker. Fix anything marked Fix and resubmit the campaign.
Common reasons the form fails
- "We may share your information with our partners" with no carve-out for mobile numbers
- An opt-in that consents to texts from "us and our marketing partners"
- A lead form whose consent covers several companies at once
- A carve-out in the policy but sharing wording left in the terms
FAQ
Do I have to stop sharing leads?
No. Other lead data can still go to the partners who answer the request, as your policy says. Only the mobile number and the consent to text must never be shared.
Can a partner text the lead using my consent?
No. Consent belongs to the business named in it and cannot pass to another. A partner that wants to text needs its own consent.
Is the carve-out enough on its own?
Only if it is true and every page agrees with it. Reviewers compare the policy, terms, opt-in and sample messages.