Mongolia SMS Best Practices, Compliance, and Features

Mongolia SMS Market Overview

Market Conditions: Mongolia has a growing mobile market with increasing SMS usage for both personal and business communications. The country has several major mobile operators including Mobicom, Unitel, and Skytel. While OTT messaging apps like WeChat and Facebook Messenger are popular in urban areas, SMS remains crucial for business communications and authentication services, especially in rural regions where internet connectivity may be limited. Android devices dominate the mobile market share in Mongolia.

Key SMS Features and Capabilities in Mongolia

Mongolia supports basic SMS functionality with some limitations on advanced features, focusing primarily on one-way messaging capabilities for business communications.

Two-way SMS Support

Two-way SMS is not supported in Mongolia according to current carrier configurations. Businesses should design their SMS strategies around one-way communications only.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messages are supported, though availability 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 are supported. Messages using Mongolian script require UCS-2 encoding, which reduces the character limit per segment.

MMS Support

MMS messages are not directly supported in Mongolia. When MMS content is sent, it is automatically converted to SMS with an embedded URL link where recipients can view the multimedia content. This ensures compatibility while still enabling rich media sharing capabilities.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Mongolia. Mobile numbers remain tied to their original carrier, which helps ensure reliable message routing and delivery.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Mongolia. Attempts to send messages to landline numbers will result in a failed delivery and an error response (400 error code 21614 for Twilio API implementations). These messages will not appear in logs and accounts will not be charged.

Compliance and Regulatory Guidelines for SMS in Mongolia

SMS communications in Mongolia are regulated by the Communications Regulatory Commission of Mongolia (CRC). While specific SMS marketing regulations are still evolving, businesses must follow general telecommunications guidelines and international best practices for messaging.

Consent and Opt-In

Explicit Consent Required: You must obtain and document clear opt-in consent before sending marketing or promotional messages. Best practices include:

• Maintaining detailed records of when and how consent was obtained
• Using double opt-in processes for marketing lists
• Clearly stating the type and frequency of messages users will receive
• Providing transparent terms and conditions in both Mongolian and English

HELP/STOP and Other Commands

While Mongolia doesn't mandate specific keywords, implementing standard opt-out mechanisms is strongly recommended:

• Support both English and Mongolian language commands
• Common keywords: STOP/??????????, HELP/??????????????
• Process opt-out requests within 24 hours
• Send confirmation messages in the same language as the opt-out request

Do Not Call / Do Not Disturb Registries

Mongolia does not currently maintain an official Do Not Call registry. However, businesses should:

• Maintain their own suppression lists
• Honor opt-out requests immediately
• Keep records of opted-out numbers for at least 12 months
• Regularly clean contact lists to remove inactive numbers

Time Zone Sensitivity

Mongolia operates in UTC+8 (Ulaanbaatar Time). While there are no strict legal time restrictions, follow these best practices:

• Send messages between 9:00 AM and 8:00 PM local time
• Avoid sending during national holidays
• Only send outside these hours for urgent or time-critical messages
• Consider seasonal variations in daylight hours

Phone Numbers Options and SMS Sender Types for in Mongolia

Alphanumeric Sender ID

Operator network capability: Supported
Registration requirements: Pre-registration not required, dynamic usage supported
Sender ID preservation: Yes, sender IDs are preserved and displayed as sent

Long Codes

Domestic vs. International:

• Domestic long codes not supported
• International long codes fully supported

Sender ID preservation: Yes, original sender ID is preserved
Provisioning time: Immediate to 24 hours
Use cases: Ideal for transactional messages, alerts, and notifications

Short Codes

Support: Not currently available in Mongolia
Provisioning time: N/A
Use cases: N/A

Restricted SMS Content, Industries, and Use Cases

Restricted Industries and Content:

• Gambling and betting services
• Adult content or services
• Unauthorized financial services
• Political campaign messages without proper authorization
• Cryptocurrency promotions

Content Filtering

Known Carrier Filtering Rules:

• Messages containing certain keywords in Mongolian or English may be blocked
• URLs from suspicious domains are filtered
• High-volume sending from new sender IDs may be throttled

Tips to Avoid Blocking:

• Avoid URL shorteners in messages
• Use consistent sender IDs
• Maintain regular sending patterns
• Keep content professional and clear
• Avoid excessive punctuation or all-caps

Best Practices for Sending SMS in Mongolia

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Personalize messages using recipient's name when appropriate
• Maintain consistent branding across messages

Sending Frequency and Timing

• Limit marketing messages to 2-4 per month per recipient
• Space out messages to avoid overwhelming users
• Consider Mongolian holidays and festivals
• Respect traditional celebration periods like Tsagaan Sar

Localization

• Support both Mongolian script and Cyrillic
• Consider bilingual messages for important communications
• Use local date and time formats
• Respect cultural nuances in message content

Opt-Out Management

• Process opt-outs within 24 hours
• Send opt-out confirmation messages
• Maintain clean suppression lists
• Regular audit of opt-out processes

Testing and Monitoring

• Test across all major Mongolian carriers
• Monitor delivery rates by carrier
• Track engagement metrics
• Regular testing of opt-out functionality
• Monitor for carrier filtering changes

SMS API integrations for Mongolia

Twilio

Twilio provides robust SMS capabilities for sending messages to Mongolia. Integration requires your Account SID and Auth Token from the Twilio Console.

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 Mongolia
async function sendSMSToMongolia(
  to: string,
  message: string,
  senderId: string
): Promise<void&gt; {
  try {
    // Ensure proper formatting for Mongolian numbers
    const formattedNumber = to.startsWith('+976') ? to : `+976${to}`;
    
    const response = await client.messages.create({
      body: message,
      from: senderId, // Alphanumeric sender ID or Twilio number
      to: formattedNumber,
    });
    
    console.log(`Message sent successfully! SID: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers direct carrier connections for reliable message delivery to Mongolia. Authentication uses Bearer token.

import axios from 'axios';

class SinchSMSService {
  private readonly apiToken: string;
  private readonly servicePlanId: string;
  private readonly baseUrl: string = 'https://sms.api.sinch.com/xms/v1';

  constructor(apiToken: string, servicePlanId: string) {
    this.apiToken = apiToken;
    this.servicePlanId = servicePlanId;
  }

  async sendSMS(to: string, message: string): Promise<void&gt; {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.servicePlanId}/batches`,
        {
          from: 'YourCompany', // Alphanumeric sender ID
          to: [to],
          body: message,
        },
        {
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Content-Type': 'application/json',
          },
        }
      );
      
      console.log('Message sent successfully:', response.data);
    } catch (error) {
      console.error('Failed to send message:', error);
      throw error;
    }
  }
}

MessageBird

MessageBird (correcting "Bird" in the template) provides reliable SMS delivery to Mongolia with straightforward integration.

import messagebird from 'messagebird';

class MessageBirdService {
  private client: any;

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

  sendSMS(to: string, message: string, senderId: string): Promise<void&gt; {
    return new Promise((resolve, reject) =&gt; {
      this.client.messages.create({
        originator: senderId,
        recipients: [to],
        body: message,
        type: 'sms',
      }, (err: any, response: any) =&gt; {
        if (err) {
          console.error('MessageBird error:', err);
          reject(err);
        } else {
          console.log('Message sent successfully:', response);
          resolve();
        }
      });
    });
  }
}

Plivo

Plivo offers SMS capabilities for Mongolia with detailed delivery reporting.

import plivo from 'plivo';

class PlivoSMSService {
  private client: any;

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

  async sendSMS(to: string, message: string, senderId: string): Promise<void&gt; {
    try {
      const response = await this.client.messages.create({
        src: senderId,
        dst: to,
        text: message,
        // Optional parameters for Mongolia
        url_strip_query_params: false,
        log_dlt_status: true,
      });
      
      console.log('Message sent:', response);
    } catch (error) {
      console.error('Plivo error:', error);
      throw error;
    }
  }
}

API Rate Limits and Throughput

• Twilio: 100 messages per second
• Sinch: 30 messages per second
• MessageBird: 60 messages per second
• Plivo: 50 messages per second

Strategies for Large-Scale Sending:

• Implement queue systems using Redis or RabbitMQ
• Use batch APIs where available
• Implement exponential backoff for retries
• Monitor delivery rates and adjust sending speed

Error Handling and Reporting

• Implement comprehensive logging with Winston or Bunyan
• Track delivery receipts (DLRs)
• Monitor common error codes:
  • Invalid number format
  • Network errors
  • Rate limit exceeded
• Set up automated alerts for error thresholds

Recap and Additional Resources

Key Takeaways:

• Always use international number format (+976)
• Implement proper opt-out handling
• Monitor delivery rates and errors
• Follow time zone best practices
• Maintain clean contact lists

Next Steps:

1. Review the Communications Regulatory Commission (CRC) guidelines
2. Implement proper consent management
3. Set up monitoring and reporting
4. Test thoroughly across all carriers

Additional Information:

• Communications Regulatory Commission of Mongolia
• Mongolia Telecommunications Law
• GSMA Mongolia Guidelines

Industry Resources:

• Mobile Network Operators Association of Mongolia
• Mongolia ICT Development Guidelines
• International SMS Best Practices Guide