1. Measure before you outsource
Get 30 days of baseline numbers: weekly ticket volume, average first-response time, CSAT (if you have it), top five ticket categories. Without a baseline, you wonu2019t know if your outsourced team is a win.
2. Categorize and macro-ize
Group the top ticket types. Write canned responses (u201cmacrosu201d) for the ones that repeat. Even a rough draft beats no draft. Macros are how a remote agent sounds like your brand from day one.
3. Pick your tool before hiring
Help-desk (Zendesk, Freshdesk, Gorgias, Help Scout, Front). Macros and SLA rules configured before anyone logs in. Reporting turned on. Donu2019t hire your first remote CS agent into a messy Gmail inbox.
4. Define what u201cescalateu201d means
Your remote agents should solve 70–80% of tickets without escalating. The remaining 20–30% need a clear path: which tickets go to whom, with what info attached, within what time window. Document this and train to it.
5. Hire for aptitude, train on the stack
Donu2019t require Zendesk experience — require judgment, written tone, and accuracy under pressure. The tool takes days to learn; judgment takes years. Our screening approach covers how we filter.
6. Onboard with shadowing, not lecture
Week 1: read all recent tickets, write draft responses a senior agent reviews. Week 2: reply live with review. Week 3: own tickets solo with QA spot-checks. Week 4+: full ownership.
7. Review the right metrics
- First-response time and resolution time
- CSAT or a proxy (thumbs-up, 1–5 star)
- Macro usage rate (signals training adoption)
- Escalation rate trending down over time
Start with a scoped pilot
See Customer support services for scope options, or share your ticket volume on Get Started. Also see Outsource customer service for service businesses if you run a service operation rather than an e-com brand.