Account Verification

Justin Dupree -

NOTE:: This applies to only. accounts are all contracted customers and as such are all enabled for outbound access. See the full list of differences between and for details.

In order to help manage and mitigate the potential for abuse, we have established an account verification process before outbound permissions are enabled. It's a three step process, and fairly straightforward.  You'll need to either email support or open a ticket directly through the portal and include the following information:

  1. A brief description of your application's intended purpose
  2. A phone number where we can send a verification code

Then last, you will need to move your account to production - you don't need to move your application to production, just your account. This doc page explains the difference (and how to move).

Note that moving to production will require a (refundable) deposit, minimum amount is $10.00.

The process generally only takes a few minutes from start to finish, barring any delays in the phone verification or payment application.

For reference, the types of applications that we would reject or would require further discussion (based on description or traffic patterns) generally fall into one of these categories:

  1. Any type of SMS application that allows users to send arbitrary content - massive amounts of monitoring and automated filtering/blocking is necessary to prevent black hat users from commandeering the application and using it for various fraudulent purposes.
  2. Any type of voice application that allows users to call any number they want - there are, and always will be, "premium" rate services that allow people to make money on incoming calls. If you allow users to call any number anywhere, especially in any form of a "trial version" that doesn't require upfront payment, black hat users will find you and abuse your application in order to make money.
  3. Any application that involves unsolicited contact of any sort - SMS, the carriers will just block you and report you to us for disabling; voice, you run the risk of involving legal resources if your recipients report you as abusive. This includes "prank" applications, as the recipients are clearly not "opting in" for the calls and are wide open for abuse.
  4. Any application that is never intended to move to production - low volume and personal applications still need to be moved to production at some point, as when you add up all the possible traffic from all the low volume applications that could use Tropo, it's no longer low volume. 

If your application could potentially match one of the above situations, it's not infeasible we can find a way to get you going, we'll just need to spend some time talking it out to find a valid approach with limited risk and exposure - feel free to reach out to at any time to discuss.

Have more questions? Submit a request


Article is closed for comments.