US Virgin Islands SMS Guide: Compliance, Best Practices, and API Integration for USVI Messaging

United States Virgin Islands (US) SMS Market Overview

Market Conditions: The US Virgin Islands telecommunications market is served by both local operators and major US carriers like AT&T, T-Mobile, and Verizon. SMS remains a primary communication channel, with high mobile penetration rates. The market follows US messaging standards and regulations, with a mix of Android and iOS devices. OTT messaging apps like WhatsApp and Facebook Messenger are popular, but SMS maintains strong business usage due to its reliability and universal reach.

Key SMS Features and Capabilities in United States Virgin Islands

The US Virgin Islands supports standard SMS features aligned with US mainland capabilities, though with some limitations on advanced features like two-way messaging and concatenation.

Two-way SMS Support

Two-way SMS is not supported in the US Virgin Islands through standard API providers. Design your messaging strategies around one-way communication flows.

Concatenated Messages (Segmented SMS)

Support: Concatenated messaging is not supported in the US Virgin Islands.
Message length rules: Keep messages within single SMS length limits:

• GSM-7 encoding: 160 characters
• UCS-2 encoding: 70 characters
  Encoding considerations: Both GSM-7 and UCS-2 encodings are supported. Use GSM-7 for basic Latin characters to maximize message length.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link to the media content. This ensures delivery while maintaining the ability to share rich media content. Use short URLs and include clear context in the message text.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in the US Virgin Islands. This simplifies message routing but means recipients must change numbers when switching carriers.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported. Attempts to send messages to landline numbers will result in delivery failure with a 400 response error (code 21614). Messages will not appear in logs and accounts will not be charged.

Compliance and Regulatory Guidelines for SMS in United States Virgin Islands (US)

The US Virgin Islands follows US federal telecommunications regulations, including the Telephone Consumer Protection Act (TCPA) and FCC guidelines.¹ The territory falls under FCC jurisdiction for telecommunications oversight, with additional oversight from the US Virgin Islands Public Services Commission.²

Consent and Opt-In

Obtain explicit consent for all marketing and non-essential messages. Best practices for consent management include:

• Maintain detailed records of opt-in date, time, and source
• Use clear, unambiguous language when requesting consent
• Implement double opt-in for marketing campaigns
• Store consent records for at least 4 years (as required by TCPA enforcement guidelines)³
• Provide clear terms and conditions at opt-in

HELP/STOP and Other Commands

• Required Keywords: Support STOP, CANCEL, UNSUBSCRIBE, QUIT, END, and HELP
• Language Requirements: English is the primary language, though Spanish support is recommended
• Response Time: Provide automated responses to HELP/STOP commands immediately
• HELP Message Content: Include service information, contact details, and opt-out instructions

Do Not Call / Do Not Disturb Registries

The US Virgin Islands follows the US National Do Not Call Registry.⁴ Best practices include:

• Scrub contact lists regularly against the National DNC Registry
• Maintain internal opt-out lists
• Process opt-out requests immediately (within 24 hours)
• Keep suppression lists updated across all campaigns

Time Zone Sensitivity

• Time Zone: Atlantic Standard Time (AST) – UTC-4 year-round (no daylight saving time observed)⁵
• Permitted Hours: 8:00 AM to 9:00 PM local time
• Exception: Urgent messages for account security or service updates
• Holiday Considerations: Observe US federal and USVI territorial holidays

Phone Numbers Options and SMS Sender Types for in United States Virgin Islands (US)

Alphanumeric Sender ID

Operator network capability: Not supported
Registration requirements: N/A
Sender ID preservation: N/A

Long Codes

Domestic vs. International:

• Domestic long codes supported with registration
• International long codes not supported

Sender ID preservation: Yes, for registered numbers
Provisioning time: 1-2 weeks for registration
Use cases:

• Transactional messages
• Customer service
• Two-factor authentication

Short Codes

Support: US short codes supported through major carriers
Provisioning time: 8-12 weeks
Use cases:

• High-volume marketing campaigns
• Time-sensitive alerts
• Customer engagement programs

Restricted SMS Content, Industries, and Use Cases

Restricted Industries and Content:

• Gambling and gaming
• Adult content
• Illegal substances
• Cryptocurrency promotions
• Political messaging without proper disclaimers
• SHAFT content (Sex, Hate, Alcohol, Firearms, Tobacco)

Content Filtering

Carrier Filtering Rules:

• Messages containing restricted keywords are blocked
• URLs must be from approved domains
• Message frequency limits enforced

Best Practices to Avoid Filtering:

• Avoid excessive capitalization
• Don't use URL shorteners
• Maintain consistent sending patterns
• Use approved message templates
• Include clear business identification

Best Practices for Sending SMS in United States Virgin Islands (US)

Messaging Strategy

• Keep messages under 160 characters
• Include clear call-to-action
• Use personalization tokens thoughtfully
• Maintain consistent sender identification

Sending Frequency and Timing

• Send maximum 2 marketing messages per week
• Wait minimum 24 hours between messages
• Respect quiet hours (9 PM – 8 AM AST)
• Avoid sending during major holidays

Localization

• Primary language: English
• Consider Spanish language support for broader reach
• Use local formatting for dates and phone numbers
• Reference local events and customs when relevant

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain centralized opt-out database
• Confirm opt-out with one final message
• Conduct regular audits of opt-out list compliance

Testing and Monitoring

• Test across all major USVI carriers
• Monitor delivery rates by carrier
• Track opt-out rates and patterns
• Test HELP/STOP flows regularly
• Monitor for carrier filtering patterns

SMS API integrations for United States Virgin Islands (US)

Twilio

Twilio provides robust SMS capabilities for the USVI through their REST API. Authentication uses account SID and auth token credentials.

import * as Twilio from 'twilio';

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

// Function to send SMS to USVI
async function sendSMStoUSVI(
  to: string,
  message: string
): Promise<void> {
  try {
    // Create message with required parameters
    const response = await client.messages.create({
      to: to,                        // Format: +1340XXXXXXX
      from: process.env.TWILIO_NUMBER, // Your registered number
      body: message,
      // Optional parameters for delivery tracking
      statusCallback: 'https://your-callback-url.com/status'
    });
    
    console.log(`Message sent successfully: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers SMS services to USVI with REST API integration. Authentication uses API token and service plan ID.

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(
  phoneNumber: string,
  messageText: string
): Promise<void> {
  try {
    const response = await sinchClient.sms.batches.send({
      sendSMSRequestBody: {
        to: [phoneNumber],           // Format: +1340XXXXXXX
        from: process.env.SINCH_NUMBER,
        body: messageText,
        // Optional delivery report flag
        delivery_report: 'summary'
      }
    });
    
    console.log('Message batch ID:', response.id);
  } catch (error) {
    console.error('Sinch SMS error:', error);
    throw error;
  }
}

MessageBird

MessageBird provides SMS API access to USVI with straightforward REST integration.

import { MessageBirdClient } from 'messagebird';

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

// Function to send SMS via MessageBird
async function sendMessageBirdSMS(
  recipient: string,
  content: string
): Promise<void> {
  const params = {
    originator: process.env.MESSAGEBIRD_NUMBER,
    recipients: [recipient],         // Format: +1340XXXXXXX
    body: content,
    // Optional delivery tracking
    reportUrl: 'https://your-callback-url.com/delivery'
  };

  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 offers SMS capabilities for USVI through their REST API platform.

import * as plivo from 'plivo';

// Initialize Plivo client
const client = new plivo.Client(
  process.env.PLIVO_AUTH_ID,
  process.env.PLIVO_AUTH_TOKEN
);

// Function to send SMS via Plivo
async function sendPlivoSMS(
  destination: string,
  message: string
): Promise<void> {
  try {
    const response = await client.messages.create({
      src: process.env.PLIVO_NUMBER,  // Your Plivo number
      dst: destination,               // Format: +1340XXXXXXX
      text: message,
      // Optional URL tracking
      url: 'https://your-callback-url.com/status'
    });
    
    console.log('Message UUID:', response.messageUuid);
  } catch (error) {
    console.error('Plivo error:', error);
    throw error;
  }
}

API Rate Limits and Throughput

• Default rate limits: 1 message per second per number
• Batch sending: Maximum 100 recipients per request
• Daily sending limits vary by provider and account type

Strategies for Large-Scale Sending:

• Implement queuing system for high-volume campaigns
• Use batch APIs when available
• Monitor throughput and adjust sending rates
• Implement exponential backoff for retries

Error Handling and Reporting

Logging Best Practices:

• Log all API responses and message IDs
• Implement webhook endpoints for delivery status
• Track error rates by error code
• Monitor delivery rates by carrier

Troubleshooting Tips:

• Verify number format (+1340XXXXXXX)
• Check carrier delivery status
• Monitor API response codes
• Implement retry logic for temporary failures

Frequently Asked Questions About US Virgin Islands SMS

Can I send SMS to the US Virgin Islands using a US phone number?

Yes, you can send SMS to the US Virgin Islands using US phone numbers. The USVI uses the +1340 dialing code and follows US messaging standards. Major US carriers like AT&T, T-Mobile, and Verizon serve the territory, and US short codes and long codes are supported with proper registration.

Is two-way SMS supported in the US Virgin Islands?

No, two-way SMS is not supported in the US Virgin Islands through standard API providers. Design your messaging campaigns around one-way communication flows. Recipients cannot reply to SMS messages sent to USVI numbers through typical SMS channels.

What are the SMS compliance requirements for USVI messaging?

The US Virgin Islands follows US federal TCPA regulations requiring explicit prior consent for marketing messages, immediate opt-out processing (within 24 hours), support for STOP/HELP keywords, and compliance with the National Do Not Call Registry. Store consent records for at least 4 years and maintain detailed opt-in documentation.

What time zone does the US Virgin Islands use for SMS sending?

The US Virgin Islands observes Atlantic Standard Time (AST), which is UTC-4 year-round. Unlike mainland US locations, USVI does not observe daylight saving time. Send marketing SMS only between 8:00 AM and 9:00 PM AST to comply with TCPA regulations.

Can I send concatenated or long SMS messages to USVI numbers?

No, concatenated messaging is not supported in the US Virgin Islands. Keep all messages within single SMS length limits: 160 characters for GSM-7 encoding or 70 characters for UCS-2 encoding (used for special characters and emojis).

Do I need to register my phone number to send SMS to the US Virgin Islands?

Yes, you need registered phone numbers to send SMS to the USVI. Domestic US long codes require registration (1-2 weeks provisioning time), and US short codes are supported (8-12 weeks provisioning). International long codes are not supported for USVI messaging.

Can I send MMS messages to US Virgin Islands recipients?

MMS messages to the US Virgin Islands are automatically converted to SMS with an embedded URL link to the media content. To optimize delivery, use short URLs and include clear context in your message text explaining what recipients will see when clicking the link.

What SMS API providers work with the US Virgin Islands?

Twilio, Sinch, MessageBird, and Plivo all provide SMS API services for the US Virgin Islands. Each uses REST API integration with the +1340 dialing code format. Rate limits typically allow 1 message per second per number, with batch sending supporting up to 100 recipients per request.

Are there content restrictions for SMS to the US Virgin Islands?

Yes, the USVI follows US content restrictions prohibiting gambling, adult content, illegal substances, cryptocurrency promotions without disclaimers, and SHAFT content (Sex, Hate, Alcohol, Firearms, Tobacco). Carrier filtering blocks messages with restricted keywords, unapproved URLs, or excessive frequency.

Can I send SMS to landline numbers in the US Virgin Islands?

No, sending SMS to landline numbers is not supported in the USVI. Attempts result in delivery failure with a 400 response error (code 21614), and you won't be charged for these failed messages. Verify all recipient numbers are mobile before sending.

Summary: Essential Guide to US Virgin Islands SMS Messaging

Implementing SMS messaging for the US Virgin Islands requires understanding the unique regulatory landscape and technical limitations of this US territory. The USVI follows US federal TCPA regulations while maintaining some distinct characteristics that affect SMS delivery and compliance.

Key Requirements:

• Regulatory Compliance: Follow TCPA consent requirements, National Do Not Call Registry, and USVI PSC oversight
• Technical Limitations: No two-way SMS, no concatenated messages (160-character limit), no number portability
• Time Zone Awareness: Atlantic Standard Time (UTC-4) year-round with no daylight saving time transitions
• Number Format: Use +1340 prefix for all USVI numbers with proper registration requirements
• Consent Management: Store records for 4+ years, implement immediate opt-out processing, support STOP/HELP keywords
• API Integration: Choose from Twilio, Sinch, MessageBird, or Plivo with rate limits of 1 message/second/number

Implementation Roadmap:

1. Review Compliance Requirements: Study FCC TCPA regulations and USVI PSC telecommunications rules to ensure your messaging strategy meets all legal requirements for consent, opt-out processing, and sending hours.
2. Select SMS API Provider: Evaluate Twilio, Sinch, MessageBird, and Plivo based on your volume needs, budget, and technical requirements. Consider provisioning times (1-2 weeks for long codes, 8-12 weeks for short codes).
3. Register Phone Numbers: Obtain US long codes or short codes through your chosen provider. Ensure registration compliance with carrier requirements and plan for the provisioning timeline.
4. Build Consent Management System: Implement robust opt-in tracking with date, time, source recording, and maintain centralized opt-out database with 24-hour processing capability.
5. Configure Time Zone Controls: Set sending windows for 8:00 AM to 9:00 PM AST (UTC-4) and implement holiday blocklists for US federal and USVI territorial holidays.
6. Implement Message Validation: Build checks for 160-character limits (GSM-7) or 70-character limits (UCS-2), verify mobile-only recipients, and validate +1340XXXXXXX number format.
7. Set Up Monitoring Infrastructure: Create dashboards for delivery rates by carrier, track opt-out patterns, monitor carrier filtering signals, and implement webhook endpoints for API callbacks.
8. Test Thoroughly Across Carriers: Validate message delivery with AT&T, T-Mobile, and Verizon in USVI, test HELP/STOP flows, verify error handling for landline rejections, and establish baseline metrics.

Recap and Additional Resources

Key Takeaways

1. Compliance Priorities:

   • Obtain explicit consent
   • Honor opt-out requests
   • Follow time window restrictions
   • Maintain proper documentation

2. Technical Considerations:

   • Use correct number formatting
   • Implement proper error handling
   • Monitor delivery rates
   • Follow rate limits

3. Best Practices:

   • Test thoroughly before sending
   • Monitor campaign metrics
   • Keep messages concise
   • Maintain clean contact lists

Next Steps

1. Review FCC regulations for USVI
2. Consult legal counsel for compliance review
3. Set up testing environment with chosen API provider
4. Implement monitoring and reporting systems

Additional Resources

• FCC Guidelines
• USVI Public Services Commission
• TCPA Compliance Guide
• SMS Best Practices

References