The chatbot: a partially fulfilled promise
Between 2018 and 2022, Swiss CIOs massively invested in chatbots: service desks, automated FAQs, virtual assistants. Results were mixed: resolution rates of 30–40% at best, and growing user frustration with bots unable to step outside their scripts.
The transition to agentic AI isn't an evolution of the chatbot — it's a fundamental break. Here's why.
The four dimensions of the break
1. From response to action
A chatbot responds. An agent acts. The difference seems subtle; it is fundamental. The agent can create a ticket, update a database, send an email, trigger a procedure — without the user having to interact with each system separately.
2. From session to persistent memory
A chatbot forgets everything at the end of a session. An agent retains context: it knows the user manages the finance scope, asked the same question three weeks ago, and prefers concise summaries over detailed reports.
3. From single tool to orchestration
A chatbot is connected to one data source. An agent orchestrates multiple tools simultaneously: Jira + Confluence + Slack + CRM + ERP — all in a single interaction.
4. From rule to reasoning
A chatbot follows a decision tree. An agent reasons about the situation and adapts its response to context. It can handle cases it has never encountered before.
Impact on Swiss CIOs: an organisational transformation
| Dimension | Chatbot era | Agentic era |
|---|---|---|
| Required profile | Bot developer, NLP engineer | Prompt engineer, Agent architect |
| Key metric | Resolution rate | Actions completed without intervention |
| Infrastructure | Centralised chatbot platform | Orchestrator + APIs + LLM |
| Governance | Validated scripts | Audit log + action boundaries |
Where to start?
Three priority processes for a first chatbot → agent migration in a Swiss IT department: Level 1 service desk (resolving common IT issues), access provisioning (account creation, rights assignment), and HR support (payroll/leave queries with HR system access).
