Country Summary

Country nameMexico
ISO codeMX
RegionNorth America
Mobile country code334
Dialing code+52
Major carriersTelcel, Movistar, AT&T

Guidelines

Two-way SMS supported Yes
Number portability availableYes
Twilio concatenated message supportYes
Message length160 ASCII characters per message
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged.
Compliance considerations

Dial Plan

The dial plan in Mexico has recently changed to remove the need to add a "1" after the country code when texting a mobile number, this means that now only the 10 digit subscriber number needs to be dialed after the +52 country prefix. An example mobile number is: +525512345678

Use Case Restrictions

You must not use SMS as a marketing or research tool in Mexican elections. Carriers will block any numbers used to promote a particular political candidate or cause.

You should not use Mexican mobile numbers to send marketing, 1-way, or application-to-person (A2P) traffic. URLs and brand names are some of the A2P content likely to be blocked when sending from Mexican numbers.

Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:

  1. Get opt-in consent from each end user before sending any communication to them, particular for marketing or other non-essential communications.
  2. Only communicate during an end user's daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end user's local language.
  4. Do not contact end users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

PreregisteredAlphanumericLong CodeShort Code
Operator network capability --- Not SupportedSupportedNot Supported
Twilio supported --- Not SupportedSupportedNot Supported
Sender ID preserved --- NoNo ---
Provisioning time--------
UCS-2 support --------
Use case restrictions --Alphanumeric is only supported towards Telcel Mexico and only through pre-registrationYou should only use Mexican mobile numbers for 2-way, person-to-person (P2P) communication. No marketing traffic is allowed. Non-Mexico long code would be overwritten with either a random long number or shortcode to ensure delivery--
Best practices ----Use a US or Canadian long code to send application-to-person (A2P) traffic instead of a local Mexican number.--
Preregistered
Operator network capability ---
Twilio supported ---
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --
Alphanumeric
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions Alphanumeric is only supported towards Telcel Mexico and only through pre-registration
Best practices --
Long Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions You should only use Mexican mobile numbers for 2-way, person-to-person (P2P) communication. No marketing traffic is allowed. Non-Mexico long code would be overwritten with either a random long number or shortcode to ensure delivery
Best practices Use a US or Canadian long code to send application-to-person (A2P) traffic instead of a local Mexican number.
Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices --

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.