VOX

Tier-3 VoIP support is forensic work. A ticket says 'calls sound bad'; the truth lives in a CDR, a packet capture, and sometimes an AI receptionist's tool-call log. Working one ticket properly means pulling all of it, reading all of it, and writing up what actually happened — slow, repetitive, and easy to shortcut when the queue is deep.

VOX is the teammate I built to do that work with me: 12 Claude Code skills and about 20 Node helper scripts that read an Intercom ticket, auto-classify it into one of five flows, resolve the tenant, pull CDRs, download packet captures from VoIPmonitor, run tshark analysis, and draft the reply as an internal note. It works my real queue at VOXO every day.

It never acts alone. Drafts land as internal notes for human review — VOX has no path to message a customer directly. Config changes go through a dry-run diff, timestamped before/after backups, an explicit YES gate, and a pre-written one-line rollback. Autopilot checks whether a human already engaged before it touches a ticket at all.

No public link here. VOX runs inside VOXO's support stack against production systems — Intercom, the admin API, VoIPmonitor — so there is nothing safe to deploy. That's what the INTERNAL badge means. What you can watch instead: a scripted replay of one Tier-3 run, with every name, number, and ID fabricated.