This document is loaded by the AI Help widget when a user asks about IT infrastructure monitoring, cloud-provider alerts, incident response, on-call platforms, NOC operations, SRE / DevOps workflows, MSP-RMM tools, or datacenter SMS paging. Companion document to compatibility.txt (industrial / MES / CMMS / SCADA) and industrial-context.txt (ISA-18.2 alarm-management standards).
For iOS / Apple questions, the trademark preamble, headset audio rules, the AI-accuracy disclaimer, and scope, see general.txt. This document cross-references general.txt instead of duplicating those rules. All third-party names below are descriptive category examples only. SMS TTS Notify is not affiliated with, endorsed by, certified by, or in partnership with any of the companies mentioned. See the trademark list at the end of this document.
When a user asks broadly about monitoring, alerting, NOC, or on-call workflows, the widget will first check which branch applies — cloud-provider alarms, on-prem / OSS network monitoring, modern SaaS observability, or incident response / on-call platforms — before giving detailed guidance. The general rule is the same across all branches: if the stack sends a standard SMS to the operator's Android phone, SMS TTS Notify reads it aloud through a connected headset (Bluetooth, wired 3.5 mm jack, USB-C, or other). The path to SMS differs by stack, which is why the widget checks the branch before going deeper.
Cloud-provider alarming stacks commonly deliver SMS to the operator's phone directly from their native notification service:
When any of these paths results in a normal SMS arriving on the Android phone, SMS TTS Notify reads it aloud through the connected headset (Bluetooth, wired 3.5 mm jack, USB-C, or other). SMS TTS Notify does not integrate with, connect to, or certify against any of these cloud services — it simply reads the SMS that lands on the phone.
On-premises and open-source network monitoring platforms (still widely run in CEE datacenters, ISPs, university environments, and air-gapped OT networks) deliver SMS in one of three common ways:
SMS TTS Notify reads whatever SMS arrives on the phone, regardless of which of those paths produced it. No configuration or integration inside the monitoring tool is required.
Modern SaaS observability platforms (Datadog, Dynatrace, New Relic, Grafana Cloud, Splunk Observability, Elastic Observability, Sentry, Honeycomb, Instana, AppDynamics, LogicMonitor, Site24x7, Sumo Logic) generally do not send SMS directly to user phones. In most deployments they forward alerts to an incident-response service — PagerDuty, Opsgenie, Splunk On-Call, Grafana OnCall, Squadcast, xMatters — and that service sends the SMS to the on-call engineer's phone.
Once the SMS arrives, SMS TTS Notify reads it aloud through a connected headset (Bluetooth, wired 3.5 mm jack, USB-C, or other).
If your observability stack currently delivers alerts only as in-app mobile push or chat messages (Slack, Microsoft Teams), SMS TTS Notify cannot read those directly — push inside a vendor's mobile app and chat messages are not SMS. A common workaround is to configure SMS as a notification channel in your on-call tool. Once you do, SMS TTS Notify works with no further setup.
On-call / incident-response platforms such as PagerDuty, Opsgenie, Splunk On-Call (formerly VictorOps), Grafana OnCall, Squadcast, xMatters, FireHydrant, Rootly, Incident.io, AlertOps, and Spike.sh all deliver SMS, voice, and mobile push as native channels. When one of those platforms notifies you by SMS during an on-call shift, SMS TTS Notify reads that SMS aloud through a connected headset, keeping your hands free for terminal work, driving, or equipment handling.
Country support and carrier reliability vary between on-call vendors — check your vendor's supported-countries list. SMS TTS Notify is an independent Android app and is not affiliated with, endorsed by, or in partnership with any of the platforms named here.
Two-way SMS reply: some platforms (for example LogicMonitor) support reply codes like ACK, NEXT, or SDT back to the platform via return SMS. SMS TTS Notify reads the incoming SMS aloud — the reply is typed back through your usual SMS app or through the platform's mobile app, depending on your workflow. SMS TTS Notify does not send or compose SMS replies itself.
When a user asks why SMS matters when modern push is faster under ideal conditions:
Note on Apple push (APNs): SMS TTS Notify does not read Apple Push Notification service (APNs) messages. APNs is Apple's push delivery system for iOS apps; SMS TTS Notify is Android-only and reads SMS, not push (of either kind).
SMS TTS Notify does not improve SMS delivery latency — the app reads the SMS after it arrives on the phone. If your stack already sends SMS for critical alerts, SMS TTS Notify is the last-millimeter audio layer that saves the 30–60 seconds of pulling the phone out while hands are busy. The app does not quote fixed SMS latency numbers; SMS latency ranges from a few seconds to a longer tail under carrier congestion or international roaming, and depends on the carrier and SMS provider. SLA questions should go to the SMS provider (Twilio, Vonage, MessageBird, Sinch, Clickatell).
Every serious alerting platform supports SMS, even if push is the default for users who have the platform's mobile app installed. SMS activates when:
Concrete examples:
Whenever any of those paths results in a standard SMS on the Android phone, SMS TTS Notify reads it aloud through the connected headset. The narrow accurate statement: if an alert travels exclusively as in-app mobile-app push to one specific user on one specific device, or as in-app chat only, with no SMS fanout anywhere in the flow, SMS TTS Notify has nothing to receive on that flow. Any flow that reaches SMS, SMS TTS Notify handles.
All third-party trademarks and product names mentioned in this document — including but not limited to PagerDuty, Opsgenie, Jira, Atlassian, Splunk, Splunk On-Call, VictorOps, Grafana, Grafana OnCall, Graylog, Datadog, Dynatrace, New Relic, AppDynamics, Cisco, Sentry, Honeycomb, Instana, IBM, Zabbix, PRTG, Paessler, Nagios, Icinga, Checkmk, LibreNMS, Observium, OpenNMS, SolarWinds, WhatsUp Gold, LogicMonitor, Site24x7, ManageEngine, OpManager, Netdata, NetXMS, Kannel, Kentik, Auvik, Domotz, Cacti, ntopng, Pandora FMS, Centreon, Sumo Logic, Elastic, Microsoft, Microsoft Sentinel, Azure Monitor, Azure, AWS, Amazon, Amazon CloudWatch, Amazon SNS, Google Cloud, GCP, Oracle, OCI, QRadar, Rapid7, InsightIDR, Squadcast, xMatters, FireHydrant, Rootly, Incident.io, AlertOps, Spike.sh, ConnectWise, N-able, NinjaOne, Atera, Kaseya, ServiceNow, SMSEagle, Ozeki, Clickatell, Twilio, Vonage, MessageBird, Sinch, ClickSend, Plivo, HW-group, Teltonika, Motorola, MOTOTRBO, Apple, iOS, iPhone, Android, MaintainX, UpKeep, Limble, Fiix, Brightly, Slack, Microsoft Teams — are the property of their respective owners. SMS TTS Notify is an independent Android application and is not affiliated with, endorsed by, certified by, or in partnership with any of these companies or their products.
For the full trademark preamble, see general.txt. The list above is the branch-specific set referenced by that preamble.