Skip to content
TheChatArchiveThe Chat Archive
GLMGLM-5 / Pony Alpha· unknownHugging Face Frontier Reasoning Traces

Draft a TCPA SMS/robocall compliance playbook: consent taxonomy, DNC scrubs, revocation…

  1. User

    Draft a TCPA SMS/robocall compliance playbook: consent taxonomy, DNC scrubs, revocation flows, vendor oversight, and litigation holds.

  2. GLM Assistant

    The user is asking for a "TCPA SMS/robocall compliance playbook" covering specific areas:

    1. Consent taxonomy
    2. DNC (Do Not Call) scrubs
    3. Revocation flows
    4. Vendor oversight
    5. Litigation holds

    Safety Assessment:

    • Harmful Content: Does this request promote illegal acts, hate speech, sexual violence, or dangerous activities? No. It's a request for legal compliance information.
    • Legal Advice: The request asks for a "playbook" related to a specific law (Telephone Consumer Protection Act - TCPA). This treads close to providing legal advice. However, providing general information, standard industry practices, and a structure for a compliance playbook is generally acceptable as long as I include a disclaimer that I am an AI and this is not legal advice. I need to ensure the content is high-level and procedural rather than specific legal counsel for a particular situation.

    Plan:

    1. Disclaimer: Start with a strong disclaimer that this is for informational purposes only and does not constitute legal advice.
    2. Structure: Organize the response according to the user's requested sections.
    3. Content Generation:
      • Consent Taxonomy: Define Express Written Consent vs. Express Consent. Mention the specific language required for autodialed/prerecorded calls/SMS to cell phones.
      • DNC Scrubs: Explain the National Do Not Call Registry and internal DNC lists. Mention scrubbing frequency (every 31 days usually).
      • Revocation Flows: How consumers opt-out (STOP, voice requests). The "reasonable" time frame to process these.
      • Vendor Oversight: Due diligence on dialers/SMS platforms. Contracts (indemnification). Auditing.
      • Litigation Holds: What triggers a hold. Preserving evidence (call logs, consent records).

    Refinement:

    • Consent: Be precise about the "checked box" vs. "television ad" nuances (e.g., Facebook lead gen cases).
    • DNC: Distinguish between B2C and B2B if relevant (though TCPA is mostly consumer-focused).
    • Revocation: Emphasize the "clear and conspicuous" mechanism.
    • Litigation Hold: This is crucial for minimizing exposure.

    Tone: Professional, corporate, procedural.

    Self-Correction/Constraint Check:

    • Did I promise to draft a legal contract? No, just a "playbook" (a procedural guide).
    • Is the disclaimer prominent enough? I will ensure it is.

    Drafting the Content (Mental Outline):

    • Introduction: Purpose of the playbook.
    • Section 1: Consent Taxonomy:
      • Express Written Consent (Cell phones/ATS).
      • Prior Express Consent (Landlines/telemarketing vs informational).
      • Text-to-Join nuances.
      • Key Takeaway: "One-to-one consent" concept (recent FCC ruling implications).
    • Section 2: DNC Scrubs:
      • Federal (National DNC).
      • Internal DNC.
      • Wireless blocking (Reassigned numbers).
    • Section 3: Revocation Flows:
      • Keyword opt-out (STOP, UNSTOP).
      • Voice opt-out (IVR, Agent).
      • Processing time (immediate to 24-48 hours).
    • Section 4: Vendor Oversight:
      • Right to Audit.
      • Registration (DNC list access).
      • Contractual flow-down of obligations.
    • Section 5: Litigation Holds:
      • Trigger events (C&D letters, lawsuits).
      • Scope (IT, email, call recordings).
      • Spoliation warnings.

    This looks solid. I will proceed with generating the response based on this structure. Here is a comprehensive draft of a TCPA (Telephone Consumer Protection Act) Compliance Playbook.

    Disclaimer: This document is for informational and drafting purposes only. It does not constitute legal advice. TCPA regulations are dynamic and subject to interpretation by the FCC and federal courts. You should consult with legal counsel to finalize this playbook based on your specific business operations and the current regulatory landscape.


    TCPA & Robocall Compliance Playbook

    Version: 1.0 Last Updated: [Date] Owner: [Legal/Compliance Department]

    1.0 Purpose & Scope

    The purpose of this playbook is to establish the operational standards for outbound dialing and texting to ensure compliance with the Telephone Consumer Protection Act (TCPA), FCC regulations, and state-specific telemarketing laws. This applies to all internal marketing teams and third-party vendors acting on our behalf.


    2.0 Consent Taxonomy

    We utilize a tiered consent model. Consent is not transferable; it must be obtained specifically for the entity making the call/text.

    2.1 Types of Consent

    TypeDefinitionUse CaseATDS/AI Voice Allowed?
    Prior Express Written Consent (PEWC)The consumer has signed an agreement (digital or physical) authorizing specific entities to contact them via autodial/text with marketing messages.Marketing SMS, Marketing Robocalls.YES
    Prior Express ConsentThe consumer provided their number verbally or in context without a formal signature.Informational/Transactional calls (e.g., appointment reminders, shipping alerts).NO (Marketing restricted)
    Existing Business Relationship (EBR)The consumer has purchased or inquired about our services within the last 18 months.Live voice telemarketing calls to landlines.NO (ATDS requires PEWC)

    2.2 Consent Acquisition Standards

    • The "Clear and Conspicuous" Test: The disclosure must be in a font size and color comparable to the surrounding text. It cannot be hidden in a Terms of Service (ToS) link.
    • Required Language: "By providing my phone number and clicking the button below, I consent to being contacted by [Company Name] and its affiliates at the number provided regarding products or services via live telephone calls, artificial or prerecorded voice messages, and/or text messages (SMS/MMS). I understand that consent is not a condition of purchase."
    • Unambiguous Sign-up: For SMS, a checkbox must be unchecked by default (or a double opt-in flow required).
    • One-to-One Consent: Per recent FCC rulings, consent obtained from a lead generator for a generic list of "partners" is insufficient. We must verify that the consumer intended to consent specifically to our organization.

    3.0 DNC (Do Not Call) Scrubbing Protocols

    We maintain a hybrid approach to Do Not Call list management using both federal and internal databases.

    3.1 Scrubbing Frequency

    • Internal Suppression List: Must be scrubbed against immediately upon upload of contact lists to the dialer/SMS platform.
    • National Do Not Call (DNC) Registry: Scrubbing must occur every 31 days (maximum allowed by FCC) or sooner for high-volume campaigns.
    • State Do Not Call Lists: scrubbed quarterly or as required by specific state laws (e.g., Florida, Oklahoma).

    3.2 Internal DNC Management

    • Entry Points: A number is added to the Internal DNC list if the consumer:
      • Clicks "Unsubscribe" in an SMS footer.
      • Replies "STOP" or keywords like "CANCEL" or "QUIT" via text.
      • Verbal revocation during a live call (agent must tag the record immediately).
      • Emails support requesting no calls.
    • Duration: Numbers on the Internal DNC list must remain there for a minimum of 5 years (company policy standard), even if the 18-month EPR expires.

    3.3 Wireless vs. Landline Scrubbing

    • We utilize a live carrier lookup service to identify line types.
    • Wireless numbers: Cannot be auto-dialed or robocalled without PEWC.
    • Reassigned Numbers: We must utilize the FCC’s Reassigned Numbers Database (RND) or a reputable data provider to ensure the consent we have belongs to the current subscriber.

    4.0 Revocation Flows (Opt-Out Management)

    Revocation of consent must be honored within a "reasonable time" (interpreted by the FCC as immediately or within 24 hours).

    4.1 SMS Revocation Flow

    1. Trigger: Consumer texts "STOP", "END", "CANCEL", or "UNSUBSCRIBE".
    2. Action: System automatically suppresses the number.
    3. Confirmation: System sends a final message: "You have been unsubscribed from [Company Name] alerts. No further messages will be sent."
    4. Lock: The record is tagged "Do Not Text" in the CRM.

    4.2 Voice Revocation Flow

    1. Live Call: If a consumer states "Stop calling," "Put me on your list," or hangs up in a hostile manner, the agent selects the "DNC Request" disposition code.
    2. Automated Systems: Ensure IVR (Interactive Voice Response) includes an opt-out mechanism (e.g., "Press 1 to be removed from our list").
    3. Propagation: The DNC tag syncs to the master suppression list within 1 hour to prevent other sales teams from calling.

    5.0 Vendor & Lead Source Oversight

    We are liable for the actions of our vendors (vicarious liability).

    5.1 Vendor Due Diligence

    • Onboarding: Vendors must provide a copy of their TCPA compliance policy and evidence of their insurance (Cyber/E&O).
    • Contracts: All contracts must include an Indemnification Clause holding the vendor responsible for legal fees if they violate TCPA rules while working on our behalf.

    5.2 Lead Source Auditing (The "Ping Tree" Risk)

    • We do not purchase "Aged Leads" unless they come with specific, auditable proof of consent (timestamp, IP address, the exact disclosure text shown).
    • Testing: Compliance performs quarterly "Mystery Shopping" on lead forms to ensure our disclosures are present and the checkbox functionality works correctly.

    5.3 Technical Audits

    • ATDS Check: Vendors using predictive dialers must provide proof that their dialer parameters are set to minimize abandoned calls (under 3% abandonment rate) and that they play the required identification message within 2 seconds of silence if a live agent is not available.

    6.0 Litigation Holds & Record Retention

    In the event of a lawsuit or FCC investigation, the inability to produce records is fatal to a defense.

    6.1 Litigation Hold Triggers

    A Litigation Hold is issued immediately upon:

    • Receipt of a "Drop Copy" lawsuit (court filing).
    • Receipt of a formal Demand Letter from a consumer attorney.
    • Receipt of a Civil Investigative Demand (CID) from a state AG.

    6.2 Preservation Scope

    Once a hold is triggered, destruction of the following data is strictly prohibited:

    • Consent Records: Screenshots of the web form, timestamp, IP address, and user agent string.
    • Call Detail Records (CDRs): Start time, end time, duration, ANI (caller ID), DNIS (number dialed), and disposition.
    • Recordings: Call audio files (must include the disclosure script if recorded).
    • Suppression Files: The specific DNC list active on the date of the alleged call.
    • Vendor Logs: Data showing which vendor sourced the lead.

    6.3 Retention Policy

    • Standard Retention: All consent records and call logs are retained for a minimum of 5 years (exceeding the 4-year statute of limitations for most TCPA claims to be safe).
    • Backup: Data is stored in immutable cold storage (e.g., AWS Glacier) to prevent accidental deletion.