Error code

30516: Toll Free verification rejection - Double opt-in required for this use case

Correctable and resubmittable. Stated by: Twilio error page for this code.

What this error means

Your use case needs a two-step confirmed opt-in and you only documented one step.

Causes, most likely first

  1. Only a single opt-in provided.
  2. Double opt-in process not documented.
  3. Confirmation step missing or incomplete.

How to fix it

If your numbers are managed by a platform

If your numbers sit inside a reseller platform, for example LeadConnector numbers inside GoHighLevel, you do not have access to the Twilio Console, and the interface shows the rejection without the code. Ask that platform's support team for the Twilio rejection error code, in writing, before you change anything. You can also read it yourself from your browser, which is faster: see how to get the code.

The substance of the fix is yours to make: the business details, the website, and the opt-in flow described in the Twilio path all belong to you, not to the platform. Make those changes first, confirm they are live, then ask support to resubmit. A resubmission filed before the underlying facts change will fail again on the same reason.

If you own the Twilio account

Implement double opt-in: (1) initial opt-in via web form or keyword, (2) a confirmation message asking the user to confirm the subscription, (3) an affirmative reply completing enrolment. Document the whole flow and supply example messages for both steps. Double opt-in is required for certain use cases including shopping cart reminders.

Timing and resubmission

Correctable, resubmit within seven days for priority review, after the two-step flow exists.

Two ways forward

Have it handled for you

A2P registration is handled for you on Growth at $597/mo and on Scale at $1,197/mo. Registration, resubmissions, and the compliance work behind them are included.

See Growth and Scale

Fix it yourself

Send your email and we will send the fix playbook for registration rejections.

Verified against Twilio documentation on 2026-08-10.