Honduras SMS Best Practices, Compliance, and Features

SMS Market Overview in Honduras

Market Conditions: Honduras has a growing mobile market with widespread SMS usage, making it an essential channel for business communications. Three main operators serve the country's telecommunications sector:

• Tigo (Millicom): One of the largest mobile operators
• Claro (América Móvil): Major market presence
• Hondutel: State-owned telecommunications provider

While OTT messaging apps like WhatsApp are popular in urban areas, SMS remains crucial for business communications and reaching rural populations where data connectivity may be limited. SMS is particularly important for transactional messages, two-factor authentication, and reaching users across all demographics and geographic areas. Android devices dominate the mobile market due to their affordability and accessibility.

SMS Features and Capabilities for Honduras

Honduras supports basic SMS functionality with some limitations on sender ID preservation and two-way messaging capabilities.

Two-Way SMS Support

Most providers do not support two-way SMS in Honduras. Businesses can send messages to customers but cannot receive replies through the same channel.

Alternative Solutions for Two-Way Communication:

• Use dedicated short codes (if available and properly provisioned)
• Implement web-based response forms with unique tracking codes
• Direct users to WhatsApp Business for interactive communication
• Use email or app-based messaging for response collection
• Include unique URL links in SMS that lead to response forms

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messages work, though support may vary by sender ID type. Message length rules: Standard SMS length limits apply – 160 characters for GSM-7 encoding, 70 characters for UCS-2 encoding. Encoding considerations: Both GSM-7 and UCS-2 encodings work. Messages using special characters automatically use UCS-2 encoding, reducing the character limit per segment.

Cost Implications: Each segment of a concatenated message bills as a separate SMS. A 200-character message using GSM-7 encoding sends as 2 segments and bills accordingly. Plan message content carefully to minimize segments when cost optimization matters.

MMS Support

Honduras does not directly support MMS messages. Instead, MMS content automatically converts to SMS with an embedded URL link where recipients can view the multimedia content. This ensures compatibility while still allowing businesses to share rich media content with their audiences.

URL Conversion Details: When MMS content converts to SMS+URL, your SMS provider hosts the multimedia content. Recipients use their mobile data to access the content. Consider that this may incur data charges for recipients and ensure URLs are accessible without authentication where appropriate.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Honduras, allowing users to keep their phone numbers when switching carriers. This feature does not significantly impact SMS delivery or routing, as messages route properly to the current carrier.

Sending SMS to Landlines

Honduras does not support sending SMS to landline numbers. Attempts to send messages to landline numbers result in delivery failures, typically generating a 400 response error (error code 21614) from SMS APIs. These messages do not appear in logs, and accounts are not charged for failed attempts.

Number Format Patterns:

• Mobile numbers: 8 digits total (format: +504 XXXX-XXXX)
• Landline numbers: 8 digits total (format: +504 2XXX-XXXX, typically starting with 2 for landlines)
• Mobile numbers typically start with 3, 7, 8, or 9
• Validate numbers before sending using HLR (Home Location Register) lookups or carrier validation APIs

SMS Compliance and Regulations in Honduras

CONATEL (Comisión Nacional de Telecomunicaciones), the national telecommunications commission, oversees general telecommunications regulations in Honduras. While specific SMS marketing regulations are not as detailed as in some countries, businesses must adhere to general consumer protection and privacy principles.

Regulatory Framework: Honduras does not have comprehensive data protection legislation equivalent to GDPR, but businesses must comply with:

• General consumer protection principles under the Dirección General de Protección al Consumidor
• Industry best practices for data privacy and security
• Telecommunications regulations enforced by CONATEL (Comisión Nacional de Telecomunicaciones)

Source: CONATEL

Consent and Opt-In

Explicit Consent Requirements:

• Obtain clear, documented opt-in consent before sending marketing messages
• Maintain records of how and when you obtained consent
• Include company identification in initial opt-in messages
• Provide clear terms of service and privacy policy information

Best Practices for Consent:

• Use double opt-in processes for marketing lists
• Document consent timestamp, source, and IP address
• Store consent records securely for at least two years
• Run regular consent refresh campaigns for long-term subscribers

HELP/STOP and Other Commands

• Support STOP, CANCELAR, and AYUDA commands
• Handle messages in both Spanish and English
• Process opt-out requests immediately
• Send confirmation messages in the same language as the opt-out request

Compliance Note: HELP/STOP support is an industry best practice rather than explicit legal requirement in Honduras, but strongly recommended for customer satisfaction and compliance with general consumer protection principles.

Example Response Messages:

• STOP response: "Has sido removido de nuestra lista. No recibirás más mensajes. Reply START to resubscribe."
• HELP response: "Servicio de SMS de [Nombre de Empresa]. Para detener mensajes responda STOP. Más info: [URL]"
• Common Spanish opt-out terms to support: BAJA, DETENER, ALTO, PARAR, REMOVER

Do Not Call / Do Not Disturb Registries

Honduras does not maintain a centralized Do Not Call registry. However, businesses should:

• Maintain their own suppression lists
• Honor opt-out requests within 24 hours
• Regularly clean contact lists
• Implement internal do-not-contact databases

Time Zone Sensitivity

Honduras operates in the Central Time Zone (UTC-6):

• Restrict messaging to 8:00 AM – 8:00 PM local time
• Avoid sending during national holidays
• Send emergency messages outside these hours if necessary
• Consider business hours for B2B communications

Honduras National Holidays (avoid sending marketing SMS):

• January 1: New Year's Day
• April (varies): Holy Week (Thursday-Sunday)
• May 1: Labour Day
• September 15: Independence Day
• October 3: Francisco Morazán Day
• October 12: Columbus Day
• October 21: Army Day
• December 25: Christmas Day

Daylight Saving Time: Honduras does not observe daylight saving time; it remains at UTC-6 year-round.

Sender ID Options for SMS in Honduras

Alphanumeric Sender ID

Operator network capability: Supported but not preserved Registration requirements: No pre-registration required Sender ID preservation: No – carriers overwrite IDs with a numeric sender ID

What Replaces Alphanumeric IDs: Carriers typically replace alphanumeric sender IDs with a short numeric code (4-6 digits) or a random long number. The replacement ID may vary by carrier and is not predictable.

Brand Recognition Impact: Since carriers do not preserve sender IDs, include your company name in the first line of the message body (e.g., "YourBrand: Your verification code is…") to maintain brand recognition.

Long Codes

Domestic vs. International:

• Domestic long codes not supported
• International long codes supported but may be overwritten

Sender ID preservation: No – carriers do not preserve original sender IDs Provisioning time: Immediate to 24 hours Use cases: Transactional messages, alerts, and notifications

Short Codes

Support: Limited availability Provisioning time: 8-12 weeks Use cases:

• High-volume messaging campaigns
• Two-factor authentication
• Customer service communications

Short Code Registration Process:

1. Apply through your SMS provider or aggregator
2. Submit business documentation and use case details
3. Undergo carrier approval process (each carrier separately)
4. Complete technical integration and testing
5. Receive approval and begin sending

Cost and Volume Considerations:

• Setup fees: $500-$2,000 USD (varies by provider)
• Monthly recurring fees: $500-$1,500 USD
• Per-message costs: Higher than long codes but better deliverability
• Volume requirements: Typically 10,000+ messages/month to justify costs
• Best for: High-volume senders with established brands

Restricted Content and Industries for Honduras SMS

Restricted Industries:

• Gambling and betting services
• Adult content
• Cryptocurrency promotions
• Unauthorized financial services
• Political messaging without proper authorization

Political Messaging Authorization: Political campaigns must be authorized by registered political parties or candidates and should include proper identification of the sender and campaign. Contact CONATEL for specific political messaging requirements during election periods.

Penalties for Violations: While specific SMS-related penalties are not explicitly codified, violations may result in:

• Account suspension by SMS providers
• Complaints to CONATEL
• Consumer protection investigations
• Potential civil liability for damages
• Reputational harm and reduced deliverability

Content Filtering

Known Carrier Rules:

• URLs must be from approved domains
• No excessive punctuation or special characters
• Maximum of 3 consecutive messages per recipient
• No misleading sender information

Domain Approval: Contact your SMS provider to submit domains for approval. Well-known domains (google.com, microsoft.com, established brands) are typically pre-approved. Custom domains may require verification of ownership and intended use.

Excessive Punctuation Examples (likely to be filtered):

• Multiple exclamation marks: "Great deal!!!!"
• Repeated special characters: "$$$$ Save money $$$$"
• ALL CAPS WITH MANY PUNCTUATION MARKS!!!!
• Mixed excessive symbols: ">>>CLICK HERE<<<"

Tips to Avoid Blocking:

• Use clear, consistent sender IDs
• Avoid URL shorteners
• Maintain consistent sending patterns
• Include clear opt-out instructions

Best Practices for SMS Campaigns in Honduras

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Use personalization tokens thoughtfully
• Maintain consistent branding

Sending Frequency and Timing

• Limit to 3-4 messages per week per recipient
• Respect local holidays and cultural events
• Schedule campaigns during business hours
• Space out bulk sends to avoid network congestion

Frequency Rationale: The 3-4 messages/week recommendation is based on industry research showing optimal engagement without subscriber fatigue. Monitor your specific opt-out rates and adjust accordingly.

Network Congestion: Network congestion manifests as delayed delivery times or temporary failures during peak hours (typically 8-10 AM and 5-7 PM local time). Spread bulk campaigns over several hours and monitor delivery reports for unusually long delivery times (>5 minutes).

Language and Localization for Honduras SMS

• Primary language: Spanish
• Consider regional dialects and expressions
• Avoid automated translations
• Test messages with local users

Honduran Spanish Considerations:

• Use "vos" (informal you) instead of "tú" in casual contexts
• Common terms: "¿Qué onda?" (What's up?), "va pues" (okay/alright)
• Avoid overly formal European Spanish constructions
• Use Latin American Spanish date formats (DD/MM/YYYY)

Character Encoding: Use GSM-7 encoding when possible. Spanish characters á, é, í, ó, ú, ñ, ü are included in GSM-7. Avoid emoji and special symbols that force UCS-2 encoding (reduces character limit from 160 to 70 per segment).

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain centralized opt-out database
• Clean and validate lists regularly
• Include clear opt-out instructions in every message

SMS Testing and Performance Monitoring

• Test across major carriers (Tigo, Claro)
• Monitor delivery rates by carrier
• Track engagement metrics
• Run regular A/B tests of message content

Key Metrics and Benchmarks:

• Delivery rate: Target >95% (Honduras typically 92-97%)
• Delivery time: Target <30 seconds for 90% of messages
• Opt-out rate: Acceptable <0.5% per campaign
• Bounce rate: Target <2%

Troubleshooting Low Delivery Rates:

1. Check for carrier-specific issues (test each carrier separately)
2. Verify phone number formatting (E.164 format required)
3. Review message content for filtering triggers
4. Confirm sender ID configuration
5. Check account balance and rate limits
6. Contact provider support with message IDs for investigation

SMS API Integration for Honduras

Twilio

Twilio provides a robust SMS API with comprehensive documentation and TypeScript support. Authenticate using your Account SID and Auth Token.

import { Twilio } from 'twilio';

// Initialize the client with your credentials
const client = new Twilio(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN);

// Function to send SMS to Honduras
async function sendSMSToHonduras(
  to: string,
  message: string
): Promise<void> {
  try {
    // Ensure number is in E.164 format for Honduras (+504)
    const formattedNumber = to.startsWith('+504') ? to : `+504${to}`;

    const response = await client.messages.create({
      body: message,
      to: formattedNumber,
      from: process.env.TWILIO_PHONE_NUMBER,
      // Optional: statusCallback URL for delivery updates
      statusCallback: 'https://your-webhook.com/status'
    });

    console.log(`Message sent successfully! SID: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
  }
}

Phone Number Validation Enhancement: For production use, implement full validation including:

• Length check (must be 8 digits after country code)
• Mobile prefix validation (should start with 3, 7, 8, or 9)
• Consider using Twilio Lookup API for real-time validation

Twilio Honduras Features: Twilio supports Honduras with international long codes. Pricing varies by destination carrier; check Twilio pricing for current rates. Typical range: $0.04-$0.10 per SMS segment.

Sinch

Sinch offers a straightforward API for SMS integration with Honduras, featuring detailed delivery reporting.

import { SinchClient } from '@sinch/sdk';

// Initialize Sinch client
const sinchClient = new SinchClient({
  apiKey: process.env.SINCH_API_KEY,
  apiSecret: process.env.SINCH_API_SECRET
});

// Send SMS function with typing
async function sendSinchSMS(
  phoneNumber: string,
  messageText: string
): Promise<void> {
  try {
    const response = await sinchClient.sms.send({
      to: phoneNumber,
      message: messageText,
      // Optional parameters
      deliveryReport: 'summary',
      expiry: '24h'
    });

    console.log('Message batch ID:', response.batchId);
  } catch (error) {
    console.error('Sinch SMS error:', error);
  }
}

MessageBird

MessageBird provides a reliable API with strong delivery rates in Honduras.

import { MessageBird } from 'messagebird';

// Initialize MessageBird client
const messagebird = MessageBird(process.env.MESSAGEBIRD_API_KEY);

// Type definition for response handling
interface MessageResponse {
  id: string;
  status: string;
  recipient: string;
}

// Send SMS function
async function sendMessageBirdSMS(
  recipient: string,
  content: string
): Promise<MessageResponse> {
  return new Promise((resolve, reject) => {
    messagebird.messages.create({
      originator: 'YourBrand',
      recipients: [recipient],
      body: content,
      datacoding: 'auto' // Automatically handles character encoding
    }, (err, response) => {
      if (err) {
        reject(err);
        return;
      }
      resolve(response);
    });
  });
}

Plivo

Plivo offers competitive rates and reliable delivery to Honduras.

import { Client } from 'plivo';

// Initialize Plivo client
const plivo = new Client(
  process.env.PLIVO_AUTH_ID,
  process.env.PLIVO_AUTH_TOKEN
);

// Send SMS with error handling
async function sendPlivoSMS(
  destination: string,
  message: string
): Promise<void> {
  try {
    const response = await plivo.messages.create({
      src: process.env.PLIVO_PHONE_NUMBER, // Your Plivo number
      dst: destination,
      text: message,
      // Optional parameters
      url: 'https://your-webhook.com/delivery-status',
      method: 'POST'
    });

    console.log('Message sent:', response.messageUuid);
  } catch (error) {
    console.error('Plivo error:', error);
  }
}

API Rate Limits and Throughput

• Twilio: 250 messages per second
• Sinch: 100 messages per second
• MessageBird: 150 messages per second
• Plivo: 200 messages per second

Strategies for Large-Scale Sending:

• Implement queue systems (Redis/RabbitMQ)
• Use batch APIs when available
• Monitor throughput and adjust sending rates
• Implement exponential backoff for retries

Error Handling and Reporting

// Common error handling implementation
interface SMSError {
  code: string;
  message: string;
  timestamp: Date;
}

class SMSLogger {
  static logError(error: SMSError): void {
    // Log to monitoring system
    console.error(`
      Error Code: ${error.code}
      Message: ${error.message}
      Time: ${error.timestamp}
    `);
  }

  static async retryWithBackoff(
    fn: () => Promise<any>,
    maxRetries: number = 3
  ): Promise<any> {
    for (let i = 0; i < maxRetries; i++) {
      try {
        return await fn();
      } catch (error) {
        if (i === maxRetries - 1) throw error;
        await new Promise(res => setTimeout(res, Math.pow(2, i) * 1000));
      }
    }
  }
}

Common Error Codes:

• 21211: Invalid phone number format → Verify E.164 formatting
• 21408: Permission denied → Check account permissions and compliance
• 21610: Unsubscribed recipient → Remove from send list
• 21614: Invalid mobile number (landline) → Validate as mobile before sending
• 30003: Unreachable destination → Number may be inactive/invalid
• 30006: Landline or unreachable carrier → Use HLR lookup to verify
• 30007: Message filtered/blocked → Review content for spam triggers

Monitoring Integration: Consider integrating with:

• Sentry or Datadog for error tracking
• PagerDuty for critical delivery failures
• Custom webhooks for delivery status callbacks
• Prometheus/Grafana for delivery metrics visualization

Recap and Additional Resources

Key Takeaways

1. Always format numbers in E.164 format (+504)
2. Implement proper error handling and retry logic
3. Monitor delivery rates and adjust sending patterns
4. Maintain compliance with local regulations
5. Use appropriate character encoding for Spanish language

Next Steps

1. Technical Setup

   • Choose an SMS provider based on your needs
   • Implement proper error handling
   • Set up monitoring and alerting

2. Compliance

   • Review CONATEL regulations
   • Implement opt-out handling
   • Document consent collection

3. Testing

   • Test with major Honduras carriers
   • Verify delivery rates
   • Monitor costs and optimization opportunities

Additional Information:

• CONATEL (Honduras Telecom Regulator): www.conatel.gob.hn
• Honduras Consumer Protection: www.protecciondelconsumidor.gob.hn
• Industry Guidelines: Mobile Marketing Association LATAM