PHILIPPINES (PH)

Country Summary

Country namePhilippines
ISO codePH
RegionAsia
Mobile country code515
Dialing code+63
Major carriersGlobe Telecom, Smart Communications, Sun Cellular

Guidelines

Two-way SMS supported Yes
Twilio concatenated message supportYes
Message length160 characters
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

Mobile operators do not allow messages with internatinal longcode. These would be overwritten into a generic alphanumeric outside of Twilio's platform. Twilio highly recommends sending from registered alphanumeric sender ID. 

Sender IDs containing the words "TEST," “MESSAGE,” and “SMS” along with all their permutations are not allowed. Sender IDs that portray other networks as "SMART" or "SUN" along with all their permutations (SMARTMONEY, SUNCELL, SMARTLIVE, SMARTLOAD, etc.) are not allowed.

You can send commercial and promotional advertisements, surveys, and other broadcast/push messages only to subscribers who have given prior consent or have specifically opted-in to receive such messages. PTEs and content providers shall also provide methods for subscribers who have opted-in to opt-out in the future. Regular opt-out instructions must be sent once per week for daily subscriptions or once per month for weekly subscriptions.

SPAM messages are those that contain details about financial loans, real estate offers, products and service promotions, and sometimes elections and other political propaganda. Adult content or any mention of alcohol, drugs, gambling, politics, or tobacco is prohibited.

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, 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

AlphanumericLong CodeShort Code
Pre-registrationDynamicDomesticInternational
Operator network capabilityRequiredNot SupportedSupportedNot SupportedSupported
Twilio supportedRequiredNot SupportedSupportedSupportedNot Supported
Sender ID preservedYes --- YesNo---
Provisioning time1 weekN/AN/AN/AN/A
UCS-2 supportSupportedN/ASupportedSupportedN/A
Use case restrictions

Messages that appear to be person-to-person (P2P) based on their content will be filtered.

Numeric Sender IDs will be overwritten with a generic Alphanumeric Sender ID, "TLNET," outside Twilio's platform. 

Sender IDs containing the words "TEST," “MESSAGE,” and “SMS” along with all of its permutations are not allowed.

Sender IDs that portray other networks as "SMART" or "SUN" along with all of its permutations (SMARTMONEY, SUNCELL, SMARTLIVE, SMARTLOAD, etc.) are not allowed.

Commercial and promotional advertisements, surveys and other broadcast/push messages may be sent only to subscribers who have given prior consent or have specifically opted-in to receive such messages.

Messages sent must provide methods for subscribers who have opted-in to opt-out in the future. Regular opt-out instructions must be sent once a week for daily subscriptions and once a month for weekly subscriptions.

Content relating to financial loans, real estate offers, products and service promotions, and sometimes elections and other political propaganda will be blocked. 

Adult content and any mention of alcohol, drugs, gambling, politics, and tobacco is prohibited.

N/A

You can only use local longcodes for application-to-person (A2P) messages.

N/A

N/A

Best practices

Only transactional traffic is allowed.

N/A

N/A

N/Av

N/A

Alphanumeric - Pre-registration
Operator network capabilityRequired
Twilio supportedRequired
Sender ID preservedYes
Provisioning time1 week
UCS-2 supportSupported
Use case restrictions

Messages that appear to be person-to-person (P2P) based on their content will be filtered.

Numeric Sender IDs will be overwritten with a generic Alphanumeric Sender ID, "TLNET," outside Twilio's platform. 

Sender IDs containing the words "TEST," “MESSAGE,” and “SMS” along with all of its permutations are not allowed.

Sender IDs that portray other networks as "SMART" or "SUN" along with all of its permutations (SMARTMONEY, SUNCELL, SMARTLIVE, SMARTLOAD, etc.) are not allowed.

Commercial and promotional advertisements, surveys and other broadcast/push messages may be sent only to subscribers who have given prior consent or have specifically opted-in to receive such messages.

Messages sent must provide methods for subscribers who have opted-in to opt-out in the future. Regular opt-out instructions must be sent once a week for daily subscriptions and once a month for weekly subscriptions.

Content relating to financial loans, real estate offers, products and service promotions, and sometimes elections and other political propaganda will be blocked. 

Adult content and any mention of alcohol, drugs, gambling, politics, and tobacco is prohibited.

Best practices

Only transactional traffic is allowed.

Alphanumeric - Dynamic
Operator network capabilityNot Supported
Twilio supportedNot Supported
Sender ID preserved ---
Provisioning timeN/A
UCS-2 supportN/A
Use case restrictions

N/A

Best practices

N/A

Long Code - Domestic
Operator network capabilitySupported
Twilio supportedSupported
Sender ID preservedYes
Provisioning timeN/A
UCS-2 supportSupported
Use case restrictions

You can only use local longcodes for application-to-person (A2P) messages.

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

N/A

Best practices

N/Av

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.