Mauritania SMS Best Practices, Compliance, and Features

Mauritania SMS Market Overview

Market Conditions: Mauritania's mobile market is characterized by three major operators: Mauritel, Mattel, and Chinguitel. SMS remains a crucial communication channel, particularly for business notifications and authentication. While OTT messaging apps like WhatsApp are gaining popularity in urban areas, SMS maintains high reliability and reach across the country's diverse geography. Android devices dominate the mobile ecosystem due to their affordability and accessibility.

Key SMS Features and Capabilities in Mauritania

Mauritania supports basic SMS functionality with some limitations on advanced features, focusing primarily on one-way messaging capabilities.

Two-way SMS Support

Two-way SMS is not supported in Mauritania according to current network capabilities. Businesses should design their messaging strategies around one-way communication flows.

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 Unicode.
Encoding considerations: Both GSM-7 and UCS-2 (Unicode) encodings are supported, with message splitting occurring at different thresholds for each encoding type.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link. This ensures compatibility across all networks while still allowing rich media content to be shared via clickable links.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Mauritania. This means mobile numbers remain tied to their original network operators, simplifying message routing but limiting consumer flexibility.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Mauritania. Attempts to send messages to landline numbers will result in delivery failure with a 400 response error (code 21614), and no charges will be incurred.

Compliance and Regulatory Guidelines for SMS in Mauritania

Mauritania's telecommunications sector is regulated by the Autorité de Régulation (ARE), which oversees SMS communications and marketing activities. While specific SMS marketing regulations are still evolving, businesses must adhere to general telecommunications laws and international best practices.

Consent and Opt-In

Explicit Consent Requirements:

• Written or electronic consent must be obtained before sending marketing messages
• Keep detailed records of when and how consent was obtained
• Clearly communicate the type and frequency of messages recipients will receive
• Provide transparent information about how personal data will be used

HELP/STOP and Other Commands

• All SMS campaigns must support standard opt-out keywords (STOP, ARRET, CANCEL)
• HELP/INFO messages should be available in both Arabic and French
• Responses to STOP commands must be processed within 24 hours
• Maintain clear documentation of opt-out requests and their processing dates

Do Not Call / Do Not Disturb Registries

While Mauritania does not maintain an official Do Not Call registry, 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 or opted-out numbers

Time Zone Sensitivity

Mauritania follows GMT/UTC+0. Best practices include:

• Sending messages between 8:00 AM and 8:00 PM local time
• Avoiding messages during prayer times
• Respecting religious observances, particularly during Ramadan
• Limiting non-essential messages during weekends (Friday-Saturday)

Phone Numbers Options and SMS Sender Types for in Mauritania

Alphanumeric Sender ID

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

Long Codes

Domestic vs. International:

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

Sender ID preservation: Yes, original sender ID is preserved for international numbers
Provisioning time: Immediate to 24 hours
Use cases: Ideal for transactional messages and two-factor authentication

Short Codes

Support: Not currently supported in Mauritania
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 messaging without proper authorization
• Cryptocurrency and speculative investments

Content Filtering

Known Carrier Filtering Rules:

• Messages containing certain keywords in Arabic or French may be blocked
• URLs should be from reputable domains
• Avoid excessive punctuation or all-caps text

Best Practices to Avoid Filtering:

• Use clear, professional language
• Avoid URL shorteners where possible
• Include company name in sender ID
• Maintain consistent sending patterns

Best Practices for Sending SMS in Mauritania

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Use personalization thoughtfully (e.g., recipient's name)
• Maintain consistent branding across messages

Sending Frequency and Timing

• Limit marketing messages to 2-4 per month per recipient
• Avoid sending during religious holidays
• Space out messages to prevent recipient fatigue
• Monitor engagement rates to optimize timing

Localization

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

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 messages across all major carriers (Mauritel, Mattel, Chinguitel)
• Monitor delivery rates by carrier
• Track engagement metrics and adjust strategy accordingly
• Regular testing of opt-out functionality

SMS API integrations for Mauritania

Twilio

Twilio provides a robust SMS API for sending messages to Mauritania. Here's how to implement it:

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

Sinch

Sinch offers comprehensive SMS capabilities for Mauritania with straightforward integration:

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

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

// Function to send SMS via Sinch
async function sendSinchSMS(
  recipientNumber: string,
  messageText: string
) {
  try {
    const response = await sinchClient.sms.send({
      to: [recipientNumber],
      message: messageText,
      // Use registered alphanumeric sender ID
      from: 'YourBrand',
      // Enable delivery reports
      deliveryReport: 'summary'
    });
    
    console.log('Message batch ID:', response.batchId);
    return response;
  } catch (error) {
    console.error('Sinch SMS Error:', error);
    throw error;
  }
}

MessageBird

MessageBird provides reliable SMS delivery to Mauritania:

import { MessageBird } from 'messagebird';

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

// Function to send SMS via MessageBird
async function sendMessageBirdSMS(
  to: string,
  message: string,
  senderId: string
) {
  const params = {
    originator: senderId,
    recipients: [to],
    body: message,
    // Optional parameters for delivery reporting
    reportUrl: 'https://your-webhook-url.com/delivery-reports'
  };

  return new Promise((resolve, reject) => {
    messagebird.messages.create(params, (err, response) => {
      if (err) {
        console.error('MessageBird Error:', err);
        reject(err);
      } else {
        console.log('Message sent successfully:', response.id);
        resolve(response);
      }
    });
  });
}

Plivo

Plivo's API offers reliable SMS delivery to Mauritania with detailed delivery tracking:

import { Client } from 'plivo';

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

// Function to send SMS via Plivo
async function sendPlivoSMS(
  destination: string,
  message: string,
  senderId: string
) {
  try {
    const response = await plivo.messages.create({
      src: senderId, // Your sender ID
      dst: destination, // Destination number
      text: message,
      // Optional parameters
      url: 'https://your-webhook-url.com/delivery-status',
      method: 'POST'
    });
    
    console.log('Message sent:', response.messageUuid);
    return response;
  } catch (error) {
    console.error('Plivo Error:', error);
    throw error;
  }
}

API Rate Limits and Throughput

• Default rate limit: 1 message per second per destination
• Batch sending limit: 500 messages per request
• Daily sending quota: Based on account level and history

Strategies for Large-Scale Sending:

• Implement queuing system for high-volume campaigns
• Use batch APIs when available
• Implement exponential backoff for retry logic
• Monitor delivery rates and adjust sending speed accordingly

Error Handling and Reporting

• Implement comprehensive logging for all API responses
• Monitor delivery receipts via webhooks
• Track common error codes and their resolutions
• Set up automated alerts for unusual error rates

Recap and Additional Resources

Key Takeaways

1. Compliance Priorities:

   • Obtain explicit consent
   • Honor opt-out requests promptly
   • Respect time zone and cultural considerations

2. Technical Best Practices:

   • Use alphanumeric sender IDs
   • Implement proper error handling
   • Monitor delivery rates

3. Localization Requirements:

   • Support both Arabic and French
   • Consider cultural sensitivities
   • Respect local business hours

Next Steps

1. Review the ARE (Autorité de Régulation) guidelines
2. Consult legal counsel for compliance verification
3. Set up test accounts with preferred SMS providers
4. Implement delivery monitoring systems

Additional Resources

• ARE Official Website
• Mauritania Telecommunications Law
• [SMS Provider Documentation]:
  • Twilio Mauritania Guidelines
  • Sinch API Documentation
  • MessageBird API Guide
  • Plivo API Reference