Call disposition codes are the bridge between a conversation and the next controlled action. If agents use overlapping labels, free text, or convenient shortcuts, the agency cannot reliably suppress a wrong number, honor a preference, schedule a promise follow-up, measure contact quality, or explain why an account changed state. A useful taxonomy is small enough to use and precise enough to drive workflow.

This framework is educational, not legal advice. Required records and actions depend on applicable law, client agreements, agency policy, debt type, and the substance of the communication.

Separate connection from business outcome

First record what happened to the call: not connected, connected to an unverified person, connected to the consumer or another person authorized for the purpose, transferred, disconnected, or failed technically. Then record the business outcome, such as dispute, promise, payment request, complaint, cease instruction, or follow-up needed.

A single code such as contacted hides whether identity was verified and whether the conversation created a legal or operational obligation. Use two controlled dimensions when one flat list would combine unrelated facts.

Create a minimum viable taxonomy

Define each code with inclusion, exclusion, required fields, and examples. Avoid duplicate concepts such as left message, voicemail, and machine unless they lead to materially different treatment.

• no answer, busy, carrier failure, or voicemail reached;
• wrong number, reassigned number, or identity uncertain;
• consumer reached but not fully verified;
• verified consumer conversation with no commitment;
• promise to pay, settlement discussion, or payment completed;
• dispute, complaint, fraud or identity-theft claim;
• cease, channel restriction, inconvenient time or place, or attorney notice;
• bankruptcy, deceased, paid, recalled, or other account-status evidence;
• scheduled callback, supervisor escalation, or documentation request.

Attach mandatory follow-up data

A disposition should prompt only the fields necessary for its outcome. A scheduled callback needs a date, time zone, permitted number, and owner. A promise needs amount, date, method or next step, and the authority governing any terms. A wrong-number report needs the number and suppression scope, not a narrative containing unnecessary personal details.

Use structured reasons for disputes, complaints, and restrictions while preserving a controlled note for context. Free text should supplement, not replace, the actionable record.

Map every code to system behavior

The CFPB's communication rule and official interpretations address consumer restrictions, inconvenient communications, and specified channels. A disposition capturing those facts should update the centralized communication preference ledger before another workflow can contact the person.

• account state or hold;
• number-level or channel-level suppression;
• next task, due date, and owner;
• frequency-counter treatment;
• script or workflow branch;
• supervisor, compliance, client, or legal notification;
• required evidence and retention class.

Prevent agent shortcuts

Make common valid codes easy to find, but do not default to a successful outcome. Require confirmation for high-impact codes, validate required fields, and restrict overrides. Review rapid repeated dispositions, unusually high unknown or other use, outcomes completed without call evidence, and notes that conflict with the selected code.

Train with examples and counterexamples. Calibration should include operations, compliance, quality, and system owners so the same conversation produces the same code and downstream action across teams.

Measure reliability, not just volume

Audit disposition accuracy against a risk-based sample of recordings or other approved evidence, building on the call quality assurance framework. Track corrections, missing required fields, time to disposition, workflow failures, suppression latency, and outcomes that remain unresolved.

Version the taxonomy and mapping. When a code changes meaning, preserve the historical definition instead of applying today's interpretation to yesterday's data.

Conclusion

A disposition taxonomy should faithfully record the connection, the business outcome, and the required next action. Keep definitions controlled, map each outcome to workflow, block ambiguous shortcuts, and measure coding accuracy over time. Kaizen's centralized account visibility and auto-logging workflow can be assessed against that design.

Frequently asked questions

How many disposition codes should a collection team use?

Use the smallest controlled set that produces every materially different follow-up, restriction, measurement, and evidence requirement. Add detail through structured subreasons where necessary.

Should agents be allowed to edit a disposition?

Corrections may be necessary, but preserve the original value, editor, reason, timestamp, and downstream changes. High-impact corrections should require approval.