Djibouti SMS Guide

Djibouti SMS Market Overview

Market Conditions: Djibouti's mobile market is characterized by a growing SMS adoption rate, with telecommunications services primarily provided through Djibouti Telecom, the country's main operator. While OTT messaging apps like WhatsApp and Telegram are gaining popularity, particularly in urban areas, SMS remains a reliable communication channel due to its universal accessibility and network independence. The mobile market shows a mix of Android and iOS devices, with Android having a larger market share due to the availability of more affordable handsets.

Key SMS Features and Capabilities in Djibouti

Djibouti supports standard SMS features including concatenated messaging and number portability, though two-way SMS functionality is limited.

Two-way SMS Support

Two-way SMS is not supported in Djibouti for A2P (Application-to-Person) messaging.
This limitation means businesses should design their SMS strategies around one-way communication flows.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is supported for most sender ID types.
Message length rules: Standard 160 characters per message segment using GSM-7 encoding.
Encoding considerations: Messages using GSM-7 encoding allow 160 characters, while UCS-2 encoding (for special characters and non-Latin alphabets) allows 70 characters per segment.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link for accessing multimedia content.
Best practice is to use short URLs and include clear instructions for accessing the content.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Djibouti.
While this affects routing, modern SMS providers automatically handle number portability to ensure reliable delivery.

Sending SMS to Landlines

Sending SMS to landline numbers is not possible in Djibouti.
Attempts to send SMS to landline numbers will result in a failed delivery and an error response (400 error code 21614) from the SMS API.

Compliance and Regulatory Guidelines for SMS in Djibouti

SMS communications in Djibouti are regulated by the MINIST??RE DE LA COMMUNICATION, DE LA CULTURE, CHARG?? DES POSTES ET T??L??COMMUNICATIONS (MCCPT). While specific SMS marketing laws are still evolving, businesses must adhere to general telecommunications regulations and international best practices.

Consent and Opt-In

Explicit Consent Requirements:

• Obtain clear, documented opt-in consent before sending any marketing messages
• Maintain detailed records of when and how consent was obtained
• Include clear terms of service and privacy policy information during opt-in

Best Practices for Consent Collection:

• Use double opt-in processes for marketing lists
• Clearly state message frequency and content type
• Document consent timestamp and method of collection

HELP/STOP and Other Commands

• All SMS campaigns must support standard STOP and HELP commands
• Support both French and Arabic keywords (STOP/ARR??TER/????????)
• Respond to HELP requests with service information in French and Arabic
• Process STOP requests within 24 hours

Do Not Call / Do Not Disturb Registries

While Djibouti does not maintain an official Do Not Call registry, businesses should:

• Maintain internal suppression lists
• Honor opt-out requests immediately
• Remove unsubscribed numbers from all future campaigns
• Implement automated filtering for opted-out numbers

Time Zone Sensitivity

Djibouti follows East Africa Time (EAT/UTC+3) Recommended Sending Windows:

• Business messages: 8:00 AM to 8:00 PM local time
• Marketing messages: 10:00 AM to 6:00 PM local time
• Emergency notifications: Can be sent 24/7 if urgent

Phone Numbers Options and SMS Sender Types for in Djibouti

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 and two-factor authentication

Short Codes

Support: Not currently supported in Djibouti
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 may be blocked
• URLs from suspicious domains are filtered
• High-frequency sending patterns may trigger spam filters

Tips to Avoid Blocking:

• Avoid excessive punctuation and all-caps text
• Use registered URL shorteners
• Maintain consistent sending patterns
• Include clear business identification
• Avoid common spam trigger words

Best Practices for Sending SMS in Djibouti

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Personalize messages using recipient name or relevant details
• Maintain consistent sender ID across campaigns

Sending Frequency and Timing

• Limit marketing messages to 2-4 per month per recipient
• Respect religious observances (especially during Ramadan)
• Avoid sending during major holidays
• Space out bulk campaigns to prevent network congestion

Localization

• Primary languages: French and Arabic
• Consider bilingual messages for important communications
• Use appropriate date formats (DD/MM/YYYY)
• Respect cultural sensitivities in message content

Opt-Out Management

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

Testing and Monitoring

• Test messages across different device types
• Monitor delivery rates by carrier
• Track engagement metrics (click-through rates for links)
• Regular review of bounce rates and failure patterns

SMS API integrations for Djibouti

Twilio

Twilio provides a robust SMS API with comprehensive support for Djibouti. Integration requires an Account SID and Auth Token from your Twilio dashboard.

import { Twilio } from 'twilio';

// Initialize Twilio client with environment variables
const client = new Twilio(
  process.env.TWILIO_ACCOUNT_SID!,
  process.env.TWILIO_AUTH_TOKEN!
);

async function sendSMSToDjibouti(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    // Ensure phone number is in E.164 format for Djibouti (+253)
    const formattedNumber = to.startsWith('+253') ? to : `+253${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 in Djibouti with support for alphanumeric sender IDs.

import axios from 'axios';

interface SinchSMSResponse {
  id: string;
  status: string;
}

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,
    senderId: string
  ): Promise<SinchSMSResponse> {
    try {
      const response = await axios.post(
        `${this.baseUrl}/batches`,
        {
          from: senderId,
          to: [to],
          body: message,
        },
        {
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Content-Type': 'application/json',
          },
        }
      );

      return response.data;
    } catch (error) {
      console.error('Sinch SMS sending failed:', error);
      throw error;
    }
  }
}

MessageBird

MessageBird provides reliable SMS delivery to Djibouti with support for high-volume messaging.

import messagebird from 'messagebird';

class MessageBirdClient {
  private client: any;

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

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

Plivo

Plivo offers competitive rates and reliable delivery to Djibouti with comprehensive delivery reporting.

import plivo from 'plivo';

class PlivoSMSClient {
  private client: any;

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

  async sendSMS(
    to: string,
    message: string,
    senderId: string
  ): Promise<any> {
    try {
      const response = await this.client.messages.create({
        src: senderId,
        dst: to,
        text: message,
        url_strip_query_params: false, // Preserve URL parameters if included
      });

      return response;
    } catch (error) {
      console.error('Plivo SMS sending failed:', error);
      throw error;
    }
  }
}

API Rate Limits and Throughput

• Default rate limit: 100 messages per second
• Burst limit: 250 messages per minute
• Daily sending quota: Based on account level

Strategies for Large-Scale Sending:

• Implement exponential backoff for retry logic
• Use message queuing systems (Redis, RabbitMQ)
• Batch messages in groups of 50-100
• Monitor delivery receipts for throttling signals

Error Handling and Reporting

Common Error Scenarios:

• Invalid phone number format
• Network timeouts
• Rate limit exceeded
• Invalid sender ID

Logging Best Practices:

• Log all API requests and responses
• Track delivery receipts
• Monitor error rates by error type
• Implement automated alerts for high failure rates

Recap and Additional Resources

Key Takeaways:

• Always use E.164 number formatting (+253)
• Implement proper opt-out handling
• Respect local time zones and cultural considerations
• Monitor delivery rates and engagement metrics

Next Steps:

1. Review MCCPT regulations for SMS communications
2. Implement proper consent management systems
3. Set up monitoring and reporting infrastructure
4. Test message delivery across different carriers

Additional Information:

• MCCPT Official Website: www.mccpt.dj
• Djibouti Telecom Guidelines: www.djiboutitelecom.dj
• International SMS Best Practices: GSMA Guidelines

Technical Resources:

• Twilio Djibouti Documentation
• Sinch API Reference
• MessageBird API Guide
• Plivo SMS API Documentation