Tuvalu SMS Best Practices, Compliance, and Features

Tuvalu SMS Market Overview

Market Conditions: Send SMS messages to Tuvalu through the Tuvalu Telecommunications Corporation (TTC), the sole provider of mobile, fixed telephone, and internet services across the island nation. Understanding Tuvalu's SMS market and TTC network requirements is essential for successful SMS integration and delivery.

SMS Pricing (2025): Expect to pay between $0.0720 to $0.1760 USD per SMS message, depending on your provider and sender ID type:

• International Numbers: $0.1760 per outbound SMS (Source: Twilio SMS Pricing)
• Alphanumeric Sender IDs: $0.1760 per outbound SMS (Source: Twilio SMS Pricing)
• Alternative Providers: $0.0720–$0.1093 per message (Source: Unimatrix, Forward Value SMS)

Delivery Times: SMS delivery to Tuvalu typically occurs within seconds to minutes under normal network conditions. Actual delivery times depend on TTC network load, satellite backhaul capacity (currently ~510 Mbps split across providers), and the specific island location. Outer islands may experience slightly longer delivery times due to satellite relay requirements.

Current Market Statistics (2025):

• Population: 9,492 (2025 projection) (Source: DataReportal Digital 2025 Tuvalu)
• Mobile Penetration: 50.5% with 4,833 cellular mobile connections (Source: DataReportal Digital 2025 Tuvalu)
• Internet Penetration: 74.3% with 7,106 internet users at the start of 2025 (Source: DataReportal Digital 2025 Tuvalu)
• Device Preference: Target Android devices primarily, as they outnumber iOS devices among Tuvalu's mobile users

Network Infrastructure: Build your SMS integration to work with TTC's 3G and 4G networks:

• 3G Services: UMTS over Band 8 (900 MHz), operational since 2014
• 4G Services: LTE over Band 5 (850 MHz), launched in April 2018 (Source: TTC official announcements)
• Coverage Areas: Reach users on Funafuti, Vaitupu, Nukulaelae, Nanumea, and Niutao islands
• Coverage Quality: Broadband coverage averages 60-70% on each island served by TTC WiFi network (Source: Tuvalu National ICT Policy 2021)
• Network Reliability: TTC relies on satellite backhaul (ABS and Kacific) for international connectivity. The ongoing Tuvalu Vaka submarine cable project (delivered 2025) will improve reliability with fiber connectivity.

Phone Number Format: Format Tuvalu phone numbers as +688 (country code) followed by 5 to 7 digits for the subscriber number. Identify the service type by the first digit of the subscriber number:

• 2 = Landline services
• 7 = Mobile services
• 9 = Premium rate services

Validation Pattern: Use this regex pattern to validate Tuvalu phone numbers: ^\+688[2-79]\d{4,6}$ or for subscriber numbers only: ^[2-79]\d{4,6}$ (matches 5-7 digit numbers starting with 2, 7, or 9).

Use SMS for official and business communications, while recognizing that data connectivity enables OTT messaging apps as an alternative channel.

Key SMS Features and Capabilities in Tuvalu

Understand Tuvalu's SMS functionality and limitations when building your integration with the TTC network infrastructure.

Two-way SMS Support

Expect limited two-way SMS capabilities for international communications. Twilio does not support inbound SMS in Tuvalu (Source: Twilio Guidelines). Use two-way messaging only within the TTC network locally – international two-way messaging is restricted due to infrastructure limitations and TTC's satellite-based backhaul constraints.

Concatenated Messages (Segmented SMS)

Support: Send concatenated messages, though availability varies by sender ID type (Source: Twilio Guidelines).

Message length rules: Apply standard SMS length limits:

• GSM-7 encoding: 160 characters for single SMS; 153 characters per segment for concatenated messages
• Unicode (UCS-2) encoding: 70 characters for single SMS; 67 characters per segment for concatenated messages

Maximum segments: Industry best practice limits concatenated messages to 6 segments (approximately 918 characters for GSM-7, 402 characters for Unicode) to ensure reliable delivery across carriers.

Encoding considerations: Choose between GSM-7 and UCS-2 encodings, with message splitting occurring at different thresholds based on your chosen encoding.

Example concatenation:

MMS Support

Expect MMS messages to automatically convert to SMS with an embedded URL link (Source: Twilio Guidelines). This conversion ensures delivery compatibility while allowing you to share rich media content via clickable links. Your SMS provider hosts the media file and generates a shortened URL that is included in the SMS body.

Recipient Phone Number Compatibility

Number Portability

Note that number portability does not exist in Tuvalu (Source: Twilio Guidelines). All mobile numbers remain with TTC, simplifying your routing logic but limiting user flexibility.

Sending SMS to Landlines

Avoid sending SMS to landline numbers (starting with digit 2) – these attempts will fail. Expect a 400 response error (code 21614) through the API, with no message delivery and no charges applied (Source: Twilio Guidelines).

Validation example:

function isValidTuvaluMobile(phone: string): boolean {
  // Remove +688 prefix if present
  const subscriber = phone.replace(/^\+?688/, '');

  // Check: 5-7 digits, starts with 7 (mobile) or 9 (premium)
  const mobilePattern = /^[79]\d{4,6}$/;
  return mobilePattern.test(subscriber);
}

Tuvalu SMS Compliance and Regulatory Requirements

Follow the Tuvalu Telecommunications Corporation Act framework when sending SMS communications. While specific SMS marketing regulations are limited, implement general best practices and TTC guidelines for message delivery.

Non-Compliance Penalties: The Tuvalu Telecommunications Corporation Act and related Telephone Regulations establish penalties for violations:

• Unauthorized telecommunications operations: Fines and potential imprisonment for up to 12 months
• License violations: Fines of up to $200 (Source: Tuvalu Telephone Regulations)
• Regulatory enforcement: The Department of ICT regulates telecommunications and ensures compliance with national standards. An independent Telecommunication Regulator is planned to oversee licensee performance (Source: Tuvalu National ICT Policy)

Consent and Opt-In

Explicit Consent Requirements:

• Obtain clear, documented opt-in consent before sending any marketing or non-essential messages
• Maintain detailed records of when and how you obtained consent
• Include clear terms of service and privacy policy references during opt-in
• Provide transparent information about message frequency and content type

HELP/STOP and Other Commands

Implement standard opt-out mechanisms as best practice, even though Tuvalu doesn't mandate specific keywords:

• Support universal STOP commands for immediate opt-out
• Implement HELP keyword responses with service information
• Process opt-out requests in both English and Tuvaluan
• Confirm opt-out status with a final confirmation message

Sample templates:

Do Not Call / Do Not Disturb Registries

Maintain your own suppression lists, as Tuvalu does not operate an official Do Not Call registry:

• Build and maintain your own suppression lists of opted-out numbers
• Honor opt-out requests immediately and permanently
• Document all opt-out requests with timestamps
• Regularly clean your contact lists to remove inactive or opted-out numbers

Time Zone Sensitivity

Schedule messages appropriately for Tuvalu's UTC+12 timezone with no daylight saving time (Source: Time and Date):

• Send messages between 8:00 AM and 8:00 PM local time
• Avoid messages during religious or cultural observances
• Limit emergency messages outside of business hours
• Schedule messages with awareness that Tuvalu maintains the same timezone year-round

2025 Public Holidays to Avoid (Source: Time and Date):

• January 1: New Year's Day
• March 10: Commonwealth Day
• April 18: Good Friday
• April 21: Easter Monday
• May 12: Gospel Day
• June 14: Anniversary of the Birthday of the Sovereign
• August 4: National Children's Day
• October 1-2: Tuvalu Day and Tuvalu Day Holiday
• November 10: Heir to the Throne's Birthday
• December 25: Christmas Day
• December 26: Boxing Day

Timezone conversion example:

import { zonedTimeToUtc, utcToZonedTime, format } from 'date-fns-tz';

function scheduleSMSForTuvalu(localTime: Date): Date {
  const tuvaluTZ = 'Pacific/Funafuti'; // UTC+12
  // Convert local time to Tuvalu timezone
  const tuvaluTime = utcToZonedTime(localTime, tuvaluTZ);
  const hour = tuvaluTime.getHours();

  // Check if within acceptable hours (8 AM - 8 PM)
  if (hour < 8 || hour >= 20) {
    throw new Error('Message scheduled outside acceptable hours (8 AM - 8 PM Tuvalu time)');
  }

  return localTime;
}

Tuvalu Phone Number Formats and Sender ID Options

Alphanumeric Sender ID

Operator network capability: Not supported for pre-registration or dynamic use (Source: Twilio Guidelines) Registration requirements: Dynamic usage is not supported Sender ID preservation: Not applicable

Why not supported: Alphanumeric sender IDs require carrier-level registration systems that TTC has not implemented. Alternative: Use international numbers or coordinate directly with TTC for custom sender ID arrangements.

Long Codes

Domestic vs. International:

• Use domestic long codes – operator networks support them
• Expect limited support for international long codes
• Note: Twilio does not currently support domestic long codes for Tuvalu (Source: Twilio Guidelines)

Sender ID preservation: Varies by carrier and message type Provisioning time: Domestic long codes through TTC typically require 2-4 weeks for provisioning and testing, subject to TTC administrative processes Use cases: Use long codes for transactional and verification messages

How to acquire: Contact TTC directly through their official channels or work with regional telecommunications brokers who have established relationships with Pacific island carriers.

Short Codes

Support: Not currently supported in Tuvalu (Source: Twilio Guidelines) Provisioning time: Not applicable Use cases: Not available for marketing or authentication

Restricted SMS Content and Filtering in Tuvalu

Align your content with telecommunications standards when sending SMS to Tuvalu:

• Avoid gambling and betting content (prohibited)
• Never send adult content (strictly forbidden)
• Verify financial services messages with additional checks: use established sender IDs, include clear identification of your financial institution, and ensure compliance with regional financial messaging standards
• Maintain privacy standards for healthcare messages: avoid including sensitive medical details in SMS; use secure links to patient portals instead

Content Filtering

Carrier Filtering:

• Expect TTC to implement basic content filtering
• Know that messages containing restricted content may be blocked
• Use URLs from reputable domains only

Best Practices to Avoid Filtering:

• Avoid excessive punctuation (more than 2 consecutive punctuation marks: "!!!", "???")
• Use clear, professional language
• Include your company name in messages
• Maintain consistent sending patterns
• Avoid spam trigger words: "FREE!!!", "Act now!!!", "Limited time!!!", excessive capitalization

Best Practices for Sending SMS to Tuvalu

Messaging Strategy

• Keep your messages under 160 characters when possible
• Include clear calls-to-action
• Maintain consistent branding across all messages
• Use personalization thoughtfully to engage recipients
• Cultural consideration: Tuvaluans value community and respect for elders. Use respectful, inclusive language that acknowledges family and community connections rather than aggressive sales tactics.

Sending Frequency and Timing

• Limit your messages to 2 – 3 per week maximum for marketing; transactional messages have no strict frequency limit
• Respect local holidays and customs (see holiday list above)
• Avoid sending during off-hours (before 8:00 AM or after 8:00 PM)
• Space out your messages appropriately to prevent fatigue
• Note: Given Tuvalu's small population (4,833 mobile connections), over-messaging can quickly lead to brand fatigue

Localization

• Support both English and Tuvaluan languages in your messaging
• Consider cultural context in your message content
• Use appropriate date and time formats (UTC+12)
• Respect local customs and sensitivities

Language Support:

• English: Widely used for business and government communications
• Tuvaluan: Preferred for community and cultural messages. Translation resources are limited; consider working with local partners or translation services like MarsTranslation or Technovate Translations for certified Tuvaluan translations
• Script: Use standard Latin alphabet; both languages use the same character set (GSM-7 compatible)

Cultural Messaging Examples:

• ✅ Appropriate: "Malo! Te komponi nei e fakamanuia koe mo te fāmili. [Company] service available now."
• ❌ Inappropriate: "BUY NOW!!! Limited spots! Don't miss out!!!" (too aggressive, not culturally aligned)

Opt-Out Management

• Process opt-outs within 24 hours of receiving them
• Maintain accurate opt-out records in your database
• Provide clear opt-out instructions in every message
• Confirm opt-out status to users with a final message

Testing and Monitoring

• Test your messages across different devices before deployment
• Monitor delivery rates regularly to identify issues
• Track engagement metrics (opens, clicks, conversions)
• Analyze opt-out patterns to improve messaging
• Adjust your strategy based on performance data

Delivery Rate Benchmarks:

• Good: 95%+ delivery rate for valid mobile numbers
• Acceptable: 85-95% delivery rate
• Poor: <85% delivery rate (investigate sender ID issues, content filtering, or number validation problems)

Recommended monitoring tools: Twilio Console, Sinch Dashboard, MessageBird Analytics, or third-party services like SMS tracking platforms

SMS API Integration for Tuvalu: Provider Comparison

Twilio SMS API for Tuvalu

Use Twilio's straightforward REST API to send SMS messages to Tuvalu. Authenticate with your Account SID and Auth Token. Pricing: $0.1760 per outbound SMS (Source: Twilio Pricing).

import { Twilio } from 'twilio';

// Initialize the client with your credentials
const client = new Twilio(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN);

// Validate Tuvalu mobile number
function validateTuvaluMobile(phone: string): boolean {
  // Check E.164 format with +688 prefix and 5-7 digit mobile number
  const pattern = /^\+688[79]\d{4,6}$/;
  return pattern.test(phone);
}

// Function to send SMS to Tuvalu with validation
async function sendSMSToTuvalu(to: string, message: string) {
  try {
    // Format number to E.164 format for Tuvalu (+688)
    const formattedNumber = to.startsWith('+688') ? to : `+688${to}`;

    // Validate number format and mobile prefix
    if (!validateTuvaluMobile(formattedNumber)) {
      throw new Error('Invalid Tuvalu mobile number. Must be +688 followed by 5-7 digits starting with 7 or 9');
    }

    const response = await client.messages.create({
      body: message,
      to: formattedNumber,
      from: process.env.TWILIO_PHONE_NUMBER,
      // Optional: Set status callback URL
      statusCallback: 'https://your-domain.com/status-callback'
    });

    console.log(`Message sent successfully! SID: ${response.sid}`);
    return response;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

// Handle status callbacks
app.post('/status-callback', (req, res) => {
  const { MessageSid, MessageStatus, ErrorCode } = req.body;

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

  if (ErrorCode === '21614') {
    console.error('Cannot send SMS to landline number');
  }

  res.sendStatus(200);
});

Sinch SMS API for Tuvalu

Send SMS through Sinch's REST API using API Token authentication.

import axios from 'axios';

interface SinchSMSResponse {
  id: string;
  to: string[];
  from: string;
  created_at: string;
  delivery_report: string;
}

class SinchSMSService {
  private readonly apiToken: string;
  private readonly serviceId: string;
  private readonly baseUrl: string = 'https://sms.api.sinch.com/xms/v1';

  constructor(apiToken: string, serviceId: string) {
    this.apiToken = apiToken;
    this.serviceId = serviceId;
  }

  // Validate Tuvalu phone number
  private validateNumber(phone: string): boolean {
    const pattern = /^\+688[79]\d{4,6}$/;
    return pattern.test(phone);
  }

  async sendSMS(to: string, message: string): Promise<SinchSMSResponse> {
    try {
      const formattedNumber = to.startsWith('+688') ? to : `+688${to}`;

      if (!this.validateNumber(formattedNumber)) {
        throw new Error('Invalid Tuvalu mobile number format');
      }

      const response = await axios.post<SinchSMSResponse>(
        `${this.baseUrl}/${this.serviceId}/batches`,
        {
          from: 'YourSenderID',
          to: [formattedNumber],
          body: message
        },
        {
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Content-Type': 'application/json'
          }
        }
      );

      return response.data;
    } catch (error) {
      if (axios.isAxiosError(error)) {
        console.error('Sinch API Error:', error.response?.data);
      }
      throw error;
    }
  }
}

MessageBird SMS API for Tuvalu

Integrate MessageBird's SMS capabilities through their REST API with API Key authentication.

import messagebird from 'messagebird';

interface MessageBirdResponse {
  id: string;
  href: string;
  direction: string;
  type: string;
  originator: string;
  body: string;
  reference: string;
  recipients: {
    totalCount: number;
    totalSentCount: number;
    totalDeliveredCount: number;
  };
}

class MessageBirdService {
  private client: messagebird.MessageBird;

  constructor(apiKey: string) {
    this.client = messagebird(apiKey);
  }

  private validateTuvaluMobile(phone: string): boolean {
    const pattern = /^\+?688[79]\d{4,6}$/;
    return pattern.test(phone);
  }

  sendSMS(to: string, message: string): Promise<MessageBirdResponse> {
    return new Promise((resolve, reject) => {
      const formattedNumber = to.startsWith('+688') ? to : `+688${to}`;

      if (!this.validateTuvaluMobile(formattedNumber)) {
        reject(new Error('Invalid Tuvalu mobile number'));
        return;
      }

      this.client.messages.create({
        originator: 'YourName',
        recipients: [formattedNumber],
        body: message
      }, (err: Error | null, response: MessageBirdResponse) => {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo SMS API for Tuvalu

Authenticate with Plivo's SMS API using your Auth ID and Auth Token.

import plivo from 'plivo';

interface PlivoSMSResponse {
  message: string;
  message_uuid: string[];
  api_id: string;
}

class PlivoSMSService {
  private client: plivo.Client;

  constructor(authId: string, authToken: string) {
    this.client = new plivo.Client(authId, authToken);
  }

  private validateTuvaluMobile(phone: string): boolean {
    const pattern = /^\+688[79]\d{4,6}$/;
    return pattern.test(phone);
  }

  async sendSMS(to: string, message: string): Promise<PlivoSMSResponse> {
    try {
      const formattedNumber = to.startsWith('+688') ? to : `+688${to}`;

      if (!this.validateTuvaluMobile(formattedNumber)) {
        throw new Error('Invalid Tuvalu mobile number format');
      }

      const response = await this.client.messages.create({
        src: 'YourSourceNumber', // Your Plivo number
        dst: formattedNumber,
        text: message,
      });

      return response as PlivoSMSResponse;
    } catch (error) {
      console.error('Plivo SMS Error:', error);
      throw error;
    }
  }
}

API Provider Comparison

API Rate Limits and Throughput

Rate limits vary by provider and account tier. Common limits:

• Twilio: Default 1 message/second per destination; higher tiers support 100+ msgs/second
• Sinch: Account-specific limits, typically 10-50 msgs/second
• MessageBird: 10-20 msgs/second for standard accounts
• General recommendation: Implement rate limiting at 1 msg/second initially, monitor delivery success, then increase

Throughput Management Strategies:

import Queue from 'better-queue';

interface QueuedMessage {
  to: string;
  text: string;
  retries?: number;
}

// Queue with retry logic
const smsQueue = new Queue<QueuedMessage>(async function (message, cb) {
  try {
    await sendSMS(message.to, message.text);
    cb(null, { success: true, messageId: message.to });
  } catch (error) {
    const retries = message.retries || 0;

    if (retries < 3) {
      // Requeue with exponential backoff
      setTimeout(() => {
        smsQueue.push({ ...message, retries: retries + 1 });
      }, Math.pow(2, retries) * 1000);
    } else {
      // Move to dead letter queue after 3 retries
      console.error('Max retries reached for', message.to);
      await deadLetterQueue.push(message);
    }

    cb(error);
  }
}, {
  concurrent: 1,
  interval: 1000, // 1 second between messages
  maxTimeout: 30000 // 30 second timeout per message
});

// Usage
smsQueue.push({ to: '+6887123456', text: 'Hello Tuvalu!' });

Error Handling and Reporting

// Common Tuvalu-specific error codes
interface SMSError {
  code: string;
  message: string;
  timestamp: Date;
  destination?: string;
}

const TUVALU_ERROR_CODES = {
  '21614': 'Cannot send SMS to landline number',
  '21408': 'Permission to send SMS not enabled for region',
  '21211': 'Invalid phone number format',
  '30003': 'Unreachable destination (network issue)',
  '30005': 'Unknown destination carrier',
  '30008': 'Message delivery failed (filtered or rejected)',
};

class SMSErrorHandler {
  private errors: SMSError[] = [];

  logError(code: string, message: string, destination?: string) {
    const error: SMSError = {
      code,
      message: TUVALU_ERROR_CODES[code] || message,
      timestamp: new Date(),
      destination
    };

    this.errors.push(error);
    console.error(`SMS Error [${code}]: ${error.message}`, { destination });

    // Alert on critical errors
    if (['21614', '30008'].includes(code)) {
      this.sendAlert(error);
    }
  }

  private sendAlert(error: SMSError) {
    // Integrate with monitoring service (e.g., Datadog, Sentry, PagerDuty)
    console.error('CRITICAL SMS ERROR:', error);
  }

  getErrorReport(): SMSError[] {
    return this.errors;
  }

  getErrorStats() {
    const stats = this.errors.reduce((acc, error) => {
      acc[error.code] = (acc[error.code] || 0) + 1;
      return acc;
    }, {} as Record<string, number>);

    return stats;
  }
}

Quick Start Checklist and Resources

Key Takeaways for Tuvalu SMS Integration:

• Format phone numbers as +688 followed by 5-7 digits; validate that mobile numbers start with 7 or 9
• Expect SMS costs of $0.0720-$0.1760 per message depending on provider
• Delivery times are typically seconds to minutes, but can be affected by satellite backhaul capacity
• Two-way SMS is not supported for international communications
• Number portability does not exist; all mobile numbers remain with TTC
• Respect UTC+12 timezone and avoid sending during public holidays
• Keep messages under 160 characters (GSM-7) or 70 characters (Unicode) to avoid segmentation
• Implement comprehensive error handling for Tuvalu-specific error codes
• Monitor delivery rates; aim for 95%+ success rate

Next Steps to Launch Your Tuvalu SMS Integration:

1. Review the Tuvalu Telecommunications Corporation Act and compliance requirements
2. Choose your SMS API provider (Twilio, Sinch, MessageBird, or Plivo) based on your volume and features
3. Implement proper opt-out handling with STOP/HELP commands in English and Tuvaluan
4. Set up delivery monitoring and webhook callbacks to track message status
5. Test thoroughly across different device types before production deployment

Pre-Launch Checklist:

• Phone number validation implemented with regex pattern
• Landline filtering in place (reject numbers starting with 2)
• Message length validation (160 chars GSM-7, 70 chars Unicode)
• STOP/HELP keyword handlers configured
• Suppression list database created
• Timezone conversion logic tested (UTC+12)
• Holiday calendar integrated to avoid sending on public holidays
• Error handling covers common codes (21614, 30003, 30008)
• Rate limiting configured (start with 1 msg/second)
• Monitoring dashboard configured with 95% delivery rate threshold
• Test messages sent to valid Tuvalu mobile numbers (+6887xxxxx, +6889xxxxx)

Additional Resources for Pacific Island SMS:

• Tuvalu Telecommunications Corporation – Official TTC network information and updates
• Tuvalu Department of ICT – Telecommunications licensing and regulation
• Pacific ICT Regulatory Resource Center – Regional telecommunications regulations
• Twilio SMS Best Practices – General SMS implementation guidelines
• Twilio Tuvalu Guidelines – Tuvalu-specific technical requirements