Guidelines

Mexico (MX)

Caret left Back to Guidelines

Locale Summary

Locale name

Mexico

ISO code
The International Organization for Standardization two character representation for the given locale.

MX

Region

North America

Dialing code
The dialing prefix used to establish a call or send an SMS from one locale to the given locale.

+52

Guidelines

Use Cases

Short codes are ideal for high-throughput programmatic messaging.

Short codes are approved for specific use cases, so if you are experiencing carrier filtering on long codes you may be a good candidate for short codes.

Some of the most common use-cases for short codes in Mexico are: 

  • Two-factor authentication (2FA) or one-time passwords (OTP)
  • Promotional or marketing alerts
  • Account alert notifications
  • Reminders (appointments, upcoming payments, etc.)

Restrictions

Short codes can only message users on carriers within the countries in which they are provisioned. If your customers do not have Mexican phone numbers on carrier networks that have approved that short code, you should not obtain a Mexico short code. If you have customers in other countries, Twilio may be able to provision short codes in those countries.

Short codes require express consent from end users before any SMS can be sent; if you cannot obtain consent you should not use a short code.

Twilio and/or the carriers will not support certain types of campaigns, including: 

  • Those in which express end-user consent cannot be obtained. This includes friend-to-friend invite-based campaigns, as well as opt-ins obtained through lead generation.
  • Campaigns containing sexual/adult content (which are prohibited by Twilio’s AUP).

Please note that if you order FTEU (Free to End User) Short Code the owner pays extra to send messages for which end users do not pay.

Minimum term commit for Mexico Short Code is 3 months.

The notice period before returning the Short Code is 1 month.

Refer to this article for detailed explanation on Mexico Short Code Best Practices.

Other Options

Requirements

To apply for Mexican Short Code the following details are needed:

  • Short Code Type
    • Random or several preferred options to choose from (in case of preferred please provider 5 options)
    • Please outline here if you need FTEU (Free To End User) Short Code or not. Please note in case of FTEU Short Code the owner pays extra to send messages for which end users do not pay.
    • MO/2-way messaging enabled?
  • Preferred Billing Term:
    • Quarterly or Yearly (prices can be reviewed from here)
  • Brand/Company
  • Type of Traffic (Marketing or Notifications) and Use case
  • Privacy Policy and Terms and Conditions
  • Monthly Volume - Approximate amount of messages sent monthly
  • Examples of SMS Text - (Please include URL, if applicable, as it must be pre-approved by the vendor)
  • For Banking or Financial Companies - A signed letter of authorization will be required. Twilio will provide a template once your short code has been assigned.

Timeframe

10 weeks, once you submit all required information and documentation.

Please expect delays on any applications submitted from December through mid January, as the wireless carriers have an annual provisioning freeze during this time.

Regulatory Bodies

Federal Telecommunications Institute (IFT)

Pricing

Click to see SMS pricing, including for short codes.

Next Steps

To apply for a Short Code in Mexico, please follow these steps:

  • Check the requirements above and collect the needful information
  • Forward them via email to sc@twilio.com.

For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.