sms compliance
sms compliance
Send SMS to Iraq: Compliance Guide & Sender ID Registration (2025)
Complete guide to sending SMS in Iraq. Learn CMC regulations, sender ID registration process, API integration for Zain, AsiaCell & Korek networks. Updated Jan 2025.
How to Send SMS to Iraq: Compliance, Features & Best Practices
To send SMS to Iraq, you must register your alphanumeric sender ID with local operators and comply with Communications and Media Commission (CMC) regulations. This comprehensive guide covers everything you need for compliant SMS messaging to Iraqi mobile numbers through Zain, AsiaCell, and Korek networks – including sender ID registration, technical requirements, API integration with Twilio, Sinch, and MessageBird, and regulatory best practices for 2025.
Iraq SMS Market: Operators & Network Infrastructure
| Locale name: | Iraq |
|---|---|
| ISO code: | IQ |
| Region | Middle East & Africa |
| Mobile country code (MCC) | 418 |
| Mobile network codes (MNC) | 05 (AsiaCell), 20/30 (Zain Iraq), 40 (Korek) |
| Dialing Code | +964 |
Market Conditions: Iraq's mobile market is dominated by three major operators with over 90% combined market share: Zain Iraq (41.9%), AsiaCell (39.2%), and Korek (18.9%) as of 2022. SMS remains a crucial communication channel for businesses and organizations, particularly for notifications and authentication. While OTT messaging apps like WhatsApp and Telegram are popular among consumers, SMS maintains its importance for business communications due to its reliability and universal reach. Android devices hold a significant market share in Iraq, making SMS an effective channel for reaching a broad audience.
Note: AsiaCell earned Best Network recognition in Opensignal's September – November 2024 report, winning all nine mobile experience awards.
What SMS Features Does Iraq Support?
Iraq supports one-way SMS messaging with concatenation capabilities. Two-way messaging and MMS are limited or unavailable.
Two-way SMS Support
Two-way SMS is not supported in Iraq. You can only send messages one-way from your business to consumers.
Concatenated Messages (Segmented SMS)
Support: Yes, concatenation is supported. Availability may vary by sender ID type.
Message length rules: Standard SMS length limits apply – 160 characters for GSM-7 encoding and 70 characters for UCS-2 encoding.
Encoding considerations: Both GSM-7 and UCS-2 encodings are supported. Messages using Arabic or special characters automatically use UCS-2 encoding, reducing the character limit per segment.
MMS Support
MMS messages are not directly supported in Iraq. When you send MMS content, it automatically converts to SMS with an embedded URL where recipients can view the multimedia content.
Recipient Phone Number Compatibility
Number Portability
Status: Mobile Number Portability (MNP) is being implemented in Iraq. The Communications and Media Commission (CMC) awarded the MNP project to PortingXS in 2019, with Zain, AsiaCell, and Korek working to launch the service.
Current State: As of January 2025, MNP rollout is in progress. Verify current operational status with your SMS provider, as mobile numbers may still be tied to their original network operators during the transition period.
Routing During Transition: During MNP implementation, routing may be affected. To ensure delivery:
- Work with your SMS provider to confirm MNP database access
- Implement number lookup APIs to verify current operator assignments
- Monitor delivery rates per operator to detect routing issues
- Build retry logic for failed deliveries due to incorrect routing
Sending SMS to Landlines
You cannot send SMS to landline numbers in Iraq. Attempts will result in delivery failure with a 400 response error (code 21614). These messages will not appear in logs, and your account will not be charged.
What Are Iraq's SMS Regulations & CMC Compliance Requirements?
The Communications and Media Commission (CMC - هيأة الاعلام والاتصالات) regulates SMS communications in Iraq. While specific SMS marketing regulations are still evolving, follow general telecommunications guidelines and international best practices for messaging.
Regulatory Authority: The Communications and Media Commission (CMC) is the independent regulatory body overseeing all telecommunications and SMS messaging in Iraq (established 2004). All SMS campaigns must comply with CMC guidelines.
Note: Regulatory requirements are subject to change. Verify current requirements with CMC before launching campaigns. Information current as of January 2025.
Consent and Opt-In
Explicit Consent Requirements:
- Obtain clear, documented opt-in consent before sending any marketing messages
- Maintain detailed records of when and how you obtained consent
- Include your business name and purpose in the initial opt-in request
- Provide clear terms and conditions regarding message frequency and content
Best Practices for Consent Collection:
- Use double opt-in verification for marketing lists
- Store consent records with timestamp and source
- Regularly clean and update subscriber lists
- Document opt-in language and methods used
HELP/STOP and Other Commands
- Support standard opt-out keywords (STOP, CANCEL, END, UNSUBSCRIBE) in all SMS campaigns
- Provide service information and support contact details for HELP/INFO commands
- Support both English and Arabic keywords for opt-out functionality
- Process opt-out requests immediately
Do Not Call / Do Not Disturb Registries
Iraq does not currently maintain a centralized Do Not Call registry. However, you should:
- Maintain your own suppression lists of opted-out numbers
- Honor opt-out requests within 24 hours
- Regularly clean contact lists against internal opt-out databases
- Implement systems to prevent messaging to previously opted-out numbers
Time Zone Sensitivity
Iraq follows Arabia Standard Time (AST/UTC+3). Best practices include:
- Send messages between 9:00 AM and 8:00 PM local time
- Avoid message delivery during prayer times (approximate times: Fajr 5:00 AM, Dhuhr 12:30 PM, Asr 3:30 PM, Maghrib sunset, Isha 7:30 PM)
- Respect religious observances, especially during Ramadan (avoid daytime hours, focus on evening)
- Limit non-urgent messages to business days (Sunday – Thursday in Iraq)
How to Register an Alphanumeric Sender ID for Iraq SMS
Alphanumeric Sender ID
Operator network capability: Fully supported across major networks Registration requirements: Required – All unregistered sender IDs will be rejected Sender ID preservation: Yes, sender IDs are preserved when properly formatted
Registration Process:
| Step | Action | Timeline |
|---|---|---|
| 1. Prepare documents | Gather business registration certificate and letter of authorization | 1 – 2 days |
| 2. Submit application | Apply through your SMS provider or directly with operators | Same day |
| 3. Review period | Wait for operator review and approval | 5 – 10 business days |
| 4. Activation | Begin using your sender ID once approved | Immediate |
| 5. Annual renewal | Renew registration annually to maintain access | Before expiration |
Document Requirements:
- Business registration certificate (certified copy)
- Letter of authorization on company letterhead
- Trade license (if applicable)
- Contact information for authorized representative
Registration Fees: Contact your SMS provider or operators directly for current fee schedules. Fees vary by operator and may include initial registration and annual renewal costs.
Common Rejection Scenarios:
- Generic terms (e.g., "INFO," "ALERT," "PROMO")
- Misleading identifiers not matching business name
- Special characters or spaces in sender ID
- Length exceeding 11 characters
- Incomplete documentation
Additional Considerations:
- Maximum length: 11 characters
- Must represent your business name or brand
- Avoid generic terms or misleading identifiers
- Special characters and spaces not recommended
- Operators will block non-compliant messages
Long Codes
Domestic vs. International:
- Domestic long codes not supported
- International long codes supported with limitations
Sender ID preservation: No, international numbers may be converted to local format Provisioning time: N/A Use cases: Not recommended for primary messaging; use alphanumeric sender IDs instead
Short Codes
Support: Not currently available in Iraq Provisioning time: N/A Use cases: N/A
What Content Is Restricted in Iraq SMS Messaging?
Restricted Content Types:
- Gambling and betting services
- Adult content or explicit material
- Political messaging without proper authorization
- Cryptocurrency and unauthorized financial services
- Religious content without proper permissions
Compliant Message Examples:
- ✓ "Your order #12345 has shipped. Track at [URL]."
- ✓ "Reminder: Your appointment is tomorrow at 2:00 PM."
- ✓ "Your verification code is 123456. Valid for 10 minutes."
Non-Compliant Message Examples:
- ✗ "Win big at our new casino! Click now."
- ✗ "Invest in Bitcoin now – guaranteed returns!"
- ✗ Messages with adult content or explicit material
Penalties: Violations may result in sender ID suspension, account termination, or regulatory fines.
Content Filtering
Known Carrier Filters:
- Certain keywords in Arabic or English (e.g., "free money," "guaranteed," "casino")
- URLs from suspicious or blacklisted domains
- High-frequency messaging patterns (exceeding 100 messages/hour per sender ID)
- Generic or numeric sender IDs
Volume Thresholds: Most operators flag accounts exceeding:
- 100 messages per hour to new recipients
- 500 messages per day without proper sender ID registration
- Repeated messages with identical content to different recipients
Best Practices to Avoid Filtering:
- Use registered alphanumeric sender IDs
- Avoid URL shorteners in messages (use full domain names)
- Maintain consistent sending patterns
- Include clear business identifier in messages
SMS Best Practices for Iraq: Timing, Frequency & Localization
Messaging Strategy
- Keep messages under 160 characters when possible
- Include clear call-to-action in each message
- Use personalization (customer name, relevant details)
- Maintain consistent sender ID across campaigns
Sending Frequency and Timing
General Guidelines:
- Limit to 3 – 4 messages per week per recipient
- Avoid sending during religious holidays
- Space out bulk campaigns to prevent network congestion
- Monitor delivery rates for optimal timing
Prayer Times (approximate, varies by season and location):
- Fajr: 5:00 AM
- Dhuhr: 12:30 PM
- Asr: 3:30 PM
- Maghrib: Sunset (around 6:00 PM)
- Isha: 7:30 PM
Avoid sending messages 15 minutes before and after prayer times.
Ramadan-Specific Guidelines:
- Do not send messages between sunrise and sunset during Ramadan
- Focus message delivery on evening hours (after Iftar, 7:00 PM – 11:00 PM)
- Reduce message frequency by 50% during this period
- Avoid promotional content; focus on essential transactional messages
Localization
- Support both Arabic and English content
- Use proper character encoding for Arabic text
- Consider cultural sensitivities in message content
- Provide customer support in both languages
Opt-Out Management
- Process opt-outs within 24 hours
- Maintain centralized opt-out database
- Include opt-out instructions in messages
- Regular audit of opt-out compliance
Testing and Monitoring
Testing Requirements:
- Test messages across all major carriers (Zain, AsiaCell, Korek)
- Monitor delivery rates by carrier
- Track engagement metrics when possible
- Regular testing of opt-out functionality
Expected Delivery Rates:
| Operator | Expected Delivery Rate | Typical Delivery Time |
|---|---|---|
| Zain Iraq | 95 – 98% | 1 – 5 seconds |
| AsiaCell | 95 – 98% | 1 – 5 seconds |
| Korek | 90 – 95% | 2 – 8 seconds |
Common Failure Scenarios:
- Unregistered sender ID (Error: Sender ID rejected)
- Invalid phone number format (Error: Invalid recipient)
- Network congestion during peak hours (Error: Temporary delivery failure)
- Content filtering triggered (Error: Message blocked by operator)
Troubleshooting Steps:
- Verify sender ID registration status
- Confirm phone number format (+964XXXXXXXXX)
- Check delivery reports for specific error codes
- Test with different operators to isolate issues
- Contact your SMS provider for operator-specific guidance
Iraq SMS API Integration: Twilio, Sinch & MessageBird
Provider Comparison
| Feature | Twilio | Sinch | MessageBird |
|---|---|---|---|
| Alphanumeric sender ID | ✓ | ✓ | ✓ |
| Arabic text support | ✓ | ✓ | ✓ |
| Delivery receipts | ✓ | ✓ | ✓ |
| Batch messaging | ✓ | ✓ | Limited |
| Rate limit (msg/sec) | Up to 250 | Up to 100 | Up to 60 |
| Iraq-specific docs | Yes | Yes | Limited |
| Pricing transparency | High | Medium | Medium |
Twilio
Twilio provides robust SMS capabilities for sending messages to Iraq through their REST API.
Key Integration Points:
- Authentication using Account SID and Auth Token
- Support for alphanumeric sender IDs
- Automatic handling of concatenated messages
- Delivery receipt webhooks
import { Twilio } from 'twilio';
// Initialize the client
const client = new Twilio(
process.env.TWILIO_ACCOUNT_SID, // Your Account SID
process.env.TWILIO_AUTH_TOKEN // Your Auth Token
);
async function sendSMSToIraq() {
try {
// Send message with proper Iraq formatting
const message = await client.messages.create({
body: 'Your message in English or Arabic',
from: 'YourBrand', // Alphanumeric sender ID
to: '+964xxxxxxxxx' // Iraq number format
});
// Log success
console.log(`Message sent successfully! SID: ${message.sid}`);
return message;
} catch (error) {
// Handle errors appropriately
console.error('Error sending message:', error);
throw error;
}
}Sinch
Sinch offers direct operator connections in Iraq with support for alphanumeric sender IDs.
Key Integration Points:
- API key authentication
- Batch messaging support
- Delivery status callbacks
- Unicode support for Arabic text
import { SinchClient } from '@sinch/sdk-core';
// Initialize Sinch client
const sinchClient = new SinchClient({
projectId: 'YOUR_PROJECT_ID',
apiToken: 'YOUR_API_TOKEN'
});
async function sendBatchMessages() {
try {
const response = await sinchClient.sms.batches.send({
from: 'CompanyName', // Your sender ID
to: ['+964xxxxxxxxx'], // Array of Iraqi numbers
body: 'Your message content',
// Optional parameters for Iraq
encoding: 'AUTO', // Handles Arabic text automatically
deliveryReport: 'FULL'
});
console.log('Batch ID:', response.id);
return response;
} catch (error) {
console.error('Batch sending failed:', error);
throw error;
}
}MessageBird
MessageBird provides reliable SMS delivery to Iraq with comprehensive delivery reporting.
Key Integration Points:
- REST API with API key authentication
- Support for multiple character encodings
- Scheduled message delivery
- Detailed delivery reports
import messagebird from 'messagebird';
// Initialize MessageBird client
const mbClient = messagebird('YOUR_API_KEY');
// Function to send SMS to Iraq
function sendMessageToIraq(
recipient: string,
message: string,
senderId: string
): Promise<any> {
return new Promise((resolve, reject) => {
mbClient.messages.create({
originator: senderId, // Your sender ID
recipients: [recipient], // Iraq number with +964
body: message,
// Optional parameters
datacoding: 'unicode', // For Arabic text
reportUrl: 'YOUR_WEBHOOK_URL'
}, (err, response) => {
if (err) {
reject(err);
return;
}
resolve(response);
});
});
}API Rate Limits and Throughput
Rate Limits (approximate – verify with your provider):
- Twilio: Up to 250 messages per second (varies by account type and region)
- Sinch: Up to 100 messages per second (varies by account configuration)
- MessageBird: Up to 60 messages per second (varies by account tier)
Note: These are general throughput guidelines. Actual rate limits depend on your account type, destination country, and provider agreements. Contact your SMS provider for Iraq-specific rate limits and throughput guarantees.
Throughput Management Strategies:
- Implement exponential backoff for retries
- Use batch APIs for bulk sending
- Queue messages during peak times
- Monitor delivery rates by carrier
Error Handling and Reporting
Common Error Codes:
| Error Code | Cause | Solution |
|---|---|---|
| 21211 | Invalid "To" phone number | Verify number format (+964XXXXXXXXX) |
| 21408 | Permission denied for sender ID | Register sender ID with operators |
| 21614 | Cannot send to landline | Use mobile numbers only |
| 30003 | Unreachable destination | Verify number is active and in service |
| 30005 | Unknown destination | Check number format and operator |
| 30006 | Landline or unreachable | Use mobile numbers only |
| RATE_LIMIT_EXCEEDED | Too many requests | Implement rate limiting and retry logic |
Best Practices:
// Example error handling implementation
async function sendSMSWithRetry(
recipient: string,
message: string,
maxRetries = 3
): Promise<void> {
let attempts = 0;
while (attempts < maxRetries) {
try {
await sendSMS(recipient, message);
return;
} catch (error) {
attempts++;
if (error.code === 'RATE_LIMIT_EXCEEDED') {
// Wait exponentially longer between retries
await delay(Math.pow(2, attempts) * 1000);
continue;
}
if (error.code === 'INVALID_RECIPIENT') {
// Don't retry invalid numbers
console.error(`Invalid recipient: ${recipient}`);
break;
}
if (attempts === maxRetries) {
console.error(`Failed to send after ${maxRetries} attempts`);
throw error;
}
}
}
}Frequently Asked Questions (FAQ)
What SMS features are supported in Iraq?
Iraq supports one-way SMS messaging with concatenation capabilities. Two-way SMS and MMS are not directly supported. MMS content automatically converts to SMS with an embedded URL link.
Do I need to register my sender ID for Iraq SMS?
Yes, alphanumeric sender ID registration is required in Iraq. Unregistered sender IDs will be rejected by operators. Submit your application with business documentation (registration certificate, authorization letter) and allow up to 10 business days for approval. Registration must be renewed annually. Your sender ID should be 11 characters maximum and represent your business name or brand clearly.
Which mobile operators serve Iraq?
The three major mobile operators in Iraq are Zain Iraq, AsiaCell, and Korek Telecom. All three support SMS messaging with alphanumeric sender IDs.
What is the regulatory authority for SMS in Iraq?
The Communications and Media Commission (CMC - هيأة الاعلام والاتصالات) regulates telecommunications and SMS messaging in Iraq. Visit www.cmc.iq for official guidelines.
Can I send SMS to landline numbers in Iraq?
No, you cannot send SMS to landline numbers in Iraq. Attempts will result in delivery failure with error code 21614, and your account will not be charged.
What time should I send SMS messages in Iraq?
Send messages between 9:00 AM and 8:00 PM Arabia Standard Time (UTC+3). Avoid messaging during prayer times (approximately 15 minutes before and after: Fajr 5:00 AM, Dhuhr 12:30 PM, Asr 3:30 PM, Maghrib sunset, Isha 7:30 PM) and respect religious observances, especially during Ramadan.
Is number portability available in Iraq?
Mobile Number Portability (MNP) is being implemented in Iraq. The CMC awarded the MNP project to PortingXS in 2019, and the three major operators are working on the rollout. As of January 2025, verify the current operational status with your SMS provider, as numbers may still be tied to their original operators during the transition period.
What character encoding should I use for Arabic text?
Use UCS-2 encoding for Arabic text messages. Standard SMS allows 160 characters with GSM-7 encoding or 70 characters with UCS-2 encoding per segment.
Do I need consent to send marketing SMS in Iraq?
Yes, obtain clear, documented opt-in consent before sending marketing messages. Maintain records of when and how you obtained consent, and support opt-out keywords (STOP, CANCEL, END, UNSUBSCRIBE) in both English and Arabic.
What API providers support SMS messaging to Iraq?
Twilio, Sinch, and MessageBird all provide reliable SMS delivery to Iraq with support for alphanumeric sender IDs, Arabic text encoding, and delivery reporting.
How much does it cost to send SMS to Iraq?
Pricing varies by provider and volume. Contact Twilio, Sinch, or MessageBird for current pricing. Expect costs between $0.02 – $0.08 per message segment, with volume discounts available.
What should I do if my messages aren't being delivered?
First, verify your sender ID registration status. Then check phone number format (+964XXXXXXXXX), review delivery reports for error codes, test with different operators, and contact your SMS provider for operator-specific guidance.
Recap and Additional Resources
Key Takeaways
-
Compliance Priorities:
- Obtain explicit consent
- Honor opt-out requests
- Respect time zone restrictions
- Maintain proper sender ID format
-
Technical Considerations:
- Use alphanumeric sender IDs
- Support Arabic character encoding
- Implement proper error handling
- Monitor delivery rates
-
Best Practices:
- Test thoroughly before bulk sending
- Maintain clean subscriber lists
- Document consent and opt-outs
- Regular monitoring and reporting
Next Steps
Quick-Start Checklist:
| Task | Timeline | Status |
|---|---|---|
| Review CMC regulations | 1 day | ☐ |
| Register sender ID with operators | 5 – 10 business days | ☐ |
| Set up test accounts with SMS providers | 1 – 2 days | ☐ |
| Implement error handling and monitoring | 2 – 3 days | ☐ |
| Establish consent collection processes | 3 – 5 days | ☐ |
| Conduct test sends across all operators | 1 day | ☐ |
| Launch pilot campaign | 1 week | ☐ |
Additional Resources
Frequently Asked Questions
How to send SMS messages in Iraq?
Use a reputable SMS API provider like Twilio, Sinch, or MessageBird, ensuring you use an alphanumeric sender ID and comply with local regulations. Iraq supports one-way SMS and concatenated messages, but not two-way messaging or direct MMS. Remember to handle Arabic encoding with UTF-8 or UCS-2.
What is the best sender ID type for Iraq SMS?
Alphanumeric sender IDs are recommended for Iraq. They allow up to 11 characters representing your brand and are fully supported across major networks. International long codes are supported but not recommended, while domestic long codes and short codes are not available.
Why does Iraq not support MMS messages directly?
MMS is not directly supported; however, when MMS content is sent, it's converted to an SMS with a URL link to the media. This workaround allows recipients to access rich media content while ensuring message delivery via the more universally supported SMS.
What are the character limits for SMS in Iraq?
Standard SMS length limits apply: 160 characters for GSM-7 encoding and 70 characters for UCS-2. Messages with Arabic or special characters use UCS-2, effectively reducing the characters per segment. Concatenation is supported for longer messages.
When should I send SMS messages in Iraq?
Adhere to Arabia Standard Time (AST/UTC+3) and send messages between 9:00 AM and 8:00 PM local time. Avoid sending during prayer times or religious holidays, especially Ramadan. Limit messages to 3-4 per week per recipient, primarily during business days (Sunday-Thursday).
Can I send SMS to landlines in Iraq?
No, sending SMS to landlines in Iraq is not possible. Attempts result in delivery failure with a 400 response error (code 21614). These messages aren't logged, and accounts aren't charged.
How to comply with SMS regulations in Iraq?
Obtain explicit opt-in consent before sending marketing messages, honor opt-out requests (STOP, CANCEL, END, UNSUBSCRIBE) within 24 hours, and respect time zone restrictions. While Iraq doesn't have a Do Not Call registry, maintain your own opt-out list.
What is the process for getting consent for SMS marketing in Iraq?
Obtain clear, documented opt-in consent, including your business name and purpose. Double opt-in verification is recommended. Maintain records of consent with timestamps and source, and provide clear terms and conditions.
What are the restricted content types for SMS in Iraq?
Avoid gambling, adult content, unauthorized political or religious content, and cryptocurrency promotions. Content filtering exists for certain Arabic and English keywords, suspicious URLs, and high-frequency messaging.
How to use Twilio for sending SMS to Iraq?
Initialize the Twilio client with your Account SID and Auth Token. Use the client's messages.create method, providing the message body, your alphanumeric sender ID, and the recipient's Iraq number in +964 format.
How to handle Arabic text in SMS messages for Iraq?
Use UTF-8 or UCS-2 encoding for Arabic text. SMS providers like Sinch offer 'AUTO' encoding, automatically handling Arabic. Ensure your chosen API supports Unicode to prevent character corruption.
What are the API rate limits for SMS providers in Iraq?
Twilio's rate limit is 250 messages per second, Sinch allows 100 per second, and MessageBird 60 per second. Manage throughput by using batch APIs, queuing messages during peak times, and using exponential backoff for retries.
What are the common SMS error scenarios in Iraq?
Common errors include invalid sender ID format, network connectivity issues, exceeding rate limits, and invalid recipient numbers. Implement proper error handling, including retries with exponential backoff and logging of persistent failures.