# SMS TTS Notify — IT Infrastructure, Monitoring, and On-Call Knowledge 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. --- ## Disambiguation — monitoring / alerting / NOC / on-call 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. --- ## Branch — cloud-provider alarms (AWS, Azure, GCP, OCI) Cloud-provider alarming stacks commonly deliver SMS to the operator's phone directly from their native notification service: - **AWS** — CloudWatch Alarm → SNS Topic → SMS subscription (phone number in E.164 format). - **Azure** — Azure Monitor Alert → Action Group → SMS action (country-restricted list; see Microsoft's supported-countries documentation). - **Oracle Cloud** — OCI Monitoring Alarm → Notifications (ONS) Topic → SMS subscription. - **Google Cloud** — Cloud Operations does not ship a direct SMS channel. The typical pattern is Pub/Sub → Cloud Function → SMS API (Twilio, MessageBird, Sinch), or routing through an on-call platform such as PagerDuty or Opsgenie. 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. --- ## Branch — on-prem / OSS network monitoring 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: - **Native GSM-modem support** — Zabbix has a built-in SMS media type that drives a USB GSM modem directly; Pandora FMS has an equivalent native module; ManageEngine OpManager ships an SMS profile; NetXMS supports both modem and gateway patterns. - **Hardware SMS gateway appliance** — widely used across Nagios, Icinga, Checkmk, LibreNMS, OpenNMS, PRTG, SolarWinds NPM, Graylog, and Splunk. The monitoring tool calls a REST API on a rack-mounted appliance with its own SIM card and GSM radio (examples: SMSEagle, Ozeki SMS Gateway, Teltonika, HW-group). Some appliances (for example SMSEagle NXS-series) support HA-Cluster and fully air-gapped operation with an internal SIM card. - **Cloud SMS API** — for example Clickatell preconfigured in PRTG and Observium, Twilio plugin in Graylog, or a custom webhook from the monitoring tool to a provider API (Twilio, MessageBird, Vonage, Sinch, Plivo, ClickSend). 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. --- ## Branch — modern SaaS observability 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. --- ## Branch — incident response / on-call platforms 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. --- ## SMS vs push — the technical rationale (for senior engineers and architects) When a user asks why SMS matters when modern push is faster under ideal conditions: 1. **Android Doze exemption.** SMS bypasses Android's Doze-mode background restrictions and the aggressive vendor-killer layers (Xiaomi MIUI, Huawei EMUI, OnePlus Oxygen, OPPO ColorOS, Vivo, Meizu, ASUS, ZTE) that deprioritize or kill third-party push. On a stock Android phone in deep Doze, an SMS wakes the device in seconds; a normal-priority FCM push is deferred to the next maintenance window. High-priority FCM attempts immediate delivery but abusing it hurts the sender's delivery quota. 2. **Coverage.** SMS rides cellular signaling (SS7 / Diameter). It reaches places where data fails — datacenters with Faraday-cage construction (metal envelope causes significant cellular signal attenuation, typically 30 to 50 dB; voice and SMS often survive via in-building DAS while LTE data does not), rural sites with only sub-GHz signaling, underground vaults, and international roaming where data roaming is disabled. 3. **Industry practice.** Every major on-call platform still sends SMS alongside push for SEV1 and SEV2 paging. A common PagerDuty escalation pattern is Push → Email → SMS → Phone, typically at 1-to-3-minute intervals (exact timing is account-configurable). Push is there because it is reliable under ideal conditions; SMS is there because push-only is not reliable enough for critical paging. **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). --- ## Mixed-channel apps — when SMS happens 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: - alerts escalate to on-call responders who don't have that platform's app installed, - the team configures SMS as a parallel channel for critical alerts (SEV1 / SEV2, standard on on-call platforms), - alerts bridge out via webhook, Zapier, email-to-SMS, or a custom integration. Concrete examples: - **PagerDuty, Opsgenie, Splunk On-Call, Grafana OnCall** — native SMS channel; SMS is part of the default escalation sequence. - **Datadog, Dynatrace, New Relic, AppDynamics** — typically route through PagerDuty or Opsgenie for paging; the downstream SMS is what lands on the phone. - **Slack, Microsoft Teams** — in-app chat alone is not SMS, but most on-call teams run SMS in parallel for critical paging; SMS TTS Notify reads the parallel SMS. - **MaintainX, UpKeep, Limble, Fiix, Brightly (CMMS in mixed IT/OT environments)** — primarily in-app mobile push, but escalation workflows to non-app recipients can go via webhook → Twilio, email-to-SMS, or a custom integration; SMS TTS Notify reads whatever arrives as an SMS. 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. --- ## What SMS TTS Notify does NOT claim (IT branch) - Not a monitoring tool, observability platform, on-call platform, SMS gateway, or SMS provider. - Not integrated with, certified for, or in partnership with any of the platforms named in this document. - Not a replacement for the on-call platform's own mobile app, voice channel, or push channel. - Does not send or compose SMS replies — it is a phone-side reader of incoming SMS only. - Does not improve SMS delivery latency, reliability, or SLA — it reads only after the SMS has arrived. - Does not hold IT-specific certifications such as SOC 2, ISO 27001, HIPAA, or PCI DSS. SMS TTS Notify is an on-device Android app that reads SMS aloud; it does not transport, store, or process customer data beyond the standard Android SMS content arriving on the phone. --- ## Trademark list (IT branch) 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.