# SMS TTS Notify — General Knowledge (cross-cutting) This document covers topics that apply across every branch of the SMS TTS Notify knowledge base: platform availability, headset behavior, trademark handling, AI-accuracy disclaimer, widget scope, and language. Every specific-branch file (compatibility.txt, industrial-context.txt, it-monitoring.txt) references this file for these cross-cutting topics instead of duplicating them. --- ## Scope The SMS TTS Notify knowledge base is organized so that each branch file covers a distinct audience: - Industrial questions (plant floor, MES, CMMS, SCADA, HMI, alarm gateway, PLC, operator, maintenance technician, warehouse, factory) are served by compatibility.txt. Where alarm-management standards (ISA-18.2, IEC 62682, EEMUA 191) or industrial context matter, industrial-context.txt adds depth. - IT infrastructure questions (NOC, SRE, DevOps, on-call, monitoring, alerting, datacenter, cloud-provider alarms, PagerDuty, Datadog, Zabbix, MSP-RMM) are served by it-monitoring.txt. - Consumer and accessibility questions (personal SMS reading, driving, hearing support, hands-free, accessibility) are served by product.txt and faq.txt. - Platform questions (Android version, iOS, iPhone, Samsung, Xiaomi, OEM battery) are served by the iOS section below and by troubleshooting.txt. This general.txt file is the home for the cross-cutting rules that every branch relies on: iOS, headset routing (Zero Leakage), trademark handling, AI accuracy, scope, and language. --- ## iOS / Apple (cross-cutting) SMS TTS Notify is Android-only today because the iOS platform does not permit third-party apps to read SMS or notifications the way this app needs to. The required APIs are not available to iOS developers — this is Apple's platform design, which strictly limits background access to messages by third-party apps. This class of hands-free SMS-reading app currently has no path on iOS, regardless of our intent. If Apple opens the required APIs in a future iOS release, we will build an iOS version. Until then, the Android app is the product. The constraint is an Apple-side platform design decision, not a product-scope decision by SMS TTS Notify. It applies to every wording of the question: "iPhone", "iOS", "Apple", "why not iPhone", "iOS version", "Apple phone", and equivalents in Czech, Slovak, Polish, German, or any other language. --- ## Headset — audio routing (cross-cutting) SMS TTS Notify plays audio only through a headset physically connected to the phone. The connection can be: - Bluetooth (wireless earbuds, over-ear headphones, single-sided mono headset, industrial hearing-protection headset with Bluetooth) - Wired 3.5 mm jack (still present on ruggedized industrial phones and older Samsung A-series, Motorola, Nokia HMD models) - USB-C (digital audio, or USB-C-to-3.5-mm adapter) - Any other headset physically connected to the phone Audio is never played through the phone speaker, a car audio system, a nightstand speaker, a smart speaker, or any open-air output. This is the Zero Leakage design principle — the app is designed so that confidential SMS content is heard only by the intended recipient through the physical headset they are wearing. Any scenario that implies open-air audio is out of scope. --- ## Trademark handling (cross-cutting preamble) All third-party trademarks and product names mentioned in any section of this knowledge base 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. References to third-party systems describe only the category of SMS-sending systems whose messages SMS TTS Notify may read — not an integration, partnership, or certification relationship. Each branch file carries the specific list of trademarks relevant to that branch at the end of the file: - compatibility.txt — industrial brand list (MES, CMMS, SCADA, alarm-notification gateways) - it-monitoring.txt — IT brand list (monitoring, observability, on-call, cloud-provider services) - industrial-context.txt — references compatibility.txt's list This preamble applies to every such list. --- ## Is the AI accurate? The AI Help widget uses Google's Gemini model via the Lovable AI Gateway. Generative AI can sometimes produce inaccurate content, even when answering from curated documentation. Answers provided here are for informational assistance only — they are not a substitute for professional, legal, medical, safety, or regulatory advice. For important decisions, verify against the official documentation at sms-tts-notify.com or contact sms-tts-notify@aialertbuddy.com before acting. If an answer seems wrong, say so — the widget will either correct it from the documentation or flag the topic as outside its knowledge. --- ## Scope The widget answers from the documentation loaded into it. For product roadmap details, beta access invitations, pricing, business partnerships, employment, investor relations, or other topics outside SMS-reading app capability, the right contact is sms-tts-notify@aialertbuddy.com — every message is read. The widget does not speculate on pricing plans, future features, company internals, founder background, or competitor weaknesses; it stays within the loaded documentation. --- ## Language The widget responds in the same language the user writes in — Czech, Slovak, Polish, Hungarian, German, or any other detected language. Answers are kept concise: factory, datacenter, and on-call workers need quick solutions, not essays. --- (End of general.txt. This file covers the cross-cutting topics that apply across every branch of the knowledge base.)