Faroe Islands SMS Best Practices, Compliance, and Features

Faroe Islands SMS Market Overview

Market Conditions: The Faroe Islands has a well-developed telecommunications infrastructure governed by the Telecommunications Act of 2015. The market features modern mobile networks with widespread SMS adoption, though specific data on OTT messaging app usage is limited. The telecommunications sector is regulated by an independent authority focused on promoting fair competition and consumer protection.

Key SMS Features and Capabilities in Faroe Islands

The Faroe Islands supports standard SMS messaging capabilities including concatenated messages and URL-based MMS conversion, though with some limitations on two-way messaging and landline SMS delivery.

Two-way SMS Support

Two-way SMS is not supported in the Faroe Islands according to current provider capabilities. This means businesses should design their SMS strategies around one-way communication flows.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is supported for messages exceeding standard length limits.
Message length rules: Standard SMS length of 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, with UCS-2 recommended for messages containing special characters or non-Latin alphabets.

MMS Support

MMS messages are automatically converted to SMS with an embedded URL link. This conversion ensures delivery compatibility while still allowing rich media content to be shared through linked resources.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in the Faroe Islands. This means phone numbers remain tied to their original mobile network operators.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in the Faroe Islands. Attempts to send SMS to landline numbers will result in a 400 response error (code 21614), with no message delivery and no account charges.

Compliance and Regulatory Guidelines for SMS in Faroe Islands

The Faroe Islands telecommunications sector is governed by the Telecommunications Act of 2015, with oversight from an independent regulatory authority. While specific SMS marketing regulations may be limited, businesses should follow EU-inspired best practices for consumer protection and data privacy.

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 of service and privacy policy references during opt-in
• Provide transparent information about message frequency and content type

HELP/STOP and Other Commands

• Support standard STOP and HELP commands in both English and Faroese
• Process opt-out requests immediately upon receipt
• Maintain a clear audit trail of opt-out requests and their processing
• Provide help information in both English and Faroese when requested

Do Not Call / Do Not Disturb Registries

While the Faroe Islands does not maintain a centralized Do Not Call registry, businesses should:

• Maintain their own suppression lists
• Honor opt-out requests immediately
• Keep records of opted-out numbers
• Regularly clean contact lists to remove unsubscribed numbers

Time Zone Sensitivity

The Faroe Islands observes GMT/UTC+0. Best practices include:

• Sending messages between 8:00 AM and 8:00 PM local time
• Avoiding messages on Sundays and public holidays
• Limiting urgent messages outside these hours to genuine emergencies

Phone Numbers Options and SMS Sender Types for in Faroe Islands

Alphanumeric Sender ID

Operator network capability: Supported
Registration requirements: Pre-registration not required
Sender ID preservation: Yes, sender IDs are preserved as specified

Long Codes

Domestic vs. International: International long codes supported; domestic not available
Sender ID preservation: Yes, original sender ID is preserved
Provisioning time: Immediate to 24 hours
Use cases: Ideal for transactional messages, alerts, and customer service

Short Codes

Support: Not supported in the Faroe Islands
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
• Misleading or fraudulent content

Content Filtering

Carrier Filtering Guidelines:

• Avoid excessive punctuation and special characters
• Limit URL usage to legitimate, secure domains
• Maintain consistent sender IDs
• Avoid spam trigger words and phrases

Best Practices for Sending SMS in Faroe Islands

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Use personalization thoughtfully
• Maintain consistent branding and tone

Sending Frequency and Timing

• Limit marketing messages to 2-4 per month
• Space messages appropriately
• Respect local holidays and customs
• Monitor engagement metrics to optimize timing

Localization

• Primary languages: Faroese and Danish
• Consider bilingual messages for important communications
• Use proper character encoding for special characters
• Respect local cultural norms and preferences

Opt-Out Management

• Include clear opt-out instructions in every message
• Process opt-outs within 24 hours
• Maintain accurate opt-out records
• Regularly audit opt-out compliance

Testing and Monitoring

• Test messages across major local carriers
• Monitor delivery rates and engagement
• Track opt-out rates and patterns
• Regular review of message performance metrics

SMS API integrations for Faroe Islands

Twilio

Twilio provides robust SMS capabilities for the Faroe Islands through their REST API. Authentication uses your Account SID and Auth Token.

import * as Twilio from 'twilio';

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

// Function to send SMS to Faroe Islands
async function sendSMSToFaroeIslands(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    // Ensure proper formatting for Faroe Islands numbers (+298)
    const formattedNumber = to.startsWith('+298') ? to : `+298${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}`);
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers SMS services via REST API with OAuth2 authentication.

import axios from 'axios';

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

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

  async sendSMS(to: string, message: string): Promise<void> {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.servicePlanId}/batches`,
        {
          from: 'YourSenderID',
          to: [to],
          body: message
        },
        {
          headers: {
            'Content-Type': 'application/json',
            'Authorization': `Bearer ${this.apiToken}`
          }
        }
      );
      
      console.log('Message sent:', response.data);
    } catch (error) {
      console.error('Sinch SMS error:', error);
      throw error;
    }
  }
}

MessageBird

MessageBird provides SMS capabilities through their REST API with API key authentication.

import { MessageBird } from 'messagebird';

class MessageBirdService {
  private client: MessageBird;

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

  async sendSMS(
    to: string,
    message: string,
    originator: string
  ): Promise<void> {
    return new Promise((resolve, reject) => {
      this.client.messages.create({
        originator, // Sender ID
        recipients: [to],
        body: message,
        datacoding: 'auto' // Automatic character encoding detection
      }, (err, response) => {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Plivo offers SMS integration through their REST API with basic authentication.

import * as plivo from 'plivo';

class PlivoSMSService {
  private client: plivo.Client;

  constructor(authId: string, authToken: string) {
    this.client = new plivo.Client(authId, authToken);
  }

  async sendSMS(
    to: string,
    message: string,
    senderId: string
  ): Promise<void> {
    try {
      const response = await this.client.messages.create({
        src: senderId,
        dst: to,
        text: message,
        url_strip_query_params: false
      });
      
      console.log('Message sent:', response);
    } catch (error) {
      console.error('Plivo SMS error:', error);
      throw error;
    }
  }
}

API Rate Limits and Throughput

• Default rate limits vary by provider (typically 1-10 messages per second)
• Implement exponential backoff for retry logic
• Use queuing systems (Redis, RabbitMQ) for high-volume sending
• Consider batch APIs for bulk messaging

Error Handling and Reporting

• Implement comprehensive error logging
• Monitor delivery receipts (DLRs)
• Track common error codes:
  • Invalid number format
  • Network errors
  • Rate limit exceeded
• Store message status updates for troubleshooting

Recap and Additional Resources

Key Takeaways:

• Always format numbers with +298 prefix for Faroe Islands
• Implement proper error handling and retry logic
• Monitor delivery rates and message status
• Follow local time restrictions and compliance requirements

Next Steps:

1. Review the Telecommunications Act of 2015
2. Implement proper opt-in/opt-out mechanisms
3. Set up monitoring and logging systems
4. Test thoroughly with local carriers

Additional Information:

• Faroe Islands Telecommunications Authority
• Telecommunications Act Documentation
• [SMS Provider Documentation]:
  • Twilio Docs
  • Sinch Docs
  • MessageBird Docs
  • Plivo Docs