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 | ----- |
| 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, the sender ID 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 messages. PTEs and content providers shall also provide methods for subscribers who have opted-in to opt out at a future time. 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 are prohibited.
|
Phone Numbers & Sender ID
| Preregistered | Alphanumeric | Long Code | Short Code | |
|---|---|---|---|---|
| Operator network capability | Required | Supported | Not Supported | Not Supported |
| Twilio supported | Required | Supported | Supported | Not Supported |
| Sender ID preserved | Yes | Yes | No | --- |
| Provisioning time | 1 week | -- | -- | -- |
| UCS-2 support | -- | -- | -- | -- |
| Use case restrictions | -- | Alphanumeric senderId is only supported through pre-registration | Non-local numeric senderId would be overwritten into generic alphanumeric outside Twilio's platform whilst local numeric senderId would be delivered intact. Local numeric senderId must only be used for A2P messages. | -- |
| Best practices | Only transactional traffic allowed. | -- | -- | -- |
| Preregistered | |
|---|---|
| Operator network capability | Required |
| Twilio supported | Required |
| Sender ID preserved | Yes |
| Provisioning time | 1 week |
| UCS-2 support | -- |
| Use case restrictions | -- |
| Best practices | Only transactional traffic allowed. |
| Alphanumeric | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Supported |
| Sender ID preserved | Yes |
| Provisioning time | -- |
| UCS-2 support | -- |
| Use case restrictions | Alphanumeric senderId is only supported through pre-registration |
| Best practices | -- |
| Long Code | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Supported |
| Sender ID preserved | No |
| Provisioning time | -- |
| UCS-2 support | -- |
| Use case restrictions | Non-local numeric senderId would be overwritten into generic alphanumeric outside Twilio's platform whilst local numeric senderId would be delivered intact. Local numeric senderId must only be used for A2P messages. |
| 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.