By Sagar Shankaran, Founder of CallSphere
New York became the first state to require companies to disclose AI-driven layoffs, but not a single company has complied. With 28,300+ workers affected by WARN notices, the enforcement gap is glaring.
Key takeaways
New York made history by becoming the first state to require employers to disclose when AI influences mass layoffs. There's just one problem: not a single company has complied.
Under New York's amended WARN Act, employers with 50+ employees planning mass layoffs must:
The numbers tell a damning story:
Zero. Not one.
flowchart TD
HUB(("The Law Nobody Follows"))
HUB --> L0["What the Law Requires"]
style L0 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L1["The Compliance Gap"]
style L1 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L2["Why Companies Aren't<br/>Complying"]
style L2 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L3["The Irony"]
style L3 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L4["What This Means"]
style L4 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
style HUB fill:#4f46e5,stroke:#4338ca,color:#fffSeveral factors explain the silence:
Hear it before you finish reading
Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.
Block's Jack Dorsey proudly announced 4,000 layoffs due to AI on CNBC, but the formal legal filings tell a different story. When it comes to SEC filings and WARN notices, the AI narrative conveniently disappears.
Without enforcement teeth, disclosure laws become virtue signaling. For workers displaced by AI, the lack of transparency means fewer resources, less retraining support, and a harder path to re-employment.
Sources: SHRM | Entrepreneur | National Law Review | HRSpotlight
flowchart TD
HUB(("The Law Nobody Follows"))
HUB --> L0["What the Law Requires"]
style L0 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L1["The Compliance Gap"]
style L1 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L2["Why Companies Aren't<br/>Complying"]
style L2 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L3["The Irony"]
style L3 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
HUB --> L4["What This Means"]
style L4 fill:#e0e7ff,stroke:#6366f1,color:#1e293b
style HUB fill:#4f46e5,stroke:#4338ca,color:#fffMost coverage of New York's AI Layoff Law Has Zero Compliance — and That's a Problem for Everyone stops at the press release. The interesting part is the implementation cost — what changes for a team running 37 agents and 90+ tools in production? On the CallSphere side, the practical filter is simple: would this make a 90-second appointment-booking call faster, cheaper, or more reliable? If the answer is "maybe in a benchmark," it doesn't ship to production.
Most AI news is noise. A new benchmark score, a leaderboard reshuffle, a leaked memo — none of it changes whether your AI receptionist books appointments without dropping the call. The handful of things that do move production AI voice and chat are concrete: realtime API stability (does the WebSocket survive 5+ minutes without a stall?), language coverage (does it handle 57+ languages with usable accents, or is English the only first-class citizen?), tool-use reliability (does the model actually call the right function with the right argument types under load?), multi-agent handoffs (do specialist agents receive structured context, or just transcripts?), and latency under load (p95 first-token under 800ms when 200 concurrent calls hit the same endpoint?). The CallSphere rule on news is: if it doesn't move at least one of those five numbers in a measurable eval, it's a blog post, not a product change. What to track: provider changelogs for realtime endpoints, tool-call schema changes, language-add announcements, and any deprecation that pins your stack to a sunset date. What to ignore: leaderboard wins on tasks that don't map to your call flow, "agentic" benchmarks that don't measure tool latency, and demos that work because the prompt was hand-tuned for the demo. The teams that ship fastest treat AI news the same way ops teams treat CVE feeds — read everything, act on the small fraction that touches your runtime, archive the rest.
Q: Does new York's AI Layoff Law Has Zero Compliance — and That's a Problem for Everyone actually move p95 latency or tool-call reliability?
Still reading? Stop comparing — try CallSphere live.
CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.
A: Most of the time it doesn't, and that's the right starting assumption. The relevant test is whether it improves at least one of: p95 first-token latency, tool-call argument accuracy on noisy inputs, multi-turn handoff stability, or per-session cost. CallSphere ships in 57+ languages, is HIPAA aligned, and runs voice, chat, SMS, and WhatsApp from the same agent stack.
Q: What would have to be true before new York's AI Layoff Law Has Zero Compliance — and That's a Problem for Everyone ships into production?
A: The eval gate is unsentimental — a regression suite that simulates real call traffic (noisy ASR, partial inputs, tool-call timeouts) measures four numbers, and a candidate has to win on three of four without losing badly on the fourth. Anything else is treated as a blog post, not a stack change.
Q: Which CallSphere vertical would benefit from new York's AI Layoff Law Has Zero Compliance — and That's a Problem for Everyone first?
A: In a CallSphere deployment, new model and API capabilities land first in the post-call analytics pipeline (lower stakes, async, easy to roll back) and only later in the live realtime path. Today the verticals most likely to absorb new capability first are After-Hours Escalation, which already run the largest share of production traffic.
Want to see after-hours escalation agents handle real traffic? Walk through https://escalation.callsphere.tech or grab 30 minutes with the founder: https://callsphere.ai/book.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
Using GPT-Realtime-2 for healthcare voice agents. BAA scope, PHI handling, retention, logging, and why a managed platform usually wins this build.
CAISI announced new agreements with Google DeepMind, Microsoft, and xAI in May 2026. What gets tested, what changes for enterprise AI buyers, what to watch.
AI Control Tower is the governance layer for ServiceNow's Project Arc — policy, monitoring, and audit logs for autonomous agents. Here is how it works.
Meta is rolling out Llama 4-powered AI agents inside WhatsApp Business — what they do and which markets get them first. Practical context for teams in New York.
Six-domain AI vendor diligence: financial, security, privacy, operational, legal, ethics. Plus 30+ specific questions, SOC 2 / ISO 27001 baselines, and review cadence.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco
The 2024 NPRM proposes mandatory penetration tests every 12 months and vulnerability scans every 6 months. Here is how an AI voice agent should be tested in 2026.