Zambia SMS Guide: Compliance, Best Practices & Carrier Requirements

Send SMS messages to Zambian mobile numbers with confidence by understanding ZICTA regulations, Data Protection Act 2021 requirements, and technical specifications for MTN Zambia, Airtel Zambia, and Zamtel networks. This comprehensive guide covers sender ID registration, character encoding limits, phone number formats, and API integration best practices for reliable SMS delivery in Zambia's mobile market.

Zambia SMS Market Overview

Market Conditions: Zambia has a competitive mobile market with three major mobile network operators (MNOs). As of 2024-2025, Airtel Zambia holds approximately 48% market share, followed by MTN Zambia with 35%, and state-owned Zamtel with approximately 17-18% of mobile subscribers (Mordor Intelligence, August 2025). Mobile penetration exceeds 100% of the population, indicating multiple SIM ownership is common. SMS remains a critical communication channel for business-to-consumer messaging, particularly in financial services, utilities, and government communications.

While over-the-top (OTT) messaging apps like WhatsApp and Facebook Messenger have gained traction in urban areas, SMS maintains universal reach across both rural and urban regions due to several factors: network reliability even on 2G coverage, zero data requirements, compatibility with all mobile devices including feature phones, and high trust levels among consumers. The mobile ecosystem is dominated by Android devices (approximately 85-90% market share), with significantly lower iOS adoption concentrated in urban centers.

Regulatory Environment: The Zambia Information and Communications Technology Authority (ZICTA) regulates telecommunications services under the Information and Communications Technologies Act No. 15 of 2009 (as amended). ZICTA oversees SMS service provision, content regulations, and consumer protection in electronic communications.

What SMS Features Are Supported in Zambia?

Zambia offers basic SMS functionality with some limitations on advanced features like two-way messaging and concatenation, while supporting both domestic and international message routing through registered sender IDs.

Two-way SMS Support

Two-way SMS is not supported in Zambia through standard API providers. Messages can only be sent one-way from businesses to consumers, limiting interactive messaging capabilities. This limitation is primarily due to carrier network configurations and regulatory restrictions that prevent inbound SMS routing to international API platforms.

Workarounds for interactive messaging:

• Use dedicated short codes where available (limited support in Zambia)
• Implement click-to-call or web-based response mechanisms with URLs in SMS
• Direct users to WhatsApp Business or other OTT platforms for two-way communication
• Use mobile money callback systems (MTN Mobile Money, Airtel Money, Zamtel Kwacha) for payment confirmations

Concatenated Messages (Segmented SMS)

Support: Concatenated messaging is not supported in Zambia due to technical limitations on carrier networks. Most Zambian operators have not implemented the User Data Header (UDH) protocol required for automatic message reassembly on recipient devices.

Message length rules: Messages must conform to standard SMS length limitations. Encoding considerations: Both GSM-7 and UCS-2 encoding are supported, with UCS-2 available for messages containing special characters or non-Latin alphabets.

MMS Support

MMS messages are not directly supported in Zambia. When attempting to send MMS content, messages are automatically converted to SMS format with an embedded URL link where recipients can view the multimedia content. This ensures message delivery while providing access to rich media through web links.

URL shortener recommendations:

• Use branded domains with HTTPS for security and trust
• Popular shorteners: bit.ly, tinyurl.com, or custom domain shorteners
• Ensure URLs are mobile-optimized for low-bandwidth connections (2G/3G)

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Zambia. Mobile numbers remain tied to their original network operators, which helps ensure consistent message routing and delivery. Mobile Number Portability (MNP) has not been implemented by ZICTA as of 2025, though industry consultations have occurred regarding future implementation.

Sending SMS to Landlines

Sending SMS to landline numbers is not supported in Zambia. Attempts to send messages to landline numbers will result in delivery failures, with API providers typically returning a 400 response with error code 21614. These messages will not appear in logs and accounts will not be charged for failed attempts.

What Are the Compliance Requirements for SMS in Zambia?

SMS communications in Zambia are regulated by the Zambia Information and Communications Technology Authority (ZICTA) under multiple legal frameworks:

• Information and Communications Technologies Act No. 15 of 2009 (as amended): Primary legislation governing electronic communications and telecommunications services
• Data Protection Act No. 3 of 2021: Comprehensive data protection framework that came into force in 2021, establishing requirements for personal data processing, consent, and user rights
• Electronic Communications and Transactions Act No. 21 of 2021: Governs electronic transactions and digital communications

While specific SMS marketing regulations continue to evolve, businesses must comply with data protection, consumer protection, and telecommunications regulations. ZICTA has authority to issue guidelines and enforce compliance standards for SMS services.

Penalties for Non-Compliance (Data Protection Act No. 3 of 2021):

• Corporate entities: Fine not exceeding ZMW 100 million (approx. USD 1,080,000) or 2% of annual turnover of the preceding financial year, whichever is higher
• Natural persons: Fine not exceeding ZMW 1 million (approx. USD 36,000) or imprisonment for up to 10 years, or both
• Failure to register as data controller: Fine of up to ZMW 200,000 (approx. USD 7,200) and/or imprisonment for up to 5 years
• SMS compliance violations (ZICTA): Fines between ZMW 10,000 and ZMW 100,000 (approx. USD 360 - USD 3,600), blocked campaigns, and potential blacklisting (Africala, September 2025)

Data Residency and Cross-Border Transfer Requirements (Data Protection Act, Section 70-71):

• All personal data must be stored on servers or data centers located in Zambia
• The Minister of Technology may prescribe categories of personal data that may be stored outside Zambia
• Sensitive personal data must remain in Zambia at all times
• Cross-border transfers of non-sensitive data require:
  • Explicit consent from the data subject
  • Standard contractual clauses approved by the Data Protection Commissioner
  • Transfers to countries with adequate data protection frameworks
  • Approval from the Data Protection Commissioner for specific transfers

Consent and Opt-In

Explicit Consent Requirements (Data Protection Act No. 3 of 2021):

• Written or electronic consent must be obtained before processing personal data for marketing messages
• Consent must be freely given, specific, informed, and unambiguous
• Consent records should be maintained for at least 2 years (recommended 5 years for audit purposes)
• Purpose of messaging must be clearly stated during opt-in process
• Double opt-in is recommended as best practice for marketing campaigns
• Data subjects have the right to withdraw consent at any time

Example compliant opt-in message:

Best Practices for Documentation:

• Maintain detailed consent logs including timestamp, source, and scope
• Store opt-in confirmation messages and responses
• Regularly update consent databases
• Provide clear terms and conditions during opt-in
• Document all opt-out requests

HELP/STOP and Other Commands

• All SMS campaigns must support standard opt-out keywords: STOP, END, CANCEL, UNSUBSCRIBE
• HELP keyword support is mandatory, providing information about the service
• Commands should work in both English and major local languages (Nyanja, Bemba)
• Responses to opt-out requests must be sent within 24 hours

Example HELP/STOP responses:

Do Not Call / Do Not Disturb Registries

Zambia does not maintain a centralized Do Not Call registry. However, businesses should:

• Maintain their own suppression lists
• Honor opt-out requests immediately
• Remove unsubscribed numbers within 24 hours
• Regularly clean contact databases
• Implement proper opt-out tracking systems

Time Zone Sensitivity

Zambia follows Central African Time (CAT, UTC+2). Best practices include:

• Sending messages between 8:00 AM and 8:00 PM CAT
• Avoiding messages during public holidays
• Limiting emergency messages outside these hours
• Considering religious and cultural observances

What Sender ID Types Are Available in Zambia?

Alphanumeric Sender ID

Operator network capability: Fully supported across all major networks Registration requirements: Pre-registration required for both international and domestic use Sender ID preservation: Yes, preserved across all major carriers Provisioning time: Approximately 3 weeks for registration approval

Sender ID naming requirements (Vonage API Support):

• Character limits: 3-11 alphanumeric characters
• Allowed characters: Letters (A-Z), numbers (0-9), and limited special characters
• Case-sensitive: Sender IDs must match registered capitalization exactly
• Must contain brand name: Generic terms like "INFO", "SMS", "NOTICE", "SALE", or "OFFER" are prohibited
• MTN Zambia (MCC 64502): Pre-registration is mandatory; dynamic alphanumeric sender IDs will not be delivered without registration

Registration process:

1. Apply through your bulk SMS provider or directly with the mobile network operator
2. Submit required documents:
   • Business registration certificate or license
   • Proof of brand/trademark ownership
   • Campaign purpose and use case description
   • Company contact information
3. Await operator approval (typically 2-4 weeks)
4. Receive confirmation and begin using registered sender ID

Associated costs: Registration fees vary by provider, typically ZMW 500-2,000 (USD 18-72) per sender ID per operator

If registration is rejected:

• Review rejection reason (usually generic terms, trademark conflicts, or incomplete documentation)
• Modify sender ID to meet requirements
• Resubmit application with corrected information
• Allow additional 2-3 weeks for re-review

Long Codes

Domestic vs. International:

• Domestic long codes not supported
• International long codes supported but with limitations

Limitations of international long codes:

• Sender ID is not preserved; recipients see a random international number
• Lower delivery rates compared to registered alphanumeric sender IDs
• May be filtered as spam by carrier networks
• No guarantee of consistent sender number across messages
• Not recommended for branded marketing campaigns

Sender ID preservation: International sender IDs are not preserved Provisioning time: Immediate for international numbers Use cases: Recommended for transactional messaging and two-factor authentication

Short Codes

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

How to Format Zambia Phone Numbers for SMS

Zambian mobile phone numbers follow a specific structure for SMS delivery:

E.164 Format: +260XXXXXXXXX (country code +260 followed by 9 digits)

Number Structure:

• Country code: +260
• Mobile numbers: 9 digits starting with 9 or 7
• Format: +260 9X XXX XXXX or +260 7X XXX XXXX

Mobile Number Ranges by Operator (Wikipedia - Telephone numbers in Zambia):

• MTN Zambia: 76, 96 prefixes
• Airtel Zambia: 77, 97 prefixes
• Zamtel: 75, 95 prefixes

Additional prefixes (Sent.dm):

• MTN also uses: 78, 79 (some shared with other operators)
• Prefixes 96 and 97 may be shared across operators in some ranges

Important Notes:

• Mobile numbers share some prefix ranges across operators (96, 97), making operator identification unreliable without number portability
• Always use E.164 international format (+260...) for API submissions
• Remove spaces, dashes, or parentheses when formatting for APIs
• Landline numbers (area code format 211-218) cannot receive SMS

Validation regex pattern:

^\+260(7[5-9]|9[5-7])\d{7}$

Example Formatting:

• Displayed format: 0977 123 456
• API format: +260977123456
• Alternative API format: 260977123456 (without + symbol, depending on provider requirements)

What Content Is Restricted for SMS in Zambia?

Restricted Industries:

• Gambling and betting services
• Adult content and dating services
• Cryptocurrency and unauthorized financial services
• Political campaign messages without proper authorization

Regulated Industries:

• Financial services require ZICTA approval
• Healthcare messages must comply with medical privacy laws
• Insurance services need regulatory clearance

Specific prohibited content examples (Vonage, Africala):

• P2P (peer-to-peer) traffic
• Political content without authorization
• Religious content used for unsolicited promotion
• Unsolicited promotional messages without opt-in consent
• Messages containing fraudulent or misleading claims
• Content promoting illegal activities

Penalties for sending restricted content:

• Immediate campaign blocking by mobile network operators
• Fines of ZMW 10,000 - ZMW 100,000 (USD 360 - USD 3,600)
• Permanent sender ID blacklisting for repeated violations
• Legal action under Data Protection Act or Electronic Communications and Transactions Act

Content Filtering

Carrier Filtering Rules:

• Messages containing spam trigger words may be blocked (e.g., "FREE!!!", "WIN NOW", "CASH PRIZE", "CLICK HERE")
• URLs should be from approved domains; suspicious or blacklisted domains will be filtered
• Message length and frequency limitations apply to prevent spam
• Excessive use of special characters, emojis, or ALL CAPS may trigger filters

Carrier-specific filtering differences:

• MTN Zambia: Strictest filtering; blocks unregistered sender IDs and suspicious URLs
• Airtel Zambia: Moderate filtering; focuses on spam keywords and high-volume senders
• Zamtel: Most lenient; primarily blocks P2P traffic and illegal content

Best Practices to Avoid Blocking:

• Avoid spam trigger words (free, winner, congratulations, urgent, limited time)
• Use registered and approved sender IDs
• Maintain consistent sending patterns (avoid sudden volume spikes)
• Keep URL usage minimal and legitimate (1-2 URLs per message maximum)
• Test messages across all three carriers before launching campaigns
• Monitor delivery rates and adjust content if filtering occurs

What Are the Best Practices for Sending SMS in Zambia?

Messaging Strategy

• Keep messages under 160 characters when possible (GSM-7) or 70 characters (Unicode)
• Include clear call-to-actions (e.g., "Visit our shop", "Reply YES", "Call 123-456")
• Personalize messages using recipient names when available
• Maintain consistent branding with registered sender ID
• Use clear, concise language appropriate for Zambian audience
• Avoid jargon, complex English, or idioms that may not translate well

Zambia-specific cultural considerations:

• Respect for elders and authority figures; use polite, formal language
• Emphasis on community and family; messaging around group benefits resonates well
• Religious values are important (Christianity 95%+); avoid content conflicting with religious norms
• English is official language, but Nyanja and Bemba are widely spoken; consider local language options

Sending Frequency and Timing

• Limit to 4-5 messages per month per recipient (industry benchmark)
• Respect local business hours (8:00 AM - 8:00 PM CAT)
• Avoid Sundays for promotional messages (primary worship day)
• Space out messages appropriately (minimum 3-5 days between promotional SMS)
• Avoid sending during major national events

Zambian public holidays to avoid:

• New Year's Day (January 1)
• Youth Day (March 12)
• Good Friday and Easter Monday (variable)
• Labour Day (May 1)
• Africa Freedom Day (May 25)
• Heroes Day (first Monday of July)
• Unity Day (first Tuesday of July)
• Farmers Day (first Monday of August)
• Independence Day (October 24)
• Christmas Day (December 25)

Localization

• Primary languages: English (official), Nyanja (Lusaka, Eastern), Bemba (Copperbelt, Northern)
• Regional preferences:
  • Lusaka and Eastern Province: English or Nyanja
  • Copperbelt and Northern Province: English or Bemba
  • Urban areas: English widely understood
  • Rural areas: Local languages preferred
• Use simple, clear language avoiding colloquialisms
• Test translations with native speakers before sending
• Consider UCS-2 encoding for Nyanja/Bemba if using special characters, but note 70-character limit

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain clean suppression lists
• Confirm opt-outs with acknowledgment message
• Regular database cleaning (monthly recommended)
• Document all opt-out requests for compliance audits

Testing and Monitoring

• Test across all major carriers (MTN, Airtel, Zamtel) before launching campaigns
• Monitor delivery rates by carrier (target: >95% delivery rate)
• Track engagement metrics (click-through rates, conversion rates, opt-outs)
• Regular performance reporting (weekly for active campaigns)
• A/B test message content, timing, and sender IDs

Key metrics to track:

• Delivery rate (target: >95%)
• Opt-out rate (acceptable: <2% per campaign)
• Response/engagement rate (varies by industry; 5-15% typical for promotional)
• Cost per delivered message
• Campaign ROI

Common delivery issues and troubleshooting:

• Low delivery rate on MTN: Verify sender ID is registered with MTN (MCC 64502)
• Messages blocked as spam: Review content for spam trigger words, reduce URL usage
• Inconsistent delivery times: Check API rate limits, implement queuing system
• High opt-out rates: Review message frequency, relevance, and targeting

How to Integrate SMS APIs for Zambia

Twilio

Twilio provides a robust REST API for sending SMS to Zambia. Authentication uses account SID and auth token credentials.

Pricing: Approximately USD 0.045 - 0.065 per SMS to Zambia (varies by message type and sender ID; check Twilio pricing for current rates)

import { Twilio } from 'twilio';

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

async function sendSMSToZambia(
  to: string,
  message: string,
  senderId: string
) {
  try {
    // Ensure number is in E.164 format for Zambia (+260...)
    const formattedNumber = to.startsWith('+260') ? to : `+260${to}`;

    const response = await client.messages.create({
      body: message,
      from: senderId, // Pre-registered alphanumeric sender ID
      to: formattedNumber,
    });

    console.log(`Message sent! SID: ${response.sid}`);
    return response;
  } catch (error) {
    // Handle Zambia-specific errors
    if (error.code === 21614) {
      console.error('Invalid phone number (possibly landline)');
    } else if (error.code === 21408) {
      console.error('Sender ID not registered or blocked');
    } else if (error.code === 30007) {
      console.error('Message filtered by carrier');
    }
    throw error;
  }
}

Sinch

Sinch offers SMS API access through REST endpoints with API token authentication.

Delivery receipts webhook setup:

import axios from 'axios';

interface SinchSMSResponse {
  id: string;
  status: string;
}

async function sendSinchSMS(
  apiToken: string,
  to: string,
  message: string,
  senderId: string
): Promise<SinchSMSResponse> {
  const SINCH_API_URL = 'https://sms.api.sinch.com/xms/v1';

  try {
    const response = await axios.post(
      `${SINCH_API_URL}/batches`,
      {
        from: senderId,
        to: [to],
        body: message,
        delivery_report: 'summary', // Request delivery receipts
        callback_url: 'https://your-domain.com/sinch-webhook', // Your webhook endpoint
      },
      {
        headers: {
          'Authorization': `Bearer ${apiToken}`,
          'Content-Type': 'application/json',
        },
      }
    );

    return response.data;
  } catch (error) {
    console.error('Sinch SMS Error:', error);
    throw error;
  }
}

// Webhook handler for delivery receipts
async function handleSinchWebhook(req, res) {
  const deliveryReport = req.body;
  console.log(`Message ${deliveryReport.batch_id} status: ${deliveryReport.statuses}`);
  res.status(200).send('OK');
}

MessageBird

MessageBird provides a simple REST API interface for SMS delivery to Zambia.

Status callback configuration:

import messagebird from 'messagebird';

class MessageBirdService {
  private client: any;

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

  async sendSMS(
    recipient: string,
    message: string,
    senderId: string,
    statusCallbackUrl?: string
  ): Promise<any> {
    return new Promise((resolve, reject) => {
      this.client.messages.create({
        originator: senderId,
        recipients: [recipient],
        body: message,
        reportUrl: statusCallbackUrl || 'https://your-domain.com/messagebird-status', // Delivery report webhook
      }, (err: any, response: any) => {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Plivo offers SMS capabilities through their REST API with auth ID and token authentication.

import plivo from 'plivo';

class PlivoService {
  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, // Your sender ID
        dst: to,      // Destination number
        text: message,
        url: 'https://your-domain.com/plivo-status', // Status callback URL
        method: 'POST'
      });

      return response;
    } catch (error) {
      console.error('Plivo SMS Error:', error);
      throw error;
    }
  }
}

API Rate Limits and Throughput

Provider-specific rate limits:

• Twilio: 10 messages per second (default); can request increase to 100+ msg/sec
• Sinch: 20 messages per second (standard tier); 100+ msg/sec (premium tier)
• MessageBird: 50 messages per second (default)
• Plivo: 10 messages per second (default); can request increase

Implementation best practices:

• Implement exponential backoff for retry logic (start with 1 second, double each retry)
• Use queuing systems (Redis, RabbitMQ) for high-volume sending
• Batch messages when possible (up to 100 recipients per request with most providers)
• Monitor throughput and adjust sending patterns accordingly
• Implement circuit breaker pattern to prevent cascading failures

Rate limiting with Redis example:

import Redis from 'ioredis';

class RateLimiter {
  private redis: Redis;

  constructor(redisUrl: string) {
    this.redis = new Redis(redisUrl);
  }

  async checkRateLimit(key: string, maxRequests: number, windowSeconds: number): Promise<boolean> {
    const current = await this.redis.incr(key);
    if (current === 1) {
      await this.redis.expire(key, windowSeconds);
    }
    return current <= maxRequests;
  }
}

// Usage
const limiter = new RateLimiter('redis://localhost:6379');
const allowed = await limiter.checkRateLimit('sms:zambia', 10, 1); // 10 msg/sec

Error Handling and Reporting

Common error codes specific to Zambia SMS delivery:

• 21614 (Twilio): Invalid phone number or landline
• 21408 (Twilio): Sender ID not registered or permission denied
• 30007 (Twilio): Message filtered by carrier (spam detection)
• 30008 (Twilio): Unknown destination number
• 30009 (Twilio): Missing sender ID or invalid sender ID format
• 400 (Generic): Invalid request format
• 403 (Generic): Unauthorized sender ID or blocked content
• 429 (Generic): Rate limit exceeded

Error handling implementation:

async function sendWithErrorHandling(to: string, message: string, senderId: string) {
  try {
    const response = await sendSMSToZambia(to, message, senderId);
    return { success: true, messageId: response.sid };
  } catch (error) {
    // Log error with context
    console.error('SMS Error:', {
      code: error.code,
      message: error.message,
      recipient: to,
      senderId: senderId,
      timestamp: new Date().toISOString()
    });

    // Categorize error
    if ([21614, 30008].includes(error.code)) {
      // Invalid number - do not retry
      return { success: false, error: 'invalid_number', shouldRetry: false };
    } else if ([21408, 403].includes(error.code)) {
      // Sender ID issue - alert admin
      alertAdmin('Sender ID blocked', { senderId, carrier: 'Zambia' });
      return { success: false, error: 'sender_id_blocked', shouldRetry: false };
    } else if ([30007].includes(error.code)) {
      // Content filtered - review message
      return { success: false, error: 'content_filtered', shouldRetry: false };
    } else if ([429].includes(error.code)) {
      // Rate limit - retry after delay
      return { success: false, error: 'rate_limit', shouldRetry: true, retryAfter: 60 };
    } else {
      // Unknown error - retry with backoff
      return { success: false, error: 'unknown', shouldRetry: true };
    }
  }
}

• Implement comprehensive error logging with message IDs
• Track delivery receipts (DLRs) for all messages
• Monitor message status updates asynchronously
• Set up automated alerts for high failure rates (>5%)
• Maintain error logs for troubleshooting and compliance audits

Character Encoding and Message Segmentation

GSM-7 Encoding (Standard):

• Single SMS: 160 characters maximum
• Concatenated SMS: 153 characters per segment (7 characters reserved for headers)
• Supports: Basic Latin alphabet, numbers, common punctuation
• Character set: @ £ $ ¥ è é ù ì ò Ç Ø ø Å å Δ _ Φ Γ Λ Ω Π Ψ Σ Θ Ξ and basic ASCII

UCS-2 Encoding (Unicode):

• Single SMS: 70 characters maximum
• Concatenated SMS: 67 characters per segment
• Required for: Emojis, Arabic script, Chinese characters, special symbols
• Automatically triggered when non-GSM-7 characters are detected

Concatenation Limitations in Zambia:

• As noted earlier, concatenated messages are not supported in Zambia
• Messages exceeding single-segment limits (160 chars GSM-7 or 70 chars UCS-2) may be truncated or rejected
• Recommendation: Keep all messages within single-segment limits
• Test thoroughly with local carriers before deploying campaigns

Best Practices:

• Always validate message length before sending
• Use GSM-7 encoding when possible to maximize character count
• Avoid emojis and special characters unless necessary (they trigger UCS-2)
• Implement client-side character counters to warn users
• Consider splitting long messages into multiple separate SMS with clear sequencing (e.g., "1/3", "2/3", "3/3")

Character counter implementation:

function countSMSSegments(message: string): { encoding: string; length: number; segments: number; perSegment: number } {
  // GSM-7 character set
  const gsm7 = /^[@£$¥èéùìòÇØøÅåΔ_ΦΓΛΩΠΨΣΘΞÆæßÉ !"#¤%&'()*+,\-.\/:;<=>?¡ABCDEFGHIJKLMNOPQRSTUVWXYZÄÖÑܧ¿abcdefghijklmnopqrstuvwxyzäöñüà\n\r\^{}\\[~\]|€]*$/;

  const isGSM7 = gsm7.test(message);
  const encoding = isGSM7 ? 'GSM-7' : 'UCS-2';
  const length = message.length;
  const singleLimit = isGSM7 ? 160 : 70;
  const concatLimit = isGSM7 ? 153 : 67;

  // Note: Concatenation not supported in Zambia
  const segments = length <= singleLimit ? 1 : Math.ceil(length / concatLimit);

  return { encoding, length, segments, perSegment: singleLimit };
}

// Usage
const info = countSMSSegments("Hello! Visit our store today 🎉");
console.log(info); // { encoding: 'UCS-2', length: 35, segments: 1, perSegment: 70 }

Recap and Additional Resources

Key Takeaways:

• Pre-register alphanumeric sender IDs (3-week process)
• Implement proper opt-out handling (STOP, HELP keywords)
• Respect time zone restrictions (8 AM - 8 PM CAT, UTC+2)
• Maintain proper consent documentation per Data Protection Act 2021
• Support multiple local languages (English, Nyanja, Bemba)
• Keep messages under 160 characters (GSM-7) or 70 characters (Unicode) – no concatenation support
• Use E.164 format for all phone numbers: +260XXXXXXXXX
• Register as a data controller with the Data Protection Commissioner

Implementation Checklist:

• Review ZICTA regulations and Data Protection Act 2021
• Obtain legal counsel for compliance review
• Register alphanumeric sender IDs with chosen SMS provider (allow 3 weeks)
• Register as data controller with Data Protection Commissioner
• Implement consent management system compliant with Data Protection Act 2021
• Set up HELP/STOP keyword handling in English and local languages
• Configure delivery monitoring and error tracking systems
• Test SMS delivery across all three carriers (MTN, Airtel, Zamtel)
• Establish data residency compliance (servers in Zambia)
• Implement opt-out management within 24-hour requirement

Next Steps:

1. Review ZICTA regulations and guidelines at www.zicta.zm
2. Obtain legal counsel for compliance review under Data Protection Act 2021
3. Register alphanumeric sender IDs with chosen SMS provider (allow 3 weeks)
4. Implement consent management system compliant with Data Protection Act 2021
5. Set up delivery monitoring and error tracking systems
6. Test SMS delivery across all three carriers (MTN, Airtel, Zamtel)

Additional Resources:

• ZICTA Official Website: www.zicta.zm
• ZICTA Consumer Protection: ZICTA SIM Registration
• Information and Communications Technologies Act No. 15 of 2009 (as amended)
• Data Protection Act No. 3 of 2021: Parliament of Zambia - Act No. 3
• Office of the Data Protection Commissioner: dataprotection.gov.zm
• Electronic Communications and Transactions Act No. 21 of 2021: Digital communications framework

Regulatory Contact:

• Zambia Information and Communications Technology Authority (ZICTA)
• Address: Haile Selassie Avenue, Longacres, Lusaka
• Email: info@zicta.zm
• Phone: +260 211 375 370
• Website: www.zicta.zm

Major Mobile Network Operators:

• MTN Zambia: Customer service 111 (toll-free from MTN) or +260 96 675 0750
• Airtel Zambia: Customer service 111 (toll-free from Airtel) or +260 97 777 0097
• Zamtel: Customer service 111 (toll-free from Zamtel) or +260 211 333 152, WhatsApp: +260 955 000 155

Note: URLs provided are for reference. Always verify current regulatory requirements directly with ZICTA and consult legal counsel for compliance matters specific to your use case.

Industry Associations:

• Zambia Information Technology Authority
• Communications Authority of Zambia
• Mobile Network Operators Association of Zambia