Andorra SMS Best Practices, Compliance, and Features

Andorra SMS Market Overview

Market Conditions: Andorra has a highly developed telecommunications infrastructure, with Andorra Telecom serving as the primary mobile operator. The country has high mobile penetration rates and widespread adoption of both SMS and OTT messaging apps. While WhatsApp and other messaging apps are popular, SMS remains crucial for business communications, authentication, and notifications due to its reliability and universal reach.

Key SMS Features and Capabilities in Andorra

Andorra supports standard SMS features including concatenated messages and alphanumeric sender IDs, though two-way SMS functionality is not currently available through most providers.

Two-way SMS Support

Two-way SMS is not supported in Andorra through major SMS providers. This means businesses cannot receive replies to their SMS messages through standard A2P channels.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenated messages are fully supported in Andorra.
Message length rules: Standard SMS length limits apply - 160 characters for GSM-7 encoding, 70 characters for UCS-2 encoding before splitting occurs.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported. Messages containing special characters automatically use UCS-2 encoding, reducing the character limit per segment to 70.

MMS Support

MMS messages are not directly supported in Andorra. Instead, when attempting to send MMS, the message is automatically converted to SMS with an embedded URL link where recipients can view the multimedia content. This ensures compatibility while still allowing businesses to share rich media content with their audience.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Andorra, allowing users to keep their phone numbers when switching mobile operators. This does not significantly impact SMS delivery or routing as messages are properly routed to the current carrier.

Sending SMS to Landlines

SMS cannot be sent to landline numbers in Andorra. Attempts to send messages to landline numbers will result in a failed delivery and typically trigger 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 Andorra

Andorra follows European-style data protection and privacy regulations, with oversight from the Andorran Data Protection Agency (APDA). SMS marketing and communications must comply with both local telecommunications laws and data protection regulations that align with EU standards.

Consent and Opt-In

Explicit Consent Requirements:

• Obtain clear, specific opt-in consent before sending any marketing messages
• Document the date, time, and method of consent collection
• Maintain detailed records of consent for at least 5 years
• Provide clear information about message frequency and content type
• Allow easy opt-out options at any time

Best Practices for Consent Collection:

• Use double opt-in processes for marketing lists
• Clearly state the business name and purpose of messages
• Offer consent options in multiple languages (Catalan, French, Spanish)
• Keep separate consent records for different types of communications

HELP/STOP and Other Commands

• Required Keywords: STOP, CANCEL, UNSUBSCRIBE, HELP
• Language Support: Must support commands in Catalan (ATURA, AJUDA), French (ARR??T, AIDE), and Spanish (PARAR, AYUDA)
• Response Time: Acknowledge opt-out requests within 24 hours
• Implementation: Maintain automated systems to process these commands immediately

Do Not Call / Do Not Disturb Registries

While Andorra doesn't maintain a centralized Do Not Call registry, businesses must:

• Maintain their own suppression lists
• Honor opt-out requests immediately
• Keep opt-out records for a minimum of 5 years
• Regularly clean contact lists against suppression databases

Time Zone Sensitivity

• Permitted Hours: 8:00 AM to 9:00 PM (UTC+1/UTC+2)
• Holiday Restrictions: Avoid sending non-essential messages during national holidays
• Emergency Exception: Urgent messages (like security alerts) may be sent outside these hours
• Best Practice: Schedule campaigns between 10:00 AM and 8:00 PM for optimal engagement

Phone Numbers Options and SMS Sender Types for in Andorra

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 specified

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: Ideal for transactional messages, alerts, and two-factor authentication

Short Codes

Support: Not currently supported in Andorra
Provisioning time: N/A
Use cases: N/A

Restricted SMS Content, Industries, and Use Cases

Restricted Industries:

• Gambling and betting services
• Adult content
• Cryptocurrency promotions
• Unregistered financial services

Regulated Industries:

• Financial services require additional disclaimers
• Healthcare messages must maintain patient confidentiality
• Insurance products need clear terms and conditions

Content Filtering

Known Carrier Filters:

• URLs from suspicious domains
• Excessive use of special characters
• Multiple exclamation marks
• All-caps messages

Best Practices to Avoid Filtering:

• Use approved URL shorteners
• Maintain consistent sender IDs
• Avoid excessive punctuation
• Include clear opt-out instructions

Best Practices for Sending SMS in Andorra

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear calls-to-action
• Personalize messages using recipient's name or preferences
• Maintain consistent branding across messages

Sending Frequency and Timing

• Limit marketing messages to 4-5 per month per recipient
• Space messages at least 48 hours apart
• Avoid sending during local holidays
• Consider seasonal timing for promotional campaigns

Localization

• Primary language: Catalan
• Consider multi-language support for French and Spanish
• Use local date and time formats
• Respect cultural sensitivities and local customs

Opt-Out Management

• Process opt-outs within 24 hours
• Send confirmation of opt-out
• Maintain centralized opt-out database
• Regular audit of opt-out compliance

Testing and Monitoring

• Test messages across different devices
• Monitor delivery rates by carrier
• Track engagement metrics
• Regular review of bounce rates and opt-out patterns

SMS API integrations for Andorra

Twilio

Twilio provides a robust REST API for sending SMS messages to Andorra. Authentication uses 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 Andorra
async function sendSmsToAndorra(
  to: string,
  message: string,
  senderId: string
) {
  try {
    // Ensure proper formatting for Andorra numbers (+376)
    const formattedNumber = to.startsWith('+376') ? to : `+376${to}`;
    
    const response = await client.messages.create({
      body: message,
      from: senderId, // Alphanumeric sender ID or phone number
      to: formattedNumber,
    });
    
    console.log(`Message sent successfully! SID: ${response.sid}`);
    return response;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers a straightforward REST API for SMS delivery to Andorra, using API Token authentication.

import axios from 'axios';

class SinchSmsService {
  private readonly apiToken: string;
  private readonly serviceId: string;
  private readonly baseUrl = 'https://sms.api.sinch.com/xms/v1';

  constructor(apiToken: string, serviceId: string) {
    this.apiToken = apiToken;
    this.serviceId = serviceId;
  }

  async sendSms(to: string, message: string, senderId: string) {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.serviceId}/batches`,
        {
          from: senderId,
          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 a simple API for sending SMS messages to Andorra recipients.

import messagebird from 'messagebird';

class MessageBirdService {
  private client: any;

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

  sendSms(to: string, message: string, senderId: string): Promise<any&gt; {
    return new Promise((resolve, reject) =&gt; {
      this.client.messages.create({
        originator: senderId,
        recipients: [to],
        body: message,
        type: 'sms'
      }, (err: any, response: any) =&gt; {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Plivo offers a comprehensive API for sending SMS to Andorra with detailed delivery tracking.

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, senderId: string) {
    try {
      const response = await this.client.messages.create({
        src: senderId, // Sender ID
        dst: to,      // Destination number
        text: message,
        url_strip_query_params: false
      });
      
      return response;
    } catch (error) {
      console.error('Plivo SMS error:', error);
      throw error;
    }
  }
}

API Rate Limits and Throughput

• Standard Rate Limits:
  • Twilio: 100 messages/second
  • Sinch: 50 messages/second
  • MessageBird: 60 messages/second
  • Plivo: 80 messages/second

Strategies for Large-Scale Sending:

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

Error Handling and Reporting

• Implement comprehensive logging
• Track delivery receipts
• Monitor common error codes
• Set up automated alerts for high failure rates

Recap and Additional Resources

Key Takeaways:

1. Ensure proper phone number formatting (+376)
2. Implement robust error handling
3. Monitor delivery rates and failures
4. Follow local compliance requirements
5. Respect time zone restrictions

Next Steps:

1. Review Andorran telecommunications regulations
2. Implement proper consent management
3. Set up monitoring and reporting systems
4. Test thoroughly before full deployment

Additional Information:

• Andorran Telecommunications Regulatory Authority
• Andorran Data Protection Agency
• SMS Best Practices Guide

Technical Resources:

• Twilio Documentation
• Sinch API Reference
• MessageBird Guides
• Plivo API Documentation