How QA Scoring Works
NeuronLens reads the full transcript of a call and evaluates it against your scorecard parameters. Each parameter is scored individually — binary (yes/no), on a numeric scale (0–10), or via keyword-presence detection — and the weighted scores combine into an overall call score between 0 and 100. You receive a score and an explanation for each parameter, not just a number.Binary Parameters
Yes/no checks: did the agent do this thing or not? Best for mandatory steps like opening greeting, required disclosure, or call close.
Scale Parameters
A 0–10 score with model-generated reasoning. Best for subjective quality dimensions like empathy, product knowledge, or objection handling.
Keyword Presence
Checks whether specific required phrases or terms appeared in the transcript. Best for compliance-adjacent disclosures and regulatory language.
Weighted Aggregation
Assign a weight to each parameter so critical items (like regulatory disclosure) carry more impact than optional best-practice items.
Configuring a QA Scorecard
You set up scorecards in the NeuronLens dashboard or via API. Each scorecard is reusable across campaigns and agent teams.Open the Scorecard Builder
Navigate to NeuronLens → QA → Scorecards → New Scorecard in your dashboard.
Name and Scope Your Scorecard
Give the scorecard a name (e.g., “BFSI Collections – Standard”) and optionally assign it to specific campaigns or agent groups so it applies automatically to matching calls.
Add Parameters
For each quality criterion, set a name, a description (used by the model to interpret the call), a scoring method (binary / scale / keyword), and a weight (1–10). Add as many parameters as you need.
Example QA scorecard parameters — BFSI collections call
Example QA scorecard parameters — BFSI collections call
The following parameters are representative of a scorecard for a collections call in the BFSI sector. Adjust weights and scoring methods to match your quality standards and regulatory requirements.
| # | Parameter | Scoring Method | Weight | Description |
|---|---|---|---|---|
| 1 | Proper opening greeting | Binary | 7 | Did the agent greet the customer by name and identify themselves and the organisation at the start of the call? |
| 2 | Disclosed purpose of call | Binary | 9 | Did the agent clearly state the reason for the call — specifically, the outstanding loan or EMI — within the first 90 seconds? |
| 3 | Correctly stated outstanding amount | Keyword + Scale | 10 | Did the agent mention the exact outstanding amount, due date, and account reference? Scored on accuracy and clarity. |
| 4 | Offered payment options | Binary | 8 | Did the agent proactively mention at least two payment methods (e.g., UPI, bank transfer, payment link via SMS)? |
| 5 | Compliance with RBI guidelines | Binary | 10 | Did the agent avoid prohibited language — no threats, no contact with third parties, no calls outside permitted hours? |
| 6 | Professional call close | Scale (0–10) | 6 | Did the agent summarise the agreed next step, confirm the customer understood, and close the call courteously? |
Fetching QA Scores via API
Single Call
Response
Weighted aggregate QA score for the call, on a 0–100 scale.
Whether the call met your scorecard’s minimum passing threshold (configurable per scorecard).
Array of individual parameter results. Each entry includes the parameter name, scoring method, weight, raw score, pass/fail flag, and a natural-language explanation of how the score was determined.
Bulk QA Scoring
Submit a batch of calls for QA scoring and receive results via webhook or polling:batch_id.
Agent Leaderboards
QA scores aggregate automatically into per-agent leaderboards in the NeuronLens dashboard under QA → Leaderboards. For each agent you see:- Average overall QA score for the selected period
- Score trend (up or down vs. previous period)
- Pass rate (percentage of calls meeting the minimum threshold)
- Weakest parameter — the single criterion where the agent scores lowest on average
- Number of calls scored
QA scoring requires transcription to be enabled for the call. When you submit recordings via the API, include
"transcription" in the features array. Without a transcript, NeuronLens cannot evaluate scorecard parameters and the call will be skipped during scoring.QA Scoring API Reference
The unique call identifier returned when the transcription job completed.
The scorecard to apply. If omitted, NeuronLens uses the default scorecard assigned to the campaign this call belongs to.
Filter bulk QA requests to calls processed after this date (
YYYY-MM-DD).Filter bulk QA requests to calls processed before this date (
YYYY-MM-DD).Filter results to a single agent’s calls.