Frequently Asked Questions
Use an SMS API provider like Twilio, Sinch, MessageBird, or Plivo. These providers offer direct carrier connections and support for alphanumeric sender IDs. Ensure correct phone number formatting with the +257 country code and implement proper error handling.
Burundi's mobile market shows increasing SMS usage for business communication. While OTT apps are growing, SMS remains reliable due to the prevalence of feature phones and strong Android dominance. The market is regulated by the ARCT (Regulatory Agency for Telecommunications).
Two-way SMS is not supported through major SMS providers in Burundi. Businesses can send outbound messages but cannot receive replies via the same channel. This limitation affects interactive SMS campaigns.
The recommended sending window for marketing messages is between 9:00 AM and 5:00 PM EAT (UTC+2). Respect local holidays, weekends, and major religious observances to avoid negative recipient reactions.
No, short codes are not currently supported in Burundi. Use international long codes for transactional messages and two-factor authentication, which are fully supported and maintain original sender IDs.
Sending SMS to landlines is not supported. Attempts will result in delivery failure with a 400 response and error code 21614. No charges will occur, and the failed messages won't appear in logs.
Obtain explicit consent before sending marketing messages, honor opt-out requests within 24 hours, and maintain comprehensive documentation of consent. Follow time zone restrictions and adhere to guidelines set by the ARCT.
Restricted content includes gambling, adult services, unauthorized financial services, political messaging without authorization, and cryptocurrency promotions. Content filtering may also block certain keywords, URLs, and excessive punctuation.
Standard SMS length limits apply. Concatenated messages are supported, with 160 characters for GSM-7 encoding and 70 characters for UCS-2 encoding before splitting occurs. The appropriate encoding is used automatically.
Keep messages concise, include clear calls-to-action, personalize content, and use consistent sender IDs. Limit marketing messages to 2-4 per month per recipient, respect local holidays and weekends, and localize content in French and Kirundi.
Process opt-out requests within 24 hours, maintain a centralized opt-out database, and always include opt-out instructions in marketing messages. Regularly audit your opt-out list for compliance.
The ARCT (Regulatory Agency for Telecommunications) oversees SMS communications in Burundi. While specific SMS marketing regulations are still developing, businesses must adhere to general telecommunications guidelines and international best practices.
Providers like Twilio, Sinch, MessageBird, and Plivo offer comprehensive SMS APIs for Burundi. You'll need account credentials for authentication and should format phone numbers with the +257 country code.
Implement detailed error logging, monitor delivery receipts, and track common error codes like invalid number format, network errors, and rate limit issues. Store delivery status updates and use webhooks for real-time notifications.
Loading...
Burundi SMS Best Practices, Compliance, and Features
Burundi SMS Market Overview
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.
Consent and Opt-In
Explicit Consent Requirements:
Best Practices for Consent Collection:
HELP/STOP and Other Commands
Do Not Call / Do Not Disturb Registries
Burundi does not maintain an official Do Not Call registry. However, businesses should:
Time Zone Sensitivity
Burundi follows East Africa Time (EAT, UTC+2) Recommended Sending Windows:
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:
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:
Content Filtering
Known Carrier Filtering Rules:
Best Practices to Avoid Filtering:
Best Practices for Sending SMS in Burundi
Messaging Strategy
Sending Frequency and Timing
Localization
Opt-Out Management
Testing and Monitoring
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.
Sinch
Sinch offers direct carrier connections in Burundi with support for alphanumeric sender IDs.
MessageBird
MessageBird provides reliable SMS delivery in Burundi with support for various sender ID types.
Plivo
Plivo offers SMS capabilities in Burundi with detailed delivery reporting.
API Rate Limits and Throughput
Error Handling and Reporting
Recap and Additional Resources
Key Takeaways
Compliance Priorities
Technical Considerations
Best Practices
Next Steps
Additional Resources