California just made reaching a real person a legal right at big companies. That's a massive shift for enterprise CX, and the clock is already running.

Governor Newsom signed AB 1609, the Right to Human Customer Service Act, on September 28. It takes effect January 1, 2027.

Plenty of teams will treat this as a legal hurdle, add an "I'm a bot" line, stand up an escalation queue, and move on. But the smartest brands will use it as a forcing function to build what I call the human moat.

What the law actually asks for

If your business does more than $500M a year nationally and serves California customers, here's the short version:

  • Honesty about bots. You can never present a chatbot as human. If a reasonable person could be fooled, you need a clear disclosure. My advice: just disclose every time.
  • An easy way out. Customers get a simple way to ask for a person during at least regular business hours. I LOVE IT.
  • A 15-minute clock. You make a good-faith effort to connect them within 15 minutes, or give them a specific appointment within one business day.
  • Limits on hold time. Once they're connected, you make a good-faith effort to keep any single hold to 15 minutes and total holds and queues to an hour.

Email, web forms, and voicemail sit outside the 15-minute window, and there are carve-outs for things like certain B2B lines, some free services, and certain hospital communications. I'm a CX gal, not your attorney, so run the specifics past counsel.

Penalties go up to $5,000 for a first violation and $10,000 for each one after. This isn't the number I'd lose sleep over, though. The bigger cost is one you're already facing if you're using AI as your customer-facing team...the customer who got stuck in a bot loop and never told you why they left.

The clock isn't the hard part

The law tells you how fast a human has to show up. It doesn't tell you what that human needs to know when they get there.

You can hit 15 minutes on the dot and still fail the customer, because they've already explained everything to a bot and now have to start over from the top.

The real winners won't stop at the 15-minute handoff letter of the law. They'll master the data handoff. When a customer moves from bot to agent, three things should move with them:

  • Context: what they've already said and what the bot already tried
  • History: their account, recent tickets, and anything still open
  • Intent: what they're actually trying to get done and how frustrated they are, not just a category tag

No starting over. No repeating themselves.

Your metrics need to catch up

If deflection rate is your headline number, this law should make you a little uneasy. I've written before about what that number can hide.

A customer asking for a person is one of your best chances to earn trust, so stop counting it as an automation failure. Automation should make that human moment better, never hide it.

Put these next to deflection on your dashboard:

  • Wait Time for Agent (the Human Agent): from the request to a real conversation, including whether scheduled appointments actually happen
  • Repeat rate: how often customers have to re-explain themselves after a handoff
  • Post-handoff resolution: whether the person could actually fix it, and how much effort it took to get there

Under $500M? Don't tune out

You may not be big enough to worry about AB 1609, but customer expectations don't check your revenue first. Once people get used to visibility and the ability to reach a human quickly at the big brands, they'll expect the same from you.

If you build or run support tools for larger companies, expect questions about your human response times in your next vendor review too.

Here's the good news: you don't need a statute to start. The human moat is the retention, trust, and relationship capital that no competitor can copy-paste, and smaller teams can start building it today.

Try this

Before January 1, be your own customer. Take your three messiest support issues through your own bot, ask for a person, and track two numbers: minutes until a human arrives, and how many times you had to repeat yourself.

If that second number isn't zero, you've found the first item for your support process roadmap.