What actually changes when you send OTP, transactional or marketing A2P SMS into Guatemala — separated into Guatemalan law, supplier route policy and what we recommend operationally.
Last reviewed: 1 August 2026 · Central America / LATAM
A quick operational read on Guatemala. Anything marked route-dependent is set by the supplier and operator path your traffic uses, and is confirmed during route assessment.
SMS to mobile
Carrier or route policy
Supported
Number format
Law / regulation
+502 followed by an eight-digit mobile number beginning with 3, 4 or 5 — there is no domestic trunk zero to remove
Alphanumeric senderID
Carrier or route policy
Operator- and route-dependent: selected Tigo routes and approved or whitelisted Claro paths may preserve a brand, while many dynamic routes rewrite it to a local longcode or shortcode — preservation is never promised
International numeric / longcode senderID
Carrier or route policy
Commonly overwritten with a route-assigned local longcode or shortcode — preservation is not promised
Local numeric / two-way sender
Carrier or route policy
Selected services only; not a default international A2P capability
Dedicated or local shortcode
Carrier or route policy
Selected carrier or supplier programmes only — do not assume availability
Two-way SMS
Carrier or route policy
Standard international routes are commonly one-way — do not assume replies
Number portability
Law / regulation
Legal framework enacted, with operational implementation pending the implementing regulation as of the review date
Concatenation
Carrier or route policy
Provider documentation conflicts — one marks it unsupported while another marks it supported. Treat it as route-dependent and do not rely on it for critical traffic
MMS
Carrier or route policy
Some provider paths convert MMS to an SMS containing a URL
SMS to fixed line
Carrier or route policy
Not supported on standard routes
Marketing
Flowstates recommendation
No authoritative nationwide statutory SMS opt-in rule identified; provider routes and Flowstates require prior express permission, clear identity, opt-out and suppression controls
Personal data
Flowstates recommendation
No comprehensive private-sector personal-data law enacted as of 1 August 2026 — legislation remained under discussion. Apply notice, purpose limitation, minimisation, security, retention and rights handling as a Flowstates standard, and check sector-specific obligations
Last reviewed
Flowstates recommendation
1 August 2026
Route-dependent: “Route-dependent” means the behaviour is decided by the supplier and operator path your traffic takes, not by Guatemalan statute. Two providers can behave differently on the same day, and a route can change its policy. Confirm before launch.
Law, route policy and recommendation
Guatemalan statute, supplier route behaviour and our own operating standard are different things — and in Guatemala the gap between them is unusually wide. Every statement on this page is labelled so the right team can act on it.
Law / regulation
Law and regulation
Binding obligations from Guatemalan legislation and regulators: SIT administration of the national numbering plan and telecom resources, Decreto 14-2025 on number portability, the Consumer Protection and User Law (Decreto 006-2003) applied by DIACO, and Decreto 47-2008 on electronic communications and signatures. These apply whichever supplier you use.
Carrier or route policy
Carrier or route policy
Rules applied by operators, aggregators or your provider on the specific A2P path your traffic takes — sender rewriting, whether a brand survives on Tigo or an approved Claro path, whether replies are possible, concatenation behaviour and MMS handling. Route-dependent and subject to change, and providers openly disagree about Guatemala.
Flowstates recommendation
Flowstates operational recommendation
What we ask customers to do because it protects deliverability and keeps you comfortably inside both the law and route policy. In Guatemala, where a comprehensive private-sector data law has not been enacted, our standard is deliberately stricter than the legal minimum.
Numbering and networks
The basics your validation layer and templates need to get right before the first send.
Law / regulationNumber format
Guatemala uses an eight-digit national numbering plan. Mobile and non-geographic subscriber numbers begin with 3, 4 or 5. There is no domestic trunk zero to remove, so the national number and the E.164 subscriber part are the same digits.
Law / regulationDialling code
Country dialling code +502. Mobile country code 704.
Law / regulationNumbering administration
The Superintendencia de Telecomunicaciones (SIT) administers the national numbering plan and telecom resources, so numbering questions are settled against SIT material rather than provider documentation.
Law / regulationFixed and geographic ranges
Fixed and geographic numbers begin with 2, 6 or 7. Standard A2P SMS routes target mobile destinations, and fixed-line destinations should be validated out.
Law / regulationNumber portability
Decreto 14-2025, the Ley de Portabilidad Numérica en Servicios de Telefonía, was published and entered into force on 28 November 2025. The legal framework therefore exists, but live operational implementation depends on the implementing regulation and technical process, which official Congress and Diario de Centro América sources still described as under review in July 2026.
Flowstates recommendationPortability handling
Until implementation is confirmed live, ranges may still reflect original assignment — but do not hard-code a permanent operator inference. Build validation and routing so a current-operator lookup can become authoritative the moment portability starts, and re-check the status before launch.
Carrier or route policyNetworks
The current major consumer mobile networks to plan for are Claro and Tigo. Some provider tables retain legacy legal or operator labels; we do not describe Movistar as a separate current consumer network. We publish no market-share or universal route-coverage claims here.
Flowstates recommendationValidation
Validate to E.164 and run mobile validation or lookup before sending, rejecting fixed and geographic destinations because standard routes do not deliver to them.
E.164 example
+502 3XXX XXXX / +502 4XXX XXXX / +502 5XXX XXXX
Country code 502, then the eight-digit mobile number beginning with 3, 4 or 5. There is no domestic trunk zero to remove. These are masked illustrative patterns, not real subscriber numbers.
SenderID options
Guatemala is a market where current provider documentation materially disagrees. One supplier supports pre-registration only toward Claro and can preserve a preregistered brand, another supports alphanumeric senders toward Tigo without registration, a third states that alphanumeric senders are overwritten to a random local longcode or shortcode, and a fourth advertises one-way alphanumeric coverage. Treat sender presentation as operator- and route-dependent, never promise preservation, and design the message body so it still identifies your brand when the visible sender changes.
Carrier or route policy
This whole comparison — best for, what the recipient sees and replies — describes carrier or route behaviour on current A2P paths into Guatemala, not Guatemalan statute. Suppliers describe Guatemala differently, behaviour varies by operator and route, and it is validated live before launch rather than guaranteed universally.
Submitted alphanumeric senderID
Best for
One-way OTP, transactional and authorised marketing on a validated operator route
What the recipient sees
The submitted brand on selected Tigo or approved / whitelisted Claro paths; otherwise a route-assigned local longcode or shortcode
Replies
No
International longcode
Best for
Selected one-way transactional or service traffic where the route accepts numeric sender submission
What the recipient sees
Commonly a route-assigned local longcode or shortcode rather than the submitted international number
Replies
Do not assume — only where an expressly selected service supports inbound SMS
Provider-assigned local numeric sender
Best for
Selected service, support or conversational use cases
What the recipient sees
The local numeric sender assigned to that service
Replies
Potentially available only when explicitly configured
Dedicated or local shortcode
Best for
Selected scale programmes and a stable numeric identity
What the recipient sees
The supported shortcode where the carrier or supplier programme is available
Replies
Route- and programme-dependent
SenderID options
Option
Best for
What the recipient sees
Replies
Submitted alphanumeric senderID
One-way OTP, transactional and authorised marketing on a validated operator route
The submitted brand on selected Tigo or approved / whitelisted Claro paths; otherwise a route-assigned local longcode or shortcode
No
International longcode
Selected one-way transactional or service traffic where the route accepts numeric sender submission
Commonly a route-assigned local longcode or shortcode rather than the submitted international number
Do not assume — only where an expressly selected service supports inbound SMS
Provider-assigned local numeric sender
Selected service, support or conversational use cases
The local numeric sender assigned to that service
Potentially available only when explicitly configured
Dedicated or local shortcode
Selected scale programmes and a stable numeric identity
The supported shortcode where the carrier or supplier programme is available
Route- and programme-dependent
Put a meaningful brand and the purpose in the message body, because the visible sender can change. Generic sender identifiers may be filtered on some provider paths, so we recommend a recognisable brand — that is route policy and a Flowstates recommendation, not Guatemalan statute. Provider-assigned local numeric or two-way services exist only where expressly offered, dedicated shortcodes only through selected carrier or supplier programmes, and selected sender arrangements may be required on a given operator path.
What changes by traffic type
Guatemala is not one rulebook. The same destination behaves differently depending on the category you send and the route it takes.
OTP / authentication
Suitable on validated high-quality routes.
Flowstates recommendation
Keep the copy purely transactional and concise, and within a single segment wherever practical.
Flowstates recommendation
Put the brand in the message body, because sender presentation may be rewritten.
Flowstates recommendation
No promotional content in OTP templates.
Flowstates recommendation
Use a branded domain for any link and avoid ambiguous link text.
Flowstates recommendation
Monitor delivery, latency, completed-verification conversion and operator or route performance.
Flowstates recommendation
Configure carrier-grade failover so a degraded path does not become a failed login queue.
Carrier or route policy
Do not rely on concatenation, because provider documentation for Guatemala disagrees about whether it is supported at all.
Carrier or route policy
Standard international A2P routes into Guatemala are generally one-way. Do not build a verification flow around replies unless a two-way service is explicitly configured.
Transactional / service
Suitable for alerts, confirmations and account or service updates.
Flowstates recommendation
Identify the brand and state the purpose of the message clearly.
Flowstates recommendation
Use a branded domain for links rather than a public or shared shortener.
Flowstates recommendation
Keep promotional content out of transactional templates.
Flowstates recommendation
Prefer a single segment, and test any necessary concatenation on the exact selected sender and operator route before relying on it.
Carrier or route policy
Enable replies only on an explicitly configured two-way service. Inbound handling is not a default on Guatemalan A2P paths.
Flowstates recommendation
Keep the distinction between a genuinely informational or service message and commercial promotion. Do not relabel marketing as transactional.
Marketing / promotional
Prior express permission, accurate and identifiable advertising, a free way to stop and prompt suppression.
Flowstates recommendation
We have not identified an authoritative current source establishing a specific nationwide statutory SMS opt-in rule or a national SMS do-not-call registry in Guatemala, and we do not claim one.
Carrier or route policy
Provider routes may nevertheless require opt-in for promotional traffic. That is route policy, applied by the supplier and operator path you use.
Flowstates recommendation
Flowstates requires prior express, purpose-specific and SMS-channel-specific permission for every promotional message.
Flowstates recommendation
Retain recipient, timestamp, source, exact wording or version, purpose and channel permission.
Law / regulation
DIACO administers the Consumer Protection and User Law (Decreto 006-2003) and handles complaints, including complaints about misleading advertising. Marketing claims must be accurate, identifiable and not misleading.
Law / regulation
Decreto 47-2008 recognises electronic communications and preserves applicable consumer-protection law. It is not a blanket marketing-SMS consent statute.
Flowstates recommendation
Provide a simple and free opt-out in every promotional SMS and suppress promptly.
Flowstates recommendation
Support natural Spanish requests such as BAJA, SALIR, CANCELAR and NO. We do not claim any one keyword is universally mandated by statute.
Flowstates recommendation
Maintain an internal suppression and do-not-disturb list regardless of any external register.
Flowstates recommendation
Schedule in recipient-local daytime as our operating recommendation, not an invented statutory campaign-hours window. A selected route may impose a stricter window, which we confirm privately.
Flowstates recommendation
Do not use purchased lists.
Carrier or route policy
Use the promotional route agreed for the traffic; category acceptance is confirmed privately for the selected route rather than published as a general list.
Guatemala’s consent, consumer-protection and data-governance position
Guatemala does not currently give you a single channel-specific SMS consent statute to point at. That makes the distinction between law, route policy and our own standard more important here than in most LATAM markets, not less.
Law / regulation
As of 1 August 2026, Guatemala had not enacted a comprehensive private-sector personal-data law. Initiative 6464 remained under legislative review in July 2026, and its proposed rights and duties must not be described as current law.
Law / regulation
Guatemala’s existing constitutional, public-information and electronic-communications rules are not a substitute for a comprehensive private-sector data law, and they do not create a blanket nationwide SMS marketing opt-in rule.
Law / regulation
DIACO is responsible for applying the Consumer Protection and User Law. Advertising must not be misleading, and consumers can complain about misleading advertising.
Law / regulation
Decreto 47-2008 applies to electronic communications and signatures while leaving consumer-protection law applicable. It does not by itself establish a universal SMS marketing-consent regime.
Carrier or route policy
Provider policies can require prior opt-in even where a specific nationwide SMS statute has not been identified. That is route policy, confirmed for the supplier and operator path you use.
Flowstates recommendation
Flowstates requires clear privacy information, a documented purpose, data minimisation, sensible retention, appropriate security, prior express permission for promotions, easy withdrawal or opt-out, and prompt suppression.
Flowstates recommendation
A direct opt-out or withdrawal must be honoured promptly, whether or not the recipient appears on any external list.
Flowstates recommendation
Do not claim every OTP or service notification is marketing. Keep purpose and template categories separate, and keep promotional copy out of transactional and verification messages.
Flowstates recommendation
Sector-specific obligations may apply to your traffic. Public category acceptance stays generic here and is validated privately for the selected route.
Flowstates recommendation
Retain the privacy notice and its version, the purpose, the permission record, any opt-out or withdrawal, the suppression action, campaign records and evidence of how the data was processed.
Operational compliance checklist
What we expect to see in place before a Guatemala route goes live.
Flowstates recommendation
Record the source, purpose and permitted use of every recipient record.
Flowstates recommendation
Provide clear privacy information and retain the version shown to the recipient.
Flowstates recommendation
For promotions, retain recipient, timestamp, source, exact wording or version, purpose and SMS-channel permission.
Flowstates recommendation
Identify the brand and the purpose in every message.
Law / regulation
Ensure advertising claims are accurate and not misleading.
Flowstates recommendation
For promotions, provide a working, simple and free method to stop the communications.
Flowstates recommendation
Support BAJA, SALIR, CANCELAR and NO without claiming a universal statutory keyword.
Flowstates recommendation
Suppress promptly and maintain an internal suppression and do-not-disturb list across all systems.
Flowstates recommendation
Do not use purchased lists.
Flowstates recommendation
Schedule by Guatemala recipient-local daytime.
Flowstates recommendation
Classify OTP, transactional or informational and marketing templates, and keep promotional copy out of OTP and service messages.
Flowstates recommendation
Use a branded short domain rather than a public or shared URL shortener.
Carrier or route policy
Keep critical templates to one segment unless the exact route has passed concatenation testing.
Carrier or route policy
Validate the exact senderID, operator path, use case and route before launch.
Carrier or route policy
Confirm category acceptance privately for the selected route, rather than relying on a published category list.
Law / regulation
Re-check the operational status of number portability before launch.
Flowstates recommendation
Keep template, privacy, permission, opt-out, campaign, suppression and route-approval records.
Encoding and delivery
Spanish copy makes encoding a real cost and delivery question in Guatemala, and concatenation is genuinely uncertain because suppliers document it differently. Test the exact path rather than trusting a generic table.
GSM-7, single segment
160 characters
GSM-7, concatenated
153 characters per segment
Unicode / UCS-2, single segment
70 characters
Unicode / UCS-2, concatenated
67 characters per segment
Flowstates recommendation
Spanish accents, smart punctuation, emoji and formatting pasted from a document can change the encoding, which shortens the segment and changes the segment count. Check the encoding your template actually produces.
Carrier or route policy
Provider documentation for Guatemala conflicts on concatenation — one supplier marks it unsupported while another marks it supported. Test the exact path, and keep OTP and critical-service templates to a single segment.
Flowstates recommendation
Run end-to-end testing across the purchased Claro and Tigo routes before launch, and repeat it whenever the sender or route changes.
Flowstates recommendation
Normalise to E.164 as +502 3XXX XXXX, +502 4XXX XXXX or +502 5XXX XXXX — there is no domestic trunk zero to remove — then run mobile validation or lookup before sending. Fixed and geographic destinations begin 2, 6 or 7 and standard routes do not deliver to them.
Law / regulation
Number portability has a legal framework in place, but its operational status must be checked before you rely on prefix-to-operator mapping for routing or reporting.
Carrier or route policy
Some provider paths convert an MMS into an SMS containing a URL. That is route policy, not a Guatemalan rule.
A country guide is only useful when the route follows it.
Reading Guatemala’s position is the easy half. Keeping every send inside it, on supplier routes that describe the same country in four different ways and change their policy, is the operational half — that is the part we run.
Per-country and per-category routing
OTP, transactional and marketing traffic take different Guatemala routes, with the right policy applied to each category.
SenderID management
We manage sender presentation where a route supports it, including selected Tigo and approved Claro behaviour, and design templates for the common case where the sender is rewritten to a local numeric one.
Carrier-grade failover
When a Guatemala route degrades, traffic moves before your verification funnel does.
Per-route visibility
Delivery, latency and OTP conversion measured per route and per operator, so a route policy change shows up as data rather than complaints.
24/7 vendor escalation
We chase the supplier and the carrier. You get the update, not the ticket queue.
BYOV / BYOG
Keep your existing supplier and contracts and let us operate the routing, or use ours.
Branded short links
Links on your own domain instead of a shared shortener, which route filters treat very differently.
A quick operational read on Guatemala. Anything marked route-dependent is set by the supplier and operator path your traffic uses, and is confirmed during route assessment. SMS to mobile: Supported. Number format: +502 followed by an eight-digit mobile number beginning with 3, 4 or 5 — there is no domestic trunk zero to remove. Alphanumeric senderID: Operator- and route-dependent: selected Tigo routes and approved or whitelisted Claro paths may preserve a brand, while many dynamic routes rewrite it to a local longcode or shortcode — preservation is never promised. International numeric / longcode senderID: Commonly overwritten with a route-assigned local longcode or shortcode — preservation is not promised.
Which sender ID options work for SMS in Guatemala?
Guatemala is a market where current provider documentation materially disagrees. Submitted alphanumeric senderID — Best for: One-way OTP, transactional and authorised marketing on a validated operator route. International longcode — Best for: Selected one-way transactional or service traffic where the route accepts numeric sender submission. Provider-assigned local numeric sender — Best for: Selected service, support or conversational use cases. Dedicated or local shortcode — Best for: Selected scale programmes and a stable numeric identity.
What are the consent and opt-out requirements for SMS in Guatemala?
Guatemala does not currently give you a single channel-specific SMS consent statute to point at. As of 1 August 2026, Guatemala had not enacted a comprehensive private-sector personal-data law. Initiative 6464 remained under legislative review in July 2026, and its proposed rights and duties must not be described as current law. Guatemala’s existing constitutional, public-information and electronic-communications rules are not a substitute for a comprehensive private-sector data law, and they do not create a blanket nationwide SMS marketing opt-in rule. DIACO is responsible for applying the Consumer Protection and User Law. Advertising must not be misleading, and consumers can complain about misleading advertising.
How many characters fit in an SMS to Guatemala?
Spanish copy makes encoding a real cost and delivery question in Guatemala, and concatenation is genuinely uncertain because suppliers document it differently. GSM-7, single segment: 160 characters. GSM-7, concatenated: 153 characters per segment. Unicode / UCS-2, single segment: 70 characters. Unicode / UCS-2, concatenated: 67 characters per segment.
Sources and change control
Regulator, statute and provider references behind this guide. Provider documentation reflects a supplier’s current route policy, not Guatemalan law — SIT controls numbering and telecom administration, official Congress and Diario de Centro América sources control the portability status and the pending data-law position, and DIACO controls consumer-protection authority wording. Where providers disagree we use route-dependent language rather than picking a winner.
One supplier’s current route policy: pre-registration supported only toward Claro Guatemala with a preregistered alpha able to be preserved, dynamic alpha not fully supported and possibly rewritten to a domestic longcode or shortcode, international numeric senders possibly overwritten, standard two-way and concatenation marked unsupported, MMS possibly converted to SMS with a URL, and fixed-line SMS unsupported.
The portability law published and in force from 28 November 2025. The legal framework exists; it does not by itself confirm live operational portability.
Official confirmation that portability was moving toward application while the regulation remained under review. Re-check before launch rather than assuming portability is already live.
Country-specific page stating that alphanumeric senderIDs are not supported and are overwritten to a random local longcode or shortcode. A broader availability table from the same supplier conflicts with it, which we treat as evidence of uncertainty rather than a universal conclusion.
States that alphanumeric senderIDs are supported toward Comcel/Tigo without registration, that older senderIDs were whitelisted on Claro and new Claro brands require a selected approval arrangement, that numeric senderIDs are unsupported except through an expressly offered two-way service, and that generic identifiers may be filtered. Its detailed category restrictions are provider policy and are not reproduced here.
States that senderIDs are unsupported and replaced by a random numeric sender and that standard two-way is unsupported, while marking concatenation supported — the direct opposite of another supplier.
Advertises one-way alphanumeric coverage for Guatemala, another reason never to promise one universal sender behaviour.
Change log
1 August 2026 — Initial draft; separated Guatemala’s current legal position from operator-specific sender preservation, pending portability implementation and route-dependent concatenation.
Last reviewed 1 August 2026
Disclaimer
This is operational guidance, not legal advice. Applicable requirements vary by operator, route, senderID, traffic category, message purpose, sector and customer configuration. Flowstates confirms the live path during onboarding.
