Disposition

What it means

A disposition is the outcome code an agent attaches to a record at the end of a call. Every dialler and every intake system has a list of them, and the list is short on purpose: no answer, busy, voicemail left, wrong number, not the owner, not interested, callback requested, appointment booked, and a handful of local variations on those.

The code is not a note. A note is prose that a human reads if they happen to open the record; a disposition is structured data that machinery reads without anyone opening anything. It decides whether the record is dialled again, when it is dialled, which list it moves to, and whether it is counted as reached. It is also the only account of the call that survives, because the conversation itself is not stored anywhere a report can read.

Every downstream rate is counted from it

This is the part that is easy to miss on the floor, and it is the whole reason the code matters more than it looks.

Contact rate is dispositions. Right party contact is dispositions. Booking rate, show rate, the share of a list still workable, the hour of day that reaches people, the performance of one list against another: all of them are counted by grouping disposition codes and dividing. None of them reads the call. None of them can tell that the code is wrong.

So a miscoded call does not produce a wrong entry in one report. It produces a consistent, quiet error in every report that touches the record, in the same direction, for as long as the record exists.

Why careless coding is invisible

A wrong disposition breaks nothing. There is no error, no alert, no failed validation and no complaint from anybody. The record simply goes on to be counted as something it was not.

Consider the two most tempting shortcuts. Coding a callback as a no answer makes the record look untouched, so it goes back into general rotation and the promise made on the call is quietly dropped. Coding a conversation with somebody else in the household as a contact makes the reach numbers look healthier than they are, which flatters the dialling and hides the list problem underneath it.

Both of those feel harmless in the second they happen. Both are undetectable afterwards, because the only evidence that the code was wrong was the conversation, and the conversation is gone.

Reading a disposition report properly

The first question to ask of any disposition report is not which code is largest. It is how many distinct codes are genuinely in use.

A team leaning on a handful of codes out of a much longer list is not a team with simple calls. It is a team that has settled on the quickest options, and every figure resting on that list is measuring habit rather than outcome. The same goes for a code that swallows an implausible share of the volume: it is usually the default one, the one already selected when the screen opens, or the one at the top of the list.

Codes that ought to appear and do not are the other signal. A storm list that records no wrong numbers and no dead lines is not a clean list; it is a list whose bad records are being filed as something else, and it will be dialled again and again at full cost.

Common mistakes

Leaving dispositions until the end of the shift. Nobody reconstructs a whole shift of calls accurately from memory, and the codes entered in the closing minutes of a day are the ones that are most uniform and least true.

Treating a neutral code as the safe choice. There is no neutral code. Every one of them is an assertion about what happened, and the harmless-looking ones are harmless precisely because nobody audits them.

Changing the code list without deciding what happens to the history. Renaming or merging codes rewrites the meaning of every report that spans the change, and a trend line that crosses it is comparing two different questions.

Judging an agent on dispositions they enter themselves without ever listening to the calls behind them. That measures coding, not calling, and it rewards the agent who codes generously over the agent who codes honestly.