Samoa SMS Guide - sms-compliance -

Samoa SMS Best Practices, Compliance, and Features

Samoa SMS Market Overview

Locale name:Samoa
ISO code:WS
RegionOceania
Mobile country code (MCC)549
Dialing Code+685

Market Conditions: Samoa has a growing mobile market with increasing SMS adoption for both personal and business communications. The primary mobile operators include Digicel Samoa and Vodafone Samoa (formerly Bluesky). While OTT messaging apps like WhatsApp and Facebook Messenger are gaining popularity, particularly in urban areas, SMS remains a reliable communication channel due to its universal reach and network stability. Android devices dominate the mobile market, though iOS usage is present among urban professionals and tourists.

Key SMS Features and Capabilities in Samoa

Samoa offers basic SMS functionality with some limitations on advanced features, making it important to understand the specific capabilities and restrictions when planning your messaging strategy.

Two-way SMS Support

Two-way SMS is not supported in Samoa according to current network capabilities. This means businesses should design their messaging strategies around one-way communications and provide alternative channels for customer responses when needed.

Concatenated Messages (Segmented SMS)

Support: Concatenated messaging is not supported in Samoa.
Message length rules: Due to the lack of concatenation support, you should keep messages within the standard SMS length limits.
Encoding considerations: It's recommended to use GSM-7 encoding to maximize character count and ensure broad compatibility.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link. This means that if you attempt to send multimedia content, recipients will receive a text message containing a link to view the content online. For optimal delivery and user experience, consider hosting images or media on a mobile-friendly webpage and sharing the link within your SMS message.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Samoa. This means mobile numbers remain tied to their original carrier, which can simplify message routing but requires customers to change numbers if they switch providers.

Sending SMS to Landlines

Sending SMS to landline numbers is not possible in Samoa. Attempts to send messages to landline numbers will result in a failed delivery and a 400 response with error code 21614. The message will not appear in logs, and your account will not be charged.

Compliance and Regulatory Guidelines for SMS in Samoa

SMS communications in Samoa are regulated by the Office of the Regulator under the Telecommunications Act 2005. The Office of the Regulator oversees telecommunications services and maintains the National Numbering Plan, which provides the framework for number management and allocation.

Explicit Consent Requirements:

  • Obtain clear, documented opt-in consent before sending any marketing messages
  • Maintain detailed records of when and how consent was obtained
  • Include your business name and purpose in the initial opt-in request
  • Provide clear terms and conditions regarding message frequency and content

Best Practices for Documentation:

  • Store consent records with timestamp and source
  • Keep opt-in confirmation messages for audit purposes
  • Regularly update and clean your consent database

HELP/STOP and Other Commands

While Samoa doesn't have specific regulatory requirements for HELP/STOP commands, implementing these features is considered best practice:

  • Support standard commands: STOP, CANCEL, UNSUBSCRIBE, HELP
  • Include both English and Samoan language options
  • Process opt-out requests within 24 hours
  • Send confirmation messages for both HELP and STOP requests

Do Not Call / Do Not Disturb Registries

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

  • Maintain their own suppression lists
  • Honor opt-out requests immediately
  • Document all opt-out requests with timestamps
  • Regularly clean contact lists to remove unsubscribed numbers

Time Zone Sensitivity

Samoa observes UTC+13 (WST - West Samoa Time). While there are no strict regulations regarding messaging hours:

  • Recommended Messaging Window: 8:00 AM to 8:00 PM WST
  • Emergency Messages: Can be sent outside standard hours if urgent
  • Cultural Considerations: Avoid sending during Sunday church hours (typically 9:00 AM to 1:00 PM)

Phone Numbers Options and SMS Sender Types for in Samoa

Alphanumeric Sender ID

Operator network capability: Supported for dynamic usage
Registration requirements: No pre-registration required
Sender ID preservation: Sender IDs are generally preserved as sent

Long Codes

Domestic vs. International:

  • Domestic long codes are not supported
  • International long codes are available with some restrictions

Sender ID preservation: Original sender IDs are typically maintained
Provisioning time: 1-2 business days for international long codes
Use cases: Recommended for transactional messages and customer support

Short Codes

Support: Short codes are not currently supported in Samoa
Provisioning time: Not applicable
Use cases: Not available for marketing or authentication purposes

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 may trigger spam filters
  • Multiple identical messages sent rapidly may be filtered

Best Practices to Avoid Filtering:

  • Use approved URL shorteners
  • Avoid excessive punctuation and all-caps text
  • Maintain consistent sending patterns
  • Include clear business identification in messages

Best Practices for Sending SMS in Samoa

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
  • Respect local holidays and cultural events
  • Avoid sending during church hours on Sundays
  • Space out messages to prevent recipient fatigue

Localization

  • Support both English and Samoan languages
  • Consider cultural context in message content
  • Use appropriate date and time formats
  • Respect local customs and traditions

Opt-Out Management

  • Process opt-outs within 24 hours
  • Send confirmation of opt-out requests
  • Maintain accurate suppression lists
  • Regular audit of opt-out compliance

Testing and Monitoring

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

SMS API integrations for Samoa

Twilio

Twilio provides a straightforward way to send SMS messages to Samoa using their REST API. Here's how to implement it:

import { Twilio } from 'twilio';

// Initialize Twilio client with your credentials
const client = new Twilio(
  process.env.TWILIO_ACCOUNT_SID,    // Your Twilio Account SID
  process.env.TWILIO_AUTH_TOKEN      // Your Twilio Auth Token
);

// Function to send SMS to Samoa
async function sendSMSToSamoa(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    // Ensure proper formatting for Samoa numbers (+685)
    const formattedNumber = to.startsWith('+685') ? to : `+685${to}`;

    const response = await client.messages.create({
      body: message,
      from: senderId,        // Your approved sender ID
      to: formattedNumber,
      // 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 robust SMS capabilities for Samoa through their REST API:

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

// Initialize Sinch client
const sinchClient = new SinchClient({
  projectId: process.env.SINCH_PROJECT_ID,
  apiToken: process.env.SINCH_API_TOKEN
});

// Function to send SMS via Sinch
async function sendSinchSMS(
  recipientNumber: string,
  messageText: string
): Promise<void> {
  try {
    const response = await sinchClient.sms.batches.send({
      sendSMSRequestBody: {
        to: [recipientNumber],    // Must include +685 prefix
        from: 'YourCompany',      // Your approved sender ID
        body: messageText,
        // Optional delivery report URL
        deliveryReport: 'URL'
      }
    });

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

MessageBird

MessageBird provides a reliable API for sending SMS to Samoa:

import { MessageBird } from 'messagebird';

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

// Function to send SMS via MessageBird
async function sendMessageBirdSMS(
  to: string,
  message: string,
  originator: string
): Promise<void> {
  const params = {
    originator: originator,    // Your sender ID
    recipients: [to],         // Must include +685 prefix
    body: message,
    // Optional parameters
    reportUrl: 'https://your-webhook.com/status'
  };

  try {
    const response = await new Promise((resolve, reject) => {
      messagebird.messages.create(params, (err, response) => {
        if (err) reject(err);
        resolve(response);
      });
    });

    console.log('MessageBird response:', response);
  } catch (error) {
    console.error('MessageBird Error:', error);
    throw error;
  }
}

Plivo

Plivo's API offers SMS capabilities for reaching Samoan numbers:

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,
  sourceNumber: string
): Promise<void> {
  try {
    const response = await plivo.messages.create({
      src: sourceNumber,     // Your Plivo number or sender ID
      dst: destination,      // Destination number with +685 prefix
      text: message,
      // Optional parameters
      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

When sending SMS to Samoa, consider these limitations:

  • Rate Limits:
    • Maximum 30 messages per second per sender ID
    • Daily quota varies by provider and plan
  • Throughput Management:
    • Implement exponential backoff for retries
    • Use queuing systems (e.g., Redis, RabbitMQ) for high volume
    • Batch messages when possible while respecting rate limits

Error Handling and Reporting

Best Practices for Error Management:

  • Implement comprehensive logging
  • Monitor delivery receipts
  • Set up automated alerts for high failure rates
  • Store message status updates in your database

Recap and Additional Resources

Key Takeaways

  1. Compliance Priorities:

    • Obtain explicit consent
    • Honor opt-out requests
    • Respect local time zones
    • Maintain proper documentation

  2. Technical Considerations:

    • Always use proper number formatting (+685)
    • Implement proper error handling
    • Monitor delivery rates
    • Test thoroughly before scaling

  3. Next Steps:

    • Review the Telecommunications Act 2005
    • Consult with local legal experts
    • Set up monitoring and reporting systems
    • Test with small volumes before full deployment

Additional Information