21216: API: Call blocked by Twilio

Twilio blocked the outbound call before connecting it to the destination. This can happen when Twilio identifies the destination as high risk for fraud, when regulatory restrictions prevent routing, or when your account does not meet the requirements for outbound calls to +1 numbers.

• The destination is in a high-risk fraud range that Twilio blocks to reduce exposure to toll fraud.
• Regulatory restrictions prevent Twilio from routing the call to the destination.
• Your account is placing a call to a +1 destination without an approved Primary Customer Profile.
• Your account was created outside the United States or Canada on or after October 8, 2025 and does not have an approved Business Primary Customer Profile. An Individual Primary Customer Profile created after October 8, 2025 does not satisfy this requirement for +1 calling.

• Confirm that the destination and use case are legitimate. If the block appears to be incorrect, contact Support from Console or through the Help Center and include the destination number and your business use case.
• If you need to place calls to +1 destinations, create and submit the required Primary Customer Profile in Trust Hub on your master account, then retry the call after the profile is approved.
• If your account was created outside the United States or Canada on or after October 8, 2025, create a Business Primary Customer Profile. Support cannot manually remove this restriction.
• Review your Voice Dialing Geographic Permissions and enable only the countries and number ranges you expect to call.
• Validate destination numbers in your application and rate-limit outbound call requests to reduce abusive or unexpected traffic that can trigger fraud controls.

• Dialing Permissions overview
• Console: Create a Primary Customer Profile
• Requirements for Calling US and Canada Numbers (+1 Country Code)