Kosovo SMS Guide - sms-compliance -

Kosovo SMS Best Practices, Compliance, and Features

Kosovo SMS Market Overview

Locale name:Kosovo
ISO code:XK
RegionEurope
Mobile country code (MCC)221
Dialing Code+383

Market Conditions: Kosovo has a growing mobile telecommunications market with increasing SMS usage for both personal and business communications. The country has several mobile operators providing SMS services, with a mix of feature phones and smartphones in use. While OTT messaging apps like WhatsApp and Viber are popular in urban areas, SMS remains a reliable communication channel, especially for business-to-consumer communications and authentication services.

Key SMS Features and Capabilities in Kosovo

Kosovo 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 supported in Kosovo through major SMS providers. This means businesses cannot receive replies to their messages through standard SMS channels.

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.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported, though support may vary by sender ID type.

MMS Support

MMS messages are not directly supported in Kosovo. Instead, MMS content is automatically converted to SMS with an embedded URL link where recipients can view the multimedia content.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Kosovo. This means mobile numbers remain tied to their original carrier.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Kosovo. Attempts to send SMS to landline numbers will result in a failed delivery and an error response (400 error code 21614 for Twilio API), with no charges applied to the sender's account.

Compliance and Regulatory Guidelines for SMS in Kosovo

While Kosovo does not have specific SMS marketing legislation, businesses should follow EU-style data protection and privacy practices. The Regulatory Authority of Electronic and Postal Communications (ARKEP) oversees telecommunications services in Kosovo.

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 of service and privacy policy during opt-in
  • Specify the types of messages users will receive and approximate frequency

HELP/STOP and Other Commands

  • All SMS campaigns must support standard HELP and STOP commands
  • Commands should be recognized in both Albanian and Serbian
  • Common keywords to support:
    • STOP, NDALO (Albanian), PRESTANI (Serbian)
    • HELP, NDIHME (Albanian), POMOĆ (Serbian)
  • Process opt-out requests within 24 hours

Do Not Call / Do Not Disturb Registries

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

  • Maintain their own suppression lists
  • Honor opt-out requests immediately
  • Keep records of opted-out numbers for at least 12 months
  • Regularly clean contact lists to remove inactive or opted-out numbers

Time Zone Sensitivity

Kosovo follows Central European Time (CET/CEST). Best practices include:

  • Send messages between 9:00 AM and 8:00 PM local time
  • Avoid sending during religious holidays and national celebrations
  • Only send outside these hours for urgent notifications or critical updates

Phone Numbers Options and SMS Sender Types for Kosovo

Alphanumeric Sender ID

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

Long Codes

Domestic vs. International: International long codes supported; domestic long codes not available
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 Kosovo
Provisioning time: N/A
Use cases: N/A

Restricted SMS Content, Industries, and Use Cases

Restricted Industries and Content:

  • Gambling and betting services
  • Adult content or services
  • Cryptocurrency promotions
  • Political campaign messages without proper authorization
  • Pharmaceutical promotions

Content Filtering

Known Carrier Filtering Rules:

  • Messages containing certain keywords related to restricted industries
  • URLs from suspicious or blacklisted domains
  • Messages with excessive punctuation or all-caps text

Tips to Avoid Blocking:

  • Avoid URL shorteners in messages
  • Use clear, professional language
  • Limit special characters and emoji usage
  • Include company name in message content

Best Practices for Sending SMS in Kosovo

Messaging Strategy

  • Keep messages under 160 characters when possible
  • Include clear call-to-action
  • Use personalization tokens (customer name, relevant details)
  • Maintain consistent sender ID across campaigns

Sending Frequency and Timing

  • Limit marketing messages to 4-5 per month per recipient
  • Space messages at least 24 hours apart
  • Avoid sending during major holidays:
    • Independence Day (February 17)
    • New Year's Day
    • Religious holidays (both Muslim and Christian)

Localization

  • Support both Albanian and Serbian languages
  • Consider using Latin alphabet for better compatibility
  • Include language preference in opt-in process
  • Offer bilingual opt-out instructions

Opt-Out Management

  • Process opt-outs within 24 hours
  • Send confirmation message for opt-out requests
  • Maintain separate opt-out lists for different types of messages
  • Regular audit of opt-out processing system

Testing and Monitoring

  • Test messages across major Kosovo carriers
  • Monitor delivery rates by carrier
  • Track opt-out rates and patterns
  • Regular testing of HELP/STOP functionality
  • Monitor for carrier filtering changes

SMS API integrations for Kosovo

Twilio

Twilio provides a robust SMS API with comprehensive support for Kosovo. Here's how to implement it:

import { Twilio } from 'twilio';

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

// Function to send SMS to Kosovo
async function sendSMSToKosovo(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    // Ensure proper formatting for Kosovo numbers (+383)
    const formattedNumber = to.startsWith('+383') ? to : `+383${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 reliable SMS delivery to Kosovo with straightforward integration:

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

// Initialize Sinch client
const sinchClient = new SinchClient({
  projectId: process.env.SINCH_PROJECT_ID,
  apiToken: process.env.SINCH_API_TOKEN
});

// Function to send SMS using Sinch
async function sendSinchSMS(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    const response = await sinchClient.sms.batches.send({
      to: [to],
      from: senderId,
      body: message,
      delivery_report: 'summary' // Enable delivery reporting
    });

    console.log(`Batch ID: ${response.id}`);
  } catch (error) {
    console.error('Sinch SMS Error:', error);
    throw error;
  }
}

MessageBird

MessageBird provides comprehensive SMS capabilities for Kosovo:

import messagebird from 'messagebird';

// Initialize MessageBird client
const mbClient = messagebird(process.env.MESSAGEBIRD_API_KEY);

// Function to send SMS via MessageBird
function sendMessageBirdSMS(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  return new Promise((resolve, reject) => {
    mbClient.messages.create({
      originator: senderId,
      recipients: [to],
      body: message,
      datacoding: 'auto' // Automatic encoding detection
    }, (err, response) => {
      if (err) {
        reject(err);
        return;
      }
      console.log('MessageBird Response:', response);
      resolve();
    });
  });
}

Plivo

Plivo offers reliable SMS delivery to Kosovo with detailed delivery tracking:

import plivo from 'plivo';

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

// Function to send SMS via Plivo
async function sendPlivoSMS(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    const response = await plivoClient.messages.create({
      src: senderId,
      dst: to,
      text: message,
      url_strip_query_params: false // Preserve URL parameters in tracking
    });

    console.log('Message UUID:', response.messageUuid);
  } catch (error) {
    console.error('Plivo Error:', error);
    throw error;
  }
}

API Rate Limits and Throughput

  • 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 using Redis or RabbitMQ
  • Use batch APIs when available
  • Implement exponential backoff for rate limit handling
  • Monitor delivery rates and adjust sending speed accordingly

Error Handling and Reporting

// Example error handling middleware
interface SMSError extends Error {
  code?: string;
  status?: number;
}

async function handleSMSError(error: SMSError): Promise<void> {
  // Log error details
  console.error({
    code: error.code,
    status: error.status,
    message: error.message,
    timestamp: new Date().toISOString()
  });

  // Handle specific error codes
  switch (error.code) {
    case '21614': // Invalid number
      await updateInvalidNumber(error);
      break;
    case '30003': // Rate limit exceeded
      await handleRateLimit(error);
      break;
    default:
      await logGenericError(error);
  }
}

Recap and Additional Resources

Key Takeaways

  1. Compliance Priorities:

    • Obtain explicit consent
    • Support HELP/STOP commands
    • Respect time zone restrictions

  2. Technical Considerations:

    • Use proper phone number formatting (+383)
    • Implement proper error handling
    • Monitor delivery rates

  3. Best Practices:

    • Test thoroughly before large campaigns
    • Maintain clean contact lists
    • Monitor API rate limits

Next Steps

  1. Review ARKEP regulations at www.arkep-rks.org
  2. Implement proper opt-out handling
  3. Set up monitoring and reporting systems

Additional Resources