Lithuania SMS Best Practices, Compliance, and Features

SMS Marketing in Lithuania: Market Overview

Lithuania offers a mature SMS marketing landscape with strict GDPR compliance requirements and excellent mobile network infrastructure. This guide covers everything you need to send SMS messages in Lithuania legally and effectively.

SMS Delivery Performance: Lithuania's SMS marketing infrastructure delivers reliably with 95-98% success rates across all three major carriers (Twilio pricing data). Domestic messages arrive in 2-8 seconds, and network coverage exceeds 99% of the population.

SMS Pricing in Lithuania: SMS costs vary by provider and volume. International API providers charge approximately $0.004-$0.0545 per message (Twilio: $0.0545, Plivo: $0.047, Sinch: $0.038, Telnyx: $0.004). Local operators (Tele2, Telia, Bitė) offer pay-as-you-go rates of €0.05-€0.10 per SMS and monthly bundled packages ranging from €5-€30 for high-volume domestic messaging.

Market Conditions: Lithuania operates a highly developed mobile telecommunications market with widespread SMS adoption. Three major operators serve the country: Tele2 (2.5M customers), Telia Lithuania (1.8M customers), and Bitė Lithuania (1.5M customers). All three provide 4G/LTE and 5G services covering over 99% of the population. While OTT messaging apps like WhatsApp and Messenger remain popular, SMS remains the primary channel for business communications, authentication, and transactional notifications. Android devices hold a slight market share edge over iOS in Lithuania.

Network Evolution: Telia shut down its 3G network at the end of 2022. Tele2 plans to complete its 3G shutdown by the end of 2025. On March 1, 2024, Lithuania changed its trunk prefix from "8" to "0" for domestic calls.

5G Deployment: All three major operators have deployed 5G networks. Telia and Tele2 operate on n28 (700 MHz) and n78 (3.6 GHz) bands, while Bitė uses n40 and n78 bands for 5G services.

SMS Features and Capabilities for Business Messaging

Lithuania supports two-way messaging, concatenated messages, and number portability – essential features for effective SMS marketing campaigns and transactional messaging.

Two-Way SMS Support

Lithuania fully supports two-way SMS with no restrictions. Deploy interactive messaging campaigns and SMS conversations for direct customer engagement.

Latency Performance: Two-way messaging in Lithuania typically achieves round-trip latency of 4-15 seconds, depending on carrier routing and network conditions. This makes it suitable for interactive use cases including customer service, surveys, and authentication workflows.

Common Use Cases:

• Customer service and support queries
• Survey responses and feedback collection
• Appointment confirmations and rescheduling
• Two-factor authentication (2FA) code delivery
• Interactive marketing campaigns with keyword responses

Concatenated Messages (Segmented SMS)

Support: Yes, all major carriers support concatenation

Message length rules:

• GSM-7 encoding: 160 characters before splitting
• Unicode (UCS-2): 70 characters before splitting

Encoding considerations: Lithuanian-specific characters require UCS-2 encoding. Messages with only Latin characters default to GSM-7 for maximum character efficiency.

Lithuanian Characters Requiring UCS-2: The following Lithuanian-specific characters trigger UCS-2 encoding: Ą ą Č č Ę ę Ė ė Į į Š š Ų ų Ū ū Ž ž. These letters are part of the 32-letter Lithuanian alphabet and are encoded in the Unicode Latin Extended-A block (U+0100 to U+017F). When any of these characters appear in your message, the entire SMS uses UCS-2 encoding, reducing the character limit from 160 to 70 characters per segment.

MMS Support

Carriers automatically convert MMS to SMS with an embedded URL link, ensuring universal device compatibility while enabling rich media sharing.

URL Hosting: MMS-to-SMS conversion typically hosts media files on carrier-managed CDN infrastructure. Most Lithuanian carriers maintain these URLs for 30-90 days, though retention policies vary by operator. For critical media requiring longer availability, host content on your own infrastructure and include direct links in standard SMS messages.

Recipient Phone Number Compatibility

Number Portability

Users keep their phone numbers when switching carriers through Lithuania's number portability system. The infrastructure handles ported numbers seamlessly with no impact on SMS delivery or routing.

Implementation: Mobile Number Portability (MNP) has operated in Lithuania since March 1, 2004, in compliance with the EU Universal Service Directive (2002/22/EC).

Porting Timeframe:

• Mobile to mobile: Fast processing, cost-free for consumers
• VoIP services: 7–14 days depending on carrier coordination

Regulatory Oversight: The Communications Regulatory Authority (RRT) oversees the system, ensuring fast processing, automated verification, and status tracking.

Sending SMS to Landlines

Lithuania does not support SMS to landline numbers. When you attempt to send messages to landlines:

• Delivery fails immediately
• System returns a 400 response with error code 21614
• Messages don't appear in logs
• Your account isn't charged

Identifying Landline Numbers: Lithuanian landline numbers use area codes beginning with 3, 4, or 5 and follow the format 0 X(X)(X) XXX XXXX, where X represents 1-3 digit area codes. Examples: 0 5 (Vilnius), 0 37 (Kaunas), 0 46 (Klaipėda), 0 41 (Šiauliai). Mobile numbers begin with 6, corporate/state numbers with 7, and premium services with 8 or 9. Always validate number prefixes before sending SMS to avoid delivery failures.

GDPR Compliance and SMS Marketing Regulations in Lithuania

Sending SMS marketing in Lithuania requires strict compliance with GDPR and national telecommunications laws. The Communications Regulatory Authority (RRT) oversees telecommunications services, while the State Data Protection Inspectorate (VDAI) handles data privacy. Understanding Lithuanian SMS regulations is essential to avoid penalties up to €20 million or 4% of annual turnover.

SMS Marketing Consent Requirements (GDPR)

How to Obtain SMS Marketing Consent in Lithuania:

• Obtain written or electronic consent before sending marketing messages
• Maintain consent records and make them easily accessible
• Disclose your company identity and message purpose clearly
• Keep consent specific to SMS marketing – don't bundle with other services
• Avoid pre-ticked consent boxes (prohibited under GDPR)
• Ensure consent is freely given, specific, informed, and unambiguous

Prohibition on Bundled Consent: The Lithuanian State Data Protection Inspectorate prohibits requiring customers to consent to marketing messages as a condition for accessing other services. Allow individuals to separately grant or withhold consent for direct marketing, regardless of other consents.

GDPR Penalties: SMS marketing consent violations can result in fines up to €20 million or 4% of total worldwide annual turnover of the preceding financial year, whichever is higher.

Best Practices for Documentation:

• Store consent timestamps and collection methods
• Maintain detailed records of opt-in sources
• Update consent databases regularly
• Implement double opt-in for additional security
• Document the specific purpose and scope of each consent

Consent Record Structure: Implement a structured data model to track consent with the following minimum fields:

interface ConsentRecord {
  userId: string;
  phoneNumber: string;
  consentGiven: boolean;
  consentTimestamp: Date;
  consentMethod: 'web_form' | 'api' | 'mobile_app' | 'point_of_sale';
  consentSource: string; // URL or location where consent was obtained
  ipAddress?: string;
  userAgent?: string;
  purpose: 'marketing' | 'transactional' | 'service_updates';
  doubleOptIn: boolean;
  doubleOptInConfirmedAt?: Date;
  lastUpdated: Date;
  revokedAt?: Date;
  revocationMethod?: string;
}

Retention Requirements: Under GDPR Article 5(2) and Article 7(1), maintain consent records for the duration of the processing activity plus a reasonable compliance period (typically 3-5 years after consent is revoked or the relationship ends). The Lithuanian State Data Protection Inspectorate recommends retaining consent documentation for at least 3 years after processing ceases to defend against potential complaints or regulatory inquiries.

HELP/STOP and Other Commands

Required Keywords: Support STOP, SUSTABDYTI (Lithuanian for "stop"), and PAGALBA (Lithuanian for "help")

Language Requirements: Recognize commands in both English and Lithuanian

Response Time: Send acknowledgment messages within 24 hours

Cost: Provide stop and help commands free of charge

Do Not Call / Do Not Disturb Registries

Lithuania maintains a national Do Not Call (DNC) registry managed by the Communications Regulatory Authority (RRT). Never send marketing calls or messages to numbers on this registry.

Accessing the DNC Registry: The RRT manages Lithuania's DNC registry. While Lithuania lacks a centralized public API for DNC queries (unlike some jurisdictions), comply through these methods:

• Contact the RRT directly via email (rrt@rrt.lt) or phone (+370 5 210 5155) to inquire about DNC compliance procedures for commercial SMS campaigns
• Implement and maintain your own internal suppression lists based on opt-out requests
• Work with your SMS provider's compliance team, as many international providers (Twilio, Sinch, Plivo) offer DNC screening services for regulated markets
• Review the Lithuanian Law on Electronic Communications for current DNC obligations

Note: The absence of a public API does not diminish legal obligations. The RRT actively enforces DNC regulations and imposes penalties for violations under telecommunications law and GDPR.

Compliance Requirements:

• Maintain internal suppression lists
• Honor opt-out requests immediately
• Remove numbers within 24 hours of STOP commands
• Keep opted-out number records for at least 2 years
• Check both the national DNC registry and internal opt-out lists

Compliance Note: DNC violations result in significant penalties under Lithuanian telecommunications law and GDPR.

Time Zone Sensitivity

Lithuania observes Eastern European Time: EET (UTC+2) in winter, EEST (UTC+3) in summer.

Recommended Sending Hours:

• Weekdays: 8:00 AM – 8:00 PM EET
• Weekends: 10:00 AM – 6:00 PM EET
• Avoid national holidays
• Emergency messages are exempt from time restrictions

SMS Sender ID Options: Alphanumeric, Long Codes & Short Codes

Alphanumeric Sender ID for SMS Marketing

Lithuania fully supports alphanumeric sender IDs for SMS campaigns, allowing businesses to display brand names instead of phone numbers.

Operator network capability: Fully supported across all major networks (Tele2, Telia, Bitė)

Registration requirements: No pre-registration required, dynamic usage allowed

Sender ID preservation: Sender IDs are preserved and displayed as sent

Length restriction: Maximum 11 characters, alphanumeric only

Character Restrictions and Examples:

• Valid characters: A-Z, a-z, 0-9 (letters and numbers; avoid spaces and special characters)
• Valid examples: BrandName, YourCompany, ALERTS2025, ServiceDesk
• Invalid examples: My Brand! (special character), Company Name (space), VeryLongCompanyName123 (exceeds 11 characters)
• Best practices: Use recognizable brand names, avoid all-numeric sender IDs (may be rejected), maintain consistency across campaigns

Sender ID Reputation: Lithuanian carriers lack formal sender ID reputation scoring systems. However, carriers monitor for abuse patterns and may filter or block sender IDs associated with spam complaints, high opt-out rates, or content policy violations. Maintain deliverability by using consistent sender IDs, avoiding frequent changes, honoring opt-out requests promptly, and monitoring delivery rates by sender ID.

Long Codes

Domestic vs. International: Both supported with full functionality

Sender ID preservation: Yes, original sender ID is preserved

Provisioning time: 1-2 business days

Use cases:

• Two-way communication
• Customer support
• Transactional messages
• Authentication services

Short Codes

Support: Yes, 4-digit short codes are supported in Lithuania

Provisioning time: 5-8 weeks depending on carrier availability and backlog

Format: Dedicated 4-digit short codes with cross-carrier support

Approval factors: Carriers approve based on time of year, price point, and service type

Provisioning Costs: Short code setup in Lithuania typically ranges from €500-€2,000 for initial provisioning, plus monthly recurring fees of €200-€800 per carrier depending on the service type (standard vs. premium rate). Total costs vary based on whether you require a dedicated or shared short code and cross-carrier support.

Application Process:

1. Submit application to your SMS provider or directly to Lithuanian carriers (Tele2, Telia, Bitė)
2. Provide business documentation, use case description, and sample message content
3. Undergo carrier review (content compliance, fraud risk assessment)
4. Receive approval and short code assignment (5-8 weeks average)
5. Complete technical integration and testing with each carrier
6. Launch service after final carrier certification

Use cases:

• Premium SMS billing
• Standard rate services
• Marketing campaigns with high volume
• Authentication and verification services

Restricted SMS Content, Industries, and Use Cases

Restricted Industries:

• Gambling and betting services
• Adult content
• Unauthorized pharmaceutical products
• Unlicensed financial services

Regulated Industries:

• Banking (requires additional authentication)
• Healthcare (must comply with patient privacy laws)
• Insurance (subject to financial services regulations)

Regulations and Penalties: Content restriction violations are enforced under the Lithuanian Law on Electronic Communications and sector-specific regulations. The RRT imposes administrative fines from €300 to €30,000 for unauthorized premium services or fraudulent messaging. GDPR violations carry penalties up to €20 million or 4% of annual turnover. Healthcare privacy violations result in additional fines of €1,000-€10,000.

Licensing for Regulated Industries:

• Gambling: Requires a gambling license from the Gaming Control Authority (Lošimų priežiūros tarnyba). Contact: lpt.lt
• Financial services: Banking/financial services licenses issued by the Bank of Lithuania. Contact: lb.lt
• Pharmaceuticals: Authorization from the State Medicines Control Agency (VVKT). Contact: vvkt.lt
• Healthcare services: Registration with the State Health Care Accreditation Agency. Contact: vaspvt.gov.lt

Content Filtering

Known Carrier Filters:

• URLs from suspicious domains
• Keywords associated with spam
• High-frequency sending patterns

Best Practices to Avoid Filtering:

• Use registered URL shorteners
• Avoid excessive punctuation
• Maintain consistent sending volumes
• Include clear company identification

SMS Marketing Best Practices for Lithuania

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear calls-to-action
• Personalize messages using recipient names or preferences
• Maintain consistent brand voice across all communications

Sending Frequency and Timing

• Limit messages to 4–5 per month per recipient
• Respect Lithuanian holidays and observances
• Avoid early morning or late evening sends
• Space out messages to prevent recipient fatigue

Localization

• Primary language: Lithuanian
• Consider bilingual messages (Lithuanian/English) for international audiences
• Use proper Lithuanian characters and UCS-2 encoding
• Respect cultural sensitivities and local customs

Lithuanian Message Templates:

Opt-Out Management

• Process opt-outs within 24 hours
• Send confirmation when users opt out
• Maintain clean, up-to-date suppression lists
• Audit your opt-out processes regularly

Testing and Monitoring

• Test messages across all major Lithuanian carriers (Tele2, Telia, Bitė)
• Monitor delivery rates by carrier
• Track engagement metrics consistently
• Run regular A/B tests on message content
• Maintain quality scores above industry benchmarks

Benchmark Performance Metrics: Based on industry data from Lithuanian SMS providers, aim for these targets:

• Delivery rate: 95-98% (98%+ indicates optimal sender reputation)
• Average delivery time: 2-8 seconds for domestic messages
• Opt-out rate: <0.5% per campaign (rates >2% suggest poor targeting or frequency issues)
• Engagement rate (clicks/responses): 5-15% for marketing, 25-40% for transactional messages
• Complaint rate: <0.1% (monitor RRT complaints through your SMS provider)

Testing Tools: Most major SMS providers offer testing capabilities:

• Twilio's Messaging Insights for delivery analytics
• Sinch's delivery reports and webhook testing
• SMS simulation tools: Use test numbers provided by your SMS API provider
• Carrier-specific testing: Request test credentials from Tele2, Telia, and Bitė for direct carrier testing

How to Send SMS in Lithuania: API Integration Guide

Twilio

Twilio provides robust SMS API support for Lithuanian numbers with delivery tracking and webhook capabilities.

Authentication & Setup:

• Requires Account SID and Auth Token
• Supports region selection (recommend EU data center for Lithuania)
• Uses E.164 number formatting (+370)

import { Twilio } from 'twilio';

// Initialize Twilio client with error handling for missing credentials
const accountSid = process.env.TWILIO_ACCOUNT_SID;
const authToken = process.env.TWILIO_AUTH_TOKEN;

if (!accountSid || !authToken) {
  throw new Error('Missing required Twilio credentials. Set TWILIO_ACCOUNT_SID and TWILIO_AUTH_TOKEN environment variables.');
}

const client = new Twilio(accountSid, authToken);

// Function to send SMS to Lithuania
async function sendSMSToLithuania(
  to: string,
  message: string,
  senderId: string
): Promise<void> {
  try {
    // Ensure proper number formatting for Lithuania
    const formattedNumber = to.startsWith('+370') ? to : `+370${to}`;

    const response = await client.messages.create({
      body: message,
      from: senderId, // Alphanumeric or phone number
      to: formattedNumber,
      // Optional parameters for delivery tracking
      statusCallback: 'https://your-webhook.com/status'
    });

    console.log(`Message sent! SID: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch

Sinch offers comprehensive SMS capabilities for Lithuania with strong delivery rates and Unicode support.

Key Features:

• REST API with JSON payload
• Batch sending support
• Delivery reports
• Unicode support for Lithuanian characters

import axios from 'axios';

interface SinchSMSConfig {
  apiToken: string;
  servicePlanId: string;
  senderId: string;
}

class SinchSMSService {
  private readonly baseUrl: string;
  private readonly headers: Record<string, string>;

  constructor(private config: SinchSMSConfig) {
    this.baseUrl = 'https://eu.sms.api.sinch.com/xms/v1';
    this.headers = {
      'Authorization': `Bearer ${config.apiToken}`,
      'Content-Type': 'application/json'
    };
  }

  async sendSMS(to: string, message: string): Promise<void> {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.config.servicePlanId}/batches`,
        {
          from: this.config.senderId,
          to: [to],
          body: message,
          encoding: 'auto' // Automatically handles Lithuanian characters
        },
        { headers: this.headers }
      );

      console.log('Message sent:', response.data.id);
    } catch (error) {
      console.error('Sinch SMS error:', error);
      throw error;
    }
  }
}

Bird (MessageBird)

Bird provides reliable SMS delivery in Lithuania with support for local number formatting and Unicode.

import { MessageBirdClient } from 'messagebird';

class BirdSMSService {
  private client: MessageBirdClient;

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

  async sendSMS(
    to: string,
    message: string,
    senderId: string
  ): Promise<void> {
    const params = {
      originator: senderId,
      recipients: [to],
      body: message,
      encoding: 'auto',
      reportUrl: 'https://your-webhook.com/delivery-reports'
    };

    try {
      const response = await new Promise((resolve, reject) => {
        this.client.messages.create(params, (err, response) => {
          if (err) reject(err);
          else resolve(response);
        });
      });

      console.log('Message sent with Bird:', response);
    } catch (error) {
      console.error('Bird SMS error:', error);
      throw error;
    }
  }
}

API Rate Limits and Throughput

Rate Limits by Provider:

• Twilio: 100 messages/second
• Sinch: 30 messages/second
• Bird: 60 messages/second

Carrier-Specific Throughput: Lithuanian carriers (Tele2, Telia, Bitė) typically accept 10-50 messages per second per connection. For high-volume campaigns exceeding 100,000 messages/hour, contact carriers directly to arrange dedicated routing and increased throughput limits.

Throughput Management Strategies:

• Implement exponential backoff for rate limit errors
• Use queue systems (Redis, RabbitMQ) for message buffering
• Batch messages when your provider supports it
• Monitor delivery rates continuously

Error Handling and Reporting

Best Practices:

• Implement retry logic for temporary failures
• Log all API responses with timestamps
• Monitor delivery rates by carrier (Tele2, Telia, Bitė)
• Set up alerting for error rate thresholds

Common Lithuania-Specific Error Codes:

• 21614 (Twilio): Message to landline number (invalid destination) – Lithuania does not support SMS to landlines
• 30003 (Twilio): Unreachable destination – number may be inactive or ported incorrectly
• 30005 (Twilio): Unknown destination – invalid Lithuanian number format
• 30007 (Twilio): Message filtered – content triggered carrier spam filters
• 30008 (Twilio): Carrier violation – content violates Lithuanian telecommunications regulations

Retry Strategy Decision Tree:

• Temporary failures (network errors, rate limits, timeouts): Retry with exponential backoff (max 3 attempts over 30 minutes)
• Invalid numbers (21614, 30005): Don't retry; remove from contact list and flag for validation
• Content filtering (30007): Don't retry; review message content and sender ID
• Carrier violations (30008): Don't retry; escalate to compliance team for regulatory review

// Example error handling implementation
interface SMSError {
  code: string;
  message: string;
  timestamp: Date;
  recipient: string;
}

class SMSErrorHandler {
  private errors: SMSError[] = [];

  logError(error: SMSError): void {
    this.errors.push(error);

    // Log to monitoring system
    console.error(`SMS Error [${error.code}]: ${error.message}`);

    // Trigger alerts if needed
    if (this.shouldTriggerAlert(error)) {
      this.sendAlert(error);
    }
  }

  private shouldTriggerAlert(error: SMSError): boolean {
    // Implement alert logic
    const criticalCodes = ['30008', '21612', '21610'];
    return criticalCodes.includes(error.code);
  }

  private sendAlert(error: SMSError): void {
    // Implement alert notification (email, Slack, PagerDuty, etc.)
    console.log(`ALERT: Critical SMS error detected - ${error.code}`);
  }
}

Recap and Additional Resources

Key Takeaways

1. Compliance Priorities:

   • Obtain explicit consent before sending marketing messages
   • Honor opt-out requests within 24 hours
   • Maintain proper documentation of all consents
   • Follow time zone restrictions (8 AM – 8 PM EET weekdays)
   • Check both national DNC registry and internal suppression lists

2. Technical Considerations:

   • Use UCS-2 encoding for Lithuanian characters (Ą ą Č č Ę ę Ė ė Į į Š š Ų ų Ū ū Ž ž)
   • Implement robust error handling and retry logic
   • Monitor delivery rates by carrier (Tele2, Telia, Bitė)
   • Manage API rate limits with queue systems
   • Format numbers in E.164 standard (+370)

3. Best Practices:

   • Localize content in Lithuanian (bilingual for international audiences)
   • Test across all major carriers before launching campaigns
   • Maintain clean, regularly audited contact lists
   • Track performance metrics and conduct regular A/B testing
   • Respect GDPR penalties (up to €20M or 4% annual turnover)

Next Steps

1. Review Communications Regulatory Authority (RRT) guidelines and the Lithuanian Law on Electronic Communications
2. Consult with legal counsel for GDPR compliance review
3. Set up test accounts with your preferred SMS providers
4. Implement monitoring and reporting systems
5. Establish internal processes for opt-out management

Implementation Checklist (Estimated Timeline: 4-8 weeks):

• Week 1-2: Legal compliance review, consent mechanism design, DNC registry inquiry
• Week 2-3: SMS provider selection and API integration development
• Week 3-4: Testing across all carriers (Tele2, Telia, Bitė), error handling implementation
• Week 4-6: Consent database setup, opt-out automation, Lithuanian message localization
• Week 6-8: Monitoring dashboard deployment, compliance documentation, soft launch pilot campaign

Additional Resources

• Lithuanian State Data Protection Inspectorate (VDAI)
• EU GDPR Guidelines
• Lithuanian Electronic Communications Law
• ETSI SMS Technical Standards
• RRT Contact Information: rrt@rrt.lt, +370 5 210 5155