The FCC confirmed TCPA applies directly to AI-generated voices. That means every outbound call your agency places using an AI voice requires prior express written consent. Miss it, and you're liable for $500 to $1,500 per violation with no aggregate cap. Read the full FCC statement.
This isn't a new rule. The Telephone Consumer Protection Act (TCPA) has been law since 1991. But for the past five years, there was a grey area around AI voices: Are they "artificial" under the law? Do they trigger the same consent requirements as predictive dialers and autodialed calls?
Today, the FCC answered: Yes, and yes.
The practical impact is immediate. Every AI voice agency operating right now is either compliant or exposed. There is no middle ground.
Why This Matters for AI Voice Agencies
You are not a passive platform. When your client deploys an AI voice agent, you are the architect of that agent. You are liable for the calls it places.
Here's the chain of liability: Your client dials 10,000 leads using your AI agent. Leads start complaining to the FCC. The FCC audits. Turns out 500 of those calls (5%) didn't have documented consent. That's 500 violations at $500 minimum each = $250,000. Your client's business folds. Your client sues you. You fight or settle. Either way, you lose.
Most AI voice agencies today use API infrastructure (Retell, VAPI, Synthflow, Bland). These platforms do not enforce consent compliance by default. You have to build it yourself on top. That means:
- Do-not-call registry checks on every call (you're building this manually)
- State-level consent tracking (California opt-in, New York DNC list, etc.)
- A2P carrier pre-approval (you're managing paperwork)
- Consent recording and audit trail (for legal defense)
- Liability tracking and incident response (if something goes wrong)
If you're duct-taping Retell + GoHighLevel + Zapier + a custom Airtable, you have zero of this. You're flying blind. And you're now officially liable for every non-compliant call.
The silver lining: Compliance is now table stakes. Agencies that move fast can position compliance as a selling point. "Use our voice agents, we handle FCC compliance" becomes a differentiator worth $100-300/month premium per client.
What We're Doing at Hermes About It
Hermes was built compliance-first. Every agent you deploy runs through three gates before placing a single call:
- Do-not-call registry check (DNCL) against FCC database, real-time per call
- A2P carrier pre-approval (we handle the submissions to AT&T, Verizon, T-Mobile). You don't touch paperwork.
- State-level consent rules (California requires written consent, New York requires DNC check, 14 other states have custom rules). We enforce all of them automatically.
On Hermes, you deploy an agent for $149/month (Starter plan). Included: 300 minutes of calling, compliance checks, carrier approval, DNC registry access, audit trail.
A2P compliance submission is $30 per agent (pass-through carrier cost). You submit once, your agent is approved for nationwide deployment.
Your end-clients don't see the complexity. They see: "Your voice agent is FCC-compliant. We handle the risk."
Action Steps for Agencies (This Week)
If you're currently running AI voice agents on any API platform, here's what to do:
- Audit your last 30 days of calls. Log into Retell/VAPI/Bland dashboard. Export your call history. Count total calls. Then count: How many went to numbers on a do-not-call list? How many had documented consent? If you don't have answers, you're exposed.
- Check your consent sourcing. Did your clients source leads from opt-in lists? Or cold outbound lists? Hermes enforces consent at the call level. API-only platforms don't. If you've been running cold outbound without consent, that's 100% of your calls violating TCPA.
- Document your current compliance posture. Write a one-pager: "Here's how we check do-not-call lists. Here's how we document consent. Here's our audit trail in case of FCC inquiry." If you can't write this, you don't have compliance. And if you don't have it, your liability insurance won't cover you.
- Calculate your compliance cost. Hiring a compliance consultant: $10K-50K upfront, then $2K-5K/month ongoing. Building compliance infrastructure: 6 months, 2 engineers, $100K+. Using Hermes: $149/month, compliance included, live in 72 hours. The math is not close.
- Plan your infrastructure migration. If you're on Retell or VAPI, you can migrate to Hermes and keep your Twilio numbers. We have a dedicated migration guide. Your clients see no change. Your compliance posture becomes institutional.
The Numbers
Scenario: You're a 5-person agency with 8 clients. Each client runs 500 calls/month. That's 4,000 calls/month, 48,000 calls/year.
If 3% of your calls are non-compliant (a conservative estimate for API-only platforms), that's 1,440 non-compliant calls/year.
FCC audit? 1,440 calls × $500 per call minimum = $720,000 in liability. Your revenue is probably $50K-200K/month. You can't survive a single FCC audit.
Hermes cost: $149/month × 12 months = $1,788/year. A2P submissions: $30 × 8 agents = $240/year. Total: $2,028/year for compliance cover.
The bet is whether $2K/year is less than the expected value of an FCC enforcement action. Spoiler: it is by a factor of 350x.
What This Means for Competition
Synthflow and Retell are infrastructure. They're agnostic about compliance. VAPI is agnostic. Bland is agnostic. They build the engine. You build the guardrails.
Hermes is the first platform to reverse that. We are the guardrails. Compliance is infrastructure, not an afterthought.
Agencies that adopt compliance-first infrastructure first will own their market verticals. Healthcare agencies will say: "We're HIPAA-aware and TCPA-compliant." Real estate agencies will say: "We call leads legally, with documented consent." Insurance agencies will say: "Our voice agents follow state rules per state."
Agencies that don't will get undercut by someone who does, or they'll face an FCC complaint and fold overnight.
FAQs
If I was already running outbound calls before today, am I automatically in violation?
No. The FCC hasn't retroactively enforced compliance. But if you did an audit today and found non-compliant calls, you now have knowledge of the violation. That makes you liable going forward. The safe move: audit, document your findings, and migrate to compliant infrastructure immediately. That posture is defensible if an FCC inquiry comes later.
Does 'prior express written consent' mean I need a signature?
Written consent can be an email, a form submission, or a recorded phone call where the caller says yes. It needs to be specific: 'I consent to be called by [Company Name] AI agents at [number].' A blanket 'I agree to terms' isn't enough. Hermes tracks this at the call level.
What about inbound calls where the lead calls me?
Inbound is simple: if someone calls you, you can use AI from the start. No prior consent needed. The TCPA complexity is outbound-only.
If my client insists on using Retell, can I still operate?
Technically yes, but you're liable for compliance. Charge a $100-300/month compliance fee on top. Build your own consent tracking, DNC checks, and audit trail. Or recommend Hermes as a white-label platform where they own the infrastructure and you own the sales relationship. Don't absorb the compliance cost into your service fee.
When does the FCC start enforcing this?
The FCC doesn't have a specific enforcement date. But complaints are already coming in from consumers. Any class action law firm can manufacture a lawsuit within 60 days of an FCC confirmation. The safe assumption: enforcement is happening now.
Next Steps
Start here: Join the Hermes beta. We'll walk you through a migration from your current stack (Retell, VAPI, etc.) to compliant infrastructure. Your Twilio numbers come with you. Your clients see no change. Your compliance posture becomes real.
Want to see how Hermes compares to your current stack? View our side-by-side comparison with Retell, VAPI, Synthflow, and Bland. We'll show you exactly where compliance is missing on those platforms.
Pricing: Starter $149/month (300 minutes, 3 workspaces), Business $399/month (1,000 minutes, 7 workspaces), Agency $699/month (2,000 minutes, 20 workspaces). A2P compliance submissions are $30 per agent.
The FCC just made compliance non-negotiable for outbound voice calling. Agencies that move first turn compliance into a competitive advantage. Agencies that wait get undercut or audited. The time to move is today.