Page a person by text message
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A text reaches a number that has not been pre-verified, from a sender the docs say is registered for that country, with STOP handled and a delivery receipt readable.
How agents ask for it: text me if production goes down
, send an SMS alert to the on-call phone
Does the job, with a limit 8
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Amazon SNS BB Amazon Web Services, Inc. | New accounts sit in an SMS sandbox reaching only up to 10 verified numbers; reaching others needs an origination identity and, in some countries, company registration. acc-31 could not reach US phones without a toll-free number registered by a person. source |
| Courier B trycourier.com, Inc. | SMS goes through a provider the owner connects (Twilio, SNS and others); the SMS guide points to that provider for registration and opt-out. source |
| Knock A Knock Labs, Inc. | SMS goes through a provider the owner connects (Twilio, MessageBird, Sinch and others); sender registration, STOP handling and carrier receipts sit with that provider, not Knock. source |
| MagicBell C MagicBell, Inc. | SMS goes through a Twilio integration the owner connects; registration and STOP handling sit with Twilio. source |
| Novu B Noti-Fire Apps Ltd. | SMS goes through a provider the owner connects (dozens listed) or a demo provider with sending limits; sender registration and STOP handling sit with that provider. source |
| OneSignal BB OneSignal, Inc. | Native SMS with STOP and HELP keyword handling, but every sender needs approval per country and use case: toll-free takes days, US 10DLC 1 to 3 weeks; Twilio trial reaches only pre-registered numbers. source |
| Pingram C Pingram | Built-in carriers: free accounts send from shared +1 650 numbers, paid ones from a dedicated number, with US 10DLC brand and campaign registration by API. Approval time and STOP handling are not stated in the pages read. source |
| SuprSend BB SuprStack Inc | SMS goes through a vendor the owner connects (Twilio, MessageBird, Gupshup), with India DLT guidance; registration and STOP sit with that vendor. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Expo Push Notifications B 650 Industries, Inc. | No SMS channel. source |
| Firebase Cloud Messaging BB Google LLC | No SMS channel. source |
| ntfy C ntfy LLC | No SMS. Phone calls exist for authenticated users, only to numbers verified in the web app first. source |
| Pushover C Pushover, LLC | No SMS channel. source |
What stops agents finishing
- SMS sandbox reaches only verified numbers
- toll-free or 10DLC registration done by a person over days
Around it
Before: observability.alert-fires. After: notifications.ask-approval.
Where this comes from
Weight 7 of 100 in Notifications: 3 accounts (acc-30 to acc-32), all blocked by sandbox or sender registration rather than by the API
The same as data: /api/v1/use-cases/notifications.sms-page.json, or the MCP tool get_use_case with id notifications.sms-page. Other jobs in this category: /api/v1/niches?category=notifications.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.