How to Send SMS to Samoa: Complete +685 Messaging Guide (2025)

Samoa SMS Market Overview: Mobile Operators and Network Coverage

Market conditions: Samoa operates a mobile duopoly with two carriers serving the +685 country code: Vodafone Samoa (formerly Bluesky Samoa) covers 98.5% of populated areas as the market leader, while Digicel Samoa achieved 100% population coverage with 4G/LTE in 2020. As of 2024, no 5G network is available – operators focus on 4G/LTE service quality. While OTT messaging apps like WhatsApp and Facebook Messenger gain popularity in urban areas, SMS remains reliable due to universal reach and network stability. Android devices dominate the market, with iOS present among urban professionals and tourists.

Mobile number format: Samoan mobile numbers consist of 7 digits using prefixes 7[1-35-7] and 8[3-7], formatted internationally as +685 XX XXXXX. Always include the +685 country code when sending SMS to Samoa from international platforms.

SMS Features and Technical Capabilities in Samoa

Understand Samoa's SMS functionality and limitations before planning your messaging strategy. The network supports basic SMS with restrictions on advanced features.

Two-Way SMS Support

Two-way SMS is not supported in Samoa. Design your messaging strategies around one-way communications and provide alternative channels (email, web forms, or WhatsApp) for customer responses. For interactive messaging solutions, consider implementing WhatsApp Business API integration alongside your SMS campaigns.

Concatenated Messages (Segmented SMS)

Concatenated messaging is not supported in Samoa. Keep messages within standard SMS length limits:

• GSM-7 encoding: 160 characters per message (recommended)
• UCS-2 encoding: 70 characters per message (for Unicode/emoji)

Messages exceeding these limits will be truncated or fail to deliver. Use GSM-7 encoding to maximize character count and ensure broad compatibility across both Vodafone Samoa and Digicel Samoa networks.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link. Recipients receive a text message containing a link to view the content online. For optimal delivery and user experience, host images or media on a mobile-friendly webpage and share the link within your SMS message.

Recipient Phone Number Compatibility

Number Portability

Mobile Number Portability (MNP) is not available in Samoa as of 2025. Mobile numbers remain tied to their original carrier, requiring customers to change numbers when switching between Vodafone Samoa and Digicel Samoa. The Office of the Regulator has indicated intentions to introduce MNP to promote competition, though no specific implementation timeline has been announced.

To identify which carrier owns a number, use the prefix patterns:

• Vodafone Samoa: Primarily 7[1-35-7] prefixes
• Digicel Samoa: Primarily 8[3-7] prefixes

Sending SMS to Landlines

You cannot send SMS to landline numbers in Samoa. Attempts will result in failed delivery with error code 21614. The message will not appear in logs, and your account will not be charged.

Landline numbers in Samoa typically use prefixes 2[0-9], 3[0-9], 4[0-9], and 5[0-9]. Filter these before sending SMS.

SMS Compliance and Regulatory Requirements in Samoa

The Office of the Regulator (OOTR), established in 2006 under the Telecommunications Act 2005 (amended 2014), regulates SMS communications in Samoa. The Office oversees telecommunications services and maintains the National Numbering Plan. The Act prohibits providing telecommunications services without a licence from the Regulator.

Consent and Opt-In Requirements

Explicit consent requirements for SMS marketing:

1. Obtain clear, documented opt-in consent before sending marketing messages
2. Maintain detailed records of when and how you obtained consent
3. Include your business name and purpose in the initial opt-in request
4. Provide clear terms about message frequency and content
5. Follow international SMS best practices and TCPA-style consent standards

Example opt-in message:

[YourBrand]: Reply YES to receive special offers & updates (2-4/month). Standard rates apply. Reply STOP to cancel. Terms: yoursite.com/terms

Documentation best practices:

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

HELP/STOP and Other Commands

While Samoa doesn't require HELP/STOP commands, implement these as best practice:

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

Example STOP response:

You've been unsubscribed from [YourBrand] messages. You won't receive further texts. Text HELP for assistance or START to resubscribe.

Example HELP response:

[YourBrand] SMS: Reply STOP to cancel, START to resubscribe. Msg frequency varies. Standard rates apply. Help: contact@yoursite.com or +685-XXXX

Do Not Call / Do Not Disturb Registries

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

• Maintain your 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 (West Samoa Time) year-round. Daylight saving time was discontinued in April 2021.

Recommended messaging windows:

• Standard messages: 8:00 AM to 8:00 PM WST (UTC+13)
• Emergency messages: Can be sent outside standard hours if urgent
• Avoid: Sunday church hours (9:00 AM to 1:00 PM) – Samoa observes Sunday as a day of rest with strong religious observance

UTC conversion examples:

• 8:00 AM WST = 7:00 PM previous day EST (UTC-5)
• 8:00 AM WST = 12:00 PM previous day PST (UTC-8)
• 8:00 AM WST = 7:00 PM previous day GMT (UTC+0)

Cultural holidays to avoid:

• New Year's Day (January 1–2)
• Good Friday and Easter Monday
• ANZAC Day (April 25)
• Independence Day (June 1–3)
• White Sunday (second Sunday in October)
• Christmas (December 25–26)

SMS Sender ID Options: Alphanumeric IDs, Long Codes, and Short Codes

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 Character limits: 3–11 characters, alphanumeric (no special characters except spaces) Allowed characters: A-Z, a-z, 0-9, spaces

Best practices:

• Use your brand name for recognition
• Keep it short (6–8 characters ideal)
• Avoid numbers only (use at least one letter)
• Test across both carriers before scaling

Long Codes

Domestic vs. International:

• Domestic long codes are not supported
• International long codes are available with 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

Recommended countries for international long codes:

• United States (+1)
• Australia (+61)
• New Zealand (+64)
• United Kingdom (+44)

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 Content and SMS Filtering Rules in Samoa

Restricted industries and content:

• Gambling and betting services
• Adult content or services
• Unauthorized financial services (services without proper licensing or regulatory approval)
• Political messaging without proper authorization
• Cryptocurrency promotions

Compliant vs. non-compliant examples:

✅ Compliant: "Your ABC Bank account balance is $500. Visit abc.com/account for details." ❌ Non-compliant: "Invest in crypto now! Guaranteed 300% returns. Click here: [suspicious link]"

✅ Compliant: "Your appointment with Dr. Smith is tomorrow at 2 PM. Reply CONFIRM or call us." ❌ Non-compliant: "Hot singles near you! Adult content available 24/7. [link]"

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

Commonly blocked keywords (avoid or use carefully):

• Free, winner, prize, claim now, urgent, act now
• Click here, limited time, guaranteed
• Cash, money, earn, investment (in promotional context)

Best practices to avoid filtering:

• Use approved URL shorteners (bit.ly, tinyurl.com, branded domains)
• Avoid excessive punctuation and all-caps text
• Maintain consistent sending patterns
• Include clear business identification in messages
• Avoid spam trigger words in combination

Best Practices for SMS Messaging Campaigns 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

Example message templates:

Transactional:

Hi [Name], your order #12345 has shipped. Track it here: [link]. Questions? Reply or call us at +685-XXXX. –[Brand]

Appointment reminder:

Reminder: Your appointment with [Provider] is tomorrow at [Time]. Reply CONFIRM to confirm or CANCEL to reschedule. –[Brand]

Marketing:

[Name], enjoy 20% off your next purchase. Use code SAVE20 at checkout: [link]. Expires [Date]. Reply STOP to opt out. –[Brand]

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 (9:00 AM to 1:00 PM WST)
• Space out messages to prevent recipient fatigue

Frequency guidelines by message type:

• Transactional: As needed (order confirmations, shipping updates)
• Appointment reminders: 24–48 hours before appointment
• Marketing: 2–4 messages per month maximum
• Urgent alerts: As needed (account security, critical updates)

Localization

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

Samoan language considerations:

• Samoan uses macrons (ā, ē, ī, ō, ū) – test encoding compatibility
• Common greetings: "Talofa" (hello), "Fa'afetai" (thank you), "Tofa" (goodbye)
• Formal tone is valued in business communications

Date and time formats:

• Use 12-hour format with AM/PM (preferred in Samoa)
• Date format: DD/MM/YYYY (e.g., 25/12/2025)

Opt-Out Management

• Process opt-outs within 24 hours
• Send confirmation of opt-out requests
• Maintain accurate suppression lists
• Conduct regular audits of opt-out compliance

Testing and Monitoring

Test messages across both carriers before launching campaigns:

Pre-launch testing checklist:

• Test on Vodafone Samoa numbers
• Test on Digicel Samoa numbers
• Verify sender ID appears correctly
• Confirm message length (under 160 characters for GSM-7)
• Test STOP/HELP functionality
• Verify links work on mobile devices
• Check special characters display correctly

Key metrics to track:

• Delivery rate: >95% is acceptable, <90% requires investigation
• Click-through rate: 2–5% typical for SMS campaigns
• Opt-out rate: <1% is good, >3% indicates issues
• Response time: Track for two-way alternative channels

Monitor by carrier:

• Track delivery rates separately for Vodafone Samoa and Digicel Samoa
• Identify carrier-specific filtering issues
• Optimize routing based on performance data

SMS API Integration: Twilio, Sinch, MessageBird, and Plivo

Twilio

Twilio provides SMS capabilities for Samoa using their REST API:

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) {
    // Handle Samoa-specific error codes
    if (error.code === 21614) {
      console.error('Cannot send SMS to landline numbers in Samoa');
    } else if (error.code === 21408) {
      console.error('Permission denied – check sender ID approval');
    } else if (error.code === 21610) {
      console.error('Message blocked by carrier spam filter');
    } else {
      console.error('Error sending message:', error);
    }
    throw error;
  }
}

// Webhook handler for delivery status callbacks
app.post('/status', (req, res) => {
  const { MessageStatus, MessageSid, To, ErrorCode } = req.body;

  console.log(`Message ${MessageSid} to ${To}: ${MessageStatus}`);

  if (ErrorCode) {
    console.error(`Delivery failed with error ${ErrorCode}`);
    // Store failure for retry logic
  }

  res.sendStatus(200);
});

Sinch

Sinch offers robust SMS capabilities for Samoa:

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 with error handling
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: 'https://your-webhook.com/delivery'
      }
    });

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

    // Implement exponential backoff for retries
    if (error.statusCode === 429) {
      console.log('Rate limit exceeded – implementing backoff');
      await exponentialBackoff(sendSinchSMS, recipientNumber, messageText);
    }

    throw error;
  }
}

// Exponential backoff implementation
async function exponentialBackoff(
  fn: Function,
  ...args: any[]
): Promise<void> {
  const maxRetries = 3;
  let retryCount = 0;

  while (retryCount < maxRetries) {
    try {
      await fn(...args);
      return;
    } catch (error) {
      retryCount++;
      const delay = Math.pow(2, retryCount) * 1000; // 2s, 4s, 8s
      console.log(`Retry ${retryCount}/${maxRetries} after ${delay}ms`);
      await new Promise(resolve => setTimeout(resolve, delay));
    }
  }

  throw new Error('Max retries exceeded');
}

MessageBird

MessageBird provides reliable SMS delivery 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);
        else resolve(response);
      });
    });

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

Plivo

Plivo's API offers SMS capabilities for 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 Provider Comparison

SMS Pricing for Samoa (+685): Costs and Optimization

Understanding SMS pricing helps with budget planning and cost optimization for messaging campaigns to Samoa.

Twilio SMS Pricing (October 2025):

• Outbound SMS: $0.2369 per segment to Samoa (+685)
• Inbound SMS: $0.2369 per segment from Samoa (+685)
• Failed Message Fee: $0.001 per message that terminates in "Failed" status
• Pricing Note: Text messages are charged per segment; prices subject to change

Character Limits and Segmentation:

• GSM-7 encoding: 160 characters per segment (recommended for Samoa)
• UCS-2 encoding: 70 characters per segment (for Unicode/emoji)
• Messages exceeding these limits are automatically split into multiple segments, with each segment billed separately

Cost Optimization Tips:

• Keep messages under 160 characters when using GSM-7 encoding to avoid multi-segment charges
• Use alphanumeric sender IDs (supported without pre-registration) instead of purchasing dedicated numbers
• Monitor delivery rates by carrier to optimize routing and reduce failed message costs
• Test messages thoroughly before scaling to minimize failed delivery fees

Cost calculator formula:

Total Cost = (Number of Recipients × Segments per Message × Price per Segment)

Example: 1,000 recipients × 1 segment × $0.2369 = $236.90
Example: 1,000 recipients × 2 segments × $0.2369 = $473.80

Pricing sources: Twilio SMS Pricing – Samoa, verified October 2025

API Rate Limits and Throughput

When sending SMS to Samoa, consider these limitations:

Rate limits by provider:

• Twilio: 60 messages per second (default), upgradeable to 100+
• Sinch: 30 messages per second per sender ID
• MessageBird: 50 messages per second (varies by plan)
• Plivo: 200 messages per second (varies by plan)

Throughput management strategies:

1. Implement exponential backoff (see Sinch example above)
2. Use queuing systems (Redis, RabbitMQ, Amazon SQS)
3. Batch messages while respecting rate limits

Queue implementation example (using Redis):

import Queue from 'bull';

const smsQueue = new Queue('samoa-sms', {
  redis: { host: 'localhost', port: 6379 }
});

// Add messages to queue
smsQueue.add('send-sms', {
  to: '+68571XXXXX',
  message: 'Your message here',
  senderId: 'YourBrand'
}, {
  attempts: 3,
  backoff: { type: 'exponential', delay: 2000 }
});

// Process queue with rate limiting
smsQueue.process('send-sms', 30, async (job) => {
  await sendSMSToSamoa(job.data.to, job.data.message, job.data.senderId);
});

Error Handling and Reporting

Common error codes for Samoa:

Error handling implementation:

async function sendWithErrorHandling(
  to: string,
  message: string
): Promise<void> {
  try {
    await sendSMSToSamoa(to, message, 'YourBrand');
  } catch (error) {
    // Log error with context
    await logError({
      timestamp: new Date(),
      recipient: to,
      message: message,
      errorCode: error.code,
      errorMessage: error.message
    });

    // Alert on high failure rates
    const recentFailures = await getFailureRate(60); // last 60 minutes
    if (recentFailures > 0.1) { // >10% failure rate
      await sendAlert('High SMS failure rate detected for Samoa');
    }

    // Decide whether to retry
    const retryableCodes = [30001, 30003, 30004]; // Temporary errors
    if (retryableCodes.includes(error.code)) {
      await addToRetryQueue(to, message);
    }
  }
}

Frequently Asked Questions (FAQ)

Which mobile operators serve Samoa and what is their coverage?

Samoa has two mobile operators as of 2025: Vodafone Samoa (formerly Bluesky Samoa) covers 98.5% of populated areas and is the market leader, while Digicel Samoa achieved 100% population coverage with 4G/LTE in 2020. Both operators provide 4G/LTE service, but no 5G network is available in Samoa as of 2024.

What is the correct phone number format for sending SMS to Samoa?

Samoan mobile numbers consist of 7 digits with prefixes 7[1-35-7] and 8[3-7]. The international format is +685 XX XXXXX (e.g., +685 71 12345). Always include the country code +685 when sending SMS to Samoa from international API providers.

Does Samoa support two-way SMS messaging and concatenated messages?

No. Two-way SMS is not supported in Samoa – design one-way communication strategies and provide alternative response channels. Concatenated messages (long SMS) are also not supported. Keep messages within standard SMS length limits (160 characters for GSM-7 encoding, 70 characters for UCS-2 encoding).

Is mobile number portability (MNP) available in Samoa?

Mobile Number Portability is not available in Samoa as of 2025. Mobile numbers remain tied to their original carrier (Vodafone Samoa or Digicel Samoa). The Office of the Regulator has indicated future plans to introduce MNP, but no implementation timeline has been announced.

What timezone should I use when scheduling SMS campaigns to Samoa?

Samoa observes UTC+13 (West Samoa Time) year-round without daylight saving time, which was discontinued in April 2021. Schedule messages between 8:00 AM and 8:00 PM WST, and avoid Sunday church hours (9:00 AM to 1:00 PM) as Samoa observes Sunday as a day of rest with strong religious observance.

How much does it cost to send SMS messages to Samoa?

As of October 2025, Twilio charges $0.2369 per segment for both outbound and inbound SMS to/from Samoa (+685). Messages using GSM-7 encoding allow 160 characters per segment, while UCS-2 encoding (for Unicode/emoji) reduces this to 70 characters per segment. Failed messages incur a $0.001 fee.

Do I need to register alphanumeric sender IDs for Samoa?

No pre-registration is required for alphanumeric sender IDs in Samoa. Sender IDs are generally preserved as sent and supported for dynamic usage, making them a cost-effective option compared to purchasing dedicated phone numbers for SMS campaigns.

What regulatory body oversees SMS communications in Samoa?

The Office of the Regulator (OOTR), established in 2006, oversees telecommunications in Samoa under the Telecommunications Act 2005 (amended 2014). The OOTR maintains the National Numbering Plan and requires explicit consent for marketing messages, though Samoa does not have specific STOP/HELP command regulations or a Do Not Call registry.

Can I send SMS messages to landline numbers in Samoa?

No. You cannot send SMS to landline numbers in Samoa. Attempts will result in failed delivery with error code 21614. The message will not appear in logs, and your account will not be charged. Filter landline numbers (prefixes 2-5) before sending.

What are the restricted content types and industries for SMS in Samoa?

Restricted content includes gambling and betting services, adult content, unauthorized financial services (services without proper licensing), political messaging without authorization, and cryptocurrency promotions. Messages containing certain keywords, URLs from unknown domains, or multiple identical messages sent rapidly may be filtered by carrier spam systems.

What should I do if my messages are being filtered or blocked?

If your messages are being filtered:

1. Review content for spam trigger words
2. Use approved URL shorteners or branded domains
3. Avoid all-caps text and excessive punctuation
4. Include clear business identification
5. Test with small volumes first
6. Contact your API provider for carrier feedback
7. Ensure you have proper consent documentation

How do I handle message delivery failures in Samoa?

Implement comprehensive error handling:

1. Log all errors with context (timestamp, recipient, error code)
2. Set up alerts for failure rates >10%
3. Retry only on temporary errors (codes 30001, 30003, 30004)
4. Filter out invalid numbers after first failure
5. Monitor delivery rates by carrier
6. Review filtered content if blocking persists

Recap and Additional Resources

Key Takeaways

1. Compliance priorities:

   • Obtain explicit consent before sending marketing messages
   • Honor opt-out requests within 24 hours
   • Respect local time zones (UTC+13, no DST)
   • Avoid Sunday church hours (9:00 AM to 1:00 PM WST)
   • Maintain proper documentation for all consent and opt-outs

2. Technical considerations:

   • Always use proper number formatting (+685 XX XXXXX)
   • Keep messages under 160 characters (GSM-7 encoding)
   • Two-way SMS is not supported – provide alternative channels
   • Implement comprehensive error handling and retry logic
   • Monitor delivery rates across both carriers
   • Test thoroughly before scaling campaigns

3. Cost optimization:

   • Use alphanumeric sender IDs (no registration required)
   • Keep messages under 160 characters to avoid segmentation
   • Monitor and optimize delivery rates to reduce failed message costs
   • Test with small volumes before full deployment

Implementation Checklist

Phase 1: Setup (Week 1)

• Choose API provider (Twilio, Sinch, MessageBird, or Plivo)
• Set up development environment and credentials
• Configure webhook endpoints for delivery status
• Implement basic error handling and logging

Phase 2: Compliance (Week 2)

• Create opt-in/opt-out workflows
• Set up consent database with timestamps
• Implement STOP/HELP command processing
• Create suppression list management system
• Review content against restricted categories

Phase 3: Testing (Week 3)

• Test on Vodafone Samoa numbers
• Test on Digicel Samoa numbers
• Verify sender ID preservation
• Test message length limits
• Test special characters and encoding
• Verify opt-out functionality
• Test error handling and retry logic

Phase 4: Launch (Week 4)

• Start with small test group (50–100 recipients)
• Monitor delivery rates and errors
• Collect user feedback
• Optimize based on results
• Gradually scale to full audience

Phase 5: Monitoring (Ongoing)

• Track delivery rates by carrier
• Monitor opt-out rates
• Review error logs weekly
• Audit consent database monthly
• Update suppression lists regularly

Additional Information

Official resources:

• Office of the Regulator Samoa
• Samoa National Numbering Plan
• Telecommunications Act 2005

Industry guidelines:

• Mobile Marketing Association Guidelines
• GSMA Messaging Services Guidelines

API provider documentation:

• Twilio SMS API Documentation
• Sinch SMS API Documentation
• MessageBird SMS API Documentation
• Plivo SMS API Documentation

Support channels:

• Twilio Support: support@twilio.com
• Sinch Support: support@sinch.com
• MessageBird Support: support@messagebird.com
• Plivo Support: support@plivo.com