Country Summary
| Country name | Philippines |
|---|---|
| ISO code | PH |
| Region | Asia |
| Mobile country code | 515 |
| Dialing code | +63 |
| Major carriers | Globe Telecom, Smart Communications, Sun Cellular |
Guidelines
| Two-way SMS supported | Yes |
|---|---|
| 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 | When sending messages to the Philippines using Twilio's global SMS-enabled numbers, Sender IDs that have not been pre-registered will be converted to a predetermined Alphanumeric value. 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.
|
Phone Numbers & Sender ID
| Alphanumeric | Long Code | Short Code | |||
|---|---|---|---|---|---|
| Pre-registration | Dynamic | Domestic | International | ||
| Operator network capability | Supported | Not Supported | Not Supported | --- | Not Supported |
| Twilio supported | Supported | Not Supported | Supported | --- | Not Supported |
| Sender ID preserved | Yes | No | No | --- | --- |
| Provisioning time | 1 week | --- | --- | --- | --- |
| UCS-2 support | --- | --- | --- | --- | --- |
| 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. | Alphanumeric Sender IDs that are not pre-registered will be overwritten with a generic Alphanumeric Sender ID, "TLNET," outside Twilio's platform. | Non-local Numeric Sender IDs will be overwritten to generic Alphanumeric Sender IDs outside Twilio's platform; however, local Numeric Sender IDs will be delivered intact. You can only use local Numeric Sender IDs for application-to-person (A2P) messages. | --- | --- |
| Best practices | Only transactional traffic is allowed. | --- | --- | --- | --- |
| Alphanumeric - Pre-registration | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | 1 week |
| UCS-2 support | --- |
| 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 capability | Not Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | No |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | Alphanumeric Sender IDs that are not pre-registered will be overwritten with a generic Alphanumeric Sender ID, "TLNET," outside Twilio's platform. |
| Best practices | --- |
| Long Code - Domestic | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Supported |
| Sender ID preserved | No |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | Non-local Numeric Sender IDs will be overwritten to generic Alphanumeric Sender IDs outside Twilio's platform; however, local Numeric Sender IDs will be delivered intact. You can only use local Numeric Sender IDs for application-to-person (A2P) messages. |
| Best practices | --- |
| 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 | Not Supported |
| 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.