All videos
0:00 / 0:00
research

Observing And Testing CX Agents | Interrupt 26

LangChain16 June 2026Watch on YouTube

Part of series

Ep. 1 · LangSmith Engine: Agents bouwen

LangChain laat zien hoe LangSmith Engine het evalueren en verbeteren van AI-agents automatiseert via trace-analyse.

View the series

Description

At Interrupt, the agent conference by LangChain, Carlos Pereira from Cisco's Customer Experience team showed how you close the loop between production feedback and code at 16 million customer interactions per year. The core problem with scaling agents: once adoption climbs, feedback volume outpaces your team. Every thumbs down, every confused user, every low-confidence routing decision is a signal. If you treat it as noise, or if your team becomes the bottleneck processing it, adoption drops. This talk walks through the system Cisco built to take a user's thumbs down all the way to a merged PR, with AI handling triage and diagnostics and humans in the loop only where decisions matter. Observing And Testing CX Agents | Interrupt 26 0:00 Introduction and Day 2 context 0:49 What today covers: observability, testing, and support 1:11 Cisco support at scale: 16M interactions per year 1:34 When network outages hit: why this matters 1:54 CX methodology and team structure 2:16 Evolution: from chatbot to autonomous teammate 2:51 Today's question: closing the production feedback loop 3:23 The approach: continuous feedback loop, not a ticket queue 4:11 Every signal matters: thumbs down, errors, and confusion 4:41 Why humans become the bottleneck at scale 5:57 Signal capture via LangSmith traces 6:12 Triage agent: LangSmith MCP and Jira MCP in practice 6:55 Code agent: clustering and diagnosing issues 7:35 Human in the loop: only on writes, not reads 7:56 Proactive and reactive feedback pipeline 9:20 Treat evals like tests, not experiments 10:56 MCP as the integration layer 11:21 Human oversight only on writes 12:47 Lessons learned 13:53 Observability is your new bottleneck 14:05 Close the feedback loop with agents 14:36 Evals are infrastructure, not a side project 15:34 Support use case: Cisco technical support 15:48 Live example: enterprise network assessment 17:04 2,176 security findings: where do you start? 18:13 Semantic routing for ambiguous prompts 19:33 Parallel pipeline with guardrails 20:55 Tracing every step with LangSmith 21:36 Self-learning routing system 21:54 Observing LangSmith itself with Splunk 22:22 Closing Extra resources: • Everything we shipped at Interrupt: https://www.langchain.com/blog/interrupt-2026-overview • Meet LangSmith Engine: https://www.langchain.com/blog/introducing-langsmith-engine • About LangChain: https://www.langchain.com/

What you'll learn

  • At scale (16 million interactions yearly), feedback becomes the bottleneck, so build automated triage and diagnosis systems with AI agents to process signals.
  • Treat evaluations as infrastructure and tests, not experiments, so you can continuously monitor and improve your AI agents' quality.
  • Put humans only on write decisions (code changes), not read operations (processing feedback), to achieve scalability.
  • LangSmith traces and MCPs (like Jira MCP) connect production feedback directly to your development pipeline.
  • Observability itself is your new bottleneck, so monitor and trace every step of your AI system to keep feedback loops closed.

Frequently asked questions

How do you prevent your team from becoming a bottleneck when scaling AI agents?
Deploy AI agents for automatic triage and diagnosis of feedback (thumbs down, errors, confusion), while your team focuses only on write decisions like approving code changes. AI handles the volume, humans make critical decisions only.
What role do LangSmith and MCPs play in Cisco's feedback system?
LangSmith traces capture all signals from production (feedback, logs, routing decisions), while MCPs (like Jira MCP and LangSmith MCP) connect this data to agents that automatically triage and diagnose. This closes the loop from production to code.
Why are evaluations infrastructure rather than experiments?
Evaluations measure whether your AI agents work correctly, like software tests, not as one-off experiments. At millions of yearly interactions, you need continuous monitoring, so evals must be baked into your build and deployment pipeline.
How does Cisco use semantic routing for complex support questions?
Semantic routing analyzes ambiguous questions and directs them to the right agent or system based on meaning rather than keywords. Cisco applies this in technical support where customers ask about network issues and security findings.

Topics