Finland SMS Guide - sms-compliance -

Finland SMS Best Practices, Compliance, and Features

Finland SMS Market Overview

Locale name:Finland
ISO code:FI
RegionEurope
Mobile country code (MCC)244
Dialing Code+358

Market Conditions: Finland has a highly developed mobile market with near-universal smartphone penetration. The three major mobile operators - DNA, Elisa, and Telia - dominate the market. While OTT messaging apps like WhatsApp are popular for personal communications, SMS remains crucial for business communications, particularly for authentication, alerts, and official notifications. The market shows a strong preference for Android devices (around 70%) over iOS (approximately 30%).

Key SMS Features and Capabilities in Finland

Finland offers comprehensive SMS capabilities including two-way messaging, concatenation support, and number portability, though MMS is handled through SMS conversion with URL links.

Two-way SMS Support

Finland fully supports two-way SMS communications with no specific restrictions. This enables interactive messaging campaigns and customer service applications through SMS.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is supported across all major Finnish operators, though support may vary by sender ID type.
Message length rules: Standard GSM-7 encoding allows 160 characters per segment, while UCS-2 encoding allows 70 characters per segment.
Encoding considerations: Messages using standard GSM-7 encoding (Latin alphabet) can contain up to 160 characters before splitting, while messages using UCS-2 encoding (supporting special characters and non-Latin alphabets) are limited to 70 characters per segment.

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 through linked web pages. Best practice is to use short URLs and include clear context in the SMS portion of the message.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Finland, allowing users to keep their phone numbers when switching operators. This feature is fully supported and does not affect message delivery or routing, as the Finnish number portability system is well-established and maintained.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Finland. Attempts to send messages to landline numbers will result in a failed delivery and a 400 response with error code 21614. These messages will not appear in logs and accounts will not be charged for the attempt.

Compliance and Regulatory Guidelines for SMS in Finland

Finland follows strict data protection and telecommunications regulations governed by Traficom (Finnish Transport and Communications Agency) and adheres to GDPR requirements. SMS marketing and communications must comply with both Finnish national laws and EU regulations.

Explicit Consent Requirements:

  • Written or electronic consent must be obtained before sending marketing messages
  • Consent must be freely given, specific, and informed
  • Records of consent must be maintained and easily accessible
  • Existing customer relationships may allow for soft opt-in for similar products/services

Best Practices for Consent:

  • Use double opt-in verification
  • Store consent timestamps and methods
  • Maintain detailed records of opt-in sources
  • Regularly clean and update consent databases

HELP/STOP and Other Commands

  • Must support both Finnish and Swedish keywords:
    • STOP/LOPETA/SLUTA
    • HELP/APUA/HJÄLP
  • Keywords must be case-insensitive
  • Response messages should be in the same language as the command received
  • Confirmation of opt-out must be sent immediately

Do Not Call / Do Not Disturb Registries

Finland does not maintain a centralized Do Not Call registry for SMS marketing. However, businesses must:

  • Maintain their own suppression lists
  • Honor opt-out requests within 24 hours
  • Implement proper screening mechanisms to filter opted-out numbers
  • Regularly update contact lists to remove unsubscribed users

Time Zone Sensitivity

Finland observes Eastern European Time (EET/EEST). While there are no strict legal time restrictions for SMS sending, best practices include:

  • Sending marketing messages between 8:00 and 20:00 local time
  • Limiting promotional messages during weekends and public holidays
  • Exception for critical notifications and authentication messages

Phone Numbers Options and SMS Sender Types for Finland

Alphanumeric Sender ID

Operator network capability: Fully supported
Registration requirements: Pre-registration not required for standard use, but protected Sender IDs must be registered with Traficom
Sender ID preservation: Yes, Sender IDs are preserved across all major networks

Long Codes

Domestic vs. International:

  • Domestic long codes fully supported
  • International long codes not supported for sending

Sender ID preservation: Yes for domestic, No for international
Provisioning time: Immediate for standard numbers
Use cases: Ideal for two-way communication, customer service, and transactional messages

Short Codes

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

Restricted SMS Content, Industries, and Use Cases

Prohibited Content:

  • Gambling and lottery-related content (strictly prohibited)
  • Adult content
  • Cryptocurrency promotions without proper disclaimers
  • Misleading financial services offers

Regulated Industries:

  • Financial services must include regulatory disclaimers
  • Healthcare messages must comply with patient privacy laws
  • Insurance products require clear terms and conditions

Content Filtering

Carrier Filtering Rules:

  • URLs must be from approved domains
  • Messages containing certain keywords may be blocked
  • High-volume sending patterns are monitored

Best Practices to Avoid Filtering:

  • Avoid URL shorteners when possible
  • Use consistent Sender IDs
  • Maintain steady sending volumes
  • Include clear opt-out instructions

Best Practices for Sending SMS in Finland

Messaging Strategy

  • Keep messages under 160 characters when possible
  • Include clear call-to-actions
  • Personalize messages using recipient's name or relevant details
  • Maintain consistent branding across messages

Sending Frequency and Timing

  • Limit marketing messages to 2-4 per month per recipient
  • Respect Finnish holidays and summer vacation period (July)
  • Avoid sending during early morning or late evening hours
  • Space out bulk sends to prevent network congestion

Localization

  • Support both Finnish and Swedish (official languages)
  • Consider regional language preferences
  • Use local date and time formats
  • Adapt content for cultural relevance

Opt-Out Management

  • Process opt-outs in real-time
  • Maintain centralized opt-out database
  • Confirm opt-outs with acknowledgment message
  • Regular audit of opt-out list compliance

Testing and Monitoring

  • Test messages across all major Finnish operators
  • Monitor delivery rates by operator
  • Track engagement metrics
  • Regular testing of opt-out functionality
  • Monitor for carrier filtering patterns

SMS API integrations for Finland

Twilio

Twilio provides a robust SMS API with comprehensive support for Finnish numbers and messaging requirements.

Key Integration Points:

  • Authentication via Account SID and Auth Token
  • E.164 number formatting required (+358)
  • Supports alphanumeric sender IDs
  • Delivery receipt webhooks available
import { Twilio } from 'twilio';

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

async function sendSMSToFinland(to: string, message: string) {
  try {
    // Ensure number is in E.164 format for Finland
    const formattedNumber = to.startsWith('+358') ? to : `+358${to.replace(/^0/, '')}`;
    
    const response = await client.messages.create({
      body: message,
      to: formattedNumber,
      from: 'YourCompany', // Alphanumeric sender ID
      statusCallback: 'https://your-webhook.com/status' // Optional delivery tracking
    });
    
    console.log(`Message sent! SID: ${response.sid}`);
    return response;
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers direct operator connections in Finland with support for high-volume messaging.

Key Integration Points:

  • Bearer token authentication
  • Batch sending capabilities
  • Delivery report webhooks
import axios from 'axios';

class SinchSMSService {
  private readonly apiToken: string;
  private readonly serviceId: string;
  private readonly baseUrl: string;

  constructor(apiToken: string, serviceId: string) {
    this.apiToken = apiToken;
    this.serviceId = serviceId;
    this.baseUrl = 'https://sms.api.sinch.com/xms/v1';
  }

  async sendBatchSMS(recipients: string[], message: string) {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.serviceId}/batches`,
        {
          from: 'YourBrand',
          to: recipients.map(num => num.startsWith('+358') ? num : `+358${num.replace(/^0/, '')}`),
          body: message,
          delivery_report: 'summary'
        },
        {
          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 reliable SMS delivery in Finland with advanced features for message handling.

import { MessageBird } from 'messagebird';

class MessageBirdService {
  private client: MessageBird;

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

  async sendMessage(recipient: string, message: string) {
    return new Promise((resolve, reject) => {
      this.client.messages.create({
        originator: 'CompanyName',
        recipients: [recipient],
        body: message,
        datacoding: 'auto' // Automatic handling of special characters
      }, (err, response) => {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Plivo offers competitive rates for Finnish SMS with good delivery rates.

import 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) {
    try {
      const response = await this.client.messages.create({
        src: 'COMPANY', // Your sender ID
        dst: to.startsWith('+358') ? to : `+358${to.replace(/^0/, '')}`,
        text: message,
        url: 'https://your-webhook.com/delivery-report' // Optional
      });
      
      return response;
    } catch (error) {
      console.error('Plivo 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 batch APIs for high-volume sending
  • Consider queue implementation for large campaigns:
import Queue from 'bull';

const smsQueue = new Queue('sms-queue', {
  redis: process.env.REDIS_URL
});

// Add rate limiting
smsQueue.process(10, async (job) => {
  // Process SMS sending logic here
});

Error Handling and Reporting

  • Implement comprehensive logging
  • Monitor delivery receipts
  • Track common error codes:
enum SMSErrorCode {
  INVALID_NUMBER = 'invalid_number',
  NETWORK_ERROR = 'network_error',
  RATE_LIMIT = 'rate_limit',
  BLOCKED = 'blocked'
}

function handleSMSError(error: any) {
  logger.error({
    errorCode: error.code,
    message: error.message,
    timestamp: new Date().toISOString()
  });
  
  // Implement specific error handling logic
  switch(error.code) {
    case SMSErrorCode.RATE_LIMIT:
      return retryWithBackoff();
    case SMSErrorCode.INVALID_NUMBER:
      return cleanupInvalidNumber();
    // Handle other cases
  }
}

Recap and Additional Resources

Key Takeaways

  1. Compliance First: Always ensure GDPR and Finnish telecommunications law compliance
  2. Technical Setup: Use proper number formatting and character encoding
  3. Best Practices: Follow sending time windows and frequency guidelines
  4. Error Handling: Implement robust error handling and monitoring

Next Steps

  1. Review Traficom's SMS regulations at www.traficom.fi
  2. Consult with Finnish legal experts for compliance verification
  3. Set up test accounts with preferred SMS providers
  4. Implement proper consent management systems

Additional Resources

Loading...