QA Sampling Calculator

Calculate optimal review volumes to catch quality issues before they become problems

šŸ“Š Team Configuration

Team Size (Agents) 18

Total number of support agents across all channels

Avg Conversations/Agent/Week 50

Average tickets/chats handled per agent weekly

Target Quality Score 90%

Your goal QA score across all agents

QA Hours Available/Week 16

Total QA reviewer hours across your team

Avg Review Time (minutes) 8

Time to review and score one conversation

Confidence Level 95%

Statistical confidence for sample accuracy

šŸŽÆ
Reviews Per Agent Per Week
7

To maintain 14% sample coverage

Low Coverage Optimal High Coverage
šŸ“‹
Total Weekly Reviews
126

Across all agents

ā±ļø
Hours Required
16.8

Within capacity āœ“

šŸ“ˆ
Sampling Rate
14%

Of total conversations

šŸ”
Issue Detection
92%

Likelihood to catch issues

šŸ’” Your sampling rate is optimal for your team size

šŸ“Š Weekly Sample Coverage Visualization

Each square represents 1% of total conversations. Purple = Reviewed, Gray = Not reviewed.

Reviewed (14%)
Not Reviewed (86%)

šŸ‘„ Per-Agent Review Distribution

Recommended reviews per agent to maintain consistent coverage

šŸ“… Suggested Weekly QA Schedule

Day Reviews Focus Area Est. Time

šŸ’” QA Best Practices

šŸŽ²

Randomize Selection

Don't just pick the newest tickets. Use random sampling across the week to get an unbiased view of quality.

āš–ļø

Balance Channel Types

If you have chat and phone support, sample proportionally from each channel to catch channel-specific issues.

šŸ“Š

Track Trends, Not Just Scores

A single low score doesn't mean much. Look for patterns over 2-4 weeks to identify real coaching opportunities.

šŸŽÆ

Calibrate Regularly

Have all QA reviewers score the same ticket monthly to ensure scoring consistency across your team.

Built by Nova Codes