The problem
When customers send support requests to an equipment service and operations team, someone has to read each one, work out what it is about, decide who should take it, and reply. That takes time before any real work begins, and it is where requests wait the longest.
The team also already tracked its work in a separate work-management tool. A new help desk that did not talk to it would mean entering everything twice.
What I built
I built a support desk that does the first pass on every ticket.
When a ticket arrives, the system:
- Categorizes it, so a billing question and a failed machine are not treated the same.
- Routes it to the right person or queue.
- Summarizes it, so whoever opens it sees the point without reading the whole thread.
- Drafts a first response, so the customer hears back quickly.
The ticket and the team's work-management tool stay in sync in both directions. A status change or a comment on either side shows up on the other, so people keep working in the place they already use.
The backend is written in Swift with Vapor. The staff interface is a SvelteKit web app for the queue, the conversation and the ticket details.
Stack
- Swift with Vapor for the API
- SvelteKit for the staff interface
- Language models for categorizing, summarizing and drafting
- Two-way sync with a work-management tool
Outcome
Every ticket is categorized, routed, summarized and answered the moment it arrives, and the team no longer has to enter the same information in two systems. People spend their time on the problem instead of on sorting and typing.