Country Summary

Country nameMexico
ISO codeMX
RegionNorth America
Mobile country code334
Dialing code+52

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, for example +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, one-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, particularly 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

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilitySupportedNot SupportedSupportedSupportedSupported
Twilio supported Supported Not Supported SupportedSupportedSupported
Sender ID preservedYes --- YesNoYes
Provisioning time2 weeksN/AN/AN/A8 weeks
UCS-2 support---N/ASupportedSupportedSupported
Use case restrictions

All promotional traffic must have clear opt out instructions.

Pre-registration only supported for Telcel, Movistar and AT&T networks. If traffic is sent to a different MNO or MVNO it will be delivered with a shared short code.

N/A

You should only use Mexican mobile numbers for two-way person-to-person (P2P) communication. One-way application-to-person (A2P) and bulk traffic will be blocked. No marketing traffic is allowed. 

N/A

Refer to our FAQs for short code best practices.

Best practices

N/A

N/A

Use a US or Canadian long code instead of a local Mexican number to send application-to-person (A2P) traffic.

SMS sent with international long codes will have the senderID overwritten with a random local long number or short code to ensure delivery.

Refer to our FAQs for short code best practices.

Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time2 weeks
UCS-2 support---
Use case restrictions

All promotional traffic must have clear opt out instructions.

Pre-registration only supported for Telcel, Movistar and AT&T networks. If traffic is sent to a different MNO or MVNO it will be delivered with a shared short code.

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported Not Supported
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - Domestic
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

You should only use Mexican mobile numbers for two-way person-to-person (P2P) communication. One-way application-to-person (A2P) and bulk traffic will be blocked. No marketing traffic is allowed. 

Best practices

Use a US or Canadian long code instead of a local Mexican number to send application-to-person (A2P) traffic.

Long Code - International
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

N/A

Best practices

SMS sent with international long codes will have the senderID overwritten with a random local long number or short code to ensure delivery.

Short Code
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time8 weeks
UCS-2 supportSupported
Use case restrictions

Refer to our FAQs for short code best practices.

Best practices

Refer to our FAQs for short code 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.