The slowest part of a ticket isn't typing the reply. It's finding out what's true.
What it does
- A ticket lands → the AI checks it against your codebase and drafts an answer
- The draft is added as a private note, ready for an agent to send or rewrite
- Looks like a defect → it's escalated as a GitHub issue instead of bouncing around the queue
- Written for support staff to read, not for engineers
What it does not do
It never sends the reply, never closes the ticket, never changes its status.
Honest note: beta — built and smoke-tested, real queues will teach it more.
Setup
clone → ./setup.sh → pick Freshdesk → answer a few questions
~5 minutes. No server, no database, free.
Get it
The recipe is open source: github.com/akshaypatel-ai/ai-automations
This is one of 30+ automations in the series — the full write-up lives on my site.
Top comments (0)