SAAS & SOFTWARE SMS COMPLIANCE

// Course Guide

Who this course is for

• Product managers building SMS features
• Compliance and trust & safety leads at platforms
• Growth and lifecycle marketers at SaaS companies
• Engineering leads responsible for messaging APIs

Why texting compliance is different for SaaS companies and software platforms

SaaS companies face SMS compliance in two roles: as senders texting their own users (onboarding, 2FA, product marketing) and as platforms whose customers send through their APIs. The second role brings platform liability questions, ISV registration responsibilities in TCR, and the need to police customer content and consent without reading every message. Mixing 2FA with marketing on one campaign and failing to register customers individually are common causes of suspension.

What each module covers

1. TCPA Foundations for SaaS. The TCPA as it applies to SaaS companies and software platforms: consent tiers, autodialer rules after Facebook v. Duguid, Do Not Call obligations, statutory damages and recent case law.
2. TCR Registration. 10DLC registration for SaaS companies and software platforms: brand and campaign structure, use case selection, vetting, and keeping registrations accurate as the business changes.
3. User Consent Framework. How to capture, scope and document consent for SaaS companies and software platforms: express versus express written consent, disclosure language, recordkeeping and consent that survives a challenge.
4. Message Classification. For SaaS companies and software platforms: classifying messages as informational, transactional, conversational or marketing, and why the classification decides which consent and which campaign apply.
5. Contamination Prevention. For SaaS companies and software platforms: preventing contamination: keeping marketing content out of informational and transactional messages so consent and registrations stay valid.
6. Opt-Out Management. For SaaS companies and software platforms: processing STOP and other opt-outs across every system, honoring revocation by any reasonable means, and keeping internal and national DNC lists synchronized.
7. Marketing Compliance. For SaaS companies and software platforms: running compliant promotional programs: express written consent, CTA disclosures, frequency, quiet hours and state laws stricter than the federal rules.
8. Platform Liability Management. For SaaS companies and software platforms: responding to complaints, demand letters, class actions and regulator inquiries: preserving evidence, common defenses and settlement considerations.
9. Data Risk Management. For SaaS companies and software platforms: assessing purchased, rented and sourced data: why lead-generation consent often fails, vendor diligence, list hygiene and the Reassigned Numbers Database.
10. Enterprise Customer Oversight. Applied guidance on enterprise Customer Oversight for SaaS companies and software platforms, with templates, checklists and case studies drawn from real programs.
11. API Audit & Oversight. For SaaS companies and software platforms: building the evidence trail: consent logs, message archives, monitoring dashboards and the records regulators, carriers and plaintiffs request.
12. Litigation Defense Strategies. Applied guidance on litigation Defense Strategies for SaaS companies and software platforms, with templates, checklists and case studies drawn from real programs.
13. Final Certification Exam. A proctored final assessment covering every module, with scenario questions drawn from real SaaS companies and software platforms situations. Passing earns the course certificate.

The problem this course prevents

A scheduling platform registers all of its customers under one TCR brand and campaign. One customer sends promotional blasts to purchased lists and the entire campaign is suspended, cutting off reminders for every other customer. The course covers ISV registration models, customer oversight and API-level controls.

Course FAQ

Do we register our customers or do they register themselves?

Platforms acting as ISVs usually register each customer as its own brand. The platform liability and API oversight modules cover the models and responsibilities.

Can 2FA and marketing share a campaign?

No. 2FA campaigns must not contain marketing. The message classification module covers separating them.

Is the course self-paced?

Yes. SaaS & Software SMS Compliance runs about 20 hours across 13 modules, including the final exam, and you can work through it at your own pace with lifetime access to updates.

Is this course legal advice?

No. It teaches the rules, carrier requirements and operational controls that apply to SaaS companies and software platforms, but it is not a substitute for advice from qualified counsel on your specific program.