INDONESIA (ID)

Country Summary

Country nameIndonesia
ISO codeID
RegionAsia
Mobile country code510
Dialing code+62
Major carriersTelkomsel, XL Axiata, Hutchinson, Indosat

Guidelines

Two-way SMS supported No
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

Delivery of messages submitted with numeric sender IDs is on best effort and will be overwritten with either random numeric or random alphanumeric sender IDs. Pre-registration of alphanumeric sender ID is required.

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. You can also read more at Indonesian Telecommunication Regulatory Authority (http://brti.or.id/).

  1. Get opt-in consent from each end user before sending any communication to them, particular 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

PreregisteredAlphanumericLong CodeShort Code
Operator network capabilityRequiredSupportedNot SupportedNot Supported
Twilio supportedRequiredNot SupportedSupportedNot Supported
Sender ID preservedYesNoYesNo
Provisioning time2-3 weeks------
UCS-2 support --------
Use case restrictions Transactional and marketing traffic are allowed.------
Best practices --Alphanumeric is only supported through pre-registrationMessages submitted with a long number might be overwritten with a generic alphanumeric outside of Twilio's platform as best effort to deliver the message--
Preregistered
Operator network capabilityRequired
Twilio supportedRequired
Sender ID preservedYes
Provisioning time2-3 weeks
UCS-2 support --
Use case restrictions Transactional and marketing traffic are allowed.
Best practices --
Alphanumeric
Operator network capabilitySupported
Twilio supportedNot Supported
Sender ID preservedNo
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices Alphanumeric is only supported through pre-registration
Long Code
Operator network capabilityNot Supported
Twilio supportedSupported
Sender ID preservedYes
Provisioning time--
UCS-2 support --
Use case restrictions --
Best practices Messages submitted with a long number might be overwritten with a generic alphanumeric outside of Twilio's platform as best effort to deliver the message
Short Code
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preservedNo
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.