Error code

30478: Toll Free verification rejection - single phone number used for multiple businesses

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

What this error means

One toll-free number is being used for more than one business; it must map 1:1.

Causes, most likely first

  1. The number is assigned to more than one business.
  2. The number is shared across businesses instead of dedicated to one.
  3. The business named in the request isn't the only one using the number.

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

Use the number for one business only. If several businesses need toll-free messaging, give each its own number and verify per business. Resubmit and explain in Additional Information how you corrected it. Check the business details, website, use case, samples and opt-in all point at a single business.

Timing and resubmission

Correctable, resubmit within seven days for priority review, with an explanation in Additional Information.

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.