Frequently Asked Questions
Use a reputable SMS API provider like Twilio, Sinch, MessageBird, or Plivo. Ensure phone numbers are in E.164 format (+677 followed by the number), obtain necessary consent, and respect local regulations.
Single SMS messages are limited to 160 characters using GSM-7 encoding or 70 characters with UCS-2 encoding. Longer messages are automatically split into segments via concatenated SMS.
MMS is converted to SMS with a URL link due to limited mobile data infrastructure. This ensures compatibility across all devices while still allowing access to rich media content through a web link.
Adhere to SBT (UTC+11). The best practice is to send messages between 8:00 AM and 8:00 PM SBT, avoiding religious holidays and Sundays. Limit urgent messages outside these hours to true emergencies.
No, short codes are not currently supported. Use international long codes for transactional messages and two-factor authentication, as domestic long codes are also not supported.
While specific marketing laws are limited, obtain explicit opt-in consent before sending marketing messages. Honor STOP and HELP commands, and maintain internal Do Not Call lists, even though no official registry exists.
Always use the E.164 format, which starts with +677 followed by the local phone number. This ensures accurate delivery and compatibility with SMS API providers.
Process opt-out requests within 24 hours, send a confirmation message to the user, and keep records of opted-out numbers for at least 12 months. Regularly audit opt-out compliance.
Gambling, adult content, and unsubstantiated medical claims are prohibited. Financial services SMS must include clear disclaimers, and all messages should adhere to general cultural and religious sensitivities.
Alphanumeric sender IDs are supported and do not require pre-registration. They are generally preserved as sent, allowing businesses to use their brand name as the sender.
Keep messages concise (under 160 characters), use clear calls-to-action, identify your business, and personalize messages thoughtfully. Limit marketing frequency and respect local time zones.
While English is official, consider bilingual messages in both English and Solomon Islands Pijin for broader reach and engagement.
The standard rate limit is 30 messages per second. Use batch processing for large volumes and implement exponential backoff for error retries. Consider time-zone throttling.
Number portability is not available in the Solomon Islands. This simplifies message delivery as numbers remain tied to their original network provider.
Twilio, Sinch, MessageBird, and Plivo all provide reliable SMS API solutions for sending messages to Solomon Islands. Use their provided code examples and documentation.
Loading...
Solomon Islands SMS Best Practices, Compliance, and Features
Solomon Islands SMS Market Overview
Market Conditions: The Solomon Islands has a growing mobile market with SMS remaining a crucial communication channel due to its reliability and widespread accessibility. While smartphone adoption is increasing, traditional SMS continues to be preferred for business communications and notifications due to limited internet infrastructure in rural areas.
Key SMS Features and Capabilities in Solomon Islands
The Solomon Islands supports basic SMS functionality with concatenated messaging support, while some advanced features like two-way SMS have limitations.
Two-way SMS Support
Two-way SMS is not supported in the Solomon Islands through major SMS providers. This means businesses should design their SMS strategies around one-way communications only.
Concatenated Messages (Segmented SMS)
Support: Yes, concatenated messaging is fully supported in the Solomon Islands.
Message length rules: Messages are limited to 160 characters before splitting occurs.
Encoding considerations: Both GSM-7 and UCS-2 encoding are supported, with UCS-2 messages limited to 70 characters per segment.
MMS Support
MMS messages are automatically converted to SMS with an embedded URL link. This ensures compatibility across all devices while still allowing rich media content to be shared through linked web pages.
Recipient Phone Number Compatibility
Number Portability
Number portability is not available in the Solomon Islands. This means phone numbers remain tied to their original mobile network operators, which helps ensure reliable message delivery routing.
Sending SMS to Landlines
Sending SMS to landline numbers is not possible in the Solomon Islands. Attempts to send messages to landline numbers will result in a failed delivery and a 400 response error (code 21614) from SMS provider APIs.
Compliance and Regulatory Guidelines for SMS in Solomon Islands
The Telecommunications Commission of Solomon Islands (TCSI) oversees telecommunications regulations. While specific SMS marketing laws are limited, businesses should follow international best practices and general consumer protection guidelines.
Consent and Opt-In
Explicit Consent Required: You must obtain and document clear opt-in consent before sending marketing messages. Best practices include:
HELP/STOP and Other Commands
While not strictly required by local law, implementing standard opt-out keywords is strongly recommended:
Do Not Call / Do Not Disturb Registries
The Solomon Islands does not maintain an official Do Not Call registry. However, businesses should:
Time Zone Sensitivity
The Solomon Islands observes SBT (UTC+11). Best practices include:
Phone Numbers Options and SMS Sender Types for Solomon Islands
Alphanumeric Sender ID
Operator network capability: Supported
Registration requirements: Pre-registration not required, dynamic usage supported
Sender ID preservation: Sender IDs are generally preserved as sent
Long Codes
Domestic vs. International:
Sender ID preservation: Original sender ID is preserved for international long codes
Provisioning time: Typically immediate for international long codes
Use cases: Ideal for transactional messages and two-factor authentication
Short Codes
Support: Short codes are not currently supported in the Solomon Islands
Provisioning time: N/A
Use cases: N/A
Restricted SMS Content, Industries, and Use Cases
The Solomon Islands maintains general content restrictions aligned with cultural and religious values:
Content Filtering
Known Carrier Rules:
Best Practices to Avoid Filtering:
Best Practices for Sending SMS in Solomon Islands
Messaging Strategy
Sending Frequency and Timing
Localization
Opt-Out Management
Testing and Monitoring
SMS API integrations for Solomon Islands
Twilio
Twilio provides reliable SMS delivery to the Solomon Islands through their REST API. Here's how to implement it:
Sinch
Sinch offers comprehensive SMS capabilities for the Solomon Islands market:
MessageBird
MessageBird provides a straightforward API for sending SMS to the Solomon Islands:
Plivo
Plivo's API offers robust SMS functionality for the Solomon Islands:
API Rate Limits and Throughput
Error Handling and Reporting
Recap and Additional Resources
Key Takeaways
Compliance Priorities
Technical Considerations
Best Practices
Next Steps
Additional Information