Conversational ITSM & Virtual Agents

Week one feels sharp. Week six feels off. By month three, users have learned the lesson. The bot is useful for a couple of things, and unreliable for everything else. Trust drops, adoption stalls, and people route around it back to email, phone, or whatever shortcut still works. That rot is rarely a technology problem. […]

A modern virtual agent is not a chatbot bolted onto ITSM. It is a service front door that lets people describe intent in plain language and still reach a structured outcome. The trap is designing it as a feature bundle. That is how teams end up with brittle topics, long menus, and link dumping. The

An Intent First way to launch conversational experiences without boiling the ocean Most organisations launch a chatbot the same way they launch a knowledge base. They try to cover everything. They start with a spreadsheet, list fifty topics, and spend months building a catalogue of flows that look impressive but rarely get used. Adoption stalls,

Messy intent in. Structured outcome out. For twenty years, enterprise service has relied on a lazy assumption: it is easier to train a human to speak “database” than it is to train a computer to speak “human”. You see it every time someone opens a portal. Select category.Select sub category.Select urgency. This is not help.

You are five minutes from a meeting. You click a file link and hit an access error. You try again. Same result. Your brain does the quick maths: if you go to the portal, you will need to sign in, find the right form, pick the right category, explain the issue, and hope it lands