Burundi SMS Guide - sms-compliance -

Burundi SMS Best Practices, Compliance, and Features

Burundi SMS Market Overview

Locale name:Burundi
ISO code:BI
RegionMiddle East & Africa
Mobile country code (MCC)642
Dialing Code+257

Market Conditions: Burundi's mobile market is characterized by growing SMS adoption for business communications and notifications. The telecommunications sector is regulated by ARCT (Regulatory Agency for Telecommunications). While OTT messaging apps are gaining popularity, SMS remains a reliable channel for reaching users across all device types, particularly given the high percentage of feature phones in use. The market maintains strong Android dominance over iOS devices.

Key SMS Features and Capabilities in Burundi

Burundi supports basic SMS functionality with concatenated messaging support and alphanumeric sender IDs, though two-way messaging capabilities are limited.

Two-way SMS Support

Two-way SMS is not supported in Burundi through major SMS providers. This means businesses can send outbound messages but cannot receive replies through the same channels.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is supported for most sender ID types, though support may vary by carrier.
Message length rules: Standard SMS length limits apply - 160 characters for GSM-7 encoding, 70 characters for UCS-2 encoding before splitting occurs.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported, with messages automatically using the appropriate encoding based on content.

MMS Support

MMS messages are not directly supported in Burundi. When attempting to send MMS, the message will be automatically converted to SMS with an embedded URL link where recipients can view the media content. This ensures message delivery while maintaining media accessibility.

Recipient Phone Number Compatibility

Number Portability

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

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Burundi. Attempts to send messages to landline numbers will result in delivery failure, typically generating a 400 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 Burundi

The Regulatory Agency for Telecommunications (ARCT) oversees SMS communications in Burundi. While specific SMS marketing regulations are still evolving, businesses must follow general telecommunications guidelines and international best practices.

Explicit Consent Requirements:

  • Obtain clear, documented consent before sending marketing messages
  • Maintain records of how and when consent was obtained
  • Specify the types of messages recipients will receive
  • Clearly communicate the sender's identity and message frequency

Best Practices for Consent Collection:

  • Use double opt-in processes for marketing lists
  • Provide clear terms and conditions
  • Document consent timestamps and methods
  • Regular consent refresh campaigns recommended every 12-24 months

HELP/STOP and Other Commands

  • All SMS campaigns must support standard HELP and STOP commands
  • Commands should be recognized in both French and Kirundi
  • Common keywords to support:
    • STOP, ARRET, DÉSABONNER (unsubscribe)
    • AIDE, HELP (help)
    • INFO (information)

Do Not Call / Do Not Disturb Registries

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

  • Maintain internal opt-out lists
  • Honor opt-out requests within 24 hours
  • Keep suppression lists updated across all campaigns
  • Regularly clean contact databases

Time Zone Sensitivity

Burundi follows East Africa Time (EAT, UTC+2) Recommended Sending Windows:

  • Business messages: 8:00 AM - 6:00 PM EAT
  • Marketing messages: 9:00 AM - 5:00 PM EAT
  • Urgent notifications: 24/7 permitted for critical alerts

Phone Numbers Options and SMS Sender Types for in Burundi

Alphanumeric Sender ID

Operator network capability: Supported
Registration requirements: Pre-registration not required, dynamic usage supported
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 preserved
Provisioning time: Typically 1-2 business days
Use cases: Ideal for transactional messages and two-factor authentication

Short Codes

Support: Not currently supported in Burundi
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 promotions

Content Filtering

Known Carrier Filtering Rules:

  • Messages containing certain keywords may be blocked
  • URLs from unknown domains often filtered
  • Multiple exclamation marks or all-caps text may trigger spam filters

Best Practices to Avoid Filtering:

  • Use registered URL shorteners
  • Avoid excessive punctuation
  • Maintain consistent sending patterns
  • Use approved sender IDs consistently

Best Practices for Sending SMS in Burundi

Messaging Strategy

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

Sending Frequency and Timing

  • Limit marketing messages to 2-4 per month per recipient
  • Respect local holidays and weekends
  • Avoid sending during major religious observances
  • Space out messages to prevent recipient fatigue

Localization

  • Primary languages: French and Kirundi
  • Consider bilingual messages for important communications
  • Use local date and time formats
  • Respect cultural sensitivities in message content

Opt-Out Management

  • Process opt-outs within 24 hours
  • Maintain centralized opt-out database
  • Include opt-out instructions in marketing messages
  • Regular audit of opt-out list compliance

Testing and Monitoring

  • Test messages across major carriers
  • Monitor delivery rates by carrier
  • Track engagement metrics
  • Regular testing of opt-out functionality
  • Monitor and analyze failure rates

SMS API integrations for Burundi

Twilio

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

import { Twilio } from 'twilio';

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

async function sendSmsToBurundi() {
  try {
    // Send message with proper Burundi phone formatting
    const message = await client.messages.create({
      body: 'Your message here', // Message content
      from: 'YourSenderID', // Alphanumeric sender ID
      to: '+25712345678' // Burundi number with country code
    });
    
    console.log(`Message sent successfully: ${message.sid}`);
    return message;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers direct carrier connections in Burundi with support for alphanumeric sender IDs.

import axios from 'axios';

async function sendSinchSms() {
  const API_TOKEN = process.env.SINCH_API_TOKEN;
  const SERVICE_PLAN_ID = process.env.SINCH_SERVICE_PLAN_ID;
  
  try {
    const response = await axios.post(
      `https://sms.api.sinch.com/xms/v1/${SERVICE_PLAN_ID}/batches`,
      {
        from: 'YourBrand', // Alphanumeric sender ID
        to: ['+25712345678'],
        body: 'Your message content',
        delivery_report: 'summary'
      },
      {
        headers: {
          'Authorization': `Bearer ${API_TOKEN}`,
          'Content-Type': 'application/json'
        }
      }
    );
    
    console.log('Message sent:', response.data);
    return response.data;
  } catch (error) {
    console.error('Sinch SMS error:', error);
    throw error;
  }
}

MessageBird

MessageBird provides reliable SMS delivery in Burundi with support for various sender ID types.

import messagebird from 'messagebird';

const client = messagebird(process.env.MESSAGEBIRD_API_KEY);

function sendMessageBirdSms() {
  const params = {
    originator: 'YourBrand', // Alphanumeric sender ID
    recipients: ['+25712345678'],
    body: 'Your message content',
    reportUrl: 'https://your-webhook-url.com/delivery-reports'
  };

  client.messages.create(params, (err, response) => {
    if (err) {
      console.error('MessageBird error:', err);
      return;
    }
    console.log('Message sent successfully:', response);
  });
}

Plivo

Plivo offers SMS capabilities in Burundi with detailed delivery reporting.

import plivo from 'plivo';

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

async function sendPlivoSms() {
  try {
    const message = await client.messages.create({
      src: 'YourBrand', // Alphanumeric sender ID
      dst: '+25712345678', // Destination number
      text: 'Your message content',
      url: 'https://your-webhook-url.com/delivery-status'
    });
    
    console.log('Message sent:', message);
    return message;
  } catch (error) {
    console.error('Plivo error:', error);
    throw error;
  }
}

API Rate Limits and Throughput

  • Default rate limits vary by provider (typically 1-10 messages per second)
  • Implement exponential backoff for retry logic
  • Use batch APIs for bulk sending
  • Consider queue implementation for high-volume sending:
    • Redis for message queuing
    • Bull for job processing
    • AWS SQS for scalable message queuing

Error Handling and Reporting

  • Implement comprehensive error logging
  • Monitor delivery receipts
  • Track common error codes:
    • Invalid number format
    • Network errors
    • Rate limit exceeded
  • Store delivery status updates
  • Implement webhook endpoints for delivery notifications

Recap and Additional Resources

Key Takeaways

  1. Compliance Priorities

    • Obtain explicit consent
    • Honor opt-out requests
    • Maintain proper documentation
    • Follow time zone restrictions

  2. Technical Considerations

    • Use proper phone number formatting
    • Implement retry logic
    • Monitor delivery rates
    • Handle errors gracefully

  3. Best Practices

    • Localize content
    • Respect sending windows
    • Maintain clean contact lists
    • Regular testing and monitoring

Next Steps

  1. Review ARCT regulations at www.arct.gov.bi
  2. Consult legal counsel for compliance review
  3. Set up test accounts with preferred SMS providers
  4. Implement delivery monitoring systems

Additional Resources