Signal Taxonomy Lab
Flagship. Twelve weeks on naming, sampling, and presenting queue motion without inventing a new KPI religion.
Open the lab outlineHardwick teaching studio · GB
Api Routecore is a small studio for people who own a support desk and need customer support signal analytics that survive a Monday stand-up. We train you to name the motion in a ticket stream — not to decorate a dashboard.
See the current programmes →From people who sat in the queue
The silence-window drill in Signal Taxonomy Lab is what I still run on Fridays. I would not use their routing score on a 40-seat desk yet — we are smaller — but the naming work stuck.
I arrived convinced CSAT lag was “just survey delay.” After Channel Atlas I could show finance where the lag actually lived in the thread, which is a less glamorous sentence and a more useful one.
Rated the cohort 8/10 on our internal wiki. The homework is unforgiving if your export is messy. That is also why it worked.
Programmes in view
Flagship. Twelve weeks on naming, sampling, and presenting queue motion without inventing a new KPI religion.
Open the lab outlineA shorter map of email, chat, and social threads so handoffs stop looking like “the other team.”
All programmesTwo working days with your own export. We return a signal list you can argue with, not a 40-page PDF.
Fee notesStudio habit
Most desks already drown in volume charts. The missing piece is a shared vocabulary for what a spike is doing: retry loops, policy fog, courier theatre, billing echo. Those are signals. They are not “sentiment.”
Cohorts meet in Hardwick or remotely. You bring a sample, we refuse to average it into a single happiness number, and you leave with a method you can defend in front of a sceptical ops director.
How we define a signal →Journal
Why collapsing every repeat contact into “failure demand” hides the only useful split in the pile.
Surveys arrive late. The ticket already told you. Here is how we timestamp that gap.