SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Documents Required and Instructions to Register Your Alphanumeric Sender ID in Philippines

Before we begin

Due to regulatory requirements, there is sometimes a need for documents to be signed by customers to ensure that registrations are done on behalf of customers that have the right to use the Sender ID. This serves to ensure that traffic is coming from legitimate sources and minimizes any potential misuse.

This article outlines the documentation requirements for a pre-registration in Philippines.

Instructions

To register your Alphanumeric Sender ID, the network operators in Philippines require that you provide the following documents: 

 

For Domestic Entities(documents found in Domestic Customer Templates folder):

  • LOA BrandOwner x Aggregator _SenderID_SMART
  • LOA BrandOwner x Aggregator_SenderID_GLOBE
  • NO OBJECTION CERTIFICATE
  • Additional documents are required for Senders related to Banking and Financial entities

For International Entities(documents found in International Customer Templates folder):

  • LOA BrandOwner x Aggregator _SenderID_SMART
  • LOA BrandOwner x Aggregator_SenderID_GLOBE
  • LOA for End Client to Aggregator
  • Additional documents are required for Senders related to Banking and Financial entities

For Banking and Financial entities, we will also require the following list of documentation in addition to the documents found in the Customer's document template(applies for only domestic sender ID registrations)

  1. Business Registration or Articles of Incorporation
  2. Business Permit
  3. Specific regulatory agency licenses depending on industry (example: Banks require BSP licenses)
  4. Business Permit or Mayor's Permit (Current Year) from the local government unit's  (Business Permit and Licensing office) BPLO 
  5. If Sender ID to be registered has no clear relevance to business:

            - Intellectual Property Rights to the Brand Name OR

            - Secretary's Certificate specifying the proof of Sender ID relevance to the business

To get you up and running as quickly as possible, please fill out the documents completely and accurately and provide any other required information. Use the examples provided for guidance. Note that mobile network carriers are very strict about the details! We highly recommend that you download the examples (hit right click, and select 'Save Image As...') and do a side by side comparison when you are filling out the documents.

Provide the SMS Masking Authorization Letters for Sender ID Registration

This document authorizes Twilio, Inc., to register and send branded messages to end users on networks on your behalf. 

Once you have downloaded the forms, follow these general instructions: 

  1. Fill in the yellow highlighted fields—completely replace each field with your own information. If a field is not highlighted, don’t change it.
  2. If you have questions on how to fill in the required fields, refer to the annotated examples we provided for each field. 
  3. Have the documents signed by an authorized signatory of the Sender.
  4. In the highlighted fields, add the Sender’s letterhead and/or logo, stamp and sign where indicated.
  5. Upload the forms to the Twilio Alphanumeric Sender ID Registration Form.

Required fields include:

  • Sender Company’s letterhead
  • Alphanumeric Sender ID requested
  • Name of Authorized Signatory
  • Sender Company Name
  • Signature of Authorized Signatory

 

LOA BrandOwner x Aggregator _SenderID_SMART

Screenshot 2024-04-03 at 8.46.27 PM.png

LOA BrandOwner x Aggregator_SenderID_GLOBE

Screenshot 2024-04-03 at 8.47.06 PM.png

LOA for End Client to Aggregator

Screenshot 2024-04-03 at 8.47.33 PM.png

NO OBJECTION CERTIFICATE

Screenshot 2024-04-03 at 8.47.49 PM.png

 

Have more questions? Submit a request
Powered by Zendesk