Locale Summary
Locale name | Philippines |
---|---|
ISO code | PH |
Region | Asia |
Mobile country code | 515 |
Dialing code | +63 |
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 | Mobile operators do not allow messages with international long codes. These will be overwritten with a generic Alphanumeric Sender ID outside of Twilio’s platform. Twilio highly recommends sending from a registered Alphanumeric Sender ID. Sender IDs containing the words “TEST”, “MESSAGE”, “SMS”, and/or permuations based on those words are not allowed. Sender IDs that portray other networks as “SMART” and/or “SUN” and/or permuations based on those words — for example, “SMARTMONEY”, “SUNCELL”, “SMARTLIVE”, “SMARTLOAD”, etc.) are not allowed. You may send commercial and promotional advertisements, surveys, and other broadcast/push messages only to subscribers who 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 which promote or offer financial loans, real estate, products and services, and sometimes relate to elections and other political messages. Adult content or any mention of alcohol, drugs, gambling, politics, and/or tobacco is prohibited.
|
Phone Numbers & Sender ID
Alphanumeric | Long Code | Short Code | |||
---|---|---|---|---|---|
Pre-registration | Dynamic | Domestic | International | ||
Operator network capability | Required | Not Supported | Supported | Not Supported | Supported |
Twilio supported |
Required
Learn more | Not Supported | Supported | Supported | Not Supported |
Sender ID preserved | Yes | --- | Yes | No | --- |
Provisioning time | 2 weeks | N/A | N/A | N/A | N/A |
UCS-2 support | Supported | N/A | Supported | Supported | N/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 outside of the Twilio platform. Sender IDs containing the words “TEST”, “MESSAGE”, “SMS”, and/or permuations based on those words are not allowed. Sender IDs that portray other networks as “SMART” and/or “SUN” and/or permuations based on those words are not allowed. See above for examples. Commercial and promotional advertisements, surveys, and other broadcast/push messages may be sent only to subscribers who 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. Financial loans, real estate offers, product and service promotions, and political messages 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 | N/A | N/A | N/A | Numeric Sender IDs will be overwritten with a generic Alphanumeric Sender ID outside of the Twilio platform and delivery is on a best-effort basis only. Twilio highly recommends sending only with a pre-registered Alphanumeric Sender ID. | N/A |
Alphanumeric - Pre-registration | |
---|---|
Operator network capability | Required |
Twilio supported |
Required
Learn more |
Sender ID preserved | Yes |
Provisioning time | 2 weeks |
UCS-2 support | Supported |
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 outside of the Twilio platform. Sender IDs containing the words “TEST”, “MESSAGE”, “SMS”, and/or permuations based on those words are not allowed. Sender IDs that portray other networks as “SMART” and/or “SUN” and/or permuations based on those words are not allowed. See above for examples. Commercial and promotional advertisements, surveys, and other broadcast/push messages may be sent only to subscribers who 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. Financial loans, real estate offers, product and service promotions, and political messages will be blocked. Adult content and any mention of alcohol, drugs, gambling, politics, and tobacco is prohibited. |
Best practices | N/A |
Alphanumeric - Dynamic | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/A |
Use case restrictions | N/A |
Best practices | N/A |
Long Code - Domestic | |
---|---|
Operator network capability | Supported |
Twilio supported | Supported |
Sender ID preserved | Yes |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | You can only use local longcodes for application-to-person (A2P) messages. |
Best practices | N/A |
Long Code - International | |
---|---|
Operator network capability | Not Supported |
Twilio supported | Supported |
Sender ID preserved | No |
Provisioning time | N/A |
UCS-2 support | Supported |
Use case restrictions | N/A |
Best practices | Numeric Sender IDs will be overwritten with a generic Alphanumeric Sender ID outside of the Twilio platform and delivery is on a best-effort basis only. Twilio highly recommends sending only with a pre-registered Alphanumeric Sender ID. |
Short Code | |
---|---|
Operator network capability | Supported |
Twilio supported | Not Supported |
Sender ID preserved | --- |
Provisioning time | N/A |
UCS-2 support | N/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.