Calibrate sales-call reviews with the team
Review recorded sales conversations against a shared checklist and involve representatives in refining the criteria before using the results for coaching.
How this works
Review recorded sales conversations against a shared checklist and involve representatives in refining the criteria before using the results for coaching.
Calibrate judgments with sales staff before turning call analysis into coaching. Use observable behaviors and exact excerpts, allow disagreement and distinguish rubric uncertainty from a representative’s actual performance.
Before you start
Defined operating scope
Sales coaching uses recorded conversations and a rubric the team can challenge.
Required source material
Obtain Authorized call transcripts; Quality criteria; Examples of effective calls. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
A criterion cannot be observed in the available transcript. Mark not observable rather than assigning a failing score.
Prepare the inputs
- call_batch
- Required
Authorized transcripts and recording references
Sample the agreed period and call types.
- rubric
- Required
Behavior definitions and evidence rules
Avoid inferred emotions and vague personality labels.
- reference_calls
- Required
Reviewed examples
Record why each example meets or misses a criterion.
- review_assignments
- Required
Representatives and calibrators
Keep permitted access and dispute route explicit.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check call_batch, rubric, reference_calls, review_assignments before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected call_batch and any missing required fields.
Agree the quality checklist with sales representatives
- Agree observable criteria such as confirming next steps and exploring constraints, with positive and borderline examples.
- Ensure every judgment has contextual evidence and a valid rubric criterion.
Checkpoint: A saved intermediate result for: Agree the quality checklist with sales representatives.
Review calls over a consistent period
- Review calls consistently and attach excerpts to every judgment; use not observable when the transcript lacks evidence.
- Compare assistant and calibrated human judgments on ordinary and disputed examples.
Checkpoint: A saved intermediate result for: Review calls over a consistent period.
Compare recurring patterns and examples of stronger practice
- Compare patterns and stronger examples without treating a generated score as an objective ranking.
- Ensure every judgment has contextual evidence and a valid rubric criterion.
Checkpoint: A saved intermediate result for: Compare recurring patterns and examples of stronger practice.
Calibrate disputed judgments with the team and use findings for coaching
- Discuss disputed judgments with the team, revise unclear rubric language and select practical coaching actions.
- Compare assistant and calibrated human judgments on ordinary and disputed examples.
Checkpoint: A saved intermediate result for: Calibrate disputed judgments with the team and use findings for coaching.
Package the result and unresolved work
- Check transcript errors and context; do not treat inferred emotions or a generated score as an objective assessment of an employee.
- Use the output for reviewed coaching, not autonomous employment decisions.
Checkpoint: Evidence-linked coaching notes and a shared call-quality rubric. Unresolved items remain visible in the review record.
Decisions along the way
A criterion cannot be observed in the available transcript.
Mark not observable rather than assigning a failing score.
Human reviewers disagree on the same passage.
Record the disagreement and refine the criterion before using it for coaching.
A transcript error changes the apparent behavior.
Check the recording and correct the evidence before retaining the judgment.
What you will produce
sales-call-quality-calibration-result.json
JSONEvidence-linked coaching notes and a shared call-quality rubric. Label proposed and completed states separately.
Include: call_id · criterion · evidence_excerpt · judgment · review_disagreement · coaching_action · rubric_version · status · evidence_reference · review_note
sales-call-quality-calibration-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving review_assignments.
Include: source_reference · question · owner · next_action
Check the result
- Ensure every judgment has contextual evidence and a valid rubric criterion.
- Compare assistant and calibrated human judgments on ordinary and disputed examples.
- Inspect call_batch and rubric in both the original and output; confirm that record identity and interpretation survived the transformation.
- Check transcript errors and context; do not treat inferred emotions or a generated score as an objective assessment of an employee.
When something goes wrong
A criterion cannot be observed in the available transcript.
Mark not observable rather than assigning a failing score. Retain the affected evidence and recovery status.
Human reviewers disagree on the same passage.
Record the disagreement and refine the criterion before using it for coaching. Retain the affected evidence and recovery status.
A transcript error changes the apparent behavior.
Check the recording and correct the evidence before retaining the judgment. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Calibrate sales-call reviews with the team for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Rubric requires confirming an agreed next step. Transcript says 'I could send a demo'; the customer gives no response before the call ends.
Expected result
Synthetic expected result: Mark next-step agreement not demonstrated, with the exact exchange. Coaching suggests explicitly checking acceptance; do not infer laziness or poor intent.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure agreement with calibrated human reviewers; useful coaching actions accepted.
Stop or revise
A transcript error changes the apparent behavior. Pause affected records and apply this recovery: Check the recording and correct the evidence before retaining the judgment.
Keep the scope clear
- Use the output for reviewed coaching, not autonomous employment decisions.
- Limit call access to the authorized coaching audience and preserve a correction path.
Check before using
Check transcript errors and context; do not treat inferred emotions or a generated score as an objective assessment of an employee.
Business activities
- Run sales conversations and proposals
- Support and develop employees
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Authorized call transcripts · Quality criteria · Examples of effective calls
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow