Honduras SMS Guide: Sender IDs, Privacy & Route Policy

At a glance

A quick operational read on Honduras. Anything marked route-dependent is decided by the supplier and operator path your traffic uses. Anything marked law applies whichever supplier you pick.

Number format: +504 followed by an eight-digit national significant number; Honduras runs a closed eight-digit plan, and no domestic trunk prefix was found in the CONATEL material reviewed
Mobile numbering: CONATEL numbering-assignment resolutions place mobile and PCS service in the 3, 7, 8 and 9 leading-digit series, structured WXYZ-MCDU
Fixed-line numbering: Geographic fixed-line numbers use the 2 series, following the November 2010 migration from seven to eight digits
Short and service codes: Three-digit and 1XY short codes are allocated individually by CONATEL and consolidated under its Códigos de Numeración Corta regulation; they are not A2P destinations
Number portability: CONATEL's Reglamento de Portabilidad Numérica (NR012/13, 2013, amended by NR010/17) covers mobile and PCS service only and expressly excluded fixed telephony; CONATEL has described the service as free to the user
Comprehensive data-protection law: None verified in force as of 17 August 2026; the sources reviewed show repeated bills before the Congreso Nacional, including a personal-data-protection bill presented on 29 April 2026. A bill is not enacted law
Constitutional privacy: Article 76 guarantees personal and family privacy, article 100 protects the inviolability and secrecy of communications including telephone communications, and article 182 recognises habeas data
Consumer advertising duties: The Ley de Protección al Consumidor (Decreto 24-2008, reformed by Decreto 75-2024) and its current Reglamento (Acuerdo 084-2021) require promotion, contest and offer information to be accurate, complete and not misleading in every advertising medium
National SMS do-not-call registry: No officially established national SMS do-not-call or do-not-disturb registry was identified in the Honduran sources reviewed on 17 August 2026
Mobile country code: Mobile country code 708
Two-way SMS: Not supported on Twilio's current Honduras route; the route is one-way
Portability on route: Twilio marks number portability as available in Honduras
Concatenation: Twilio marks it as supported with a caveat: it may not be supported for certain sender ID types, and where messages are split and rejoined can vary with character encoding
MMS: Twilio converts MMS into an SMS with an embedded URL
SMS to landline: Not supported on that route: messages to a Honduran fixed-line destination are rejected rather than delivered
Preregistered alphanumeric sender: Operator networks support preregistration with no segregation between international and domestic traffic, Twilio supports it, and the sender ID is preserved
Dynamic alphanumeric sender: Not supported by Honduran operator networks; Twilio accepts it but the sender ID is not preserved and may be overwritten with a local long code or short code outside the Twilio platform
Claro caveat: For the Claro network specifically, alphanumeric sender IDs are only supported through preregistration
Domestic long code: Not supported by Honduran operator networks on that route
International long code: Operator-supported and Twilio-supported, but the sender ID is not preserved and may be overwritten with a local long code or short code outside the Twilio platform
Short code: Twilio's current Honduras page publishes no short-code capability or support value, so treat it as unavailable unless your supplier confirms otherwise in writing
Unicode / UCS-2: Marked supported for the preregistered alphanumeric sender type; no value is published for the other sender types
Sender strategy: Preregister the alphanumeric sender you intend to use, because it is the only sender type on this route that the operator networks preserve
Operator resolution: Because mobile portability is live, resolve the destination network with a live lookup or supplier routing intelligence rather than inferring it from the leading digit
Permission standard: Send promotional SMS only with prior express, attributable, purpose-specific and SMS-channel-specific permission
Opt-out: Offer a free opt-out that does not depend on a reply, because the route is one-way, and suppress it immediately everywhere
Last reviewed: 17 August 2026

Route-dependent: “Route-dependent” means the behaviour is decided by the supplier and operator path your traffic takes, not by Honduran law. Two providers can behave differently on the same day and a route can change its policy without notice. Numbering, mobile portability, constitutional privacy protections and consumer-advertising duties, by contrast, are law and apply to every route.

Law, route policy and recommendation

Honduras is a market where the legal layer is thinner than teams expect and the route layer is where launches actually break. There is no comprehensive personal-data statute in force, so the discipline has to come from constitutional privacy protections, consumer law and our own operating standard.

Law / regulation
Honduran law and regulation
CONATEL administers the national numbering plan for country code +504 under the Ley Marco del Sector de Telecomunicaciones (Decreto 185-95) and operates a mobile-only number-portability regime under Resolución NR012/13, amended by NR010/17. The Constitution guarantees personal and family privacy (article 76), the inviolability and secrecy of communications including telephone communications (article 100) and habeas data (article 182, as reformed). The Ley de Transparencia y Acceso a la Información Pública (Decreto 170-2006) provides the habeas data mechanism and protects personal data held by public bodies, but it binds state entities rather than private marketers. The Ley de Protección al Consumidor (Decreto 24-2008, reformed by Decreto 75-2024) and its current Reglamento (Acuerdo 084-2021) govern truthful advertising, promotions and offers. As of 17 August 2026 no comprehensive personal-data-protection law was verified in force.
Carrier or route policy
Supplier and carrier route policy
Whether your sender survives, whether a reply can reach you and whether a long message concatenates cleanly are decided by the supplier and operator path. On Twilio's current Honduras route, two-way SMS is not supported, number portability is marked available, concatenation is marked supported with a sender-type and encoding caveat, MMS is converted into an SMS with an embedded URL, SMS to landline numbers is rejected rather than delivered, preregistered alphanumeric senders are supported by the operator networks with no segregation between international and domestic traffic and are preserved, dynamic alphanumeric senders are not supported by the operator networks and may be overwritten with a local long code or short code outside the platform, alphanumeric sender IDs towards Claro are only supported through preregistration, domestic long codes are not supported by the operator networks, and international long codes are supported but not preserved. Another supplier can differ on any of these on the same day.
Flowstates recommendation
Flowstates recommendation
We ask for validation that accepts the current mobile series, live network resolution instead of prefix inference, a preregistered alphanumeric sender wherever brand presentation matters, prior express and channel-specific permission for promotional SMS, a free opt-out that never depends on a reply, immediate suppression across every system, recipient-local daytime sending and single-segment discipline for anything time-critical. These are our operating standards, held above the statutory floor, not restatements of Honduran law.

Numbering and networks

Get the numbering right before you debug delivery. Honduras runs a closed eight-digit plan, so normalisation is simple — the traps are stale seven-digit records and operator inference on a market where mobile portability has been live for years.

Law / regulationCountry code
Honduras uses country code +504.
Law / regulationNumber length
Honduras runs a closed eight-digit national significant number plan. Mobile numbering moved to the eight-digit WXYZ-MCDU structure under a 2008 CONATEL resolution and fixed-line numbering migrated from seven to eight digits on 14 November 2010.
Law / regulationMobile ranges
CONATEL numbering-assignment resolutions place mobile cellular and PCS service in the 3, 7, 8 and 9 leading-digit series, including the 801-0000 to 899-9999 block attributed to mobile and PCS operators in 2006 and the 96x, 97x and 98x blocks assigned earlier.
Law / regulationFixed-line range
Geographic fixed-line numbers use the 2 series under the same eight-digit plan.
Law / regulationShort and service codes
Three-digit and 1XY short codes such as 911 and the 185 consumer line are allocated individually by CONATEL and consolidated under its Códigos de Numeración Corta regulation (NR010/22).
Law / regulationMobile portability
CONATEL's Reglamento de Portabilidad Numérica (Resolución NR012/13, 16 August 2013, amended by Resolución NR010/17) applies to mobile cellular and PCS service. Its recitals record that conditions were favourable for mobile portability and not for fixed telephony, so fixed-line service was expressly excluded.
Law / regulationPortability in practice
CONATEL has publicly described mobile portability as free to the user, completed within twenty-four hours and available to both prepaid and postpaid subscribers, with porting volumes reported every year since the 2014 launch.
Flowstates recommendationTrunk prefix
No domestic trunk prefix was identified for Honduras in the CONATEL numbering material reviewed on 17 August 2026, and no CONATEL resolution reviewed names an international access code. Treat both as unconfirmed rather than assuming a regional default, and normalise to E.164 instead.
Flowstates recommendationE.164 normalisation
Normalise every destination to E.164 as +504 followed by the eight national digits before submitting it to an A2P API.
Flowstates recommendationLegacy seven-digit records
Audit any Honduran contact data captured before the eight-digit migrations. Seven-digit records will not normalise cleanly and will fail silently at submission.
Flowstates recommendationFixed-line filtering
Filter 2-series fixed-line numbers and any short or service code out of A2P mobile campaigns before submission; neither is a mobile A2P destination.
Flowstates recommendationOperator resolution
Because mobile portability has been live since 2014, the leading digit cannot be relied on to identify the current operator. Use a current network lookup or your supplier's routing intelligence before making any route-specific decision, including the Claro preregistration caveat.
Flowstates recommendationOperator mapping
CONATEL does not publish a single consolidated current table mapping every mobile prefix to every operator, so do not build routing logic on a third-party prefix-to-operator list. Test destinations across the mobile series and the main consumer networks before scaling.
Carrier or route policyPortability on route
Twilio marks number portability as available in Honduras on its current route.
Carrier or route policyFixed-line destinations
Twilio's current route cannot send SMS to a Honduran landline destination: such messages are rejected rather than delivered, so a fixed-line number is not a usable A2P destination on that route.

E.164 example

+504 3XXX XXXX / +504 7XXX XXXX / +504 8XXX XXXX / +504 9XXX XXXX

A domestic mobile number written as eight digits becomes +504 followed by those same eight digits. A number beginning with 2 is a fixed line, not a mobile A2P destination, and a three-digit or 1XY short code is a service code rather than a subscriber number.

SenderID options

Sender presentation in Honduras is decided by the selected route and the destination network. Nothing below describes a universal Honduran sender behaviour: each row is the behaviour of a selected supplier path.

Carrier or route policy

Every field in this table is carrier or route behaviour on a selected supplier path, and it varies by supplier and by destination network. None of it is Honduran law, and none of it should be read as a general Honduran sender rule. Commercial and provisioning detail is handled privately during onboarding rather than published here.

Preregistered alphanumeric sender

Best for: Any brand-visible OTP, service or promotional traffic, and the only option that works towards Claro where alphanumeric senders are supported through preregistration only
Recipient sees: The approved brand sender, preserved by the operator networks, with no segregation between international and domestic traffic on that path
Replies: Not supported on that route

Dynamic alphanumeric sender

Best for: Not recommended; included because traffic often defaults into it when no preregistration exists
Recipient sees: Honduran operator networks do not support dynamic alphanumeric senders, so the submitted sender is not preserved and may be overwritten with a local long code or short code outside the sending platform
Replies: Not supported on that route

International numeric sender (international long code)

Best for: Traffic that must terminate while a preregistered alphanumeric sender is not yet available on the selected path
Recipient sees: A numeric origin that is not the number you submitted: the sender is not preserved and may be overwritten with a local long code or short code outside the sending platform
Replies: Not supported on that route

Domestic long code

Best for: Nothing on the current route; included so teams stop designing around a local subscriber origin that the networks do not accept
Recipient sees: Not applicable — Honduran operator networks do not support domestic long codes as an A2P origin on the selected route, so traffic has to use one of the options above
Replies: Not available

SenderID options
Option	Best for	Recipient sees	Replies
Preregistered alphanumeric sender	Any brand-visible OTP, service or promotional traffic, and the only option that works towards Claro where alphanumeric senders are supported through preregistration only	The approved brand sender, preserved by the operator networks, with no segregation between international and domestic traffic on that path	Not supported on that route
Dynamic alphanumeric sender	Not recommended; included because traffic often defaults into it when no preregistration exists	Honduran operator networks do not support dynamic alphanumeric senders, so the submitted sender is not preserved and may be overwritten with a local long code or short code outside the sending platform	Not supported on that route
International numeric sender (international long code)	Traffic that must terminate while a preregistered alphanumeric sender is not yet available on the selected path	A numeric origin that is not the number you submitted: the sender is not preserved and may be overwritten with a local long code or short code outside the sending platform	Not supported on that route
Domestic long code	Nothing on the current route; included so teams stop designing around a local subscriber origin that the networks do not accept	Not applicable — Honduran operator networks do not support domestic long codes as an A2P origin on the selected route, so traffic has to use one of the options above	Not available

Confirm the actual visible sender, and the fallback behaviour when the primary route is unavailable, before you launch. A fallback route that silently substitutes a local long code or short code will break OTP recognition and brand trust even when delivery reports look healthy.

What changes by traffic type

OTP, transactional and marketing traffic fail in different ways in Honduras. Split them across routes, templates and permission records rather than running one blended stream.

OTP and authentication

Short-lived codes where a rewritten sender or an unexpected split costs you conversions, not just deliveries.

Carrier or route policy
Two-way SMS is not supported on Twilio's current Honduras route.
Carrier or route policy
Only the preregistered alphanumeric sender is preserved; a dynamic alphanumeric sender or an international long code may be overwritten with a local long code or short code outside the sending platform.
Carrier or route policy
Concatenation is marked supported with a caveat: it may not be supported for certain sender ID types, and where messages are split and rejoined can vary with character encoding.
Carrier or route policy
UCS-2 is marked supported for the preregistered alphanumeric sender type, with no value published for the other sender types.
Flowstates recommendation
Design OTP as one-way and never depend on the recipient replying.
Flowstates recommendation
Put the code early in the message and keep promotional content out of it.
Flowstates recommendation
Identify the brand and the purpose in the message body, because the visible sender may be rewritten if the preregistered sender is not in use.
Flowstates recommendation
Include a clear expiry cue so the recipient knows how long the code is valid.
Flowstates recommendation
Keep the message inside a single segment where practical rather than relying on concatenation.
Flowstates recommendation
Test sender rewriting, concatenation, character handling, delivery and latency on the exact contracted route before scaling.
Flowstates recommendation
Measure completed verifications, delivery and latency by route and by operator rather than in aggregate, so a single-network sender problem is visible early.
Flowstates recommendation
Keep carrier-grade failover in place, with fallback senders that are themselves valid for Honduras.

Transactional and service

Messages the recipient expects because of something they already did with you.

Carrier or route policy
MMS is converted into an SMS with an embedded URL on Twilio's current Honduras route.
Carrier or route policy
SMS to a Honduran landline destination is rejected rather than delivered on that route, so validate line type before sending.
Flowstates recommendation
Keep the purpose expected and tied to the existing relationship rather than to a marketing objective.
Flowstates recommendation
Do not blend promotional copy into service templates to avoid the discipline you would apply to marketing.
Flowstates recommendation
Identify the brand and the purpose in the message body where sender presentation can change.
Flowstates recommendation
Use branded short domains rather than public or shared shorteners, so the link matches the brand in the body.
Flowstates recommendation
Design service flows as one-way while the route does not support replies, and give an alternative contact route in the body.
Flowstates recommendation
Monitor delivery, latency and filtering per route and per operator, with carrier-grade failover behind it.

Marketing and promotional

Promotional traffic where consumer law, constitutional privacy protections, provider policy and a one-way route all shape the design.

Law / regulation
The Ley de Protección al Consumidor (Decreto 24-2008, reformed by Decreto 75-2024) and its current Reglamento (Acuerdo 084-2021) require promotion, contest and offer information to be accurate, complete and not misleading in every advertising medium, and misleading advertising is a groundable consumer complaint.
Law / regulation
The Constitution guarantees personal and family privacy in article 76 and the inviolability and secrecy of communications in article 100, and article 182 gives an individual a habeas data remedy over personal data held in public or private records.
Law / regulation
No comprehensive personal-data-protection statute was verified in force in Honduras as of 17 August 2026, so there is no national statutory consent standard, objection right or suppression deadline specific to marketing SMS to rely on.
Carrier or route policy
The current route is one-way, so a reply-based opt-out keyword cannot be relied on, and the provider's own guidance asks customers to obtain opt-in consent, to message during the recipient's daytime hours unless urgent, to support HELP and STOP style messages in the recipient's language, and not to contact end users on do-not-call or do-not-disturb registries.
Flowstates recommendation
Use prior express, attributable, purpose-specific and SMS-channel-specific permission as our standard, because Honduran statute does not supply one.
Flowstates recommendation
Identify the sending brand and the purpose in the message body, because the visible sender may be rewritten.
Flowstates recommendation
Offer a free and simple opt-out that works without a reply: a link, an account setting, a web form, an email address or another accessible mechanism.
Flowstates recommendation
Suppress every opt-out immediately across all sending systems and lists as our own operating standard.
Flowstates recommendation
Keep offer terms accurate, complete and non-misleading in the message and on the landing page.
Flowstates recommendation
Send in recipient-local daytime hours as our operating standard, not because a Honduran statutory window was identified.
Flowstates recommendation
Do not use purchased or rented lists.

Honduras privacy, consent and marketing position

Honduras is not a comprehensive data-protection jurisdiction today. The protections that exist are constitutional, public-sector transparency, consumer-protection and sector telecom rules — which means the operating standard you apply is doing most of the work, and you should say so internally rather than pretending a statute is carrying it.

Law / regulation
Article 76 of the Constitution guarantees the right to honour, to personal and family privacy and to one's own image.
Law / regulation
Article 100 of the Constitution protects the inviolability and secrecy of communications, expressly including telephone communications, save by judicial decision. Its text addresses communications secrecy rather than commercial use of contact data.
Law / regulation
Habeas data was introduced by Decreto Legislativo 381-2005 and consolidated by Decreto Legislativo 10-2013, which reformed article 182 so that a person whose personal or family data appears in public or private records can bring the action; it is procedurally implemented through the Ley sobre Justicia Constitucional.
Law / regulation
The Ley de Transparencia y Acceso a la Información Pública (Decreto Legislativo 170-2006) provides the habeas data mechanism in article 23, addresses the systematisation of personal-data files and access to them in article 24, and restricts disclosure of confidential personal information in article 25. Its obligations bind public sujetos obligados, and the IAIP supervises them; it is not a private-sector marketing statute.
Law / regulation
No comprehensive personal-data-protection law was verified in force in Honduras in the sources reviewed on 17 August 2026. Successive bills have been presented to the Congreso Nacional, including a personal-data-protection bill presented on 29 April 2026 by deputy Kritza Pérez, but no enacted decree with a La Gaceta publication was identified. Pending legislative activity is context only and creates no obligation. Treat this as a dated source-review conclusion and re-check before relying on it in a compliance memo.
Law / regulation
Because no general statute is in force, Honduran law reviewed here does not supply a statutory definition of marketing consent, a statutory objection or withdrawal right specific to direct marketing, statutory retention limits or a statutory controller-to-processor allocation of data-protection responsibility. No vendor-responsibility rule of that kind was identified.
Law / regulation
The Ley de Protección al Consumidor (Decreto 24-2008, published in La Gaceta on 7 July 2008 and reformed by Decreto 75-2024) protects consumers' right to truthful information in consumption relationships, and the operative Reglamento de la Ley de Protección al Consumidor (Acuerdo 084-2021) set out the information, advertising and offer rules: promotion, contest and offer conditions must be presented accurately, completely and without misleading the consumer in the medium used. The 2009 regulation previously cited is superseded, and no specific article numbers are quoted here because they could not be confirmed from a clean official text of the 2021 instrument.
Law / regulation
Misleading advertising, publicidad engañosa, is expressly a groundable consumer complaint in CONATEL's user-protection regulation, and the Dirección General de Protección al Consumidor enforces the consumer statute. Specific article numbering inside Decreto 24-2008 itself for the general misleading-advertising prohibition could not be confirmed from a clean official text in the review for this page, so it is not quoted here.
Law / regulation
CONATEL's Reglamento de Protección al Usuario (Resolución NR001/26, 28 February 2026) requires an operator to notify a user of an impending suspension for non-payment by one SMS and/or call, during office hours on business days only, one day before suspension. That is a narrow operator billing-notice rule and is not a general marketing-hours rule for A2P senders.
Law / regulation
The Ley sobre Comercio Electrónico (Decreto 149-2014, in force from 27 February 2015) defines electronic communications broadly, but no provision on unsolicited commercial electronic communications, sender identification or opt-out was confirmed in the portion reviewed for this page, so none is claimed either way.
Law / regulation
No officially established national SMS do-not-call or do-not-disturb registry was identified in the CONATEL normativa index or the Ley Marco del Sector de Telecomunicaciones reviewed on 17 August 2026. This is a dated source-review conclusion, not proof that none could exist, and it should be confirmed with CONATEL if it is decision-critical for your programme.
Law / regulation
No statutory quiet hours for marketing SMS and no mandatory statutory STOP keyword were identified in Honduran law in the sources reviewed on 17 August 2026.
Law / regulation
An OTP or an expected service message is not automatically marketing. Equally, marketing must not be relabelled as transactional: the test is the purpose of the message and what the recipient was told when the number was collected, not the template it is sent from.
Carrier or route policy
The provider's own Honduras guidance asks customers to obtain opt-in consent before communicating, particularly for marketing, to message during the recipient's daytime hours unless urgent, to support HELP and STOP style messages in the recipient's local language, and not to contact end users on do-not-call or do-not-disturb registries. That is provider policy, enforceable by the provider, not Honduran statute.
Flowstates recommendation
Capture promotional permission as prior express, attributable, purpose-specific and SMS-channel-specific, and keep the evidence: recipient, timestamp, source, exact wording and version shown at capture, purpose, channel and the privacy notice presented.
Flowstates recommendation
Publish and link a privacy notice that a Honduran recipient can actually reach from the journey where the number was collected, even though no statute reviewed here mandates its content.
Flowstates recommendation
Offer an opt-out that is free and simple and that does not depend on a reply, because the current route is one-way.
Flowstates recommendation
Recognise natural Spanish opt-out requests such as BAJA, SALIR, CANCELAR, NO and STOP wherever a reply path or another inbound channel exists. None of these is a statutory Honduran keyword; treat them as recipient intent to be honoured.
Flowstates recommendation
Suppress immediately across every list, sender and sending system. That is our own operating standard, and in Honduras there is no statutory deadline sitting behind it.
Flowstates recommendation
Send promotional traffic in recipient-local daytime hours as our operating standard, not as an invented statutory window.
Flowstates recommendation
Do not use purchased or rented lists, and do not accept a list vendor's claim of registry screening as meaningful in a market where no national SMS registry was identified.
Flowstates recommendation
Take Honduran legal advice on marketing programmes and on any personal-data commitments you make contractually, especially while a comprehensive data-protection bill is pending.
Carrier or route policy
Sender rewriting, the absence of two-way SMS, conditional concatenation, UCS-2 handling, MMS conversion and landline rejection are route policy. None of them are Honduran law, and complying with one says nothing about the other.

Operational compliance checklist

The controls we expect to see before Honduran traffic goes into production, and the records we expect you to be able to produce afterwards.

Law / regulation
Store destinations as +504 followed by the eight national digits.
Law / regulation
Treat the 3, 7, 8 and 9 series as mobile, the 2 series as fixed line, and three-digit or 1XY codes as service codes rather than A2P destinations.
Law / regulation
Keep promotional claims, conditions and duration accurate and complete in the message and on the landing page, in line with the consumer statute and its Reglamento.
Law / regulation
Do not describe Honduras internally as a comprehensive data-protection jurisdiction, and re-check the status of the pending bill before making contractual commitments that assume one.
Flowstates recommendation
Audit legacy seven-digit Honduran records and repair or retire them before they reach a sending queue.
Flowstates recommendation
Filter fixed-line and service numbers out of A2P mobile campaigns before submission.
Flowstates recommendation
Resolve the live destination network with a lookup or supplier routing intelligence rather than inferring it from the leading digit, because mobile portability is live.
Flowstates recommendation
Preregister the alphanumeric sender you intend to use, and confirm it covers the Claro path where alphanumeric senders require preregistration.
Flowstates recommendation
Confirm the actual visible sender, and the fallback behaviour, on the contracted route before launch.
Flowstates recommendation
Identify the sending brand and the purpose inside the message body.
Flowstates recommendation
Keep critical OTP and service copy inside a single segment where practical, and verify the real segment count on the exact route.
Flowstates recommendation
Do not build any flow that depends on the recipient replying while the route is one-way.
Flowstates recommendation
Keep OTP, service and marketing purposes, templates and permission records separate.
Flowstates recommendation
Offer a free, non-reply opt-out in promotional messages and suppress immediately across every sending system.
Flowstates recommendation
Honour BAJA, SALIR, CANCELAR, NO and STOP as opt-out intent on any inbound channel you do operate.
Flowstates recommendation
Do not use purchased or rented lists.
Flowstates recommendation
Use branded short domains rather than public or shared shorteners.
Flowstates recommendation
Test sender preservation and rewriting, UCS-2 handling, concatenation behaviour and MMS conversion on the exact contracted route.
Flowstates recommendation
Monitor delivery, latency, filtering and completed-verification conversion per route and per operator, with carrier-grade failover configured.
Flowstates recommendation
Keep evidence of templates, notices, permission, route approval, opt-outs and suppression.
Flowstates recommendation
Get Honduran legal review for marketing programmes and for any data-handling commitments.

Encoding and delivery

Segment maths, Spanish-language traps and what to test on the real route before launch.

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
E.164 example: +504 3XXX XXXX / +504 7XXX XXXX / +504 8XXX XXXX / +504 9XXX XXXX

Carrier or route policy
Twilio marks concatenation as supported with a caveat on its current Honduras route: it may not be supported for certain sender ID types, and where messages are split and rejoined can vary with character encoding.
Carrier or route policy
UCS-2 is marked supported for the preregistered alphanumeric sender type, and no UCS-2 value is published for dynamic alphanumeric, domestic long code, international long code or short code.
Flowstates recommendation
Spanish copy does not automatically force UCS-2. ñ, ¿, ¡ and é are in the basic GSM-7 alphabet, but á, í, ó, ú, curly quotation marks, pasted formatting and emoji can force UCS-2 and cut your segment from 160 characters to 70.
Flowstates recommendation
Because the concatenation caveat depends on sender type and encoding, test your real Spanish copy and its real segment count on the exact sender and route you will use, not in a generic calculator.
Flowstates recommendation
Keep critical OTP and service messages in a single segment wherever practical. Do not treat a provider's maximum segment count as a copywriting target.
Carrier or route policy
MMS is converted into an SMS with an embedded URL on that provider's route, so design for text and a link rather than an image.
Law / regulation
Honduran national significant numbers are eight digits under a closed plan, so E.164 normalisation is simply +504 plus those eight digits.

A country guide is only useful when the route follows it.

Country rules only help if the route your traffic actually takes respects them. That is the part we operate.

Per-country and per-category routing
Multi-vendor routing decided per country and per traffic category, so OTP, service and marketing traffic into Honduras do not share one compromise route.
SenderID management
We manage sender presentation per route, per category and per operator path, including preregistered alphanumeric senders and the Claro preregistration requirement, and we check what the recipient actually sees before launch.
Carrier-grade failover
Automatic failover between vendors, with fallback senders that are themselves valid for Honduras rather than a route that quietly substitutes a local long code or short code.
Per-route visibility
Delivery, latency and OTP-completion visibility per route, so a quality change on one Honduran operator path is visible while it is still small.
24/7 vendor escalation
We chase the vendor. Escalation runs around the clock rather than waiting for a support queue in another time zone.
BYOV / BYOG
Bring your own vendors or gateway and keep your commercial relationships while we operate the routing, sender policy and monitoring.
Branded short links
Branded short domains instead of public shorteners, so Honduran recipients see a link that matches the brand in the message body.

Developer docs Branded short links

What we need to validate your Honduras route

Send us these and we can tell you what your Honduran traffic will actually do, per operator path, before you commit to a launch date.

Your legal entity and the website the traffic relates to
Traffic categories in scope: OTP, transactional, marketing
Sample message templates in the real English and Spanish copy you will send
Monthly volume by category and your expected peak sending rate
Sender presentation you want, and whether you can preregister an alphanumeric sender
Promotional permission journey, supporting evidence and the exact disclosure wording
How the numbers were collected and where the data came from, plus your privacy notice URL
Your internal opt-out and suppression process and the person who owns it
Link domains you intend to use
Whether you need replies or two-way messaging
Whether any message exceeds a single segment, and any Unicode or accented-character requirements
Target launch date

Validate my Honduras route Book a messaging review

Frequently asked questions about SMS in Honduras

Can I send SMS to mobile numbers in Honduras?

A quick operational read on Honduras. Anything marked route-dependent is decided by the supplier and operator path your traffic uses. Anything marked law applies whichever supplier you pick. Number format: +504 followed by an eight-digit national significant number; Honduras runs a closed eight-digit plan, and no domestic trunk prefix was found in the CONATEL material reviewed. Mobile numbering: CONATEL numbering-assignment resolutions place mobile and PCS service in the 3, 7, 8 and 9 leading-digit series, structured WXYZ-MCDU. Fixed-line numbering: Geographic fixed-line numbers use the 2 series, following the November 2010 migration from seven to eight digits. Short and service codes: Three-digit and 1XY short codes are allocated individually by CONATEL and consolidated under its Códigos de Numeración Corta regulation; they are not A2P destinations.

Which sender ID options work for SMS in Honduras?

Sender presentation in Honduras is decided by the selected route and the destination network. Preregistered alphanumeric sender — Best for: Any brand-visible OTP, service or promotional traffic, and the only option that works towards Claro where alphanumeric senders are supported through preregistration only. Dynamic alphanumeric sender — Best for: Not recommended; included because traffic often defaults into it when no preregistration exists. International numeric sender (international long code) — Best for: Traffic that must terminate while a preregistered alphanumeric sender is not yet available on the selected path. Domestic long code — Best for: Nothing on the current route; included so teams stop designing around a local subscriber origin that the networks do not accept.

What are the consent and opt-out requirements for SMS in Honduras?

Honduras is not a comprehensive data-protection jurisdiction today. Article 76 of the Constitution guarantees the right to honour, to personal and family privacy and to one's own image. Article 100 of the Constitution protects the inviolability and secrecy of communications, expressly including telephone communications, save by judicial decision. Its text addresses communications secrecy rather than commercial use of contact data. Habeas data was introduced by Decreto Legislativo 381-2005 and consolidated by Decreto Legislativo 10-2013, which reformed article 182 so that a person whose personal or family data appears in public or private records can bring the action; it is procedurally implemented through the Ley sobre Justicia Constitucional.

How many characters fit in an SMS to Honduras?

Segment maths, Spanish-language traps and what to test on the real route before launch. 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

Official Honduran sources control the law and numbering statements on this page. Provider sources describe only their own current route. Where a provider page conflicts with CONATEL, we follow CONATEL and say so.

Provider route policy
Twilio — Honduras SMS guidelines
Controls every route statement here: mobile country code 708 and dialling code +504, two-way SMS not supported, number portability available, concatenation supported with a sender-type and encoding caveat, MMS converted to SMS with an embedded URL, SMS to Honduran landline destinations rejected rather than delivered, alphanumeric preregistration supported by the operator networks with no segregation between international and domestic traffic and the sender preserved, dynamic alphanumeric senders unsupported by the networks and possibly overwritten with a local long code or short code outside the platform, alphanumeric senders towards Claro supported only through preregistration, domestic long codes unsupported, international long codes supported but not preserved, no short-code capability or support value published, and UCS-2 supported for the preregistered alphanumeric sender type. This is that supplier's current route position, not Honduran law.
Official numbering and regulation
CONATEL — Normativas y Regulaciones archive
The regulator's resolution archive. Controls the numbering statements here: the eight-digit WXYZ-MCDU mobile structure adopted in 2008, the fixed-line migration from seven to eight digits, the 801-0000 to 899-9999 mobile and PCS block attributed in 2006, the earlier 96x, 97x and 98x mobile assignments, and the individual short-code allocations. CONATEL does not publish a single consolidated current prefix-to-operator table in this archive, which is why none is reproduced here.
Regulation
CONATEL — Reglamento de Portabilidad Numérica para el Servicio de Telefonía Móvil (NR012/13)
Resolución NR012/13 of 16 August 2013. Controls the statement that number portability in Honduras covers mobile cellular and PCS service, and that its recitals record fixed telephony as expressly excluded at that time.
Regulation
CONATEL — Modificaciones al Reglamento de Portabilidad Numérica (NR010/17)
The 2017 amendment, published in La Gaceta on 19 January 2018, removing restrictive elements from the portability process. The regime title and scope remain mobile only.
Regulation
CONATEL — Códigos de Numeración Corta (NR010/22)
The consolidated short-code regulation of 17 December 2022 covering mobile and fixed telephony. Cited for the statement that three-digit and 1XY codes are allocated by the regulator and are not A2P subscriber destinations.
Regulator
CONATEL — regulator home
Institutional home of the telecommunications regulator, including the free 185 consumer line referenced here. Cited for institutional context rather than for any legal wording.
Secondary numbering reference
ITU — National Numbering Plans, Honduras
The ITU country entry for the Honduran national numbering plan, listing plan documents posted on 30 November 2010. Used only as a secondary authoritative locator. Where it differs from current CONATEL material, CONATEL controls.
Constitution
Constitución de la República de Honduras (Decreto 131 de 1982)
Controls the constitutional statements here: article 76 on honour and personal and family privacy, article 100 on the inviolability and secrecy of communications including telephone communications, and the habeas data guarantee in article 182 as reformed by Decreto Legislativo 10-2013 after Decreto Legislativo 381-2005. Confirm against the current consolidated text before citing article 182 to a counterparty.
Statute
Ley de Transparencia y Acceso a la Información Pública (Decreto 170-2006)
Controls the statements on the habeas data mechanism in article 23, personal-data files and access in article 24 and the restriction on disclosing confidential personal information in article 25. This statute binds public sujetos obligados and is not a private-sector marketing law.
Statute
Ley de Protección al Consumidor (Decreto 24-2008) — official library entry
The consumer statute published in La Gaceta on 7 July 2008 and reformed by Decreto 75-2024. It controls only the duty to give consumers accurate, complete and non-misleading information about promotions and offers. Article numbering is not quoted because it could not be confirmed from a clean official text.
Regulation
Reglamento de la Ley de Protección al Consumidor (Acuerdo 084-2021) — official library entry
The 2021 regulation is the operative implementing instrument for the consumer statute and supersedes the 2009 regulation, which is no longer cited as controlling on this page. Used only for the accurate, complete and non-misleading promotion and offer information duty; no article numbers are quoted.
Statute
Ley Marco del Sector de Telecomunicaciones (Decreto 185-95)
The framework statute under which CONATEL administers numbering, portability and user protection. Reviewed for any unsolicited-commercial-message or do-not-contact provision; none was identified, which is why no national SMS registry is claimed on this page.
Statute
Ley sobre Comercio Electrónico (Decreto 149-2014)
In force from 27 February 2015. Reviewed for provisions on unsolicited commercial electronic communications, sender identification and opt-out; none was confirmed in the portion reviewed, so no claim is made in either direction.
Statute
Ley sobre Firmas Electrónicas (2013)
Published in La Gaceta on 11 December 2013. Cited only to record that it governs the validity and evidentiary value of electronic signatures and does not supply a marketing consent or opt-out rule.
Regulator
IAIP — Instituto de Acceso a la Información Pública
The transparency authority supervising Decreto 170-2006 and habeas data claims against public entities. Cited to make clear it has no general mandate over private A2P SMS marketing.

Change log

17 August 2026 — Editorial audit; corrected the pending personal-data-protection bill to the 29 April 2026 initiative, replaced the superseded 2009 consumer regulation with the operative Acuerdo 084-2021 and removed provider API error, log and billing detail from the fixed-line route statements.
17 August 2026 — Initial publication; adopted CONATEL's closed eight-digit +504 plan with the 3, 7, 8 and 9 mobile series and the 2 fixed-line series, recorded number portability as mobile and PCS only under NR012/13 as amended by NR010/17, recorded that no comprehensive Honduran personal-data statute and no national SMS do-not-call registry were verified in force, and documented preregistered alphanumeric sender preservation, dynamic and international numeric sender rewriting, unsupported domestic long codes and one-way route behaviour as provider route policy.

Last reviewed 17 August 2026

Disclaimer

This page is operational guidance, not legal advice. Requirements vary by law, message purpose, sender, provider, carrier route, recipient context and customer setup, and they change. Flowstates confirms the live route with you during onboarding, and you should take your own Honduran legal advice on marketing and data-handling obligations.

Honduras SMS guide