The following is a description of current ISN policy vs. Spectora. It can and should be updated and changed to stay in-line with how people communicate: The primary difference between how ISN and Spectora handle automated text messages boils down to compliance philosophy, liability shifting, and software defaults.While both platforms are subject to the exact same FCC rules and Telephone Consumer Protection Act (TCPA) regulations, they approach the user experience and the legal "burden of proof" from completely opposite angles. Default Opt-In vs. Manual Safeguards ISN’s Approach (The Conservative/Strict Safeguard): ISN chooses to strictly enforce a "blank slate" default. Because the FCC states that a sender cannot pre-check consent boxes for a user (meaning a default setting to "always text everyone" is a compliance violation unless prior consent is documented), ISN disables the text option by default. They force your team to manually check the box for each client, ensuring you have either a verbal or written confirmation. They do this to legally protect both you and themselves from heavy TCPA fines (which can range from $500 to $1,500 per unauthorized text message). Spectora’s Approach (The Shifted Liability Model): Spectora allows automated "Smart Reminders" (text/SMS) to be set up globally and triggered automatically based on inspection events. Instead of forcing a manual check-box per inspection, Spectora builds the legal requirement into their Terms of Service and Client Portals. When you use Spectora, you sign a subscription agreement stating that you are responsible for ensuring you have consent to message your clients. The Nature of "Transactional" vs. "Marketing" Messages Under FCC guidelines, transactional/informational messages (like an appointment confirmation or a reminder that an inspection report is ready) require a lower threshold of consent than marketing texts. Implied or verbal consent is legally sufficient for informational texts if a client voluntarily gave you their phone number in the context of booking a business service. Spectora builds its workflow around the presumption that because a client actively booked an inspection with you (or an agent provided the info to facilitate the transaction), the communication is strictly transactional, and implied consent exists. Therefore, they allow the texts to deploy automatically. ISN takes a harder line, recognizing that if a client or an agent complains or claims they never gave permission, a business has no automated "paper trail" of that verbal consent. They force the manual toggle so that the inspector takes explicit responsibility for that specific contact. Integrated Consent in Spectora’s Portals When clients and agents interact with Spectora, they are heavily guided through a unified digital pipeline (e.g., signing agreements, paying for inspections, and viewing reports online). Spectora often embeds the necessary text-messaging disclosures and opt-out mechanisms directly into these user-facing portals. By agreeing to the terms to view the inspection report or sign the contract, the client is digitally confirming their contact info, satisfying the FCC's requirements seamlessly behind the scenes. Spectora didn’t have qualms because they designed a smoother automated workflow that assumes consent based on the transaction, while legally passing the liability to you in their terms of use. ISN, on the other hand, chose an older, strictly locked-down interface design that forces you to manually acknowledge consent for every single job to guarantee compliance.
