> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Philippines NTC Sender Rules

> Philippines sender and marketing guidance for SMS: NTC sender registration, accepted sender identities, English and Filipino opt-out handling, tenant-owned consent and quiet hours, and the KYC profile steps before launch.

# Philippines NTC Sender Rules

The Philippines (`PH`) is a sender-registration market under the live
[country-rules row](/compliance/country-requirements). The National
Telecommunications Commission (NTC) and the mobile operators apply the
registration requirements for commercial SMS sender identities. Use the live
row for the current channel-specific answer: it identifies the accepted
sender types and whether registration is `required`.

This page documents tenant-owned controls. Devotel Orbit provides the
country-rules reference, sender-registration tracking, consent ledger,
suppression, and quiet-hours surfaces; your organization owns its legal
posture, filings, and message content. This page is documentation, not legal
advice.

<Note>
  The NTC and Philippine operators can filter unregistered or misleading
  sender identities and can take action on unwanted traffic. Confirm the
  current filing requirements with your carrier or counsel before launch.
  Do not treat an approved Orbit profile as regulator approval.
</Note>

***

## 1. Accepted sender types and registration level

Start with the live PH row before choosing a sender:

```bash theme={null}
curl "https://api.orbit.devotel.io/api/v1/compliance/country-rules?channel=sms&country=PH" \
  -H "Authorization: Bearer $ORBIT_API_KEY"
```

The current feed marks the Philippines registration level as `required` and
supports alphanumeric sender identities. A sender registration is a
precondition for an alphanumeric A2P SMS launch; do not infer that a sender
will deliver simply because it passes local format validation. If the live
row lists another sender type for your channel, follow that row and confirm
operator support before sending.

| PH posture | What you do |
| - | - |
| Alphanumeric sender | Submit a brand-aligned sender through [Sender-ID Registration](/compliance/sender-id-registration) and wait for the PH entry to reach `approved`. |
| Registration | Treat `required` as a launch prerequisite. Keep campaign traffic in rehearsal until the registration is approved. |
| Brand identity | Use a sender that recipients can associate with your organization. Keep the business and authorization documents that support it in your KYC profile. |
| Other sender types | Check `sender_types` in the live row and the operator's current rules before using a long code, short code, or another identity. |

A tenant-owned send gate may hold traffic while the registration is pending.
That is different from a carrier rejection. If a send is held, inspect the
PH row and the registration status before changing the message.

***

## 2. English and Filipino stop-keyword family

Publish the opt-out instruction in the language your audience understands.
For Philippine SMS, keep the standard English terms visible and support the
common Filipino equivalents in the tenant's opt-out rules:

| Action | Suggested keywords |
| - | - |
| Stop messages | `STOP`, `UNSUBSCRIBE`, `CANCEL`, `HINTO`, `TIGIL`, `ITIGIL` |
| Resume messages | `START`, `SUBSCRIBE`, `SIMULA` |

Configure the exact terms used in the campaign's consent text and footer in
[Opt-Out Keyword Alias Table](/compliance/opt-out-keyword-alias-table). Match
case and trailing punctuation according to the alias-table rules, and test a
sample reply before launch. Treat an opt-out as a tenant suppression at scope
`all` when the recipient is asking your organization to stop contacting them,
not merely as a delivery preference for one campaign.

If you use a different Filipino-language term, add it as a tenant-owned alias
and document it in the campaign record. Do not assume that a free-form
sentence is an exact keyword match; make the instruction and the matcher
agree.

***

## 3. Consent for marketing traffic

Capture express, purpose-specific consent before sending promotional SMS. The
Philippines' privacy regime is led by the Data Privacy Act of 2012 (Republic
Act No. 10173), enforced by the National Privacy Commission, alongside
telecommunications and operator rules. Keep a record of:

* the recipient identifier and the `sms` channel;
* the purpose and consent text version shown at capture;
* when and how the recipient gave consent; and
* a proof reference that your team can retrieve.

Record the evidence in the [Consent Management](/compliance/consent-management)
ledger. A registration-approved sender does not replace recipient consent,
and consent does not replace the sender-registration requirement.

```bash theme={null}
curl -X POST https://api.orbit.devotel.io/api/v1/compliance/consent \
  -H "Authorization: Bearer $ORBIT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "identifier": "+639171234567",
    "channels": ["sms"],
    "opt_in": true,
    "lawful_basis": "consent",
    "purpose": "PH marketing SMS — promotional updates",
    "consent_text_version": "ph-marketing-v1",
    "consent_proof_url": "https://example.com/consent/evt_ph_123"
  }'
```

Set the tenant's unknown-marketing policy deliberately. For a marketing
program without a consent record, `refuse` is the safer tenant-owned posture;
review the policy and its evidence in [Consent Default Policy](/compliance/consent-default-policy).

***

## 4. Quiet-hours convention

There is no single Orbit-enforced Philippines SMS quiet-hours window. Set a
recipient-local tenant window that your counsel and operator accept. A
conservative starting convention is **21:00–08:00 Philippine Time (UTC+8)**
for marketing traffic, with emergency, transactional, or recipient-requested
messages classified separately under your policy.

This is a tenant choice, not a platform-wide PH block. Configure and preview
it in [Quiet-Hours Configuration](/guides/quiet-hours-configuration) and
[Quiet-Hours Preview](/compliance/quiet-hours-preview). Keep the setting in
the campaign record so the consent and send-time decisions are auditable.

***

## 5. KYC profile submission for a PH sender

Assemble the tenant-owned compliance profile before filing the sender. Follow
the complete [KYC Profile Submission Runbook](/compliance/kyc-profile-submission-runbook):

1. Upload current business registration, address, identity, and authorization
   documents that support the sender and the entity submitting it. Keep the
   returned `doc_…` identifiers.
2. Create a profile for the Philippines with
   `use_case: "sms_sender_id_alphanumeric"` and the PH destination.
3. Attach the document IDs, including an authorization document when an
   agency submits for a brand, then submit the profile for review.
4. Wait for the profile to reach `approved`; a draft or pending profile is not
   carrier approval.
5. Submit the PH sender registration through [Sender-ID Registration](/compliance/sender-id-registration),
   reference the approved profile, and wait for the PH registration to report
   `approved`.
6. Recheck the live PH row, consent record, opt-out aliases, and quiet-hours
   preview before the first campaign send.

Renew documents before expiry. The runbook's clone-and-replace sequence keeps
an approved profile attached while its replacement is under review.

***

## 6. Worked configuration before the first PH send

<Steps>
  <Step title="Read the PH row">
    Call `GET /compliance/country-rules?channel=sms&country=PH` and record
    `sender_types`, `registration`, `content_restrictions`, and
    `stop_requirement`.
  </Step>

  <Step title="Choose and support the sender">
    Choose a brand-aligned alphanumeric sender supported by the live row and
    collect the documents that connect it to your organization.
  </Step>

  <Step title="Submit the KYC profile">
    Use the [KYC Profile Submission Runbook](/compliance/kyc-profile-submission-runbook)
    and wait for the profile to reach `approved`.
  </Step>

  <Step title="Register the sender">
    File the PH sender registration, reference the profile, and wait for the
    PH entry to reach `approved` before production traffic.
  </Step>

  <Step title="Capture consent and publish opt-out terms">
    Confirm the recipient has an `sms` consent record and that the message
    exposes the English or Filipino stop terms configured in your alias table.
  </Step>

  <Step title="Set and preview quiet hours">
    Configure the tenant's recipient-local window, starting with 21:00–08:00
    Philippine Time for marketing, and verify the preview result.
  </Step>

  <Step title="Send a controlled test">
    Verify the sender, consent, suppression, and registration status, then
    send a small tenant-owned test before scaling the campaign.
  </Step>
</Steps>

***

<Warning>
  This page is documentation, not legal advice. The NTC, the National Privacy
  Commission, and Philippine mobile operators may change their requirements.
  Have counsel and your carrier review the sender filing, consent language,
  stop keywords, and sending hours before you launch.
</Warning>

***

## Related references

* [Country Compliance Requirements](/compliance/country-requirements) — read
  the live PH row and its channel-specific fields.
* [Regional Posture Hub](/compliance/country-rules-directory) — the matrix of
  country pages and the check-the-row-first workflow.
* [Sender-ID Registration](/compliance/sender-id-registration) — submit and
  track the PH sender entry.
* [KYC Profile Submission Runbook](/compliance/kyc-profile-submission-runbook)
  — upload, assemble, submit, approve, and renew the profile.
* [Consent Management](/compliance/consent-management) — capture and retrieve
  marketing consent evidence.
* [Opt-Out Keyword Alias Table](/compliance/opt-out-keyword-alias-table) —
  configure English and Filipino tenant aliases.
* [Quiet-Hours Configuration](/guides/quiet-hours-configuration) — set the
  tenant-owned recipient-local window.
* [Send Gates](/compliance/send-gates) — understand the send-time surfaces.

The legal posture remains tenant-owned; confirm current NTC and operator
requirements before each materially different campaign.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.