QA & reporting
QA and CSAT Reporting for Outsourced Customer Support Teams
Outsourcing without QA and CSAT is just hoping it goes well. Here's how to actually measure an outsourced eCommerce support team.
The problem
Brands hand off support, then realize three months later they have no idea whether it's going well. CSAT might be decent, but tickets are answered inconsistently, refunds drift, and there's no way to coach because nothing was ever measured against a written standard.
Why it matters
You can't improve what you can't see. QA and CSAT are how an outsourced operation stays honest — both for the brand owner and for the agents. Without them, the relationship becomes faith-based and quality drifts in whichever direction is easiest.
What good measurement looks like
QA
- Written rubric (policy, accuracy, tone, completeness, tagging).
- 5–10 tickets per agent per week, weighted to high-risk categories.
- Per-agent scorecard with trend over time.
- Coaching notes tied to specific tickets, not vague feedback.
CSAT
- Post-resolution survey from the helpdesk.
- Reported per agent, per channel, and per category.
- Low-CSAT tickets reviewed inside 48 hours.
Operational reporting
- Weekly: first-reply time, resolution time, volume by category, refund rate, CSAT.
- Monthly: QA scorecards, dispute win rate, category trends, narrative summary.
- Quarterly: SOP review tied to what the reports surfaced.
How Virtual Freelance Solutions helps
QA and reporting are part of every engagement. We run per-agent QA scorecards, send weekly metrics on response time, CSAT, and category trends, and review the operation with you in a monthly ops session. We can't guarantee a specific CSAT or refund rate, but we can guarantee the rhythm — measured weekly, coached weekly, reviewed monthly.
See our pricing for how reporting scales with package, or book a discovery call.
Frequently asked questions
- What's the difference between QA and CSAT?
- QA is an internal score — a reviewer rates a sample of an agent's tickets against a written rubric (policy adherence, tone, accuracy, completeness). CSAT is the customer's score, usually a one-question survey after a ticket closes. You need both: QA catches things customers won't tell you about, CSAT catches the experience customers had even when the reply was technically correct.
- How many tickets should be QA-reviewed per agent per week?
- A statistically thin sample is still better than nothing. Most teams target 5–10 tickets per agent per week, weighted toward higher-risk categories like refunds, disputes, and escalations. The goal isn't perfect coverage — it's enough signal to coach trends, not just isolated mistakes.
- What should a QA rubric actually score?
- Keep it tight: policy adherence (was the right rule applied), accuracy (correct information), tone (on-brand), completeness (did the reply solve the issue without a follow-up), and tagging (right helpdesk tags for reporting). Five categories, each scored 1–3 or pass/fail. Anything more granular tends to be ignored.
- How should reporting be delivered?
- Weekly: first-reply time, resolution time, ticket volume by category, refund rate, CSAT. Monthly: QA scorecards per agent, category trend analysis, dispute win rate, and a short narrative on what changed. Reporting that nobody reads is overhead; the rhythm matters more than the depth.
Want to see how this would look for your brand?
We'll walk through your current support stack, ticket categories, and tooling — and show you what an operationalized version looks like inside Zendesk, Gorgias, or Help Scout.