Source: Why We Built an AI Service Desk

Source: console.com/blog/why-we-built-an-ai-service-desk

What It Covers

Console’s manifesto post on the AI Service Desk category. Argues that traditional service desks optimized to manage tickets rather than solve the underlying problems, and that an agent-first design inverts the model.

Key Claims

  • “Service desks evolved to manage tickets, not to solve the core issue.” (extracted)
  • Every IT request requires human triage today: topic identification, urgency, routing, missing-info collection — all before resolution work begins. (extracted)
  • Categories, forms, and routing rules exist to translate user intent into system shape. They are not the work; they are the cost of the system’s design. (extracted)
  • Console’s agent-first model: an agent gathers context, asks follow-ups, and enriches with org context before a ticket is created. Humans receive ready-to-resolve work. (extracted)
  • “Tickets [become] a record of what happened, not the mechanism of work.” (extracted)

Notable Phrasing

  • “Agent first, human second”
  • “Removes work that exists only to manage the desk itself”
  • “Inbox designed to stay empty”

Limitations

  • Manifesto-style — light on technical mechanism, heavy on framing.
  • No customer numbers in this specific post (those live in product/case-study posts).
  • Doesn’t engage with where agent-first fails (truly novel incidents, regulated work).