The Agent Channel Has a People Problem
Plus: when AI starts reshaping sales, service, and regulation, the handoff plan matters as much as the model.
Your daily signal on AI and CX — minus the hype.
DCX Stat of the day: State Farm has roughly 19,000 independent-contractor agents, and WSJ reports the company told them current contracts will end by 2027 as it rolls out an AI-backed sales model. The Wall Street Journal
In this issue:
→ State Farm rewires the human channel
→ Agents become a trust-design problem
→ AI trust keeps sliding
→ Capacity connects the support stack
→ Your handoff map needs names
🔍 DEEP DIVE
The Good Neighbor Gets a Rewrite
The company told agents that current contracts will end by 2027. The new model ties more of the business to sales targets, digital assistants, AI summaries of household concerns, tailored product recommendations, and an AI assistant being piloted for customers reporting auto losses.
That is where this stops being a labor story and becomes a CX story. Insurance customers do not experience the brand as a neat org chart. They experience it through quotes, claims, confusing bills, coverage questions, price shocks, renewals, and the person who explains what happens next.
If AI makes that system faster but less accountable, customers feel the tradeoff immediately. If AI gives the agent better context and the customer a cleaner recovery path, it can reduce effort without flattening the relationship.
Bottom Line: The risk is not that AI enters the insurance journey. The risk is that the business redesigns the channel before it redesigns ownership.
📬 Copy-Paste Take
Before we put AI into a relationship channel, we need to name what the AI can recommend, what the human still owns, what the customer can challenge, and who fixes the problem when the system is technically efficient but emotionally wrong.
🧭 OPERATOR PLAYBOOK
Put Names on the Handoff
Start with one customer journey where AI is moving closer to the decision: quote, renewal, claim, refund, eligibility, appointment, complaint, or cancellation.
Audit every AI-assisted handoff for four things:
The customer decision the AI can influence.
The human role that still owns judgment.
The moment a customer can challenge or correct the recommendation.
The recovery owner when the AI-supported path creates confusion.
Then test whether the customer can tell who is responsible without reading your operating model. (They won’t. Fun little problem.)
Ask your team: If this AI recommendation creates a bad customer outcome, who has authority to unwind it?
Signal: Relationship channels do not become better just because the software got faster. They become better when speed, judgment, and recovery are assigned clearly.
📊 MARKET REALITY CHECK
Adoption Is Outrunning Trust
57% of Americans have used AI tools for search, brainstorming, work, school, or related tasks, according to Census Bureau Household Trends and Outlook Pulse Survey data.
That is the adoption side. The trust side is where CX gets interesting. 35.1% of adults said someone in their household used AI to find information, but only 13.8% of AI users said they trust the information they get from it.
That gap belongs right underneath the State Farm story. Customers may use AI, but usage is not the same as trust. When the journey involves money, coverage, claims, eligibility, or a decision they do not fully understand, trust does not automatically transfer from the brand to the machine.
Why it matters: If AI adoption is rising while trust remains thin, the human handoff becomes part of the product. Customers need to know where the machine stops and where accountable judgment starts.
AI usage + low trust = visible human ownership
🧰 TOOL WORTH KNOWING
Capacity
What it does: Capacity is an agentic support automation platform built around one AI knowledge layer for customer and employee support.
CX use case: Useful for teams trying to stop support AI from turning into a pile of disconnected tools. Capacity connects AI agents, agent assist, post-interaction QA, conversational intelligence, and outbound voice or SMS campaigns to the same knowledge base.
Worth watching because: Consistency is the boring problem that becomes very expensive. If chat, email, SMS, voice, QA, and human-agent guidance all learn from different sources, customers get different answers depending on the door they picked. Capacity’s platform pitch is simple: connect the knowledge once, then use it across the support journey.
Bottom line: Capacity is worth watching because CX teams do not need five AI pilots with five knowledge bases. They need a single answer system that improves self-service, supports human agents, checks quality, and shows where automation breaks down.
The news: Today, the company also announced it crossed $100M ARR, which is a useful sign that buyers are moving past chatbot demos toward integrated support automation. Capacity built one of the largest agentic AI businesses in the market on a fraction of the capital and many times the customer base of its better-funded rivals
“The market spent the last two years buying AI point solutions and is now waking up to the bill: five vendors, five contracts, five knowledge bases that don’t talk to each other,” said David Karandish, founder and CEO of Capacity. “Customers don’t want another chatbot. They want the work to get done. That’s what an agentic platform delivers, and that’s what’s behind every dollar of our $100M.”
Learn more: Capacity
The DCX AI Today - AI Tool Directory - If you lead a CX team and want a curated shortlist of tools worth evaluating, this is your starting point.
📡 90-SECOND CX RADAR
AI preemption gets tangled with child safety
The Verge reported that efforts to create a federal AI preemption package are getting mixed with online child-safety legislation, making an already messy policy fight even harder to land.
Why it matters: If customer-facing AI rules keep shifting between federal and state control, CX teams should stop waiting for perfect clarity and start documenting the decisions their AI systems can influence.
✅ YOUR MOVE
AI is moving from an answer box to an operating channel.
That means the customer may not know whether a recommendation came from a person, a model, a policy rule, or all three wearing the same company badge.
Pick one journey this week where AI is being added to a human relationship channel. Then write down the ownership map in plain English: what the AI can do, what the human owns, what the customer can challenge, and who fixes the outcome.
If the map sounds vague, the customer experience will feel vague too.
Before you automate the handoff, decide who owns the recovery.
Until tomorrow,
👥 Share This Issue
Think of one person who’s wrestling with AI in CX right now
and forward this to them.
I’m obsessed with Wispr Flow Pro! Get a Free Month on me.
If someone forwarded this to you, they thought you needed to see it before your next AI planning meeting. Get your own copy.