The scenario
TicketZero is an IT helpdesk copilot that decides, per question, where the answer should come from. It checks the company knowledge base in a vector store, falls back to web search for vendor issues, and drafts a step-by-step fix — or opens a ticket with everything already filled in. Built with FastAPI and LangGraph, containerised, and deployed to a managed cloud host.
System architecture
01 Employee Describes the issue
02 Router agent KB first, web if needed
03 Pinecone KB Runbooks + past fixes
04 Web search Vendor docs
05 Answer or ticket Steps or pre-filled ticket
High-level flow of TicketZero, from input to output.
What you will learn
- Routing between internal knowledge and web search
- Structuring troubleshooting answers as steps
- Creating tickets from an agent with the context pre-filled
- Containerising and deploying an agent service
What you will build
- Knowledge base ingestion from IT runbooks
- Router agent with KB, web and ticket tools
- Employee-facing chat UI
- Docker image and cloud deployment
Build plan
- Ingest runbooks into the vector store
- Build the routing graph
- Add web search and ticket tools
- Ship the chat UI
- Containerise and deploy