Antigua and Barbuda SMS Guide - sms-compliance -

Antigua and Barbuda SMS Best Practices, Compliance, and Features

Antigua and Barbuda SMS Market Overview

Locale name:	Antigua and Barbuda
ISO code:	AG
Region	North America
Mobile country code (MCC)	344
Dialing Code	+1268

Market Conditions: Antigua and Barbuda has a well-developed mobile telecommunications infrastructure with widespread SMS usage. The market is served by major operators including FLOW (formerly LIME) and Digicel. While OTT messaging apps like WhatsApp are popular, SMS remains a reliable communication channel, particularly for business communications and notifications. The market shows a relatively even split between Android and iOS devices, with a slight preference for Android.

Key SMS Features and Capabilities in Antigua and Barbuda

Antigua and Barbuda supports standard SMS features including concatenated messages and alphanumeric sender IDs, though two-way SMS functionality is limited.

Two-way SMS Support

Two-way SMS is not currently supported in Antigua and Barbuda through major SMS providers. Businesses should design their messaging strategies around one-way communications.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messages are fully supported in Antigua and Barbuda.
Message length rules: Standard SMS length of 160 characters for GSM-7 encoding, or 70 characters for Unicode (UCS-2) encoding.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported. Messages using GSM-7 can contain up to 160 characters before splitting, while UCS-2 messages split at 70 characters.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link. This ensures compatibility across all devices while still allowing rich media content to be shared. Recipients can access multimedia content by clicking the provided link.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Antigua and Barbuda, allowing users to keep their phone numbers when switching between mobile operators. This does not significantly impact SMS delivery or routing.

Sending SMS to Landlines

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

Compliance and Regulatory Guidelines for SMS in Antigua and Barbuda

SMS communications in Antigua and Barbuda are governed by the Telecommunications Bill 2016, which provides a framework for telecommunications services. The Telecommunications Division of the Ministry of Information, Broadcasting, Telecommunications and Information Technology oversees regulatory compliance.

Explicit Consent Requirements:

Obtain clear, documented opt-in consent before sending marketing messages
Maintain records of how and when consent was obtained
Include clear terms and conditions during the opt-in process
Provide transparent information about message frequency and content type

HELP/STOP and Other Commands

All SMS campaigns must support standard STOP and HELP commands
Keywords should be in English, as it's the primary language
Required commands include:
- STOP, CANCEL, END, QUIT for opting out
- HELP, INFO for assistance
Respond to HELP requests with service information and support contact details
Process STOP requests immediately and send confirmation message

Do Not Call / Do Not Disturb Registries

While Antigua and Barbuda does not maintain an official Do Not Call registry, businesses should:

Maintain their own suppression lists
Honor opt-out requests immediately
Keep records of opted-out numbers for at least 12 months
Implement proper filtering systems to prevent messaging to opted-out numbers

Time Zone Sensitivity

Antigua and Barbuda follows Atlantic Standard Time (AST/UTC-4). Best practices include:

Send messages between 8:00 AM and 8:00 PM local time
Avoid sending during national holidays
Only send outside these hours for urgent or emergency communications
Consider religious and cultural observances

Phone Numbers Options and SMS Sender Types for in Antigua and Barbuda

Alphanumeric Sender ID

Operator network capability: Fully supported
Registration requirements: No pre-registration required, dynamic usage allowed
Sender ID preservation: Sender IDs are preserved and displayed as sent

Long Codes

Domestic vs. International:

Domestic long codes not supported
International long codes fully supported

Sender ID preservation: Yes, original Sender ID is preserved
Provisioning time: Typically 1-2 business days
Use cases:

Transactional messages
Customer support
Appointment reminders
Account notifications

Short Codes

Support: Not currently supported in Antigua and Barbuda
Provisioning time: N/A
Use cases: N/A

Restricted SMS Content, Industries, and Use Cases

Restricted Content Types:

Gambling and betting services
Adult content
Cryptocurrency promotions
Unauthorized financial services
Illegal products or services

Industry-Specific Guidelines:

Financial services must include regulatory disclaimers
Healthcare messages must maintain patient privacy
Educational institutions must obtain parental consent for recipients under 18

Content Filtering

Known Carrier Filtering Rules:

Messages containing certain keywords may be blocked
URLs should be from reputable domains
Excessive punctuation may trigger spam filters

Best Practices to Avoid Blocking:

Avoid URL shorteners where possible
Use clear, professional language
Limit special characters and excessive capitalization
Include company name in message body
Maintain consistent sending patterns

Best Practices for Sending SMS in Antigua and Barbuda

Messaging Strategy

Keep messages under 160 characters when possible
Include clear call-to-action
Personalize messages with recipient's name
Maintain consistent brand voice
Include opt-out instructions in marketing messages

Sending Frequency and Timing

Limit marketing messages to 4-8 per month
Space messages at least 24 hours apart
Avoid sending during major cultural events
Respect local holidays and weekends
Send time-sensitive messages during business hours

Localization

Use English as the primary language
Consider local dialects for certain campaigns
Use clear, simple language
Avoid colloquialisms that might not translate well

Opt-Out Management

Process opt-outs within 24 hours
Send confirmation of opt-out
Maintain updated suppression lists
Regular audit of opt-out database
Train staff on opt-out procedures

Testing and Monitoring

Test messages across all major carriers
Monitor delivery rates daily
Track engagement metrics
Conduct A/B testing for marketing campaigns
Regular review of bounce rates and failed deliveries

SMS API integrations for Antigua and Barbuda

Twilio

Twilio provides a robust SMS API for sending messages to Antigua and Barbuda. Integration requires your Account SID and Auth Token from the Twilio Console.

import { Twilio } from 'twilio';

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

async function sendSMS() {
  try {
    // Send message using E.164 format for Antigua and Barbuda (+1268)
    const message = await client.messages.create({
      body: 'Hello from Antigua and Barbuda!',
      from: 'YourCompany',           // Alphanumeric sender ID
      to: '+12681234567'            // Recipient number
    });
    
    console.log(`Message sent successfully! SID: ${message.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
  }
}

Sinch

Sinch offers SMS capabilities with straightforward authentication using API key and secret.

import { SinchClient } from '@sinch/sdk-core';

// Initialize Sinch client
const sinchClient = new SinchClient({
  projectId: 'YOUR_PROJECT_ID',
  keyId: 'YOUR_KEY_ID',
  keySecret: 'YOUR_KEY_SECRET'
});

async function sendSMS() {
  try {
    const response = await sinchClient.sms.batches.send({
      sendSMSRequestBody: {
        to: ['+12681234567'],
        from: 'YourBrand',
        body: 'Your message here',
        // Optional delivery report
        deliveryReport: 'summary'
      }
    });
    console.log('Message sent:', response);
  } catch (error) {
    console.error('Sending failed:', error);
  }
}

MessageBird

MessageBird provides a simple API for sending SMS messages with comprehensive delivery tracking.

import { MessageBird } from 'messagebird';

// Initialize MessageBird client
const messagebird = MessageBird('YOUR_ACCESS_KEY');

// Message sending function
function sendSMS() {
  const params = {
    originator: 'YourCompany',
    recipients: ['+12681234567'],
    body: 'Your message content',
    // Optional parameters
    reportUrl: 'https://your-webhook.com/delivery-reports'
  };

  messagebird.messages.create(params, (err, response) => {
    if (err) {
      console.error('Error:', err);
      return;
    }
    console.log('Message sent:', response);
  });
}

Plivo

Plivo offers reliable SMS delivery with detailed delivery tracking and analytics.

import { Client } from 'plivo';

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

async function sendSMS() {
  try {
    const response = await client.messages.create({
      src: 'YourBrand',             // Sender ID
      dst: '12681234567',          // Destination number
      text: 'Your message here',
      // Optional parameters
      url: 'https://your-url.com/delivery-status',
      method: 'POST'
    });
    console.log('Message sent:', response);
  } catch (error) {
    console.error('Error sending message:', error);
  }
}

API Rate Limits and Throughput

Default rate limits vary by provider:
- Twilio: 100 messages per second
- Sinch: 30 messages per second
- MessageBird: 60 messages per second
- Plivo: 50 messages per second

Strategies for Large-Scale Sending:

Implement queue systems (Redis, RabbitMQ)
Use batch sending APIs where available
Add exponential backoff for retries
Monitor throughput and adjust sending rates

Error Handling and Reporting

Logging Best Practices:

Log all API responses
Track delivery receipts
Monitor error rates and types
Implement retry logic for failed messages

Troubleshooting Tips:

Verify number formatting
Check sender ID compliance
Monitor API response codes
Set up automated alerts for high failure rates

Recap and Additional Resources

Key Takeaways

Compliance Priorities:
- Obtain explicit consent
- Honor opt-out requests
- Maintain proper documentation
- Follow time zone restrictions
Technical Considerations:
- Use E.164 number formatting
- Implement proper error handling
- Monitor delivery rates
- Test across all carriers
Best Practices:
- Send during business hours
- Keep messages concise
- Include opt-out instructions
- Regular testing and monitoring

Next Steps

Review the Telecommunications Bill 2016
Consult legal counsel for compliance review
Set up test accounts with SMS providers
Implement monitoring and reporting systems

Additional Information

Industry Resources:

American Samoa SMS Guide