Quick answer: Mexico is not a "register your alphanumeric sender ID" market — it is a market where mobile-terminated (MT) SMS no longer carries your sender ID at all. Mexican operators terminate A2P SMS with generic short-code reader numbers, so the sender-identity question that dominates the US (10DLC) and India (DLT) playbook barely exists here. What does exist: PROFECO's REPEP opt-out registry and the Ley Federal de Protección al Consumidor (LFPC) consent and disclosure rules on the SMS side, and Meta's WABA regime on the WhatsApp side — which is where most business messaging in Mexico actually happens. This post is the first in a country-lane series: a single market, its SMS reality, its consumer-protection law, its carrier structure, and its channel mix, walked end to end.
Mexico is not yet a row in the country-rules reference the sender-ID playbook is built on, so this post is the planning narrative for a market you launch by exception, not by lookup: everything below is framed as tenant-owned controls and market intelligence, not legal advice, and the legal interpretation of Mexican law stays with you and your counsel.
The SMS reality: your sender ID does not arrive
Start with the fact that breaks the mental model imported from Europe or the US. The existing coverage of Latin America in the MENA and LatAm playbook states it in one line — "numeric long codes; alphanumerics commonly blocked" — and Mexico is the market where that line deserves a full explanation, because the mechanism is more specific than "blocked":
- MT SMS terminates with a reader number, not your sender. A2P traffic into Mexico is delivered with a generic short-code recipient number ("reader number") as the displayed originator. An alphanumeric sender ID you set does not reliably survive to the handset; it is either overwritten at the border or blocked upstream.
- Two-way identity comes from a Mexican virtual long code. If you need replies — OTP confirmations, keyword opt-ins, customer replies — you rent a Mexican virtual number, and that number is both the displayed sender and the reply path. This is the closest thing Mexico has to a "sender-ID regime," and it is a number rental, not a registration.
- Concatenation and encoding are liberal; filtering is not. Long messages concatenate (up to ten segments is commonly supported), Unicode/UCS-2 works, and binary content is accepted. What gets traffic stopped is content and consent posture, not message shape.
The planning consequence: do not budget an alphanumeric registration flow for Mexico (there is effectively nothing to register), and do not promise a recipient that "the message will come from YOURBRAND." The brand has to live in the message body — which interacts directly with PROFECO, below.
PROFECO, REPEP, and what the LFPC asks of marketing SMS
The consumer-protection layer is PROFECO — the Procuraduría Federal del Consumidor, Mexico's federal consumer attorney's office, enforcing the LFPC. Three obligations matter for anyone sending commercial SMS to Mexican recipients:
- REPEP — the do-not-call registry. The Registro Público de Consumidores lets consumers register their numbers to opt out of advertising calls and messages. Senders of marketing traffic are expected to check contact lists against REPEP and exclude registered numbers. REPEP is enforceable: consumers can and do file complaints, and PROFECO can sanction businesses that keep advertising to registered numbers.
- Consent and identification. Marketing messages require the recipient's prior consent under the LFPC, and a commercial message must identify the business behind it. Because the sender line is a generic reader number (above), identification happens in the message body itself — your brand name belongs in the text, every time, not just the first message of a program. This is the structural coupling of Mexican A2P: the network strips your identity from the envelope, the law requires it in the payload.
- Transactional vs. marketing posture. Transactional traffic (OTP, delivery updates, appointment reminders) faces the same delivery mechanics but a lighter consent burden than advertising. Keep the two streams separable — a template audit that mixes promotional language into transactional sends is the fastest route to a PROFECO complaint.
Orbit carries per-tenant compliance controls — consent tracking, quiet hours, message suppression, frequency caps — that you configure for a Mexico program the same way you would for a 10DLC campaign in the US; the specifics are on the compliance overview. None of that substitutes for checking your list against REPEP, which happens outside the platform.
The carrier map: two networks, one incumbent, and why "dual-carrier" is a simplification
Mexico's mobile market looks, at first glance, like a clean duopoly — and operationally, that is mostly true:
- Telcel (América Móvil) is the dominant network, carrying the large majority of A2P termination.
- AT&T Mexico absorbed the former Iusacell and Nextel networks and is the established second national operator.
- Movistar exited as a carrier: Telefónica sold its Mexican operations, and the Movistar brand now rides as an MVNO on AT&T Mexico's network.
So "Mexico is a dual-carrier market" is really: two physical radio networks do nearly all termination, one of them overwhelmingly dominant, plus a layer of MVNOs (Movistar, Bait, and others) whose subscribers terminate on one of the two host networks. For an A2P sender this means two things. Delivery characteristics and filtering behavior are effectively per-network, not per-brand — a number on a Movistar SIM behaves like an AT&T number because it is one. And interconnect concentration is high: a route that reaches Telcel and AT&T well is a complete Mexico route, which is why Mexico termination quality varies so visibly between providers that own direct operator relationships and providers that re-sell capacity. (The re-sold layer is also where gray routes live — the SMS pumping and gray-route explainer is the field guide. Outbound SMS from Orbit exits over Devotel's own wholesale network, which removes that layer.)
WhatsApp: the channel Mexican customers actually answered first
The Mexico row in every channel matrix comes out the same: WhatsApp is the dominant business-messaging surface, and SMS is the fallback for OTP, delivery updates, and recipients without the app. WhatsApp penetration in Mexico sits above 90% of internet users, so an SMS-first Mexico plan inverts the market.
The rules here are Meta's, not Mexican law's, and they are the same WABA rules as everywhere else: template categories pre-approved before you send outside the 24-hour customer-initiated window, display-name review, quality rating that throttles senders recipients block or report, per-country per-message pricing on utility vs. marketing templates. Where Mexico-specific planning enters is volume and expectation: because WhatsApp is the default surface customers answer on, Mexican programs skew heavier on marketing templates and heavier on inbound customer-initiated conversations than a comparable US program, and the quality-rating feedback loop bites faster at that volume.
The WhatsApp channel reference documents the send and template fields on Orbit; the RCS channel reference is where the third channel lives, though for Mexico specifically RCS should be treated as optional cover — carrier support there lags Brazil, and it is additive, never the primary reach.
Planning a Mexico launch on Devotel Orbit
Pulling the three sections above into a checklist, the Mexico plan differs from the generic five-step sender-ID launch in exactly the places the reader-number reality touches:
- Skip the alphanumeric registration step — there is no national alphanumeric regime to register into. If your platform or aggregator offers a "Mexico sender-ID pre-registration" form, what it is really selling is a place in an aggregator-side allowlist, not a Mexican regulator's approval; treat it accordingly.
- Rent a Mexican long code if you need two-way. It is the only durable sender identity Mexican recipients will see on SMS.
- Write identification into the message body. Brand name in every commercial message — the envelope does not carry it for you, and the LFPC expects it.
- Screen your marketing list against REPEP and suppress registered numbers before sending; keep transactional and marketing streams separable for consent posture.
- Lead with WhatsApp for the customer-facing program — WABA templates, quality hygiene, and an inbound-conversation posture planned around WhatsApp as the primary surface, SMS as fallback, RCS optional.
Since Mexico is not yet in the country-rules reference, there is no live row to consult for it the way the sender-ID playbook instructs for France, Singapore, or India — this post is the current planning source, and we will link the rules row in the further reading of this series when Mexico lands in the reference.
Frequently asked questions
Do I need to register a sender ID to send A2P SMS to Mexico?
No — there is no Mexico alphanumeric sender-ID registry to register into, because alphanumeric sender IDs do not reliably reach Mexican handsets at all. MT SMS terminates with generic short-code reader numbers. Plan sender identity around a rented Mexican long code (for two-way) and brand identification in the message text (for compliance), not around a sender-ID approval.
Is PROFECO registration mandatory before I market by SMS?
PROFECO is the regulator, not a registry you join. What is mandatory in practice is honoring REPEP — the public do-not-call registry — by screening marketing lists against it, and following the LFPC's consent and identification rules for commercial messages. Consumers whose numbers sit in REPEP and who receive advertising anyway can file complaints that lead to sanctions.
Is Mexico really a "dual-carrier market" — and what are the two carriers?
Telcel and AT&T Mexico run the two national radio networks that terminate the overwhelming majority of A2P traffic. Movistar is often listed as a third "carrier" in older writeups, but Telefónica sold its Mexican network operations and Movistar now operates as an MVNO on AT&T Mexico. Operationally, a Mexico route is judged by its Telcel and AT&T termination quality.
Can recipients reply to my SMS in Mexico?
Yes, if you send from a Mexican virtual long code — replies route back to that number. Sender-replaced traffic terminating on reader numbers is not two-way. If replies matter (keywords, confirmations, support), the long code is the mechanism, and the SMS channel reference documents how inbound messages surface on Orbit.
Should Mexico be an SMS-first or WhatsApp-first launch?
WhatsApp-first. With WhatsApp usage above 90% among Mexican internet users, customers expect businesses to be reachable there, and Meta's template regime is the registration-analogous hurdle to plan into your calendar. SMS remains necessary — OTP, delivery updates, uninstalled recipients — but as the fallback layer, not the primary conversation surface.
Source and further reading
- Sender-ID registration playbook by country: the five-step launch checklist this Mexico note modifies — steps 1 and 3 change shape when there is no alphanumeric regime to register.
- MENA and LatAm messaging channels playbook: the regional matrix in which Mexico's "numeric long codes; alphanumerics commonly blocked" row lives.
- WhatsApp channel reference: templates, the customer-initiated window, and quality rating on the region's primary channel.
- SMS channel reference: sender identity, reader-number behaviour, long codes, and delivery receipts.
- SMS pumping and gray-route fraud explainer: why interconnect provenance matters in a two-network termination market.
- Compliance overview: the tenant-owned consent, quiet-hours, and suppression controls a Mexico program configures.
Published 11 October 2026. This post is market intelligence and tenant-onboarding guidance, not legal advice; the legal interpretation of the LFPC and PROFECO's enforcement posture stays with you and your counsel.