SMS

The SMS subscribers page is your org-wide list of text-message notification recipients. Each row ties a phone number to a status dashboard and a set of components; when a published event with Notifications enabled affects overlapping components, matching verified subscribers receive a text alert.

Admin-added and bulk-imported rows are created pre-verified. Public visitors can also subscribe from a status dashboard when the SMS channel is enabled. For the public /subscribe flow, see SMS subscriptions. For message format, delivery logs, STOP/START, and suppression, see SMS notifications.

---

Transactional SMS

When visitors subscribe or request a manage link on a status dashboard, StatusDashboard sends a transactional text. These messages do not count toward your monthly event notification SMS quota.

Business Name appears in the message as your organization's display name — the same value shown as Business name on the Account page.

Admin-added and bulk-imported subscribers are created pre-verified; no verification text is sent for those entries.

Replying STOP blocks future texts but does not remove a row from this subscriber list; use Delete subscriber when you want the subscription gone entirely. See SMS notifications — STOP and START.

Subscriber list

The list shows one entry per dashboard + phone subscription record:

Use Prev / Next pagination to browse large lists (10 entries per page). Enter a phone number in the search box to look up a specific subscriber.

There is no admin-managed (locked) option for SMS — that concept applies only to email (for example distribution lists). See Email subscribers.

Quota bar

The quota bar shows unique phone numbers in your organization vs your plan limit — e.g. 3 of 100 unique phone numbers. Pending and verified subscriptions both count toward quota. This may be lower than the number of list entries when the same number appears on multiple dashboards.

Each new unique number consumes one slot when its first subscription record is created (public signup, admin add, or import). The same number on additional dashboards does not use another slot.

If a visitor never completes verification, the pending subscription record expires after 24 hours (matching the verification link validity). The quota slot is released automatically once that pending record is removed (the same behavior as email subscribers). It may take up to an additional 48 hours to process the removal — during that window the slot may still appear consumed in the quota bar even though the subscriber no longer exists.

Add subscriber

Admins can add a single pre-verified subscriber via Add Subscriber:

1. Select country and enter the phone number (the admin console converts this to E.164 before saving)
2. Select the target dashboard (any dashboard in your organization)
3. Select one or more components assigned to that dashboard

The subscriber is created pre-verified (no verification text).

Edit subscriber

Click the pencil icon on a verified entry to update component selections. Phone and dashboard are fixed for the subscription record.

Clear all components to stop notifications without deleting the subscription. Status shows No components; the entry remains verified. That is different from replying STOP, which blocks delivery org-wide — see SMS suppression.

Verify subscriber

Click the checkmark icon on a Pending entry to admin-verify that subscription as-is (phone, dashboard, and components from the signup). Confirm in the dialog — no verification text is sent.

The phone number already counts toward quota while pending; verifying does not consume an additional slot.

Delete subscriber

Click the delete icon on any entry and confirm in the dialog. The subscription is removed from that dashboard. The quota slot is released only when no other subscription (pending or verified) for that number remains in your organization.

Bulk import

Admins can import pre-verified subscribers via Import:

1. Prepare CSV or pasted rows: phone,dashboard,components
2. phone = E.164 number (e.g. +14155552671) — national numbers without a country calling code are not accepted
3. dashboard = status dashboard display name (e.g. Production Status) — must match an existing dashboard name in your org (case-insensitive)
4. components = pipe-separated component names (e.g. API|Website)
5. Preview classification, then start the import (large files upload in the background; up to 50,000 rows per import; CSV files up to 15 MB)

Imported subscribers are pre-verified (no verification text). Importing an existing org phone onto another dashboard does not consume an additional slot.