Skip to content

PCA analytics

PCA analytics answers the questions supervisors ask every week:

  • How many calls did we analyze?
  • Is average quality going up or down?
  • What share is good vs poor?
  • Which tags fire most often?

Numbers update as analyses complete (and are easy to read after a nightly intake run). This is trend-level insight — for a single call, use Analyzed records.

  • Inside a Call Analyzer project → Analytics, or
  • Org Analytics with a Call Analyzer project selected

When the selected project is a Call Analyzer project, CXGear shows PCA metrics instead of outreach funnel charts.

Screenshot needed
PCA analytics header with period selector and metric cards.
Where: Call Analyzer project → Analytics
Save as: src/assets/screenshots/53-pca-analytics.png
MetricMeaning
Calls analyzedHow many calls completed analysis in the period
Avg QA scoreAverage numeric score across those calls
Good / Fair / PoorCounts in each grade band

These cards are the “health check” at a glance.

A day-by-day bar view of how many calls were analyzed (often with average score on the day). Use it to spot:

  • Missing nights (schedule or runtime issues)
  • Spikes after a campaign weekend
  • Gradual volume growth as more recordings land
Screenshot needed
Daily volume bars for analyzed calls.
Where: Call Analyzer project → Analytics → Daily volume
Save as: src/assets/screenshots/54-pca-analytics-daily.png

Tags ranked by how often they matched. This is your coaching backlog in chart form:

  • High “prohibited phrase” hits → urgent training
  • Low “disclosure read” hits → script reinforcement
  • Unexpected extract values → prompt tuning on GenAI tags
Screenshot needed
Top tags list with relative bar widths and counts.
Where: Call Analyzer project → Analytics → Top tags
Save as: src/assets/screenshots/55-pca-analytics-tags.png

Choose a reporting window:

PeriodWindow
Last 7 daysWeek-over-week coaching
Last 30 daysMonthly quality review
Last 90 daysQuarterly trend

Pick a period that matches your operating rhythm. Short windows are noisy when volume is low.

AnalyticsRecords
GrainAggregatesOne call
JobTrends and mixCoaching and audit
WhenWeekly / monthly reviewsDaily desk work

Analytics is built from daily rollups as calls finish analysis. If Records has calls but Analytics is empty, wait for rollup after successful analysis or confirm the period includes those days.

  1. Intake spinner analyzes a call.
  2. Score, grade, and tag results are stored on the analysis.
  3. CXGear updates a daily rollup (call count, average score, grade counts, tag hits).
  4. Analytics reads those rollups for the selected period.

No separate “export to BI” step is required for the built-in views.

  • After nightly intake, morning analytics reflects yesterday’s volume.
  • Grade mix matches what supervisors see sampling Records.
  • Top tags align with known script issues.
  • Empty state only appears for brand-new projects (with a clear “upload recordings / wait for overnight run” message).
SymptomLikely causeWhat to try
All zerosNo analyses in periodRun intake; widen period
Volume flatlined mid-weekSchedule or runtime stoppedCheck runtime and spinner schedule
Avg score looks wrongScorecard or band changeRemember history is snapshot-based; new calls use new card
Top tags emptyNo matching tags or tags not configuredConfigure tags; confirm they match on Records
Outreach-style charts shownWrong project type selectedSelect a Call Analyzer project
Permission deniedRole lacks analytics readAssign Supervisor / Admin or grant permission

A simple weekly rhythm:

  1. Analytics — grade mix and top tags for the week.
  2. Records — open a sample of poor-grade calls.
  3. Tags / QA — adjust keywords, prompts, or questions if the model is wrong.
  4. Coaching — train agents on real patterns, not anecdotes alone.
  5. Re-check analytics the following week.

CXGear’s Post Call Analyzer is meant to scale listening — analytics is how you know the system is changing outcomes, not only producing scores.