> Markdown version of [/events/world-congress-2026-europe/sessions/1347-beyond-chat-ai](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1347-beyond-chat-ai). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Beyond Chat: AI Workflows That Actually Investigate Alerts (So You Don't Have To Know Everything)


- **Date:** Friday, Jul 10, 2026
- **Time:** 14:20–14:50 (30 min)
- **Room:** Stage 12
- **Event:** World Congress 2026 Europe

## Recording

[Watch recording](https://www.wearedevelopers.com/videos/100308-beyond-chat-ai-workflows-that-actually-investigate-alerts-so-you-don-t-have-to-know-everything)

## Description

"You build it, you run it" sounds great until you're on-call for a Kafka consumer lag spike at 3 AM—and you spent the last six months building the React frontend, not the event pipeline. Modern teams own their services end-to-end, but no one can be an expert in everything. And the AI chatbots we've been promised? They just add another window to alt-tab through while the pager screams.

This talk argues that chat-based AI is fundamentally wrong for incident investigation. I'll break down why the chat paradigm fails: it expects you to provide context you don't have at 3 AM, assumes you know where to look, burns time with back-and-forth, and interrogates instead of investigates.

Then I'll show what actually works: AI workflows that investigate like a teammate who knows the system—automatically discovering affected resources, correlating metrics with deployments, querying the right logs without being asked, and delivering hypotheses with evidence.

We'll cover real engineering challenges: orchestrating tools across Kubernetes, logs, and metrics; solving the "where do I even start?" problem; building outputs that explain unfamiliar systems; and what breaks when you let AI loose on production.

Live Demo: A simulated 3 AM alert comparing the chatbot experience ("Can you tell me more about your cluster configuration?") versus a workflow that delivers: "Your deployment rolled out 47 minutes ago with a memory limit reduction. Three pods are OOMKilling. Here's the diff and the kubectl command to rollback."

## Speakers

### [Aram Hakobyan](https://www.wearedevelopers.com/@aram-hakobyan)

Head of Platform Engineering at zooplus
### [Nune Isabekyan](https://www.wearedevelopers.com/@nune-isabekyan)

CTO of OpsWorker


## Related talks at this congress

- [Agentic employees in world's most downloaded FinTech app](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1133-agentic-employees-in) — Sasa Fajkovic
- [Unlocking the AI Black Box: Building Trust in the Era of Agentic Production](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1445-unlocking-the-ai) — Jemiah Sius, Harry Kimpel
- [The day the chatbot asked for sudo](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1027-the-day-the-chatbot) — Alex Olivier
- [What Production Knows: Closing the Loop Between AI Agents and the Systems They Build](https://www.wearedevelopers.com/events/world-congress-2026-europe/sessions/1470-what-production) — May Walter