Mauritius SMS Best Practices, Compliance, and Features

Mauritius SMS Market Overview

Market Conditions: Mauritius has a robust mobile telecommunications infrastructure with widespread SMS usage. The market is served by major operators including Mauritius Telecom (My.T), Emtel, and MTML. While OTT messaging apps like WhatsApp and Messenger are popular, SMS remains a critical channel for business communications and authentication services due to its reliability and universal reach across all mobile devices.

Key SMS Features and Capabilities in Mauritius

Mauritius supports standard SMS features including concatenated messaging and alphanumeric sender IDs, though two-way SMS functionality is not available.

Two-way SMS Support

Two-way SMS is not supported in Mauritius. Businesses cannot receive direct replies through the same channel used for sending messages.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messaging is fully supported in Mauritius, though support may vary by sender ID type.
Message length rules: Standard SMS messages are limited to 160 characters using GSM-7 encoding, or 70 characters using Unicode (UCS-2) encoding before splitting occurs.
Encoding considerations: Messages using GSM-7 encoding can be up to 160 characters, while Unicode messages are limited to 70 characters per segment.

MMS Support

MMS messages are not directly supported in Mauritius. Instead, MMS content is automatically converted to SMS with an embedded URL link where recipients can view the multimedia content online. This ensures compatibility across all devices while still enabling rich media sharing.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Mauritius. Mobile subscribers cannot transfer their numbers between different network operators.
This means phone numbers remain tied to their original network operator, which can simplify message routing and delivery.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Mauritius. Attempts to send messages to landline numbers will result in a 400 error response with error code 21614. These messages will not appear in logs and accounts will not be charged for failed attempts.

Compliance and Regulatory Guidelines for SMS in Mauritius

SMS communications in Mauritius are regulated by the Information and Communication Technologies Authority (ICTA) and must comply with the Data Protection Act 2017. The ICTA oversees telecommunications services and enforces guidelines for commercial messaging.

Consent and Opt-In

Explicit Consent Requirements:

• Written or electronic consent must be obtained before sending marketing messages
• Consent records should be maintained and easily accessible
• Purpose of messaging must be clearly stated during opt-in
• Consent should specify the types of messages recipients will receive

Best Practices for Consent:

• Use double opt-in processes for marketing lists
• Maintain detailed consent logs including timestamp and opt-in method
• Provide clear terms and conditions during signup
• Regular consent refresh for long-term subscribers

HELP/STOP and Other Commands

• All SMS campaigns must support standard STOP and HELP commands
• Keywords should work in both English and French
• Common variations like "ARRET" (French for STOP) should be honored
• Automated response confirming opt-out must be sent
• HELP responses should include customer service contact information

Do Not Call / Do Not Disturb Registries

While Mauritius does not maintain a centralized Do Not Call registry, businesses must:

• Maintain their own suppression lists
• Honor opt-out requests within 24 hours
• Implement proper screening processes for blocked numbers
• Regularly update internal DND databases
• Document all opt-out requests for compliance purposes

Time Zone Sensitivity

Mauritius follows MUT (Mauritius Time, UTC+4) and has specific guidelines for message timing:

• Recommended sending hours: 08:00 - 20:00 MUT
• Restricted hours: Avoid sending between 20:00 - 08:00 unless urgent
• Holiday considerations: Respect public holidays and weekends
• Emergency messages: Can be sent 24/7 if truly urgent

Phone Numbers Options and SMS Sender Types for in Mauritius

Alphanumeric Sender ID

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

Long Codes

Domestic vs. International:

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

Sender ID preservation: Yes, original sender ID is maintained
Provisioning time: Typically immediate to 24 hours
Use cases: Ideal for transactional messages and two-factor authentication

Short Codes

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

Restricted SMS Content, Industries, and Use Cases

Restricted Industries:

• Gambling and betting services
• Adult content and services
• Unauthorized financial services
• Unregistered healthcare providers

Regulated Industries:

• Banking and financial services require ICTA approval
• Healthcare messages must comply with medical privacy laws
• Insurance services need proper disclaimers

Content Filtering

Known Carrier Filters:

• URLs from unknown domains may be blocked
• Messages containing certain keywords related to restricted content
• Multiple exclamation marks or all-caps messages

Best Practices to Avoid Filtering:

• Use registered URL shorteners
• Avoid excessive punctuation
• Maintain consistent sender IDs
• Use clear, professional language

Best Practices for Sending SMS in Mauritius

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-action
• Use personalization tokens thoughtfully
• Maintain consistent brand voice

Sending Frequency and Timing

• Limit to 4-5 messages per month per recipient
• Respect religious and cultural holidays
• Avoid sending during off-hours
• Space out messages appropriately

Localization

• Support both English and French
• Consider Creole for specific campaigns
• Use appropriate date formats (DD/MM/YYYY)
• Account for local cultural nuances

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain clear opt-out records
• Confirm opt-out with acknowledgment message
• Regular database cleaning

Testing and Monitoring

• Test across all major carriers (My.T, Emtel, MTML)
• Monitor delivery rates by carrier
• Track engagement metrics
• Regular A/B testing of message content

SMS API integrations for Mauritius

Twilio

Twilio provides a robust SMS API with comprehensive support for Mauritius. Integration requires an account SID and auth token for authentication.

Key Parameters:

• to: Recipient number in E.164 format (+230XXXXXXXX)
• from: Alphanumeric sender ID or virtual number
• body: Message content (supports Unicode)

import * as Twilio from 'twilio';

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

async function sendSMSToMauritius(
  to: string,
  message: string,
  senderId: string
): Promise<void&gt; {
  try {
    // Validate Mauritius phone number format
    if (!to.startsWith('+230')) {
      throw new Error('Invalid Mauritius phone number format');
    }

    const response = await client.messages.create({
      body: message,
      from: senderId,
      to: to,
      // Optional parameters for delivery tracking
      statusCallback: 'https://your-webhook.com/status'
    });

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

Sinch

Sinch offers reliable SMS delivery to Mauritius with straightforward API integration. Authentication uses API key and secret.

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

class SinchSMSService {
  private client: SinchClient;

  constructor() {
    this.client = new SinchClient({
      projectId: process.env.SINCH_PROJECT_ID,
      keyId: process.env.SINCH_KEY_ID,
      keySecret: process.env.SINCH_KEY_SECRET
    });
  }

  async sendSMS(to: string, message: string): Promise<void&gt; {
    try {
      const response = await this.client.sms.batches.send({
        sendSMSRequestBody: {
          to: [to],
          from: 'YourBrand',
          body: message,
          // Enable delivery reports
          delivery_report: 'summary'
        }
      });

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

MessageBird

MessageBird provides extensive SMS capabilities for Mauritius with simple API integration.

import { MessageBird } from 'messagebird';

class MessageBirdService {
  private client: MessageBird;

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

  async sendSMS(
    to: string,
    message: string,
    senderId: string
  ): Promise<void&gt; {
    const params = {
      originator: senderId,
      recipients: [to],
      body: message,
      // Optional parameters
      reportUrl: 'https://your-webhook.com/delivery-reports'
    };

    return new Promise((resolve, reject) =&gt; {
      this.client.messages.create(params, (err, response) =&gt; {
        if (err) {
          reject(err);
          return;
        }
        resolve(response);
      });
    });
  }
}

Plivo

Plivo offers reliable SMS delivery to Mauritius with comprehensive API features.

import * as plivo from 'plivo';

class PlivoSMSService {
  private client: plivo.Client;

  constructor() {
    this.client = new plivo.Client(
      process.env.PLIVO_AUTH_ID,
      process.env.PLIVO_AUTH_TOKEN
    );
  }

  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 URL tracking
        url: 'https://your-webhook.com/status'
      });

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

API Rate Limits and Throughput

• Default rate limit: 30 messages per second
• Batch sending limit: 500 numbers per request
• Daily sending limits vary by provider

Strategies for Large-Scale Sending:

• Implement queuing system for high-volume campaigns
• Use batch APIs for multiple recipients
• Schedule messages across optimal time windows
• Monitor throughput and adjust sending rates

Error Handling and Reporting

Common Error Scenarios:

• Invalid phone numbers
• Network timeouts
• Rate limit exceeded
• Invalid sender ID

Best Practices:

• Implement retry logic with exponential backoff
• Log all API responses and errors
• Monitor delivery rates by carrier
• Set up automated alerts for error thresholds

Recap and Additional Resources

Key Takeaways

1. Compliance Requirements:

   • Obtain explicit consent
   • Honor opt-out requests within 24 hours
   • Respect sending time restrictions

2. Technical Considerations:

   • Use E.164 number formatting
   • Implement proper error handling
   • Monitor delivery rates

3. Best Practices:

   • Maintain clean contact lists
   • Test across all carriers
   • Regular performance monitoring

Next Steps

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

Additional Resources

• ICTA Guidelines
• Data Protection Office
• Mauritius Telecommunications Act

Industry Resources:

• Carrier compliance guidelines
• SMS best practices documentation
• API provider documentation