Tuvalu SMS Best Practices, Compliance, and Features

Tuvalu SMS Market Overview

Market Conditions: Tuvalu's telecommunications landscape is managed exclusively by the Tuvalu Telecommunications Corporation (TTC), which serves as the sole provider of mobile, fixed telephone, and internet services. Mobile phone usage is widespread, with Android devices being more common than iOS. While SMS remains a crucial communication channel, data connectivity allows for OTT messaging apps, though traditional SMS maintains importance for official and business communications.

Key SMS Features and Capabilities in Tuvalu

Tuvalu supports basic SMS functionality with some limitations on advanced features, primarily operating through the TTC network infrastructure.

Two-way SMS Support

Two-way SMS is not supported in Tuvalu for international communications. Local two-way messaging within the TTC network is possible, but international two-way messaging capabilities are restricted.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messaging is supported, though availability may vary by sender ID type.
Message length rules: Standard SMS length limits apply - 160 characters for GSM-7 encoding, 70 characters for Unicode.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported, with message splitting occurring at different thresholds based on the chosen encoding.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link. This conversion ensures delivery compatibility while still allowing rich media content to be shared via clickable links.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Tuvalu. All mobile numbers remain with their original carrier (TTC), simplifying routing but limiting user flexibility.

Sending SMS to Landlines

Sending SMS to landline numbers is not possible in Tuvalu. Attempts to send messages to landline numbers will result in a 400 response error (code 21614) through the API, with no message delivery and no charges applied.

Compliance and Regulatory Guidelines for SMS in Tuvalu

SMS communications in Tuvalu are governed by the Tuvalu Telecommunications Corporation Act, which establishes the framework for telecommunications services. While specific SMS marketing regulations are limited, businesses must follow general best practices and TTC guidelines for message delivery.

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 consent was obtained
• 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

While Tuvalu doesn't mandate specific keywords, implementing standard opt-out mechanisms is considered best practice:

• 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

Do Not Call / Do Not Disturb Registries

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

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

Time Zone Sensitivity

Tuvalu operates in UTC+12 timezone. Best practices include:

• Sending messages between 8:00 AM and 8:00 PM local time
• Avoiding messages during religious or cultural observances
• Limiting emergency messages outside of business hours
• Considering the impact of daylight saving time changes

Phone Numbers Options and SMS Sender Types for in Tuvalu

Alphanumeric Sender ID

Operator network capability: Not supported for pre-registration
Registration requirements: Dynamic usage is not supported
Sender ID preservation: Information not available for Tuvalu

Long Codes

Domestic vs. International:

• Domestic long codes are supported by operator networks
• International long codes have limited support
• Twilio does not currently support domestic long codes

Sender ID preservation: Varies by carrier and message type
Provisioning time: Standard setup time applies
Use cases: Recommended for transactional and verification messages

Short Codes

Support: Not currently supported in Tuvalu
Provisioning time: Not applicable
Use cases: Not available for marketing or authentication

Restricted SMS Content, Industries, and Use Cases

Content restrictions align with general telecommunications standards:

• Gambling and betting content prohibited
• Adult content strictly forbidden
• Financial services require additional verification
• Healthcare messages must maintain privacy standards

Content Filtering

Carrier Filtering:

• TTC implements basic content filtering
• Messages containing restricted content may be blocked
• URLs should be from reputable domains

Best Practices to Avoid Filtering:

• Avoid excessive punctuation and special characters
• Use clear, professional language
• Include company name in messages
• Maintain consistent sending patterns

Best Practices for Sending SMS in Tuvalu

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Maintain consistent branding
• Use personalization thoughtfully

Sending Frequency and Timing

• Limit messages to 2-3 per week maximum
• Respect local holidays and customs
• Avoid sending during off-hours
• Space out messages appropriately

Localization

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

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain accurate opt-out records
• Provide clear opt-out instructions
• Confirm opt-out status to users

Testing and Monitoring

• Test messages across different devices
• Monitor delivery rates regularly
• Track engagement metrics
• Analyze opt-out patterns
• Adjust strategy based on performance data

SMS API integrations for Tuvalu

Twilio

Twilio provides a straightforward REST API for sending SMS messages to Tuvalu. Authentication requires your Account SID and Auth Token.

import { Twilio } from 'twilio';

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

// Function to send SMS to Tuvalu
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}`;
    
    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;
  }
}

Sinch

Sinch offers SMS capabilities through their REST API, requiring API Token authentication.

import axios from 'axios';

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;
  }

  async sendSMS(to: string, message: string) {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.serviceId}/batches`,
        {
          from: 'YourSenderID',
          to: [to],
          body: message
        },
        {
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Content-Type': 'application/json'
          }
        }
      );
      
      return response.data;
    } catch (error) {
      console.error('Sinch SMS Error:', error);
      throw error;
    }
  }
}

MessageBird

MessageBird provides SMS capabilities through their REST API with API Key authentication.

import messagebird from 'messagebird';

class MessageBirdService {
  private client: any;

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

  sendSMS(to: string, message: string): Promise<any> {
    return new Promise((resolve, reject) => {
      this.client.messages.create({
        originator: 'YourName',
        recipients: [to],
        body: message
      }, (err: any, response: any) => {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Plivo's SMS API requires Auth ID and Auth Token for authentication.

import plivo from 'plivo';

class PlivoSMSService {
  private client: any;

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

  async sendSMS(to: string, message: string) {
    try {
      const response = await this.client.messages.create({
        src: 'YourSourceNumber', // Your Plivo number
        dst: to,
        text: message,
      });
      
      return response;
    } catch (error) {
      console.error('Plivo SMS Error:', error);
      throw error;
    }
  }
}

API Rate Limits and Throughput

• Default rate limit: 1 message per second per destination
• Batch sending recommended for large volumes
• Implement exponential backoff for retry logic
• Queue messages during peak times

Throughput Management Strategies:

// Example queue implementation
import Queue from 'better-queue';

const smsQueue = new Queue(async function (message, cb) {
  try {
    await sendSMS(message.to, message.text);
    cb(null, { success: true });
  } catch (error) {
    cb(error);
  }
}, { concurrent: 1, interval: 1000 });

Error Handling and Reporting

// Error handling example
interface SMSError {
  code: string;
  message: string;
  timestamp: Date;
}

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

  logError(error: SMSError) {
    this.errors.push(error);
    console.error(`SMS Error [${error.code}]: ${error.message}`);
    // Implement your error reporting logic here
  }

  getErrorReport() {
    return this.errors;
  }
}

Recap and Additional Resources

Key Takeaways:

• Always format numbers with Tuvalu's country code (+688)
• Implement proper error handling and retry logic
• Monitor delivery rates and adjust sending patterns
• Maintain compliance with local regulations

Next Steps:

1. Review the Tuvalu Telecommunications Corporation Act
2. Implement proper opt-out handling
3. Set up delivery monitoring
4. Test thoroughly before production deployment

Additional Information:

• Tuvalu Telecommunications Corporation
• Pacific ICT Regulatory Resource Center
• SMS Best Practices Guide