Qatar SMS Compliance Guide: Regulations, Best Practices & API Integration

Qatar SMS Market Overview

Qatar's Communications Regulatory Authority (CRA) enforces strict SMS regulations: mandatory sender ID registration, explicit consent requirements, and restricted messaging hours. Send business messages successfully through Ooredoo and Vodafone Qatar networks by following these compliance requirements and best practices.

Market Conditions: Qatar operates a highly developed mobile market with near-universal smartphone penetration and mobile connection rates exceeding 156% of the population (indicating widespread multi-device usage). Work with two primary mobile operators: Ooredoo and Vodafone Qatar. While customers use WhatsApp and Telegram for personal communication, SMS remains crucial for business communications – especially for authentication and notifications. Android dominates with 77.23% market share, while iOS accounts for 22–23% (StatCounter, March 2025).

Key SMS Features and Capabilities in Qatar

Qatar supports most standard SMS features, including concatenated messaging and alphanumeric sender IDs. Two-way messaging is not available through standard channels. MMS converts automatically to SMS with an embedded URL link.

Two-way SMS Support

Qatar does not support two-way SMS through standard channels. For interactive messaging capabilities, use WhatsApp Business API, implement web-based callbacks triggered by one-way SMS, or use QR codes linking to web forms.

Concatenated Messages (Segmented SMS)

Support: Yes. Send concatenated messages for most sender ID types.

Message length rules: GSM-7 encoding allows 160 characters per segment. UCS-2 encoding (for Arabic or special characters) allows 70 characters per segment.

Cost implications: Carriers charge per segment. A 200-character message counts as 2 segments and costs 2× the base rate.

MMS Support

Qatar converts MMS messages to SMS with an embedded URL link to your media content. Use short URLs and include clear context in your message body.

Technical specifications:

• Maximum file size: 5 MB per attachment
• Supported formats: JPG, PNG, GIF, MP4, PDF
• URL expiration: 30 days from delivery

Recipient Phone Number Compatibility

Number Portability

Qatar supports Mobile Number Portability (MNP) since 2013. Customers switch between Ooredoo and Vodafone Qatar while retaining their mobile numbers. The porting process takes one working day after application submission. Messages automatically route to the current carrier regardless of the number's original operator. Format all phone numbers using E.164 format (+974 followed by the subscriber number).

MNP statistics: Approximately 15,000–20,000 numbers port annually between carriers. Update your carrier routing tables monthly to maintain optimal delivery rates.

Source: Qatar Communications Regulatory Authority (CRA), MNP Service Documentation

Sending SMS to Landlines

SMS to landline numbers fails in Qatar. The API returns a 400 error (code 21614) with no message delivery and no charge.

Number validation strategy: Validate numbers before sending using this regex pattern for Qatar mobile numbers: ^\+?974[3567]\d{7}$. Use the Numverify API or similar lookup services to verify number types and prevent landline attempts.

Compliance and Regulatory Guidelines for SMS in Qatar

The Communications Regulatory Authority (CRA), established by Emiri Decree 42 of 2014, regulates SMS communications in Qatar under Decree Law Number 34 of 2006. Comply with Qatar's telecommunications laws and data protection regulations, particularly Qatar Law No. 13 of 2016 on Personal Data Privacy. For businesses sending SMS to US numbers, review the 10DLC SMS registration requirements.

Penalties for non-compliance: Fines range from QAR 50,000 to QAR 3,000,000 depending on violation severity. Repeat violations result in sender ID suspension (30–90 days) or permanent revocation.

Important 2025 Update: The CRA mandates cessation of 3G mobile telecommunications services (IMT-2000) by December 31, 2025. Both Ooredoo and Vodafone Qatar will cease third-generation services by this deadline to optimize spectrum resources for 4G/LTE and 5G networks.

Source: CRA Decision on 3G Service Termination (2025)

Consent and Opt-In

Explicit Consent Requirements:

• Obtain written or electronic consent before sending marketing messages
• Store consent records for minimum 3 years (CRA requirement)
• State the purpose of communication during opt-in
• Obtain separate consent for different message types (transactional vs. marketing)

Consent template example:

"I agree to receive SMS messages from [Company Name] about [specific purpose: promotions/account updates/etc.]. Standard message rates apply. Reply STOP to unsubscribe. View our privacy policy at [URL]."

Best Practices for Consent:

• Implement double opt-in verification
• Log timestamp, source channel, IP address, and consent scope
• Update consent records when customers modify preferences
• Provide clear terms and conditions during opt-in

HELP/STOP and Other Commands

Support these standard keywords in English and Arabic:

• STOP/إيقاف
• HELP/مساعدة
• UNSUBSCRIBE/إلغاء_الاشتراك

Response templates:

• STOP: "You've been unsubscribed from [Company Name]. No further messages will be sent. Text START to resubscribe."
• HELP: "[Company Name] SMS help: Reply STOP to unsubscribe. Message and data rates may apply. Contact: support@company.com"

Implementation: Use keyword detection with language auto-detection (check for Arabic Unicode ranges U+0600 to U+06FF). Respond within 60 seconds in the detected language.

Do Not Call / Do Not Disturb Registries

Qatar doesn't maintain a centralized DND registry. Maintain your own:

• Store suppression lists in a dedicated database table with indexed phone_number field
• Process opt-out requests within 24 hours
• Filter opted-out numbers before every campaign send
• Audit suppression lists monthly

Database schema recommendation:

CREATE TABLE suppression_list (
  phone_number VARCHAR(20) PRIMARY KEY,
  opt_out_date TIMESTAMP NOT NULL,
  opt_out_source VARCHAR(50),
  reason TEXT
);
CREATE INDEX idx_opt_out_date ON suppression_list(opt_out_date);

Time Zone Sensitivity

Messaging Hours:

• Send messages between 8 AM and 9 PM Qatar time (GMT+3)
• Allow exceptions for critical service notifications: fraud alerts, system outages, emergency account access, time-sensitive authentication codes
• Respect weekend timing (Friday–Saturday in Qatar)
• Avoid sending during prayer times

Prayer time integration: Use the Aladhan API (api.aladhan.com) to fetch daily prayer times for Doha. Block message sending ±15 minutes around each of the five daily prayers (Fajr, Dhuhr, Asr, Maghrib, Isha).

Phone Number Options and SMS Sender Types in Qatar

Alphanumeric Sender ID

Operator network capability: Fully supported

Registration requirements:

• Complete pre-registration for both Ooredoo and Vodafone Qatar networks (mandatory)
• Allow 5–10 business days for approval (up to 2 weeks maximum)
• Provide company documentation (Commercial Registration Certificate for Qatar-based companies, or No Objection Certificate for international companies)
• Use 3–11 alphanumeric characters
• Match your sender ID to your company name or brand
• Do not use dynamic sender IDs

Step-by-step registration process:

1. Prepare NOC letters on company letterhead with authorized signature and stamp
2. Email Ooredoo at enterprise@ooredoo.qa with "Sender ID Registration" in subject
3. Email Vodafone Qatar business support at business@vodafone.qa
4. Attach: NOC letter (PDF), Commercial Registration Certificate, SMS use case description
5. Wait 5–10 business days for approval confirmation
6. Configure approved sender ID in your SMS provider dashboard

Common rejection reasons:

• Generic sender IDs (e.g., "INFO", "ALERT", "SMS")
• Missing company stamp or unauthorized signatory
• Sender ID doesn't match company registration documents
• Incomplete NOC letter missing required fields

Sender ID preservation: Yes, your registered IDs preserve across both Ooredoo and Vodafone networks

Required Documentation:

• Submit NOC letters for both Local Ooredoo NOC Qatar and Vodafone Qatar Pre-Reg Letter
• Use company letterhead with authorized signatory signature and stamp
• Submit documents in PDF format

Source: Twilio Qatar Registration Requirements, Unifonic Qatar Sender ID Documentation (2025)

Long Codes

Domestic vs. International:

• Domestic long codes: Not supported
• International long codes: Available with limitations

Limitations: Carriers may modify international numbers during routing. Delivery rates are 15–20% lower than registered alphanumeric sender IDs. Some carriers block international long codes for marketing messages.

Sender ID preservation: No

Provisioning time: Not applicable for domestic

Use cases: Transactional messaging and 2FA only

Short Codes

Support: Not available in Qatar. No timeline announced for future availability.

Alternative: Use alphanumeric sender IDs for premium messaging and brand recognition.

Provisioning time: Not applicable

Use cases: Not available

Restricted SMS Content, Industries, and Use Cases

Prohibited Content:

• Adult content: sexually explicit material, adult entertainment services
• Gambling: betting, casinos, lottery services
• Political messages: campaign communications, political party promotions
• Religious content: proselytizing, religious conversion messages
• Government impersonation: falsely representing government agencies
• Cryptocurrency promotions: trading platforms, ICO announcements

Regulated Industries:

• Financial services: Submit Qatar Financial Centre Regulatory Authority (QFCRA) license, use case documentation, and message templates
• Healthcare: Comply with Qatar's health data privacy regulations, obtain patient consent for health-related communications
• Insurance: Provide Qatar Financial Centre or Ministry of Commerce approval documentation

Content Filtering

Carrier Filtering Rules:

• Carriers block messages containing restricted keywords automatically
• URLs must come from approved domains
• Content screening filters prohibited terms

Examples of blocked keywords: "free money," "guaranteed win," "casino," "18+," specific Arabic terms related to prohibited content (carriers do not publish complete lists).

URL domain approval process: Submit domain ownership verification (DNS TXT record) and website content review to carrier compliance teams. Approval takes 3–5 business days.

Best Practices:

• Use full domain URLs instead of shortened links
• Submit message templates for pre-approval in regulated industries
• Maintain consistent sender IDs across campaigns
• Keep content professional and clear

Best Practices for Sending SMS in Qatar

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear calls-to-action
• Use approved sender IDs consistently
• Personalize messages appropriately

Message template examples:

Transactional: "Your verification code is 123456. Expires in 10 minutes. Do not share this code. – [CompanyName]"

Marketing: "[CompanyName]: New sale starts today! Get 25% off sitewide. Shop now: company.com/sale Reply STOP to opt out"

Reminder: "Hi [Name], your appointment is tomorrow at 2 PM. Reply C to confirm or R to reschedule. – [CompanyName]"

Sending Frequency and Timing

• Limit to 3–4 messages per week per recipient
• Respect local holidays and Ramadan timing
• Avoid peak hours (12–2 PM, 6–8 PM) to ensure better delivery
• Space out bulk campaigns

Ramadan-specific guidelines: Reduce frequency to 1–2 messages per week. Send only between 9 AM–12 PM or 9–10 PM (after Iftar). Avoid all marketing messages during prayer times and the last 10 days of Ramadan.

Qatar public holidays: Eid al-Fitr (3–4 days), Eid al-Adha (4–5 days), Qatar National Day (December 18), National Sports Day (February). Avoid marketing messages on these dates.

Localization

• Support both Arabic and English
• Use right-to-left text formatting for Arabic
• Consider local cultural sensitivities
• Use local date and time formats

RTL implementation: Use Unicode bidirectional algorithm. Set text direction with HTML dir="rtl" attribute or Unicode Right-to-Left Override (U+202E). Test Arabic text rendering across devices. Encode Arabic characters in UCS-2 (UTF-16).

Cultural sensitivities in Qatar: Avoid references to alcohol, pork, or romantic relationships. Use formal Arabic (Modern Standard Arabic) rather than colloquial dialects for business communications. Respect Islamic holidays and prayer times. Address recipients respectfully (use honorifics when appropriate).

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain clear opt-out records
• Include opt-out instructions in every message
• Regularly audit opt-out compliance

Opt-out message placement examples:

• Footer format 1: "Reply STOP to unsubscribe"
• Footer format 2: "Text STOP to opt out | Msg rates may apply"
• Footer format 3: "إيقاف STOP للإلغاء"

Testing and Monitoring

• Test across Ooredoo and Vodafone networks
• Monitor delivery rates by carrier
• Track engagement metrics
• Regularly test opt-out functionality

KPI benchmarks for Qatar:

• Delivery rate: 95–98% (target)
• Acceptable failure rate: <2%
• Response rate (marketing): 2–5%
• Opt-out rate: <0.5% per campaign

Monitoring tools: Use Twilio Console, Sinch Dashboard, or third-party tools like MessageBird Analytics. Set alerts for delivery rates below 90%, error rates above 5%, or unusual spike in opt-outs (>1% in 24 hours).

SMS API Integrations for Qatar

Twilio

Authenticate with your Account SID and Auth Token to send SMS through Twilio's REST API.

import { Twilio } from 'twilio';

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

// Function to send SMS to Qatar
async function sendSMSToQatar(
  message: string,
  recipientNumber: string,
  senderId: string
) {
  try {
    // Ensure number is in E.164 format for Qatar (+974)
    const formattedNumber = recipientNumber.startsWith('+974')
      ? recipientNumber
      : `+974${recipientNumber}`;

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

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

Webhook implementation for status callbacks:

// Express webhook endpoint
app.post('/status', (req, res) => {
  const { MessageSid, MessageStatus, To, ErrorCode } = req.body;

  console.log(`Message ${MessageSid} to ${To}: ${MessageStatus}`);

  if (ErrorCode) {
    console.error(`Error ${ErrorCode}: ${req.body.ErrorMessage}`);
  }

  // Update database with delivery status
  // await updateMessageStatus(MessageSid, MessageStatus);

  res.sendStatus(200);
});

Sinch

Send SMS directly to Qatar with Sinch's carrier connections and Unicode message support.

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 sendSMS(message: string, recipient: string, senderId: string) {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.serviceId}/batches`,
        {
          from: senderId,
          to: [recipient],
          body: message,
          // Qatar-specific parameters
          encoding: 'AUTO',  // Handles Arabic text automatically
          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

Send SMS to Qatar with MessageBird's strong delivery rates and comprehensive features.

import { MessageBird } from 'messagebird';

class MessageBirdService {
  private client: MessageBird;

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

  async sendSMS(
    message: string,
    recipient: string,
    senderId: string
  ): Promise<any&gt; {
    return new Promise((resolve, reject) =&gt; {
      this.client.messages.create({
        originator: senderId,
        recipients: [recipient],
        body: message,
        // Qatar-specific options
        datacoding: 'unicode',  // For Arabic support
        reportUrl: 'https://your-domain.com/delivery-reports'
      }, (err, response) =&gt; {
        if (err) {
          reject(err);
        } else {
          resolve(response);
        }
      });
    });
  }
}

Plivo

Send reliable SMS to Qatar with Plivo's high-volume messaging capabilities.

import plivo from 'plivo';

class PlivoSMSService {
  private client: plivo.Client;

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

  async sendSMS(message: string, recipient: string, senderId: string) {
    try {
      const response = await this.client.messages.create({
        src: senderId,  // Registered sender ID
        dst: recipient, // Qatar number in E.164 format
        text: message,
        // Qatar-specific parameters
        url_strip_query_params: false,
        powerpack_id: 'your_powerpack_id'  // If using Powerpack
      });

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

Batch sending example for high-volume campaigns:

// Batch sending with rate limiting
async function sendBatchSMS(
  messages: Array<{to: string_ body: string}>,
  senderId: string,
  rateLimit: number = 10 // messages per second
) {
  const delay = 1000 / rateLimit;

  for (const msg of messages) {
    try {
      await sendSMSToQatar(msg.body, msg.to, senderId);
      await new Promise(resolve => setTimeout(resolve, delay));
    } catch (error) {
      console.error(`Failed to send to ${msg.to}:`, error);
      // Log failure for retry
    }
  }
}

API Rate Limits and Throughput

Provider-specific rate limits for Qatar:

• Twilio: 1 message/second (default), upgrade to 10–100/second
• Sinch: 10 messages/second (default), contact for higher limits
• MessageBird: 5 messages/second (default), 50/second for enterprise
• Plivo: 5 messages/second (default), 20/second with Powerpack

Implementation:

• Implement exponential backoff for retry logic (start with 1s, double on each retry, max 30s)
• Use queuing systems (Redis, RabbitMQ) for high-volume sending
• Consider batch APIs for bulk messages

Queuing system implementation example:

import Queue from 'bull';

const smsQueue = new Queue('sms-qatar', 'redis://127.0.0.1:6379');

// Add messages to queue
smsQueue.add({
  to: '+9741234567',
  body: 'Your message',
  senderId: 'YourBrand'
}, {
  attempts: 3,
  backoff: { type: 'exponential', delay: 2000 }
});

// Process queue
smsQueue.process(async (job) => {
  const { to, body, senderId } = job.data;
  return await sendSMSToQatar(body, to, senderId);
});

Error Handling and Reporting

// Common error handling implementation
interface SMSError {
  code: string;
  message: string;
  timestamp: Date;
  provider: string;
}

class SMSErrorHandler {
  static handleError(error: any, provider: string): SMSError {
    return {
      code: error.code || 'UNKNOWN',
      message: error.message,
      timestamp: new Date(),
      provider
    };
  }

  static async logError(error: SMSError): Promise<void&gt; {
    // Implement your logging logic here
    console.error(`SMS Error [${error.provider}]:`, error);
  }
}

Common error codes specific to Qatar:

Frequently Asked Questions About Qatar SMS

How long does sender ID registration take in Qatar?

Sender ID registration in Qatar takes 5–10 business days for approval, with a maximum timeframe of 2 weeks. Complete pre-registration for both Ooredoo and Vodafone Qatar networks. Submit company documentation (Commercial Registration Certificate for Qatar-based companies or No Objection Certificate for international companies) along with NOC letters for both operators on company letterhead with authorized signatory and stamp.

Is number portability available in Qatar?

Yes, Qatar supports Mobile Number Portability (MNP). The service has been operational since 2013, allowing customers to switch between Ooredoo and Vodafone Qatar while retaining their mobile numbers. The porting process takes one working day after application submission. Messages automatically route to the current carrier regardless of the number's original operator, so MNP does not significantly impact SMS delivery.

What time can I send SMS messages in Qatar?

Send SMS messages between 8 AM and 9 PM Qatar time (GMT+3). Allow exceptions only for critical service notifications. Respect weekend timing (Friday–Saturday in Qatar) and avoid sending during prayer times. Violating these time restrictions may result in regulatory penalties (QAR 50,000–3,000,000) and damage your sender reputation.

What are Qatar's SMS compliance requirements?

Qatar's Communications Regulatory Authority (CRA) enforces strict SMS compliance requirements: obtain explicit written or electronic consent before sending marketing messages, register all alphanumeric sender IDs with both Ooredoo and Vodafone Qatar networks, respect messaging hours (8 AM–9 PM Qatar time), support HELP/STOP keywords in English and Arabic, process opt-outs within 24 hours, and maintain consent records for 3 years. The CRA regulates telecommunications under Decree Law Number 34 of 2006.

Can I use alphanumeric sender IDs in Qatar?

Yes, alphanumeric sender IDs are fully supported in Qatar, but mandatory pre-registration is required for both Ooredoo and Vodafone Qatar networks. Use 3–11 alphanumeric characters that match your company name or brand. Dynamic sender IDs are not allowed. Your registered sender IDs preserve across both networks after approval.

What content is prohibited in Qatar SMS messages?

Prohibited SMS content in Qatar includes: adult content, gambling, political messages, religious content, government impersonation, and cryptocurrency promotions. Regulated industries like financial services, healthcare, and insurance require additional verification and special approval. Carriers automatically block messages containing restricted keywords and screen content for prohibited terms.

Do I need separate registrations for Ooredoo and Vodafone Qatar?

Yes, complete separate sender ID registrations for both Ooredoo and Vodafone Qatar networks. Submit individual NOC letters (Local Ooredoo NOC Qatar and Vodafone Qatar Pre-Reg Letter) for each operator on company letterhead with authorized signatory signature and stamp. Both registrations process within 5–10 business days. Submit documentation for both networks simultaneously to ensure complete coverage.

Does Qatar support two-way SMS messaging?

No, Qatar does not support two-way SMS through standard channels. For interactive messaging capabilities, use WhatsApp Business API, implement web-based callbacks triggered by one-way SMS, or use QR codes linking to web forms. Long codes and short codes for two-way messaging are not currently available in Qatar's telecommunications infrastructure.

Recap and Additional Resources

Key Takeaways

1. Compliance Priorities

   • Pre-register all sender IDs (allow 5–10 business days)
   • Respect time restrictions (8 AM–9 PM Qatar time, GMT+3)
   • Maintain proper opt-out mechanisms (process within 24 hours)

2. Technical Considerations

   • Support Unicode for Arabic text
   • Implement proper error handling
   • Monitor delivery rates across both operators

3. Next Steps

   • Review CRA regulations at www.cra.gov.qa
   • Implement proper consent management
   • Set up monitoring and reporting systems

Implementation checklist:

• Week 1: Submit sender ID registrations to Ooredoo and Vodafone (5–10 days)
• Week 1: Implement consent management system with 3-year record retention
• Week 2: Configure SMS provider accounts and API integration
• Week 2: Set up HELP/STOP keyword auto-responses in English and Arabic
• Week 2: Build suppression list database with indexed phone numbers
• Week 3: Implement prayer time blocking using Aladhan API
• Week 3: Add number validation (E.164 format, mobile vs. landline)
• Week 3: Configure delivery webhooks and error handling
• Week 4: Test across Ooredoo and Vodafone networks
• Week 4: Set up monitoring dashboards and alerting (delivery rate <90%)
• Ongoing: Audit opt-out compliance monthly

Additional Resources

• Qatar Communications Regulatory Authority: www.cra.gov.qa
  • Telecommunications Regulations: www.cra.gov.qa/en/regulations-policies
  • License Applications: www.cra.gov.qa/en/services/licensing
• Ooredoo Business Solutions: Ooredoo.qa
  • Enterprise SMS Services: www.ooredoo.qa/en/business/sms
• Vodafone Qatar Business: business.vodafone.qa
• Qatar Data Protection Law: www.qcb.gov.qa
  • Law No. 13 of 2016 on Personal Data Privacy

Industry Guidelines:

• Qatar SMS Marketing Association Guidelines
• CRA Compliance Framework for Messaging Services (CRA Circular 2023-04)
• Qatar Digital Business Guidelines

Developer communities:

• Twilio Qatar Community: community.twilio.com
• GCC Telecom Developers Forum: gcc-telecom-dev.slack.com
• Qatar IT Society: qitcom.org.qa