SMS paging

SMS is a controlled preview, not an automatically available free or self-service transport. A platform administrator must activate a funded provider path, and the recipient must opt in and verify the number before live paging.

Before setup

• Confirm controlled-preview access and applicable pricing with HowlOps.
• Add the recipient in international E.164 form and complete the verification/consent flow under Settings → Notifications.
• Keep SMS as one step in an escalation policy, not the only recovery path.

After activation, select the verified destination in the notification chain or create the permitted channel, then use the guarded test flow. HowlOps sends short incident paging messages; replies do not acknowledge incidents. Carrier acceptance is not proof of handset delivery.

Safety, privacy, and troubleshooting

Telephony maintenance fences, rate/cost limits, verified-recipient checks, and consent evidence can block a send. Never paste provider credentials into a workspace channel; they are platform-managed. Remove numbers that change owner and retain consent evidence only as required. Inspect the delivery log and contact support before repeated paid tests. See Voice and SMS paging.