Country Summary

Country namePakistan
ISO codePK
RegionAsia
Mobile country code410
Dialing code+92

Guidelines

Two-way SMS supported No
Number portability availableYes
Twilio concatenated message supportYes
Message length-----
Twilio MMS supportConverted to SMS with embedded URL
Sending SMS to landline numbersYou 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

Per local regulations, peer-to-peer (P2P) traffic is prohibited toward operators in Pakistan.

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:

  1. Get opt-in consent from each end-user before sending any communication to them, particularly for marketing or other non-essential communications.
  2. Only communicate during an end-user’s daytime hours unless it is urgent.
  3. SMS campaigns should support HELP/STOP messages, and similar messages, in the end-user’s local language.
  4. Do not contact end-users on do-not-call or do-not-disturb registries.

Phone Numbers & Sender ID

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilitySupportedNot SupportedNot SupportedNot SupportedSupported
Twilio supported Supported Supported
Learn more
--- SupportedNot Supported
Sender ID preservedYesNo --- No---
Provisioning time15 business daysN/AN/AN/AN/A
UCS-2 supportSupportedSupportedN/ASupportedN/A
Use case restrictions

Pre-registration is currently only supported for domestic customers.

Dynamic Alphanumeric Sender IDs are not supported by all mobile operators in Pakistan. Sender IDs may be overwritten with a random shortcode or a generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability.

N/A

Dynamic Numeric Sender IDs are not supported by all mobile operators in Pakistan. Sender IDs may be overwritten with a random shortcode or a Generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability.

N/A

Best practices

N/A

N/A

N/A

---

N/A

Alphanumeric - Pre-registration
Operator network capabilitySupported
Twilio supported Supported
Sender ID preservedYes
Provisioning time15 business days
UCS-2 supportSupported
Use case restrictions

Pre-registration is currently only supported for domestic customers.

Best practices

N/A

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supported Supported
Learn more
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

Dynamic Alphanumeric Sender IDs are not supported by all mobile operators in Pakistan. Sender IDs may be overwritten with a random shortcode or a generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability.

Best practices

N/A

Long Code - Domestic
Operator network capabilityNot Supported
Twilio supported ---
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - International
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedNo
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

Dynamic Numeric Sender IDs are not supported by all mobile operators in Pakistan. Sender IDs may be overwritten with a random shortcode or a Generic Alphanumeric Sender ID outside the Twilio platform to ensure deliverability.

Best practices---
Short Code
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preserved---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

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.