Philippines SMS Guide: Senders & Opt-In

At a glance

A quick operational read on the Philippines. Sender registration and blocking dates come from the provider and operator layer; opt-in, quiet-period and privacy duties come from the NTC circulars and the Data Privacy Act. Anything marked route-dependent is confirmed for the specific path your traffic uses.

SMS to mobile: Supported on selected A2P routes
Number format: +63 9XX XXX XXXX — ten national digits after +63
Domestic trunk zero: A domestic form written 09XX XXX XXXX carries a trunk 0 that is not part of the international number
Number validation: Confirm the destination is Philippine, messaging-capable mobile and resolve the current operator before routing
Mobile number portability: Available under Republic Act 11202; subscribers keep the number when they change operator
Prefix is not the operator: Do not infer the current operator from the prefix; resolve it at send time
Registered alphanumeric sender: Supported and preserved on Twilio's current preregistered Philippines route
Unregistered alphanumeric sender: Blocked on Twilio's route since 7 April 2025
Dynamic alphanumeric sender: Not supported on Twilio's current Philippines route
Domestic long code: Supported on Twilio; inbound MO is available when configured, and outbound MT may be filtered or restricted on that route
International long code: Not supported on Twilio's current Philippines route
Dedicated short code: Operator-capable in the Philippines but not offered by Twilio's current route
Two-way SMS: Supported when the selected service is explicitly configured for inbound messaging
Inbound testing: Treat replies as unavailable until inbound is configured and tested end to end on the path you buy
Concatenation: Supported, with sender-type and encoding qualifications
Unicode / UCS-2: Supported on Twilio's registered-alphanumeric and domestic-long-code rows
Encoding validation: Test the real English, Filipino and other local-language copy and its true segment count on the exact route
MMS: Converted by Twilio to an SMS containing a URL
SMS to fixed lines: Not supported on Twilio's standard Philippines route
URL handling: URL registration, allow-listing, filtering and sender compatibility are provider and operator policy on the selected path
Marketing and broadcast: Commercial and promotional broadcast/push messages require prior consent or a specific opt-in, and an opt-out method must be provided, under the NTC broadcast-message framework
Broadcast quiet period: Within the NTC broadcast/push framework, covered messages are not to be sent between 21:00 and 07:00, except for paid subscription services
Subscription content services: NTC MC 07-08-2018 adds double opt-in, disclosure, record-keeping and keyword duties for the content and information subscription services it covers
Direct marketing and privacy: Republic Act 10173 requires transparency, a declared legitimate purpose, valid consent where consent is the basis, and it gives data subjects the right to withdraw consent and object to direct marketing
Permission standard: Launch on prior affirmative, attributable, purpose-specific and SMS-channel-specific permission unless qualified Philippine counsel documents another valid basis
SIM registration: Republic Act 11934 governs the registration of subscriber SIMs; it is a separate regime from marketing permission
SIM registration and sender programmes: Subscriber SIM registration does not satisfy an A2P provider sender-registration or sender-programme requirement on the selected route
Last reviewed: 1 August 2026

Route-dependent: “Route-dependent” means the behaviour is decided by the provider, aggregator and operator path your traffic uses, not by Philippine law. Two suppliers can behave differently on the same day, and a route can change its policy. Confirm before launch.

Law, route policy and recommendation

Philippine A2P messaging is regularly described as one rulebook. It is not. Sender registration is a route requirement, consent and quiet hours come from the NTC circulars, privacy duties come from the Data Privacy Act, and none of them substitutes for the others.

Law / regulation
Law and regulation
Philippine numbering, mobile number portability under Republic Act 11202, the NTC broadcast and push-message circulars, the separately scoped subscription content-service rules, and Republic Act 10173 with its implementing rules. These bind you whichever supplier you use.
Carrier or route policy
Carrier or route policy
Sender preregistration and blocking, dynamic-sender support, domestic and international long-code behaviour, short-code availability, inbound support, concatenation, UCS-2, MMS conversion, landline handling, URL allow-listing and content filtering, and category acceptance. This layer changes independently of the law.
Flowstates recommendation
Flowstates operational recommendation
What we ask customers to do because it protects deliverability and keeps you comfortably inside both of the layers above. Deliberately stricter than the legal or route minimum.

Numbering and networks

The basics your validation layer and templates need to get right before the first send.

Law / regulationNumbering plan
The Philippines uses ITU country code +63 and mobile country code 515. Ordinary Philippine mobile numbers are stored internationally as +63 followed by ten national digits beginning with 9.
Law / regulationDomestic trunk zero
A domestic mobile number may be written 09XX XXX XXXX. The leading 0 is a national trunk prefix and is not part of the international number.
Flowstates recommendationNormalisation
Remove the domestic trunk 0 when normalising to E.164 and store +63 plus the ten national digits. Normalise at capture rather than at send time, so the same contact cannot exist in two formats.
Flowstates recommendationValidation before sending
A syntactically valid number is not automatically messaging-capable. Validate Philippine jurisdiction, line type and mobile capability, and resolve the current operator before routing.
Law / regulationMobile number portability
Mobile number portability is available under Republic Act 11202, the Mobile Number Portability Act. Telecommunications Connectivity Inc. is the official service entity for Philippine mobile number portability, and the national service began operating in 2021.
Flowstates recommendationCurrent-operator lookup
Because portability is live, the prefix does not prove the current operator. Resolve the operator at send time instead of caching one against a contact record.
Carrier or route policyNetworks to plan for
Representative operational paths include Globe, Smart and DITO, plus other current or contracted MVNO paths where applicable. Not every supplier holds direct coverage on every path.
Flowstates recommendationPath testing
Test each representative network you actually need, and re-test after a route or sender change rather than assuming one successful path represents the country.
Carrier or route policyFixed lines
SMS to Philippine fixed-line destinations is unsupported on Twilio's standard route.
Flowstates recommendationFixed-line destinations
Do not treat Philippine fixed-line destinations as a delivery channel. Validate line type before routing and route them to a voice or email path instead.

E.164 example

+63 9XX XXX XXXX

A deliberately masked example: country code 63, then the ten national digits beginning with 9. If the number arrives as 09XX XXX XXXX, drop the domestic trunk 0 before storing it.

Sender options

Philippine A2P sender choice is largely determined by the route you buy. Registered alphanumeric senders carry brand identity on current paths, and domestic long codes are the inbound-capable option.

Carrier or route policy

This whole comparison — best for, what the recipient sees and replies — describes provider and operator route behaviour and programme availability on current Philippine paths, not Philippine law. NTC consent, identification, opt-out and quiet-period duties and Data Privacy Act obligations apply regardless of which sender you choose.

Registered alphanumeric sender

Best for: One-way OTP, transactional or service and permissioned marketing traffic where the selected provider and operator path accepts the category
What the recipient sees: The approved brand sender; preserved on Twilio's current preregistered route
Replies: No direct reply path; provide a working alternative support and opt-out route

Philippines domestic long code

Best for: Inbound-capable conversational and service flows, and responses to user-initiated messages where provider and operator policy permits outbound MT
What the recipient sees: The local Philippine number assigned to the service
Replies: Yes, when inbound SMS is explicitly configured and tested

Dedicated short code

Best for: Selected local high-scale programmes where carrier and provider support is confirmed
What the recipient sees: The approved short code
Replies: Route- and programme-dependent

International numeric or dynamic sender

Best for: Not a supported production choice on Twilio's current Philippines route
What the recipient sees: Unavailable, rejected or not preserved according to the selected route
Replies: No reliable reply path

Sender options
Option	Best for	What the recipient sees	Replies
Registered alphanumeric sender	One-way OTP, transactional or service and permissioned marketing traffic where the selected provider and operator path accepts the category	The approved brand sender; preserved on Twilio's current preregistered route	No direct reply path; provide a working alternative support and opt-out route
Philippines domestic long code	Inbound-capable conversational and service flows, and responses to user-initiated messages where provider and operator policy permits outbound MT	The local Philippine number assigned to the service	Yes, when inbound SMS is explicitly configured and tested
Dedicated short code	Selected local high-scale programmes where carrier and provider support is confirmed	The approved short code	Route- and programme-dependent
International numeric or dynamic sender	Not a supported production choice on Twilio's current Philippines route	Unavailable, rejected or not preserved according to the selected route	No reliable reply path

Route policy: on Twilio's current Philippines route, alphanumeric sender IDs require preregistration and unregistered ones have been blocked since 7 April 2025, dynamic alphanumeric senders are unsupported, domestic long codes are supported with inbound MO when configured while outbound MT may be filtered, international long codes are unsupported, and short codes are operator-capable but not offered.

What changes by traffic type

The same Philippine destination behaves very differently depending on the category you send, the sender type you registered and the permission you actually hold.

OTP / authentication

Suitable on a registered alphanumeric sender, or on an approved domestic long code where an inbound flow is intentional.

Flowstates recommendation
Prefer a registered alphanumeric sender for one-way OTP, and use a domestic long code only where an intentional inbound flow is approved and tested.
Flowstates recommendation
Keep the copy purely transactional, concise and within one segment where practical.
Flowstates recommendation
Identify the brand and the purpose, and include an appropriate code-expiry cue.
Flowstates recommendation
No promotional copy in authentication templates.
Flowstates recommendation
Use a branded full domain only when a link is genuinely necessary and accepted on the selected route.
Flowstates recommendation
Document the user action and context that caused the OTP. That record supports the authentication exchange; it is not marketing permission.
Flowstates recommendation
Monitor delivery, latency, completed-verification conversion and per-route and per-operator performance rather than submitted-versus-delivered counts alone.
Flowstates recommendation
Configure failover, but make sure every fallback sender and path is itself valid for the Philippines and for the traffic you are sending.
Carrier or route policy
Replies only exist where inbound is configured on the selected service.
Flowstates recommendation
Do not design an authentication flow around a reply unless inbound is configured and tested on the path you buy.

Transactional / service

Suitable for expected alerts, confirmations, account updates and support on a valid sender.

Flowstates recommendation
Keep the content within the purpose for which the number was provided.
Flowstates recommendation
Identify the brand and the purpose in the body of the message.
Carrier or route policy
Branded links are deliverable only where the URL and the sender type are accepted on the selected path.
Flowstates recommendation
A service context does not create permission for unrelated marketing. The category follows the content and purpose, not the template name.
Flowstates recommendation
Test sender preservation or replacement, URLs, concatenation, Unicode and MMS conversion on the exact path before launch.
Flowstates recommendation
Maintain an objection, revocation and suppression process for every recurring programme, with a named owner.
Flowstates recommendation
Keep marketing copy out of transactional templates.

Marketing / promotional

NTC broadcast-message duties and Data Privacy Act obligations both apply, and route acceptance is a separate question again.

Law / regulation
NTC Memorandum Circular 03-03-2005 and Memorandum Circular 04-07-2009 cover commercial and promotional advertisements, surveys and other broadcast or push messaging.
Law / regulation
Covered broadcast and push messaging requires prior written consent or a specific affirmative opt-in or operative act by the subscriber.
Law / regulation
A subscriber who does not respond to an opt-in request has not opted in, and the covered broadcast messaging must stop.
Law / regulation
Covered broadcast and push messages are not to be sent between 21:00 and 07:00, except for paid subscription services.
Law / regulation
The message must identify the public telecommunications entity or content-provider company and provide a valid address or number, together with an opt-out command, as required by the NTC framework.
Law / regulation
NTC Memorandum Circular 07-08-2018 imposes stricter double opt-in, disclosure, record-retention, weekly opt-out-instruction and keyword requirements on the content and information subscription services it covers. It is a scoped rule, not a universal requirement for every ordinary A2P marketing campaign.
Law / regulation
Republic Act 10173 requires personal data to be processed transparently, for a declared and legitimate purpose and proportionately. Where consent is the basis it must be freely given, specific and informed, and a data subject may withdraw consent and object to direct marketing.
Flowstates recommendation
Flowstates launch standard is prior affirmative, attributable, purpose-specific and SMS-channel-specific permission for every promotional programme, unless qualified Philippine counsel documents another valid basis.
Flowstates recommendation
Do not use bought or rented lists.
Flowstates recommendation
Recognise STOP, END, CANCEL, UNSUBSCRIBE and QUIT plus reasonable natural-language English or Filipino equivalents. Outside the specifically scoped NTC subscription-service rule, do not present one keyword as the only way to opt out.
Flowstates recommendation
Suppress immediately and across every sending system rather than at the next campaign build.
Flowstates recommendation
Use a branded full domain. Do not use public or shared shorteners.
Carrier or route policy
Category acceptance, URL allow-listing and sender eligibility remain route-specific and are confirmed privately rather than published as a list.

Philippines broadcast messaging and data-privacy rules

Three separate bodies of Philippine rule are involved, and they are constantly merged in supplier documentation: the NTC broadcast and push-message circulars, the scoped subscription content-service circular, and the Data Privacy Act. Route policy is a fourth layer that is not law at all.

Law / regulation
NTC Memorandum Circular 03-03-2005 and Memorandum Circular 04-07-2009 govern commercial and promotional advertisements, surveys and other broadcast or push messages sent to mobile subscribers.
Law / regulation
Covered broadcast and push messages may only be sent to subscribers who have given prior written consent or specifically opted in through an affirmative operative act.
Law / regulation
Silence is not consent: a subscriber who does not respond to an opt-in request is treated as not having opted in, and the covered broadcast must be stopped.
Law / regulation
Covered broadcast and push messages are not to be sent between 21:00 and 07:00, except for paid subscription services.
Law / regulation
The sending public telecommunications entity or content-provider company must be identified, with a valid address or contact number and an opt-out command, as the NTC framework requires.
Law / regulation
Emergency, distress, public-service, network and consumer-advisory messaging falls outside the commercial broadcast description to the extent the regulation excludes it.
Flowstates recommendation
Do not use an excluded service or advisory category to carry marketing content. Send promotional material only under the covered broadcast rules and your documented permission.
Law / regulation
NTC Memorandum Circular 07-08-2018 applies to the content and information subscription-service framework it covers, not to every A2P SMS use case.
Law / regulation
Within that scoped framework the rule requires double opt-in with confirmation disclosures, retention of opt-in and opt-out records until at least six months after opt-out, free opt-out instructions provided at least weekly, and recognition of STOP, END, CANCEL, UNSUBSCRIBE and QUIT on a case-insensitive basis.
Law / regulation
Within that same scoped framework, opt-in, opt-out and covered customer-service messages and calls are free to the subscriber.
Flowstates recommendation
Do not present the subscription-service requirements as universal. Apply them where the covered service model genuinely applies, and apply the ordinary broadcast rules plus our permission standard everywhere else.
Law / regulation
Republic Act 10173, the Data Privacy Act of 2012, and its implementing rules apply to processing personal data. Direct marketing is processing targeted at particular individuals, so it is squarely within scope.
Law / regulation
Processing must be transparent, for a specified and legitimate declared purpose, and proportionate to that purpose.
Law / regulation
Where consent is the basis, it must be freely given, specific and informed, and evidenced by a declaration or an affirmative action by the data subject.
Law / regulation
The data subject has the right to be informed about the processing, including its purpose and scope.
Law / regulation
The data subject may withdraw consent and may object to processing for direct marketing. Where a valid objection is made, processing for direct marketing must cease unless another lawful basis genuinely applies and is explained.
Flowstates recommendation
Retain attributable evidence for every permission: the purpose, the channel, the notice version presented, the source, the timestamp and the full suppression history.
Law / regulation
Republic Act 11934, the SIM Registration Act, and its implementing rules govern the registration of subscriber SIMs. It is a separate regime from marketing permission and does not create permission to send marketing.
Carrier or route policy
Subscriber SIM registration does not register an A2P brand sender and does not satisfy a provider sender-registration or sender-programme requirement on the route you buy.
Flowstates recommendation
Keep SIM-registration questions separate from your sender and permission evidence, so a subscriber registration record is never presented as sender approval or as marketing consent.
Carrier or route policy
Sender preregistration and blocking dates, alphanumeric, long-code and short-code availability, inbound support, URL and content filtering, template allow-listing, UCS-2 support, MMS conversion, landline handling and category acceptance are provider and operator route policy. They are neither NTC consent law nor the Data Privacy Act, and satisfying one does not satisfy the other.

Operational compliance checklist

What we expect to see in place before a Philippines route goes live.

Flowstates recommendation
Store destinations as +63 plus the ten national mobile digits, removing the domestic trunk zero.
Flowstates recommendation
Validate Philippine jurisdiction, line type and mobile capability before routing.
Flowstates recommendation
Resolve the current operator at send time and never infer it from the prefix, because portability is available.
Flowstates recommendation
Select a registered alphanumeric sender, an approved domestic long code or an approved short code as applicable to the route you buy.
Flowstates recommendation
Confirm sender registration status, preservation or replacement, inbound support and fallback behaviour before launch rather than during it.
Flowstates recommendation
Keep brand, website, use case, permission journey, templates and live traffic materially aligned.
Flowstates recommendation
Separate OTP, service and marketing purposes, templates and permission records.
Law / regulation
Covered marketing and broadcast traffic requires prior written consent or a specific affirmative opt-in from the subscriber.
Flowstates recommendation
Retain evidence of that permission, including the exact disclosure, source, timestamp, purpose and channel.
Law / regulation
Provide the required sender or company identity and a working opt-out route in covered broadcast messages.
Law / regulation
For covered subscription content and information services, apply double opt-in, confirmation disclosures, weekly free opt-out instructions, six-month post-opt-out record retention and the official keywords.
Law / regulation
Apply the 21:00 to 07:00 restriction within the NTC broadcast and push-message scope.
Law / regulation
Honour withdrawal of consent and objections to direct marketing.
Flowstates recommendation
Suppress immediately across every sending system rather than at the next campaign build.
Flowstates recommendation
Do not use bought or rented lists.
Flowstates recommendation
Use a branded full domain rather than a public or shared shortener.
Flowstates recommendation
Test Globe, Smart, DITO and any other current or contracted paths that your traffic will actually use.
Flowstates recommendation
Test registered-alphanumeric and domestic-long-code presentation, inbound replies, concatenation, Unicode and UCS-2, MMS URL conversion, link filtering and opt-out handling.
Flowstates recommendation
Keep template, notice, consent, sender, route-approval, opt-out and suppression evidence in one retrievable place.

Encoding and delivery

English Philippine copy normally fits GSM-7, but Filipino and other Philippine-language copy, smart punctuation and emoji can switch a template to Unicode and change what you pay for and what arrives.

GSM-7, single segment: 160 characters
GSM-7, concatenated: 153 characters per segment
Unicode / UCS-2, single segment: 70 characters
Unicode / UCS-2, concatenated: 67 characters per segment

Carrier or route policy
Twilio's registered-alphanumeric and domestic-long-code rows for the Philippines currently support UCS-2. That is provider route policy for those sender types, not a national guarantee.
Flowstates recommendation
Smart punctuation, emoji and non-basic or diacritic characters in Filipino and other Philippine-language copy can force UCS-2 and shorten every segment. Check the encoding your template actually produces.
Flowstates recommendation
Test the real encoded English, Filipino and other local-language copy, and its true segment count, on the exact sender and operator paths you will use.
Flowstates recommendation
Use the masked format +63 9XX XXX XXXX in documentation and test fixtures. Never publish or share a real subscriber number.
Flowstates recommendation
Remove the domestic trunk zero when normalising, and resolve the live operator rather than relying on the prefix, because portability is active.
Carrier or route policy
MMS conversion to an SMS containing a URL, URL filtering, media handling and sender presentation are decided by the provider and operator path.
Flowstates recommendation
Keep OTP to one segment where practical. A provider maximum is a technical ceiling, not a copy target.

A country guide is only useful when the route follows it.

Knowing the Philippine rules is the easy half. Keeping every send inside them — on registered senders, across route policy that changes independently of the NTC and the Data Privacy Act — is the operational half, and that is the part we run.

Per-country and per-category routing
OTP, transactional and marketing traffic take different Philippine paths, with the right sender type and policy applied to each category.
SenderID management
We manage sender identity across registered Philippine alphanumeric senders and validated domestic numeric senders, and keep the approved use case aligned with what you actually send.
Carrier-grade failover
When a Philippine path degrades, traffic moves to another valid approved sender rather than to whatever is available.
Per-route visibility
Delivery, latency and OTP conversion measured per sender and per operator path, so a filtering change shows up as data rather than as complaints.
24/7 vendor escalation
We chase the supplier and the operator. You get the update, not the ticket queue.
BYOV / BYOG
Keep your existing Philippine supplier, senders and contracts and let us operate the routing, or use ours.
Branded short links
Links on your own domain instead of a shared shortener, which Philippine route filters treat very differently.

Developer docs Branded short links

What we need to validate your Philippines route

Send us these and we will come back with the sender options that apply, the route behaviour we can confirm and the rules that govern your category.

Company or legal entity and website
Customer-facing brand name
Traffic category and use case
English, Filipino and other local-language sample templates for each distinct use case
Expected monthly volume and peak sending rate
Preferred sender type
Existing Philippines sender inventory and current provider at a high level
Opt-in and permission journey, screenshots or evidence and the exact wording
Privacy-notice and terms URLs
Marketing legal basis and the owner of the legal review
Internal objection, opt-out and suppression process and its owner
Link domains you intend to use
Whether you need replies or two-way messaging
MMS, Unicode and multi-segment requirements
How numbers are collected, normalised and validated
Target launch date

Validate my Philippines route Book a messaging review

Frequently asked questions about SMS in Philippines

Can I send SMS to mobile numbers in Philippines?

A quick operational read on the Philippines. Sender registration and blocking dates come from the provider and operator layer; opt-in, quiet-period and privacy duties come from the NTC circulars and the Data Privacy Act. Anything marked route-dependent is confirmed for the specific path your traffic uses. SMS to mobile: Supported on selected A2P routes. Number format: +63 9XX XXX XXXX — ten national digits after +63. Domestic trunk zero: A domestic form written 09XX XXX XXXX carries a trunk 0 that is not part of the international number. Number validation: Confirm the destination is Philippine, messaging-capable mobile and resolve the current operator before routing.

Which sender ID options work for SMS in Philippines?

Philippine A2P sender choice is largely determined by the route you buy. Registered alphanumeric sender — Best for: One-way OTP, transactional or service and permissioned marketing traffic where the selected provider and operator path accepts the category. Philippines domestic long code — Best for: Inbound-capable conversational and service flows, and responses to user-initiated messages where provider and operator policy permits outbound MT. Dedicated short code — Best for: Selected local high-scale programmes where carrier and provider support is confirmed. International numeric or dynamic sender — Best for: Not a supported production choice on Twilio's current Philippines route.

What are the consent and opt-out requirements for SMS in Philippines?

Three separate bodies of Philippine rule are involved, and they are constantly merged in supplier documentation: the NTC broadcast and push-message circulars, the scoped subscription content-service circular, and the Data Privacy Act. NTC Memorandum Circular 03-03-2005 and Memorandum Circular 04-07-2009 govern commercial and promotional advertisements, surveys and other broadcast or push messages sent to mobile subscribers. Covered broadcast and push messages may only be sent to subscribers who have given prior written consent or specifically opted in through an affirmative operative act. Silence is not consent: a subscriber who does not respond to an opt-in request is treated as not having opted in, and the covered broadcast must be stopped.

How many characters fit in an SMS to Philippines?

English Philippine copy normally fits GSM-7, but Filipino and other Philippine-language copy, smart punctuation and emoji can switch a template to Unicode and change what you pay for and what arrives. GSM-7, single segment: 160 characters. GSM-7, concatenated: 153 characters per segment. Unicode / UCS-2, single segment: 70 characters. Unicode / UCS-2, concatenated: 67 characters per segment.

Sources and change control

Regulator, statute and provider references behind this guide. NTC, Lawphil, the Supreme Court E-Library, the National Privacy Commission and the ITU control the legal, regulatory and numbering wording; Twilio material describes that provider's current route behaviour only.

Provider documentation
Twilio — Philippines SMS guidelines
One supplier's current Philippines route: preregistered alphanumeric senders supported and preserved, unregistered ones blocked from 7 April 2025, dynamic senders unsupported, domestic long codes supported, international long codes unsupported, short codes not offered, MMS converted to SMS with a URL, and no SMS to fixed lines.
Standards body
ITU — national numbering plans
Authoritative reference for the Philippine country code +63 and the national numbering plan structure behind the ten national digits.
Statute
Republic Act 11202 — Mobile Number Portability Act
The statute establishing mobile number portability in the Philippines, so a number range does not identify the current operator.
Official service entity
Telecommunications Connectivity Inc. — Philippine mobile number portability
The official Philippine mobile number portability service entity, and the reference point for the national service being live.
Regulator circular
NTC Memorandum Circular 03-03-2005
Official copy of the broadcast and push-message rules covering commercial and promotional advertisements and surveys, opt-in, opt-out and the 21:00 to 07:00 restriction.
Regulator circular
NTC Memorandum Circular 04-07-2009
Official copy of the amending circular on broadcast and push messaging, subscriber consent and sender identification duties.
Regulator circular
NTC Memorandum Circular 07-08-2018
Official copy of the scoped content and information subscription-service rules: double opt-in, confirmation disclosures, record retention, weekly opt-out instructions and the official keywords.
Regulator
NTC — frequently asked questions
Current regulator summary of the push-message framework, including prior consent or specific opt-in, non-response not being an opt-in, and the 21:00 to 07:00 restriction except for paid subscription services.
Statute
National Privacy Commission — Data Privacy Act of 2012
Republic Act 10173: transparency, legitimate purpose and proportionality, the definition of consent and the rights of data subjects.
Implementing rules
National Privacy Commission — Data Privacy Act IRR
Implementing rules and regulations expanding on lawful processing criteria, consent and the exercise of data-subject rights.
Regulator guidance
National Privacy Commission — right to object
Regulator explanation of the right to object, including objection to processing for direct marketing and the withdrawal of consent.
Regulator guidance
National Privacy Commission — right to be informed
Regulator explanation of the transparency duty owed to data subjects before their personal data is processed.
Statute
Republic Act 11934 — SIM Registration Act
The subscriber SIM registration regime, which is separate from A2P sender programmes and from marketing permission.
Implementing rules
Implementing rules of Republic Act 11934
Implementing rules for SIM registration, confirming the regime is about subscriber SIMs rather than about brand sender identities.

Change log

1 August 2026 — Initial publication; separated Philippine broadcast-message and data-privacy duties from sender, URL and route policy, recorded active mobile number portability and documented Twilio's registered-sender and two-way route options.

Last reviewed 1 August 2026

Disclaimer

This is operational guidance, not legal advice. Requirements vary by law, message purpose, sender, provider, carrier route, recipient context and customer setup. Flowstates confirms the live route during onboarding.

Philippines SMS guide