The Spotlight Still Describes the Failure Modes Correctly
The CFPB published its chatbots issue spotlight in June 2023. By the time most banks finished circulating it internally, the agency that wrote it had been cut toward a third of its former headcount and had stopped running most of the examinations that would have tested compliance with it. The natural question inside a bank in 2026 is whether the document still matters.
It does, because the spotlight is not a rule that the Bureau can decline to enforce. It is a description of how chatbots break consumer-finance law that was already on the books. The agency reported that roughly 37 percent of the U.S. population interacted with a bank's chatbot in 2022 and projected that number would pass 110 million users by 2026. It then named the way these systems fail. A customer trying to dispute a charge gets caught in what the Bureau called a "doom loop," a continuous cycle of repetitive, unhelpful jargon with no offramp to a human. A chatbot ingests a customer's words, fails to recognize that the customer is invoking a federal right, and the clock on that right keeps running. The bot gives an answer that is wrong, the customer acts on it, and a fee or a missed payment follows.
We build the agents that have to avoid all three. The spotlight is the most useful adversarial test document a bank's compliance team has, because it tells you exactly what an enforcer will look for.
Who Enforces a Chatbot Failure in 2026
The change since 2023 is not that the risk went away. The change is who shows up.
Section 1042 of Dodd-Frank gives state attorneys general the authority to bring actions to enforce the consumer-protection provisions of the Act, including the prohibition on unfair, deceptive, and abusive acts and practices. That authority does not depend on the CFPB being at full strength. State banking departments have their own UDAP statutes, and New York and California have both the statutes and the investigative staff to pursue large institutions. Reporting through early 2026 has tracked former Bureau staff moving to state regulators and state AG offices, which means the institutional knowledge of how a chatbot violates federal consumer law moved with them.
Then there is the private bar. A chatbot that fails to act on a Regulation E error notice does not create a regulatory finding so much as it creates a private claim under the Electronic Fund Transfer Act, which carries statutory damages and attorney's fees. The plaintiffs who bring those claims were never relying on a CFPB exam to find the violation for them.
So the practical exam in 2026 is not "will the CFPB examine this." It is "if a state AG or a plaintiff's lawyer pulls our chat transcripts, what do they find." We design the agent so the answer is defensible.
The Doom Loop Is a Design Choice, So We Designed Against It
The doom loop is not an AI problem. It predates chatbots by a decade in IVR trees. A model makes it worse only if the escape hatch is missing. The control is an intent classifier that runs on every inbound turn and watches for a small set of escalation triggers: an explicit request for a human, a repeated unresolved question, a rising-frustration signal, and any utterance that maps to a protected category of request. When a trigger fires, the agent routes to a person and carries the full context across.
We hold the human-handoff path to a measurable bar rather than a promise. The metric we track is the false-negative rate on escalation, meaning the share of conversations where the customer needed a human and did not get routed to one. We review that number weekly against a sampled and labeled set, and we treat any miss on a federal-rights trigger as a defect, not a tuning opportunity. A containment rate that looks good because the agent refused to let people out is the failure the spotlight described, so we do not optimize containment in isolation.
Recognizing a Federal Right When the Customer Invokes One
This is the part of the spotlight that most chatbot deployments still get wrong, because it requires the agent to understand intent, not keywords. A customer rarely says "I am invoking my Regulation E error-resolution rights." They say "there's a charge I didn't make" or "someone took money out of my account." The agent has to recognize that this is a notice of error and that a clock just started.
We maintain a rights-recognition layer that maps customer language to the specific obligations it triggers, because the timing rules are unforgiving and statutory. The categories we treat as hard interrupts:
- An unauthorized-transaction or billing-error statement, which is a Regulation E or Regulation Z error notice and starts the investigation clock
- A debt-collection cease-communication or dispute statement, which triggers FDCPA obligations the agent cannot talk past
- A servicemember identifying active duty, which can implicate the SCRA
- A statement of bankruptcy filing, which is an automatic-stay event
- Any hardship or loss-mitigation request on a mortgage, which starts Regulation X duties
When any of these is detected, the agent stops trying to self-serve, records the notice with a timestamp, opens the matching case in the system of record, and hands to the right queue. The agent's job at that moment is to capture the right and protect the clock, not to resolve the matter.
The Disclosure Question Compliance Counsel Actually Argues About
Every bank we work with debates the same point. The spotlight warns about consumers being given a false sense that they are dealing with a human. Counsel wants a clear disclosure. Operations worries that a heavy-handed "you are talking to a robot" line tanks the experience and pushes everyone straight to the call center.
The pattern that has gotten sign-off from compliance counsel at the banks we serve is a plain identification at the top of the session, in the customer's language, that names the assistant as automated and states that a representative is available. We do not bury it, and we do not dress it up to sound human. The disclosure is a versioned artifact reviewed by counsel, the same as any other required notice, so when the wording is questioned later there is a record of who approved it and when. We learned to treat the greeting as a controlled document the first time a customer-experience team quietly edited it to sound friendlier and removed the word "automated" in the process.
Inaccurate Answers Are a Grounding Problem
The third harm in the spotlight is the chatbot that gives wrong information about a product or a payment. A model that generates from its own weights will eventually state a fee, a cutoff time, or a payoff figure that is not true for this customer's account. In consumer finance, telling a customer something false about their money can be a deceptive act under the UDAAP standard, with the consumer harm and the regulatory exposure that follows.
The architecture we deploy does not let the model answer policy or account questions from memory. It retrieves from approved, versioned sources, and the answer has to carry a citation back to the source passage or the agent declines and routes to a person. Confidence gating sits in front of any answer that touches money. We have written separately on the grounding and citation architecture, and the chatbot context is where it earns its place, because the spotlight's "harm to consumers" category is mostly the absence of grounding.
What We Log
A defensible chatbot program in 2026 is the one whose transcripts survive a subpoena, so logging is part of the control, not an afterthought. For every conversation we retain the full transcript with timestamps, the disclosure that was shown, the intent classifications and any rights triggers that fired, the retrieval sources and citations behind each substantive answer, the escalation decision and its basis, and the handoff context passed to the human. When a state AG or a plaintiff asks what the customer was told and whether the bank acted on a federal right, the bank produces the record rather than reconstructing it.
The Honest Version
A chatbot that does all of this is more expensive to build and slower to ship than one that does not. The rights-recognition layer, the grounding requirement, and the escalation bar all reduce the share of conversations the agent handles end to end, which is the number a vendor selling on deflection wants to maximize. We make the case the other way on the first call. The deflection rate that ignores the spotlight is a liability the bank carries, not a saving, and the institution that finds that out from a state AG learns it at the worst possible price. The CFPB stepping back did not lower the bar. It moved the bar to enforcers who are less predictable and, in the case of the private bar, paid to find the failure. Build for them.
Pranay Shetty
CEO & Co-Founder