How to Send SMS in Nicaragua: TELCOR Compliance & API Integration Guide (2025)

Send SMS messages to Nicaragua by following TELCOR telecommunications regulations, understanding Claro and Tigo carrier requirements, and properly formatting +505 phone numbers. This comprehensive guide covers Nicaragua SMS compliance under Law No. 1223 (effective 2025), step-by-step API integration with Twilio, Sinch, MessageBird, and Plivo, plus proven best practices for reaching Nicaragua's 8-digit mobile numbers with high delivery rates.

Nicaragua SMS Market Overview and Carrier Landscape

Market Conditions: Nicaragua's mobile market shows moderate SMS usage, with growing preference for OTT messaging apps like WhatsApp and Facebook Messenger. For businesses needing to send SMS internationally or implement two-factor authentication via SMS, understanding Nicaragua's unique market dynamics is essential. Tigo (Millicom) leads with 53% market preference, while Claro (América Móvil) holds 46% as of 2024. Tigo acquired Telefónica's Movistar operations in May 2019 for $430 million, adding approximately 4 million mobile subscribers. A third operator, CooTel (Xinwei Nicaragua), launched in 2016 but remains a minor player using a proprietary non-SIM card system. SMS remains critical for business communications, notifications, and authentication – especially in areas with limited internet connectivity.

Phone Number Structure: Nicaragua uses a closed 8-digit numbering plan established in 2009. Mobile numbers use prefixes 5, 7, or 8 (format: [5|7|8]XXXXXXX), while landlines start with 2 (format: 2XXXXXXX). Emergency numbers include 118 (Police), 115/911 (Fire), and 128 (Ambulance). Toll-free numbers follow the format 1800XXXX.

Regulatory Framework: TELCOR (Instituto Nicaragüense de Telecomunicaciones y Correos) oversees telecommunications. Nicaragua's National Assembly approved the General Law on Convergent Telecommunications (Law No. 1223) on October 31, 2024, effective November 2025. This law grants TELCOR expanded powers, introduces 10–20 year licenses, and establishes a digital inclusion fund. Businesses should also review SMS compliance requirements for other Latin American markets.

Equipment Certification (Effective 2025): Law No. 1223 requires telecommunications equipment sold in Nicaragua to display labels certifying compliance with national regulations. TELCOR will publish specific labeling requirements throughout 2025. Equipment type approval requires acceptable CE reports.

SMS Messaging Features and Technical Capabilities

Nicaragua supports basic SMS functionality with limitations on advanced features. Plan your messaging strategy around one-way communications and standard message lengths.

Does Nicaragua Support Two-Way SMS?

Nicaragua does not support two-way SMS through standard API providers. Send messages one-way from your business to consumers only. Design your messaging strategies around this limitation and provide alternative channels for customer responses:

• Email addresses for detailed inquiries
• Web forms for structured feedback
• App notifications with in-app response options
• QR codes linking to response portals

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messages work, though availability varies by sender ID type.

Message length rules: Standard 160 characters for GSM-7 encoding before splitting. Messages using UCS-2 encoding split at 70 characters.

Encoding considerations: Use GSM-7 for optimal message length and cost efficiency.

MMS Support

Nicaragua does not support MMS messages directly. When you attempt to send MMS, carriers automatically convert it to SMS with an embedded URL where recipients can view the media content.

Recipient Phone Number Compatibility

Number Portability

Number portability is not implemented in Nicaragua. A 2023 feasibility study recommended the All Call Query technique for future implementation. Mobile numbers remain tied to their original carrier. The three main carriers operate on these prefixes:

• Claro: Prefixes 7 and 8
• Tigo (formerly Movistar): Prefixes 5 and 7
• CooTel: Limited availability, proprietary system

Sending SMS to Landlines

You cannot send SMS to landline numbers in Nicaragua. Attempts fail with a 400 response error (code 21614) from SMS API providers, with no charges incurred.

Phone Number Validation: Validate Nicaragua phone numbers before sending using these regex patterns:

• Landline: /^2\d{7}$/ (8 digits starting with 2)
• Mobile: /^[578]\d{7}$/ (8 digits starting with 5, 7, or 8)
• Full international format: /^\+505[2578]\d{7}$/

Note: Nicaragua transitioned from 7-digit to 8-digit numbering in 2009. Mobile numbers added prefix digits (5, 7, 8), while landlines added prefix 2.

Nicaragua SMS Compliance: TELCOR Regulations and Legal Requirements

Nicaragua does not have specific SMS marketing legislation. Follow telecommunications regulations overseen by TELCOR (Instituto Nicaragüense de Telecomunicaciones y Correos). The General Law on Convergent Telecommunications (Law No. 1223), approved October 31, 2024 and effective November 2025, expands TELCOR's regulatory authority.

SMS Compliance Checklist for Nicaragua

✓ Obtain explicit consent before sending marketing messages ✓ Maintain detailed records of consent with timestamps ✓ Include opt-out instructions in every message ✓ Honor opt-out requests within 24 hours ✓ Store consent records with source and date ✓ Maintain suppression list of opted-out numbers ✓ Send during recommended hours (8 AM – 8 PM local time) ✓ Validate phone numbers before sending ✓ Monitor delivery rates and adjust strategy

Consent and Opt-In

Explicit Consent Requirements:

• Obtain clear, documented opt-in consent before sending marketing messages
• Maintain detailed records of when and how you obtained consent
• Include terms of service and privacy policy information during opt-in
• Specify message frequency and content type during opt-in

Best Practices for Documentation:

• Store consent records with timestamp and source
• Maintain audit trails of opt-in methods
• Regularly update and verify consent status
• Implement double opt-in for marketing campaigns

HELP/STOP and Other Commands

Support these standard opt-out keywords:

• STOP, CANCELAR, NO
• AYUDA, HELP

Process messages in both Spanish and English. Include opt-out instructions in Spanish: "Envía STOP para cancelar." Respond to HELP/AYUDA requests with service information in Spanish.

Do Not Call / Do Not Disturb Registries

Nicaragua does not maintain an official Do Not Call registry. Implement these practices:

• Maintain your own suppression lists
• Honor opt-out requests within 24 hours
• Keep records of opted-out numbers
• Clean contact lists regularly

Time Zone Sensitivity

Nicaragua operates in Central Time (UTC-6).

• Recommended Sending Window: 8 AM – 8 PM local time
• Avoid Sending: Sundays and national holidays unless urgent
• Emergency Messages: Send 24/7 for critical notifications

Nicaragua Phone Number Format and Sender ID Options

Alphanumeric Sender ID

Operator network capability: Supported Registration requirements: Pre-registration not required Sender ID preservation: No – Carriers overwrite sender IDs with short codes

Practical behavior: When you send a message with alphanumeric sender ID "YourBrand," recipients see a numeric short code instead (e.g., "1234"). This affects brand recognition. Include your brand name in the message body to maintain identity.

Choosing Your Sender Type

Use this decision tree:

1. Need brand recognition? → Use alphanumeric sender ID + include brand name in message body
2. Sending transactional messages? → Use international long code (expect overwriting)
3. Sending OTP/2FA? → Use international long code
4. High-volume campaigns? → Use alphanumeric sender ID with brand in message

Long Codes

Domestic vs. International:

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

Sender ID preservation: No – Numbers are overwritten with short codes Provisioning time: Immediate Use cases:

• Transactional messages
• Two-factor authentication
• Customer service communications

Short Codes

Support: Not currently supported in Nicaragua Provisioning time: N/A Use cases: N/A

SMS Content Restrictions and Prohibited Industries in Nicaragua

Prohibited Content:

• Gambling and betting services
• Adult content or explicit material
• Illegal products or services
• Cryptocurrency promotions
• Political campaign messages without proper authorization

Regulated Industries:

• Financial services require clear sender identification
• Healthcare messages must maintain patient privacy
• Educational institutions need explicit student consent

Content Filtering

Known Carrier Filters:

• URLs from unknown domains
• Multiple exclamation marks
• ALL CAPS messages
• Excessive special characters

Best Practices to Avoid Filtering:

• Use clear, professional language
• Avoid URL shorteners
• Limit special characters and emojis
• Maintain consistent sending patterns

Consequences of Filtering: Messages that trigger carrier filters may be blocked without delivery notification. You'll see reduced delivery rates but won't receive specific error codes. Repeated filtering may result in sender reputation damage, affecting future delivery rates across campaigns.

Best Practices for High-Delivery SMS Campaigns in Nicaragua

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear calls-to-action
• Personalize messages with recipient's name
• Use a consistent sender ID

Sending Frequency and Timing

• Limit to 2–3 messages per week per recipient
• Respect local holidays and cultural events
• Maintain consistent sending schedules
• Allow at least 24 hours between marketing messages

Localization

• Primary language: Spanish
• Use formal Spanish ("usted" instead of "tú")
• Include both Spanish and English for international services
• Consider local cultural context and expressions

Opt-Out Management

• Process opt-outs within 24 hours
• Send confirmation of opt-out completion
• Maintain centralized opt-out database
• Regular audit of opt-out list compliance

Testing and Monitoring

• Test across Claro and Tigo networks (CooTel uses proprietary system)
• Monitor delivery rates by carrier
• Track opt-out rates and patterns
• Regular testing of opt-out functionality
• Validate phone number format before API calls to reduce errors

SMS API Integration: Twilio, Sinch, MessageBird & Plivo Code Examples

API Provider Comparison

Twilio

Twilio provides robust SMS API support for Nicaragua:

import { Twilio } from 'twilio';

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

// Send SMS to Nicaragua
async function sendSMSToNicaragua(
  to: string,
  message: string
): Promise<void> {
  try {
    // Validate Nicaragua mobile number format
    const mobilePattern = /^[578]\d{7}$/;
    const cleanNumber = to.replace(/\D/g, '').slice(-8);

    if (!mobilePattern.test(cleanNumber)) {
      throw new Error('Invalid Nicaragua mobile number format. Must be 8 digits starting with 5, 7, or 8.');
    }

    // Format with +505 country code
    const formattedNumber = to.startsWith('+505') ? to : `+505${cleanNumber}`;

    const response = await client.messages.create({
      body: message,
      to: formattedNumber,
      from: process.env.TWILIO_PHONE_NUMBER,
      statusCallback: 'https://your-callback-url.com/status'
    });

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

Sinch

Sinch offers direct carrier connections in Nicaragua:

import axios from 'axios';

class SinchSMSClient {
  private readonly baseUrl: string;
  private readonly apiToken: string;

  constructor(apiToken: string) {
    this.baseUrl = 'https://sms.api.sinch.com/xms/v1';
    this.apiToken = apiToken;
  }

  async sendSMS(to: string, message: string): Promise<void> {
    try {
      const response = await axios.post(
        `${this.baseUrl}/batches`,
        {
          from: 'YourSenderID',
          to: [to],
          body: message
        },
        {
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Content-Type': 'application/json'
          }
        }
      );

      console.log('Message sent:', response.data.id);
    } catch (error) {
      console.error('Sinch SMS error:', error);
      throw error;
    }
  }
}

MessageBird

MessageBird provides reliable SMS delivery to Nicaragua:

import { MessageBird } from 'messagebird';

class MessageBirdClient {
  private client: MessageBird;

  constructor(apiKey: string) {
    this.client = new MessageBird(apiKey);
  }

  sendSMS(to: string, message: string): Promise<void> {
    return new Promise((resolve, reject) => {
      this.client.messages.create({
        originator: 'YourCompany',
        recipients: [to],
        body: message,
        datacoding: 'auto' // Automatically handles character encoding
      }, (err, response) => {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Plivo offers competitive rates for Nicaragua SMS:

import plivo from 'plivo';

class PlivoSMSClient {
  private client: plivo.Client;

  constructor(authId: string, authToken: string) {
    this.client = new plivo.Client(authId, authToken);
  }

  async sendSMS(to: string, message: string): Promise<void> {
    try {
      const response = await this.client.messages.create({
        src: 'YourSourceNumber', // Your Plivo number
        dst: to,
        text: message,
        url: 'https://your-callback-url.com/status',
        method: 'POST'
      });

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

Common Error Codes

Webhook Implementation

import express from 'express';

const app = express();
app.use(express.urlencoded({ extended: false }));

// Twilio delivery status webhook
app.post('/status', (req, res) => {
  const { MessageSid, MessageStatus, To } = req.body;

  console.log(`Message ${MessageSid} to ${To}: ${MessageStatus}`);

  // Update your database with delivery status
  // Statuses: queued, sent, delivered, failed, undelivered

  res.sendStatus(200);
});

app.listen(3000);

API Rate Limits and Throughput

Rate Limits:

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

Queue System Implementation:

import Queue from 'bull';

const smsQueue = new Queue('sms', process.env.REDIS_URL);

// Add messages to queue
smsQueue.add({ to: '+50581234567', message: 'Hello!' });

// Process with rate limiting
smsQueue.process(async (job) => {
  const { to, message } = job.data;
  await sendSMS(to, message);
});

// Exponential backoff for retries
smsQueue.on('failed', (job, err) => {
  console.log(`Job ${job.id} failed: ${err.message}`);
  // Bull automatically retries with exponential backoff
});

Error Handling and Reporting

Implement comprehensive error handling:

class SMSErrorHandler {
  async sendWithRetry(
    to: string,
    message: string,
    maxRetries: number = 3
  ): Promise<void> {
    for (let attempt = 1; attempt <= maxRetries; attempt++) {
      try {
        await this.sendSMS(to, message);
        this.logSuccess(to, message);
        return;
      } catch (error) {
        this.logError(to, message, error, attempt);

        if (attempt === maxRetries) {
          this.alertFailure(to, message, error);
          throw error;
        }

        // Exponential backoff: 1s, 2s, 4s
        await this.delay(Math.pow(2, attempt - 1) * 1000);
      }
    }
  }

  private delay(ms: number): Promise<void> {
    return new Promise(resolve => setTimeout(resolve, ms));
  }

  private logError(to: string, message: string, error: any, attempt: number) {
    console.error(`Attempt ${attempt} failed for ${to}:`, error);
  }

  private alertFailure(to: string, message: string, error: any) {
    // Send alert to monitoring system
    console.error(`Final failure for ${to}:`, error);
  }

  private logSuccess(to: string, message: string) {
    console.log(`Successfully sent to ${to}`);
  }
}

Troubleshooting Common Issues

Issue: Low Delivery Rates

Symptoms: Messages sent but not reaching recipients Possible Causes:

• Invalid phone number format
• Carrier filtering due to content
• Sender ID not recognized

Solutions:

1. Validate all numbers against regex patterns before sending
2. Test message content with different carriers
3. Include brand name in message body
4. Monitor delivery receipts to identify patterns

Issue: Messages Blocked

Symptoms: High failure rates with no error codes Possible Causes:

• Content triggers carrier filters
• Too many messages in short time
• URLs flagged as spam

Solutions:

1. Remove URL shorteners, use full domains
2. Reduce sending frequency
3. Avoid ALL CAPS and excessive punctuation
4. Test across both Claro and Tigo networks

Issue: Sender ID Appears as Number

Symptoms: Recipients see random numbers instead of your brand name Cause: Nicaragua carriers overwrite sender IDs Solution: Include your brand name at the start of every message: "YourBrand: Your message content here"

Issue: Two-Way Communication Not Working

Symptoms: Cannot receive replies Cause: Nicaragua does not support two-way SMS Solution: Direct recipients to alternative response channels (email, web form, app)

Frequently Asked Questions

Q: Can I use short codes in Nicaragua? A: No, short codes are not currently supported. Use alphanumeric sender IDs or international long codes.

Q: How much does SMS cost in Nicaragua? A: Pricing varies by provider and volume. Contact your SMS provider for current rates. Expect higher costs than US/EU markets.

Q: Can I send promotional messages without consent? A: No. Always obtain explicit opt-in consent before sending marketing messages.

Q: How do I handle accent marks in Spanish text? A: Use UCS-2 encoding for proper accent rendering. Note that UCS-2 reduces message length to 70 characters per segment.

Q: Why are my messages being overwritten with short codes? A: Nicaragua carriers automatically replace sender IDs with short codes. Include your brand name in the message body.

Q: Can I send SMS to toll-free numbers (1800XXXX)? A: No, SMS only works for mobile numbers starting with 5, 7, or 8.

Recap and Additional Resources

Key Takeaways

1. Compliance Priorities:

   • Obtain explicit consent
   • Honor opt-out requests within 24 hours
   • Maintain proper documentation with timestamps

2. Technical Considerations:

   • Format numbers with +505 prefix
   • Validate mobile prefixes (5, 7, 8)
   • Expect sender ID overwriting
   • Support Spanish language

3. Best Practices:

   • Send during business hours (8 AM – 8 PM)
   • Keep messages under 160 characters
   • Include brand name in message body
   • Test across Claro and Tigo networks
   • Monitor delivery rates by carrier

Next Steps

1. Review TELCOR regulations at official website
2. Implement opt-in/opt-out systems with Spanish keywords
3. Set up monitoring and delivery tracking
4. Test with both Claro and Tigo carrier numbers
5. Configure webhooks for delivery status updates

Additional Resources

• TELCOR Official Website
• Nicaragua Telecommunications Law
• SMS Best Practices Guide

Contact Information:

• TELCOR Support: +505 2222-7348
• Technical Support: regulacion@telcor.gob.ni