Mexico
Name

Mexico

ISO Code

MX

Region

North America

Mobile Country Code

334

Dialing code

+52

Major carriers

Telcel, Movistar, AT&T

Guidelines for Mexico
Two-way SMS supported

Yes

Number portability available

Yes

Twilio concatenated message support

Yes

Message length

160 ASCII characters per message.

Twilio MMS support

Converted to SMS with embedded URL

Sending SMS to landline numbers

You 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.

Best practices

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.

Mexico has a unique dialing plan. When texting a mobile number, you must use the following format: "+52" + "1" + area code + subscriber number An example number is: +5215512345678

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 ensure 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 and Sender ID
Preregistered
Operator network capability

Not Available

Twilio supported

--

Sender ID format

--

Sender ID preserved

--

Two-way support

--

Provisioning time

--

Cost
--
Throughput (messages per second)
--
Use case restrictions
--
Best practices
--
Alphanumeric
Operator network capability

Not Available

Twilio supported

--

Sender ID format

--

Sender ID preserved

--

Two-way support

--

Provisioning time

--

Cost

--

Throughput (messages per second)

--

Use case restrictions

--

Best practices

--

Long Code
Operator network capability

Available

Twilio supported

Supported

Sender ID format

Mobile

Sender ID preserved

No

Two-way support

No

Provisioning time

--

Cost
Throughput (messages per second)

10 messages/second

Use case restrictions

You should only use Mexican mobile numbers for 2-way, peer-to-peer communication.

No marketing traffic is allowed.

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 capability

Not Available

Twilio supported

--

Sender ID format
--
Sender ID preserved
--
Two-way support
--
Provisioning time
--
Cost
--
Throughput (messages per second)
--
Use case restrictions
--
Best practices
--
The Twilio advantage
  • Communicate reliably

    Experience a 99.95% uptime SLA made possible with automated failover and zero maintenance windows.

  • Operate at scale

    Extend the same app you write once to new markets with configurable features for localization and compliance.

  • Many channels

    Use the same platform you know for voice, SMS, video, chat, two-factor authentication, and more.

  • No shenanigans

    Get to market faster with pay-as-you-go pricing, free support, and the freedom to scale up or down without contracts.