Templates

Four scorecards to start from

Sensible starting points with the weights and severities already set. Download as JSON that imports directly, or as CSV for the spreadsheet you have now.

Customer support

Inbound service calls: verification, acknowledgement before resolution, and clear next steps.

The two parameters that most often need changing are the disclosure, which depends on your jurisdiction, and the resolution weight, which should be higher on a team measured on FCR.

support-scorecard.json6 params
Recording disclosure20%ZTP
Identity verification15%Fatal
Problem acknowledged before solving15%Non-Fatal
Correct resolution offered25%Fatal
Next steps and timeline stated15%Non-Fatal
Tone and pace10%Non-Fatal

Sales floor

Outbound and inbound sales: discovery before pitching, real objection handling, an agreed next step.

Discovery is weighted as Fatal on purpose: a pitch delivered before the need is understood is the failure mode this scorecard exists to catch. Lower it if your product genuinely is a one-call close.

sales-scorecard.json6 params
Discovery before pitching20%Fatal
Qualification questions asked20%Non-Fatal
Objection handled, not deflected20%Non-Fatal
Mandatory statements read20%ZTP
Clear next step agreed15%Fatal
Talk-to-listen within range5%Non-Fatal

Collections & recovery

Recovery calls where the mandatory statements matter more than the tone.

Three zero-tolerance parameters is more than most scorecards should carry, and it is deliberate here. Replace "No prohibited language" with the specific list your own regime defines. We do not know what that is for you, and this template does not assert it.

collections-scorecard.json6 params
Identity and mini-disclosure25%ZTP
Recording disclosure15%ZTP
No prohibited language20%ZTP
Dispute logged, not argued15%Fatal
Payment terms stated accurately15%Fatal
Professional tone under pressure10%Non-Fatal

Compliance-only

A short scorecard for teams that want assurance on the mandatory parts and nothing else.

Useful as a second scorecard rather than a replacement. Run it across everything, and run a fuller quality scorecard on a sample. Every parameter here is pass or fail by design; there is nothing subjective to disagree about.

compliance-scorecard.json4 params
Recording disclosure25%ZTP
Consent captured before processing25%ZTP
Identity verified to policy25%Fatal
Required closing statement25%ZTP

These are starting points, not compliance instruments

A template cannot know which statements your regulator requires, which disclosures your legal team has approved, or what your clients contracted for. The collections set in particular has a placeholder where your own prohibited-language list belongs.

Use them to skip the blank page, then make them yours.

Score a call against one

Import a template, upload a recording, and see what comes back.