Error code

30755: Brand Registration Failure: Unsupported country code

What this error means

The business address country isn't supported for the US A2P registration flow you used.

Causes, most likely first

  1. iso_country not in the supported list.
  2. Country submitted in a format other than a two-letter ISO code.
  3. Wrong registration path. Sole Prop is US/Canada only, for businesses without an EIN or Canadian BN.

Fields Twilio names for this error

Twilio’s page for this error names these submission fields:

  • iso_country

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

Submit the correct two-letter ISO code. If registering Sole Prop, confirm the business is genuinely US or Canada and eligible; otherwise use Standard / Low-Volume Standard with the required business information. Correct the Customer Profile first if the brand is already failed, then resubmit.

Timing and resubmission

No review window.

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.