Guyana SMS Best Practices, Compliance, and Features

Guyana SMS Market Overview

Market Conditions: Guyana's mobile telecommunications market is developing, with SMS remaining a crucial communication channel. The market is served by major operators including GTT Mobile and Digicel. While OTT messaging apps like WhatsApp are gaining popularity, SMS maintains importance for business communications and notifications due to its reliability and universal reach across all mobile devices.

Key SMS Features and Capabilities in Guyana

Guyana supports basic SMS functionality with some limitations on advanced features, focusing primarily on one-way messaging capabilities.

Two-way SMS Support

Two-way SMS is not supported in Guyana. Businesses should design their SMS strategies around one-way communications only, such as notifications, alerts, and marketing messages.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messages are 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 encoding 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 means any multimedia content must be hosted separately and shared via a link within the SMS message. For optimal user experience, ensure your multimedia content is mobile-optimized and hosted on reliable, fast-loading servers.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Guyana. This means mobile numbers remain tied to their original carrier, simplifying message routing but limiting consumer flexibility in switching providers while keeping their number.

Sending SMS to Landlines

Sending SMS to landline numbers is not possible in Guyana. Attempts to send messages to landline numbers will result in a failed delivery and an error response (400 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 Guyana

SMS communications in Guyana are governed by the Telecommunications Act (Chapter 47:02). The primary regulatory authority is the Telecommunications Agency, which oversees telecommunications services including SMS messaging. While specific SMS marketing regulations are still evolving, businesses should follow international best practices for compliance.

Consent and Opt-In

Explicit Consent Requirements:

• Obtain clear, documented opt-in consent before sending marketing messages
• Maintain detailed records of when and how consent was obtained
• Include clear terms and conditions during the opt-in process
• Specify the types of messages users will receive and approximate frequency

HELP/STOP and Other Commands

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

• Support "STOP" for opt-out requests
• Include "HELP" functionality for user support
• Process opt-out requests immediately
• Send confirmation messages in English, the primary business language in Guyana

Do Not Call / Do Not Disturb Registries

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

• Maintain their own suppression lists
• Honor opt-out requests within 24 hours
• Regularly clean contact lists to remove unengaged users
• Document all opt-out requests for compliance purposes

Time Zone Sensitivity

Guyana operates in the GMT-4 time zone. While there are no strict legal restrictions on messaging hours, follow these best practices:

• Send messages between 8:00 AM and 8:00 PM local time
• Avoid sending during national holidays
• Reserve after-hours messaging for urgent communications only
• Consider business hours (9:00 AM - 5:00 PM) for B2B communications

Phone Numbers Options and SMS Sender Types for in Guyana

Alphanumeric Sender ID

Operator network capability: Supported
Registration requirements: Pre-registration not required, dynamic usage supported
Sender ID preservation: Yes, 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: Immediate to 24 hours
Use cases:

• Transactional messages
• Customer support
• Notifications and alerts

Short Codes

Support: Limited availability
Provisioning time: Not specified due to limited implementation
Use cases: Not commonly used in Guyana

Restricted SMS Content, Industries, and Use Cases

Restricted Content:

• Gambling and betting services
• Adult content
• Illegal products or services
• Unauthorized financial services

Regulated Industries:

• Financial services require appropriate licenses
• Healthcare messages must comply with privacy regulations
• Government services require proper authorization

Content Filtering

Known Filtering Rules:

• Messages containing certain keywords may be blocked
• URLs should be from reputable domains
• Avoid excessive capitalization and special characters

Best Practices to Avoid Filtering:

• Use clear, professional language
• Avoid spam trigger words
• Include company name in messages
• Keep URLs short and recognizable

Best Practices for Sending SMS in Guyana

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Identify your business in each message
• Use personalization thoughtfully

Sending Frequency and Timing

• Limit to 2-4 messages per month per user
• Space messages at least 48 hours apart
• Respect local holidays and cultural events
• Monitor engagement rates to optimize timing

Localization

• Use English as the primary language
• Consider cultural context and local expressions
• 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 completion
• Maintain accurate opt-out records
• Regular audit of opt-out compliance

Testing and Monitoring

• Test messages across major carriers (GTT, Digicel)
• Monitor delivery rates and engagement
• Track opt-out rates and patterns
• Regular review of message performance metrics

SMS API integrations for Guyana

Twilio

Twilio provides a robust SMS API with comprehensive support for messaging in Guyana.

Key Parameters:

• Account SID and Auth Token for authentication
• From number (alphanumeric sender ID supported)
• E.164 formatted recipient numbers (+592XXXXXXX)
• Message body (supports Unicode)

import { Twilio } from 'twilio';

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

async function sendSMSToGuyana(
  to: string,
  message: string,
  from: string
): Promise<void&gt; {
  try {
    // Ensure number is in E.164 format for Guyana
    const formattedNumber = to.startsWith('+592') ? to : `+592${to}`;
    
    // Send message
    const response = await client.messages.create({
      body: message,
      from: from,  // Can be alphanumeric sender ID
      to: formattedNumber
    });
    
    console.log(`Message sent successfully! SID: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers reliable SMS delivery to Guyana with straightforward REST API integration.

Key Parameters:

• API Token for authentication
• Service Plan ID
• Destination number in E.164 format
• Message content and optional parameters

import axios from 'axios';

interface SinchSMSResponse {
  id: string;
  status: string;
}

async function sendSinchSMS(
  to: string,
  message: string
): Promise<SinchSMSResponse&gt; {
  const API_TOKEN = process.env.SINCH_API_TOKEN;
  const SERVICE_PLAN_ID = process.env.SINCH_SERVICE_PLAN_ID;
  
  try {
    const response = await axios.post(
      `https://sms.api.sinch.com/xms/v1/${SERVICE_PLAN_ID}/batches`,
      {
        from: "YourCompany",
        to: [to],
        body: message
      },
      {
        headers: {
          'Authorization': `Bearer ${API_TOKEN}`,
          'Content-Type': 'application/json'
        }
      }
    );
    
    return response.data;
  } catch (error) {
    console.error('Sinch SMS Error:', error);
    throw error;
  }
}

MessageBird

MessageBird provides a developer-friendly API for sending SMS to Guyana.

import messagebird from 'messagebird';

const client = messagebird(process.env.MESSAGEBIRD_API_KEY);

interface MessageBirdResponse {
  id: string;
  status: string;
}

function sendMessageBirdSMS(
  to: string,
  message: string
): Promise<MessageBirdResponse&gt; {
  return new Promise((resolve, reject) =&gt; {
    client.messages.create({
      originator: 'YourBrand',
      recipients: [to],
      body: message
    }, (err, response) =&gt; {
      if (err) {
        reject(err);
      } else {
        resolve(response);
      }
    });
  });
}

API Rate Limits and Throughput

• Standard Rate Limits:
  • Twilio: 250 messages per second
  • Sinch: 30 messages per second
  • MessageBird: 60 messages per second

Throughput Management Strategies:

• Implement exponential backoff for retries
• Use queuing systems (Redis, RabbitMQ) for high volume
• Batch messages when possible
• Monitor delivery rates and adjust sending patterns

Error Handling and Reporting

Best Practices:

• Log all API responses and errors
• Implement retry logic for failed messages
• Monitor delivery receipts
• Track common error patterns

// Example error handling implementation
async function sendSMSWithRetry(
  to: string,
  message: string,
  maxRetries = 3
): Promise<void&gt; {
  let attempts = 0;
  
  while (attempts &lt; maxRetries) {
    try {
      await sendSMSToGuyana(to_ message_ 'YourCompany');
      return;
    } catch (error) {
      attempts++;
      if (attempts === maxRetries) {
        throw new Error(`Failed to send SMS after ${maxRetries} attempts`);
      }
      // Exponential backoff
      await new Promise(resolve =&gt; 
        setTimeout(resolve, Math.pow(2, attempts) * 1000)
      );
    }
  }
}

Recap and Additional Resources

Key Takeaways

1. Compliance Priorities:

   • Obtain explicit consent
   • Honor opt-out requests
   • Maintain proper documentation
   • Follow time-zone appropriate sending

2. Technical Considerations:

   • Use E.164 number formatting
   • Implement proper error handling
   • Monitor delivery rates
   • Test across different carriers

3. Best Practices:

   • Keep messages concise
   • Personalize content
   • Respect frequency limits
   • Monitor engagement metrics

Next Steps

1. Review the Telecommunications Act (Chapter 47:02)
2. Consult with local legal counsel for compliance
3. Set up test accounts with preferred SMS providers
4. Implement proper monitoring and logging systems

Additional Resources

• Telecommunications Agency of Guyana
• Guyana National Frequency Management Unit
• Telecommunications Act

Industry Guidelines:

• Mobile Marketing Association Guidelines
• GSMA Messaging Principles
• International Best Practices for A2P Messaging