Locale Summary
| Locale name | Qatar |
|---|---|
| ISO code | QA |
| Region | Middle East & Africa |
| Mobile country code | 427 |
| Dialing code | +974 |
Guidelines
| Two-way SMS supported | No |
|---|---|
| Twilio concatenated message support | Yes |
| Message length | 160 Characters |
| Twilio MMS support | Converted to SMS with embedded URL |
| Sending SMS to landline numbers | You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged. |
| Compliance considerations | Adult, political, governmental, and religious content is prohibited. Messages containing such content will be filtered out and accounts deny-listed. Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:
|
Phone Numbers & Sender ID
| Alphanumeric | Long Code | Short Code | |||
|---|---|---|---|---|---|
| Pre-registration | Dynamic | Domestic | International | ||
| Operator network capability | Supported | Supported | Supported | --- | --- |
| Twilio supported | Supported |
Supported
Learn more | Supported | --- | Not Supported |
| Sender ID preserved | Yes | Yes | Yes | --- | --- |
| Provisioning time | 2 weeks | --- | --- | --- | --- |
| UCS-2 support | --- | --- | --- | --- | --- |
| Use case restrictions | Adult, political, governmental, and religious content is prohibited. Messages containing such content will be filtered out and accounts deny-listed. | --- | --- | --- | --- |
| Best practices | Local network operators tend to deactivate Sender IDs which were registered in the past but are not used for a considerable period of time. We suggest our clients make sure that they keep sending traffic periodically to the specific destination once they register their Alpha Sender IDs. If the Sender ID is deactivated due to inactivity then the customer needs to reinitiate the registration procedure. | Use only pre-registered Alphanumeric Sender IDs to ensure message delivery. | Messages submitted with Numeric Sender IDs may experience delivery issues. Twilio recommends pre-registering an Alphanumeric Sender ID to ensure message delivery. | --- | --- |
| Alphanumeric - Pre-registration | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | 2 weeks |
| UCS-2 support | --- |
| Use case restrictions | Adult, political, governmental, and religious content is prohibited. Messages containing such content will be filtered out and accounts deny-listed. |
| Best practices | Local network operators tend to deactivate Sender IDs which were registered in the past but are not used for a considerable period of time. We suggest our clients make sure that they keep sending traffic periodically to the specific destination once they register their Alpha Sender IDs. If the Sender ID is deactivated due to inactivity then the customer needs to reinitiate the registration procedure. |
| Alphanumeric - Dynamic | |
|---|---|
| Operator network capability | Supported |
| Twilio supported |
Supported
Learn more |
| Sender ID preserved | Yes |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | Use only pre-registered Alphanumeric Sender IDs to ensure message delivery. |
| Long Code - Domestic | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | Messages submitted with Numeric Sender IDs may experience delivery issues. Twilio recommends pre-registering an Alphanumeric Sender ID to ensure message delivery. |
| Long Code - International | |
|---|---|
| Operator network capability | --- |
| Twilio supported | --- |
| Sender ID preserved | --- |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | --- |
| Short Code | |
|---|---|
| Operator network capability | --- |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | --- |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.