American Samoa SMS Best Practices, Compliance, and Features
American Samoa SMS Market Overview
Locale name: | American Samoa |
---|---|
ISO code: | AS |
Region | Oceania |
Mobile country code (MCC) | 544 |
Dialing Code | +1684 |
Market Conditions: American Samoa's telecommunications market is relatively small but growing, with mobile services playing an increasingly important role in daily communications. The territory follows U.S. telecommunications standards and regulations while maintaining its own unique characteristics. Mobile penetration is high, with most residents using smartphones for daily communication. SMS remains a crucial communication channel, particularly for business and emergency communications.
Key SMS Features and Capabilities in American Samoa
American Samoa supports standard SMS features including concatenated messaging and URL-based MMS conversion, though two-way SMS functionality is not currently available.
Two-way SMS Support
Two-way SMS is not supported in American Samoa through most major providers. This limitation affects interactive messaging campaigns and automated response systems.
Concatenated Messages (Segmented SMS)
Support: Yes, concatenated messaging is fully supported in American Samoa.
Message length rules: Standard SMS length limits apply - 160 characters for GSM-7 encoding and 70 characters for Unicode messages.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported, with GSM-7 being more efficient for basic Latin characters.
MMS Support
MMS messages are automatically converted to SMS with an embedded URL link. This conversion ensures delivery while maintaining the ability to share rich media content through linked resources. Best practice is to use short URLs and include clear context about the linked content.
Recipient Phone Number Compatibility
Number Portability
Number portability services are available in American Samoa, following U.S. telecommunications standards. This feature allows users to retain their phone numbers when switching carriers, though it may occasionally impact message routing times.
Sending SMS to Landlines
SMS to landline numbers is not supported in American Samoa. Attempts to send SMS to landline numbers will result in a failed delivery and typically generate a 400 response with error code 21614. These messages will not appear in logs, and accounts will not be charged for failed attempts.
Compliance and Regulatory Guidelines for SMS in American Samoa
As a U.S. territory, American Samoa follows U.S. telecommunications regulations, including the Telephone Consumer Protection Act (TCPA) and CAN-SPAM Act. The Office of the Regulator in American Samoa oversees local telecommunications compliance, while broader U.S. regulations are enforced by the Federal Communications Commission (FCC).
Consent and Opt-In
Explicit Consent Requirements:
- Written or electronic consent must be obtained before sending marketing messages
- Consent records must be maintained and easily accessible
- Purpose and frequency of messages must be clearly stated during opt-in
- Double opt-in is recommended for marketing campaigns
Best Practices for Documentation:
- Store consent timestamps and IP addresses
- Maintain detailed records of opt-in sources
- Keep copies of opt-in forms and messages
- Document any consent changes or updates
HELP/STOP and Other Commands
- Required Keywords: STOP, CANCEL, UNSUBSCRIBE, QUIT, END must be supported
- Language Support: Commands must be recognized in English and Samoan
- Response Time: Acknowledgment messages must be sent within 24 hours
- Implementation: Auto-response system must be maintained for these keywords
Do Not Call / Do Not Disturb Registries
American Samoa follows the U.S. National Do Not Call Registry. Best practices include:
- Regular checks against the National DNC Registry
- Maintenance of internal do-not-contact lists
- Immediate processing of opt-out requests
- Proactive filtering of registered numbers before campaigns
Time Zone Sensitivity
American Samoa observes Samoa Standard Time (UTC-11):
- Recommended Sending Hours: 8:00 AM to 8:00 PM SST
- Emergency Messages: Can be sent outside these hours if urgent
- Holiday Considerations: Avoid sending during major local holidays
- Cultural Sensitivity: Respect Sunday as a day of rest
Phone Numbers Options and SMS Sender Types for in American Samoa
Alphanumeric Sender ID
Operator network capability: Fully supported
Registration requirements: No pre-registration required, dynamic usage allowed
Sender ID preservation: Yes, sender IDs are preserved as sent
Long Codes
Domestic vs. International:
- International long codes fully supported
- Domestic long codes availability limited
Sender ID preservation: Yes, original sender ID is preserved
Provisioning time: Immediate for international numbers
Use cases: Ideal for transactional messages and customer support
Short Codes
Support: Not currently supported in American Samoa
Provisioning time: N/A
Use cases: N/A
Restricted SMS Content, Industries, and Use Cases
Restricted Industries:
- Gambling and betting services
- Adult content and services
- Cryptocurrency promotions
- Unauthorized financial services
Regulated Industries:
- Financial services require appropriate disclaimers
- Healthcare messages must comply with HIPAA
- Insurance-related messages need proper disclosures
Content Filtering
Known Carrier Filters:
- URLs from unknown domains
- Multiple exclamation marks
- ALL CAPS messages
- Excessive special characters
Best Practices:
- Use approved URL shorteners
- Avoid spam trigger words
- Maintain consistent sender IDs
- Keep message formatting professional
Best Practices for Sending SMS in American Samoa
Messaging Strategy
- Keep messages under 160 characters when possible
- Include clear calls-to-action
- Personalize using recipient's name or relevant details
- Maintain consistent brand voice
Sending Frequency and Timing
- Limit to 2-4 messages per week per recipient
- Respect local time zones and cultural events
- Avoid sending during major holidays
- Space out messages appropriately
Localization
- Support both English and Samoan languages
- Consider cultural nuances in message content
- Use appropriate date and time formats
- Include local contact information
Opt-Out Management
- Process opt-outs within 24 hours
- Maintain centralized opt-out database
- Confirm opt-outs with acknowledgment message
- Regular audit of opt-out list
Testing and Monitoring
- Test across major local carriers
- Monitor delivery rates daily
- Track engagement metrics
- Regular testing of opt-out functionality
SMS API integrations for American Samoa
Twilio
Twilio provides robust SMS capabilities for American Samoa through their REST API. Authentication uses account SID and auth token credentials.
import { 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 American Samoa
async function sendSMSToAmericanSamoa(
to: string,
message: string
): Promise<void> {
try {
// Ensure number is in E.164 format for American Samoa (+1684)
const formattedNumber = to.startsWith('+1684') ? to : `+1684${to}`;
const response = await client.messages.create({
body: message,
to: formattedNumber,
from: process.env.TWILIO_PHONE_NUMBER, // Your Twilio number
// Optional parameters for delivery tracking
statusCallback: 'https://your-webhook.com/status'
});
console.log(`Message sent! SID: ${response.sid}`);
} catch (error) {
console.error('Error sending message:', error);
}
}
Sinch
Sinch offers SMS services to American Samoa with RESTful API integration. Authentication uses API key and secret.
import { SinchClient } from '@sinch/sdk-core';
// Initialize Sinch client
const sinchClient = new SinchClient({
projectId: process.env.SINCH_PROJECT_ID,
keyId: process.env.SINCH_KEY_ID,
keySecret: process.env.SINCH_KEY_SECRET
});
// 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],
from: process.env.SINCH_SENDER_ID,
body: messageText,
// Optional delivery report settings
deliveryReport: 'summary'
}
});
console.log('Message sent successfully:', response);
} catch (error) {
console.error('Failed to send message:', error);
}
}
MessageBird
MessageBird provides SMS connectivity to American Samoa through their REST API platform.
import { MessageBird } from 'messagebird';
// Initialize MessageBird client
const messagebird = MessageBird(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_SENDER_ID,
recipients: [recipient],
body: content,
// Optional parameters
reportUrl: 'https://your-webhook.com/delivery-reports'
};
messagebird.messages.create(params, (err, response) => {
if (err) {
console.error('Error sending message:', err);
return;
}
console.log('Message sent successfully:', response);
});
}
Plivo
Plivo offers SMS capabilities for American Samoa with straightforward API integration.
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
): Promise<void> {
try {
const response = await plivo.messages.create({
src: process.env.PLIVO_SENDER_ID, // Your Plivo number
dst: destination, // Destination number
text: message,
// Optional URL callback
url: 'https://your-webhook.com/status'
});
console.log('Message sent:', response);
} catch (error) {
console.error('Failed to send message:', error);
}
}
API Rate Limits and Throughput
- Default rate limit: 1 message per second per destination
- Batch sending limit: 100 messages per request
- Daily sending quota: Based on account level and provider
Strategies for Large-Scale Sending:
- Implement queuing system for high-volume campaigns
- Use batch APIs when available
- Implement exponential backoff for retries
- Monitor throughput and adjust sending rates
Error Handling and Reporting
Common Error Scenarios:
- Invalid phone number format
- Network connectivity issues
- Rate limit exceeded
- Invalid sender ID
Logging Best Practices:
- Log all API requests and responses
- Implement structured error handling
- Track delivery status callbacks
- Maintain audit trails for compliance
Recap and Additional Resources
Key Takeaways
-
Compliance Priorities:
- Follow U.S. TCPA regulations
- Maintain proper consent records
- Honor opt-out requests promptly
-
Technical Considerations:
- Use E.164 number formatting
- Implement proper error handling
- Monitor delivery rates
-
Best Practices:
- Respect local time zones
- Maintain clean opt-out lists
- Regular testing and monitoring
Next Steps
- Review the Office of the Regulator's telecommunications guidelines
- Consult legal counsel for compliance requirements
- Set up test accounts with preferred SMS providers
- Implement proper consent management systems