Training a Global EOR Support Org

Rippling’s EOR product was growing fast across 20+ countries, and the support side had to grow with it or become the bottleneck. I led APAC support for R&D Global Payroll — Australia, New Zealand, India, Singapore, the Philippines — the part of the world where a payroll question usually arrives with a statutory deadline already attached to it.

Good support at scale isn’t a heroics problem; it’s a training-and-systems problem. New people took too long to become genuinely trustworthy on country-specific payroll, the institutional knowledge mostly lived in a few veterans’ heads and a wiki nobody could navigate, and there was no real way to tell whether quality was improving or whether we just felt like it was.

A three-track certification curriculum — Standard, Partner, Premium — so capability was something we tested and tiered, not something we assumed. A QA case-tracking system that scored real cases against a defined standard, which finally turned quality into a number we could watch week over week. Incident-response docs that turned escalations from improvisation into procedure. And a full rebuild of the knowledge base, so a question had one home instead of four.

The numbers from that stretch: 4,000+ cases across 20+ countries at 99.9% accuracy, with the triage frameworks taking roughly a third off handling times. The certification tracks became the way new people got onboarded. Somewhere in there came two back-to-back Year-End MVP awards and a Q1 Payroll Ops Rockstar — which I’ll happily take, though the tickets that never had to be escalated are the part I’m actually proud of.

The real takeaway was the playbook itself — train, measure, document, restructure — and it’s exactly what I run now on implementations at Crimson, just from the other side of the relationship.