I’ve been mapping how AI voice agents hold up against TCPA enforcement: consent flows, DNC scrubbing, opt-out handling, AI disclosure rules, vendor contracts. The pattern that keeps coming up in enforcement actions and lawsuits: most deployments have at least one gap that would hurt in an audit or a dispute. $500 to $1,500 per call adds up fast, and the professional litigators know it. I’m opening 3 pilot audits at $1,500 (one-time). What you get: - Full review of your consent architecture (how consent is collected, stored, and proven) - DNC list handling + call-time rules check - Opt-out mechanism test (can someone revoke, via your designated channel, or by any reasonable means if none is designated?) - AI disclosure requirements by state for your use case - Vendor contract review (how your contracts allocate TCPA risk) - A written findings report with prioritized fixes Written report delivered within 7 business days of your completed intake. Not a lawyer. This is operational and technical compliance work, and I’ll tell you straight when you need actual legal counsel. Why a pilot: I’m building this in public and I want 3 real deployments to pressure-test the process before pricing it properly. If you’re running outbound voice AI (Vapi, Retell, Bland, GHL…) and you’d rather find the gap yourself than have a litigator find it for you. Comment here or DM me. 3 spots. First come, first served.

Been mapping how AI voice agents hold up against TCPA enforcement. Three gaps keep coming up in enforcement actions, lawsuits, and deployment discussions: **1. Consent with no paper trail** Most teams HAVE consent — a checkbox, a form, a verbal “yes”. But they can’t PROVE it: no timestamp, no source, no copy of what the person actually agreed to. In a dispute, unprovable consent = no consent. Fix: log every consent event with timestamp, source, and the exact language agreed to. Keep consent records at least 4 years (5 to be safe). **2. Opt-outs that don’t actually work** “Reply STOP to opt out” is table stakes for SMS, but voice deployments often have no equivalent: no “press 9 to be removed”, no suppression-list update after the call, and the DNC list never gets scrubbed against the dialer. The FCC’s Sept 30, 2026 order updated the revocation rules: a sender can now designate one exclusive opt-out channel (e.g., an IVR keypress) if it’s clearly disclosed — otherwise “any reasonable means” still applies, including telling the AI “stop calling me” mid-call. If your agent can’t handle that and you haven’t designated an exclusive channel, you have a gap. **3. Nobody knows who owns compliance in the contract** Agency deploys the agent, client owns the numbers, vendor provides the infra. When a $500–$1,500-per-call problem shows up, everyone points at each other. Few service agreements assign TCPA responsibility explicitly. One paragraph fixes it — check whether yours has it. Not a lawyer — operational notes from research, not legal advice. Curious: which of these have you actually run into in production?

I run an SMS lead-response and booking service (n8n + Twilio) for local service businesses. Before I sign my first client I need a service agreement, and I'm stuck on the legal side. What I need the agreement to cover: 1. Authorization to register their business for A2P 10DLC texting on their behalf (their EIN, brand, campaign), since the registration has to be in the client's name 2. Who is responsible for texting consent (TCPA), opt-outs, and message content 3. How their lead data is stored and handled, and what happens when they cancel Attorneys I've talked to quoted $2,000-3,000 for this. That's a lot before I have a single client. Has anyone dealt with this? - Did you pay a lawyer, use a template, or write your own? - What did it cost, and what did you actually get? - Did anyone ever have a client dispute or a carrier rejection over it? - Is anyone willing to share the clauses that mattered (not your whole contract)? Thanks. Even a "here's what I'd skip" helps.