Onboarding Patch Notes
Every cohort's first 30 days with customers writes the next onboarding release.
The job
When each new cohort goes live, see what customers experienced from it in its first 30 days compared with tenured staff on the same requests, turn the biggest gaps into versioned onboarding fixes, prove on the next cohort whether they are gone, and report days to tenured parity priced per agent-day. Everything is at cohort level, never per person.
The moment
Graduation day: instead of a slideshow, the screen shows Onboarding v8 release notes. Fixed: wrong fee quoted for a replacement card, 3 complaints in Cohort 23's first 30 days against 41 for Cohort 19. Improving: transferred to licensing and back. Known issue: the new account category, answered wrong at three times the tenured rate. Then the diff scrolls: red lines for what customers stopped saying, green for what they started. The academy head taps patch, and before Monday's class the trainers have a lesson brief built from five masked real calls. The last line: Cohort 23 reached tenured parity in 19 days instead of 31, worth $184K of agent-days on this programme.
What it does
- Write a syllabus patch from a customer gap
- Send the lesson brief with five masked calls to trainers
- Ship a curriculum release
- Extend nesting for a class with a weak readiness check
- Tell the graduating class what their customers taught the academy
- Send the parity exhibit to the client QBR
What you see
Software release notes for the onboarding programme (Fixed / Improving / Known issues) with a red-green changelog diff between cohorts, read aloud at graduation.
What it moves
Days to tenured parity per cohort (priced per agent-day), and share of patch lines stamped Fixed on the next cohort.
Built for
- Contact-centre operations
- HR & employee experience
- Partners & ecosystem
