Egypt SMS Best Practices, Compliance, and Features

Understanding Egypt's SMS Market and Mobile Landscape

Market Conditions: Egypt has a vibrant mobile messaging ecosystem with over 120 million mobile subscriptions as of 2024. Four major operators dominate the market: Vodafone Egypt (40-45%), Orange Egypt (~26%), Etisalat (e& Egypt) (~22%), and WE (~14%). The telecom market is valued at $6.20 billion in 2024 and projected to reach $12.80 billion by 2032 (CAGR 9.4%). While OTT messaging apps like WhatsApp and Facebook Messenger dominate personal communications, SMS remains crucial for business communications – particularly for authentication, notifications, and marketing. Android devices hold a significant market share in Egypt, making SMS an essential channel for reaching a broad audience.

Key SMS Features and Capabilities in Egypt

When sending SMS to Egypt, you'll find robust messaging capabilities including support for concatenated messages and alphanumeric sender IDs, though two-way messaging is not supported for business communications.

Two-way SMS Support

Egypt does not support two-way SMS for A2P (Application-to-Person) messaging. Use one-way messaging for all business communications.

Alternative communication methods:

• Use WhatsApp Business API for two-way conversations
• Implement web-based chat or mobile app messaging
• Direct customers to customer service phone lines for responses
• Use email for detailed two-way communications

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is supported, though availability may vary based on sender ID type.

Message length rules: Standard 160 characters before splitting occurs using GSM-7 encoding.

Segmentation examples:

• 160 characters = 1 SMS segment
• 161-306 characters = 2 SMS segments (each max 153 characters due to concatenation headers)
• 307-459 characters = 3 SMS segments
• For Arabic (UCS-2): 70 characters = 1 segment, 71-134 characters = 2 segments (each max 67 characters)

Cost implications: Each segment is billed separately at approximately $0.3959 per segment (based on Twilio pricing). A 300-character message costs 2x a 150-character message. Plan message length accordingly to manage costs.

Encoding considerations: GSM-7 encoding supports up to 160 characters per segment, while UCS-2 encoding (used for Arabic and special characters) supports up to 70 characters before splitting.

MMS Support

MMS messages automatically convert to SMS with an embedded URL link. This ensures compatibility across all devices while still allowing rich media content to be shared through a web link. MMS is not natively supported; the conversion process generates a hosted URL where media is accessible.

Recipient Phone Number Compatibility

Number Portability

Number portability is available in Egypt through NTRA regulations. This feature doesn't significantly impact message delivery or routing – messages automatically route to the current carrier through the Mobile Number Portability (MNP) database lookup system maintained by NTRA.

Sending SMS to Landlines

You cannot send SMS to landline numbers in Egypt. Attempts to send messages to landline numbers will result in a 400 response with error code 21614, and you will not be charged.

SMS Compliance Requirements and Regulatory Guidelines in Egypt

The National Telecommunications Regulatory Authority (NTRA) is Egypt's primary regulatory body for SMS communications and telecommunications. All SMS marketing and communications must comply with NTRA guidelines, which emphasize consumer protection and proper business practices. The regulatory framework requires businesses to maintain transparency and respect user privacy rights.

Non-compliance penalties: NTRA regulation violations result in fines up to EGP 500,000 (approximately $10,000 USD). Businesses using unauthorized "gray routes" face immediate suspension and potential criminal prosecution. Egypt's Personal Data Protection Law (PDPL No. 151/2020) imposes additional fines ranging from EGP 100,000 to EGP 5 million for data protection violations.

Consent and Opt-In

Obtain explicit consent before sending any marketing or promotional messages. Best practices for obtaining and documenting consent include:

• Collect written or digital opt-in confirmation
• Maintain detailed records of consent acquisition
• Clearly state the type and frequency of messages users will receive
• Provide transparent terms and conditions
• Include the business name and purpose in consent requests

Consent retention requirements: Under Egypt's Personal Data Protection Law (PDPL No. 151/2020), retain consent records for a minimum of 3 years from the date of the last marketing message sent. Records must include timestamp, consent method, message content preview, and Data Subject information. Recipients can withdraw consent at any time.

HELP/STOP and Other Commands

• Support HELP and STOP commands in both English and Arabic for all SMS campaigns
• Standard keywords include:
  • STOP/إيقاف
  • HELP/مساعدة
  • UNSUBSCRIBE/إلغاء_الاشتراك
• Include clear opt-out instructions in all messages
• Process STOP requests immediately and send confirmation

Implementation example:

"Summer Sale! 30% off all items. Reply STOP to opt-out. Text HELP for support. - YourBrand"

"خصم 30٪ على جميع المنتجات. رد إيقاف لإلغاء الاشتراك. - علامتك التجارية"

Do Not Call / Do Not Disturb Registries

Egypt doesn't maintain a centralized Do Not Call registry. Your responsibilities:

• Maintain your own suppression lists
• Honor opt-out requests within 24 hours
• Document all opt-out requests
• Regularly clean contact lists to remove unsubscribed numbers
• Best Practice: Proactively filter numbers that have previously opted out before sending campaigns

Time Zone Sensitivity

Egypt observes strict messaging curfews:

• Marketing Messages:
  • Prohibited between 21:00 and 09:00 local time (GMT+02:00 / UTC+02:00)
  • No messages allowed on Fridays, Saturdays, or official holidays
• Transactional Messages: Can be sent 24/7 if urgent
• Time Zone: Egypt follows Eastern European Time (EET)

Time zone conversions for international senders:

• Egypt 09:00 (safe start) = 07:00 UTC = 03:00 EST = 00:00 PST
• Egypt 21:00 (cutoff) = 19:00 UTC = 15:00 EST = 12:00 PST

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

Alphanumeric Sender ID Registration

Operator network capability: Fully supported across all Egyptian carriers

Registration requirements for sending SMS to Egypt:

• Pre-registration required for domestic traffic
• Registration takes approximately 3 weeks
• Provide company documentation and NOC (No Objection Certificate) letter
• International pre-registration optional but recommended

Required documentation for domestic registration:

1. SMS Delegation Letter (LOA - Letter of Authorization) on company letterhead with authorized signatory
2. Local Trade/Company Registration License (Commercial Registry extract)
3. Company Tax Card (Egyptian tax registration certificate)
4. NOC Letter: No Objection Certificate from company authorizing SMS sender ID registration and usage
5. Proof of business operations in Egypt
6. Sample message content for approval

Registration costs: Most providers charge no direct fee for sender ID registration, though some charge administrative fees ($0-$330 USD one-time setup depending on provider). Monthly SMS costs apply separately at approximately $0.3959 per message segment.

Sender ID preservation: Yes, registered IDs are preserved across networks

Long Codes

Domestic vs. International:

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

Limitations for international long codes:

• May be blocked or filtered by local carriers
• Lower delivery rates compared to registered alphanumeric sender IDs
• Cannot guarantee sender ID preservation (carrier may replace)
• Not recommended for commercial or marketing traffic
• Best used only for international P2P messaging

Sender ID preservation: No, international long codes may be modified

Provisioning time: N/A for domestic, immediate for international

Use cases: Primarily for international communications

Short Codes

Support: Not currently supported in Egypt

Provisioning time: N/A

Use cases: N/A

Restricted SMS Content and Prohibited Industries in Egypt

Before sending SMS campaigns to Egypt, be aware that the following content categories and industries face strict restrictions under NTRA regulations and Egypt's cybersecurity laws. Violations result in fines, sender ID suspension, or criminal prosecution.

• Gambling and betting
• Political messages
• Religious content
• Adult-related material
• Alcohol and tobacco
• Pharmaceutical/drug-related content
• Cryptocurrency and financial speculation

Violation examples:

• Gambling: Any lottery, betting odds, casino promotions, or links to gambling sites
• Political: Campaign messages, party promotion, political opinions or endorsements
• Religious: Proselytizing, religious debate, or sectarian content
• Adult: Dating services, adult content, suggestive language
• Pharma: Prescription drugs, controlled substances, medical claims without approval

Content Filtering

Known carrier filtering rules:

• Carriers automatically filter messages containing blocked keywords
• URLs must be from approved domains
• Generic sender IDs (e.g., "INFO", "SMS", "NOTICE") are prohibited

Tips to avoid blocking:

• Use registered sender IDs
• Avoid spam-triggering words
• Include local brand/service name in text
• Keep URLs short and from trusted domains

SMS Marketing Best Practices for Egypt: Timing, Frequency & Localization

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear call-to-actions
• Personalize messages with recipient's name
• Use a consistent sender ID across campaigns

Sending Frequency and Timing

• Limit marketing messages to 2-3 per week per user
• Respect quiet hours and religious observances
• Plan campaigns around major holidays
• Space out messages to avoid overwhelming recipients

Localization

Language selection guidance:

• Use Arabic for consumer-facing B2C campaigns (higher engagement)
• Use English for B2B, tech-savvy audiences, or international brands
• Consider bilingual messages for broad reach (counts as longer message)
• Arabic text requires UCS-2 encoding (70 chars vs 160 for English)

Example messages:

English: "Your OTP is 123456. Valid for 10 minutes. - BankName"

Arabic: "رمز التحقق الخاص بك هو 123456. صالح لمدة 10 دقائق. - اسم البنك"

Bilingual: "Your OTP: 123456 | رمز التحقق: 123456 - BankName"

• Support both Arabic and English content
• Use proper character encoding for Arabic text
• Consider cultural sensitivities in message content
• Ensure proper rendering of special characters

Opt-Out Management

• Process opt-outs within 24 hours
• Send confirmation of successful opt-out
• Maintain comprehensive opt-out records
• Regularly audit opt-out compliance

Testing and Monitoring

Acceptable delivery rate benchmarks:

• Target: ≥95% delivery rate for transactional messages

• Acceptable: ≥90% for marketing messages

• Below 85%: Investigate sender ID issues, content filtering, or carrier blocks

• Monitor by carrier: Each of the 4 major operators should show >90% individually

• Test messages across all major carriers

• Monitor delivery rates by carrier

• Track opt-out rates and patterns

• Regularly review message performance metrics

• Test Arabic character rendering across devices

SMS API Integrations for Egypt: Twilio, Sinch, MessageBird & Plivo

Twilio SMS API for Egypt

Twilio provides a robust SMS API with comprehensive support for Egypt's messaging requirements, including sender ID registration and delivery tracking. Integration requires account credentials and proper sender ID registration.

Pricing: $0.3959 per outbound SMS segment using alphanumeric sender IDs or international numbers. Volume discounts and enterprise pricing available through sales team. View full pricing.

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 Egypt
async function sendSMSToEgypt(
  to: string,
  message: string,
  senderId: string
): Promise<void&gt; {
  try {
    // Ensure proper phone number formatting for Egypt
    const formattedNumber = to.startsWith('+20') ? to : `+20${to}`;

    const response = await client.messages.create({
      body: message,
      from: senderId, // Must be pre-registered for Egypt
      to: formattedNumber,
      // Optional parameters for delivery tracking
      statusCallback: 'https://your-callback-url.com/status'
    });

    console.log(`Message sent successfully! SID: ${response.sid}`);
  } catch (error) {
    // Egypt-specific error handling
    if (error.code === 21614) {
      console.error('Cannot send to landline number');
    } else if (error.code === 21408) {
      console.error('Sender ID not registered or blocked');
    } else if (error.code === 30007) {
      console.error('Message blocked by content filter');
    }
    throw error;
  }
}

Sinch

Sinch offers comprehensive SMS capabilities for Egypt with support for both transactional and marketing messages.

import axios from 'axios';

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

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

  async sendSMS(to: string, message: string, senderId: string): Promise<void&gt; {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.servicePlanId}/batches`,
        {
          from: senderId,
          to: [to],
          body: message,
          delivery_report: 'summary'
        },
        {
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Content-Type': 'application/json'
          }
        }
      );

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

MessageBird

MessageBird provides reliable SMS delivery in Egypt with support for Arabic content and delivery reporting.

import messagebird from 'messagebird';

class MessageBirdService {
  private client: any;

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

  sendSMS(
    to: string,
    message: string,
    senderId: string
  ): Promise<any&gt; {
    return new Promise((resolve, reject) =&gt; {
      this.client.messages.create({
        originator: senderId,
        recipients: [to],
        body: message,
        type: 'sms',
        datacoding: 'unicode' // For Arabic content support
      }, (err: any, response: any) =&gt; {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Plivo offers SMS capabilities with specific features for the Egyptian market.

import plivo from 'plivo';

class PlivoSMSService {
  private client: any;

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

  async sendSMS(
    to: string,
    message: string,
    senderId: string
  ): Promise<void&gt; {
    try {
      const response = await this.client.messages.create({
        src: senderId, // Registered sender ID
        dst: to,
        text: message,
        // Egypt-specific parameters
        url_strip_query_params: false,
        method: 'POST'
      });

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

API Rate Limits and Throughput

Provider-specific rate limits:

• Twilio: Default 100 msg/sec per account; request increase to 1,000+ msg/sec
• Sinch: 200-600 msg/sec depending on plan; enterprise plans support higher
• MessageBird: 50-100 msg/sec standard; up to 300 msg/sec on enterprise
• Plivo: 50-100 msg/sec; can be increased with carrier approval

Egypt carrier throughput limits: Local carriers support approximately 100-200 messages per second per sender ID. Exceeding this may cause queuing or temporary blocks.

• Default rate limit: 100 messages per second
• Batch processing recommended for large volumes
• Implement exponential backoff for retry logic

Strategies for Large-Scale Sending:

• Use message queuing systems (Redis, RabbitMQ)
• Implement batch processing (50-100 messages per batch)
• Monitor throughput and adjust sending rates
• Schedule campaigns during off-peak hours

Error Handling and Reporting

Common Egypt-specific error codes:

• 21614: Invalid destination (landline number)
• 21408: Unregistered or blocked sender ID
• 30007: Message blocked by content filter
• 30008: Unknown destination carrier
• 30006: Landline or unreachable carrier
• 4001: Invalid sender ID format or not registered
• 4002: Message blocked by NTRA regulations
• 4003: Number blacklisted or opted out

Retry strategies by error type:

• Permanent errors (21614, 21408, 4003): Do not retry; remove from list

• Temporary errors (rate limit, timeout): Retry with exponential backoff (5s, 15s, 45s)

• Content filter (30007, 4002): Review message content; do not retry same content

• Implement comprehensive logging

• Monitor delivery receipts

• Track common error codes

• Store delivery status updates

• Set up automated alerts for high failure rates

Recap and Additional Resources

Key Takeaways

1. Compliance First: Register your sender ID and ensure content compliance
2. Timing Matters: Respect quiet hours and cultural considerations
3. Technical Setup: Implement proper error handling and monitoring
4. Content Quality: Focus on relevant, well-formatted messages

Next Steps

1. Review Regulations

   • Visit NTRA website: www.tra.gov.eg
   • Download compliance guidelines
   • Register sender IDs (allow 3 weeks for approval)
   • Review PDPL requirements at ICLG Egypt Data Protection

2. Technical Implementation

   • Choose appropriate SMS provider (Twilio, Sinch, MessageBird, or Plivo)
   • Set up monitoring systems with delivery rate alerts
   • Test message delivery across all four carriers (Vodafone, Orange, Etisalat, WE)
   • Implement error handling for Egypt-specific error codes

3. Legal Compliance

   • Consult with local legal counsel on PDPL compliance
   • Document consent procedures with 3-year retention
   • Establish privacy policies aligned with PDPL No. 151/2020
   • Prepare for potential NTRA audits with proper record-keeping

Troubleshooting Common Issues

Issue: Low delivery rates (<85%)

• Verify sender ID is properly registered with NTRA
• Check for content filter triggers (restricted keywords/industries)
• Test across individual carriers to isolate carrier-specific issues
• Ensure phone numbers use correct E.164 format (+20XXXXXXXXXX)

Issue: Messages blocked by content filter

• Remove URLs from unapproved domains
• Avoid generic sender IDs (INFO, SMS, ALERT)
• Check message against restricted content categories
• Test with transactional content first to verify sender ID

Issue: Sender ID not displaying correctly

• Confirm registration completed for domestic traffic
• International sender IDs may be replaced by carriers
• Alphanumeric IDs must be 3-11 characters
• Avoid special characters in sender ID

Issue: High opt-out rates

• Reduce sending frequency (max 2-3 per week)
• Improve targeting and personalization
• Respect time zone restrictions (09:00-21:00 EET)
• Avoid Fridays, Saturdays, and major holidays

Additional Information:

• NTRA Guidelines: www.tra.gov.eg/en/regulation
• Egyptian Consumer Protection Law
• Mobile Operator Guidelines:
  • Vodafone Egypt
  • Orange Egypt
  • Etisalat Egypt
  • WE