← Exercises|

Knowing when to hand it to a person

Write22 of 26 · about 9 min

Knowing when to hand it to a person

Tom Brennan, five months in, will stop looking at a suggestion that is wrong twice. That is not impatience: a suggestion he cannot trust costs him more than no suggestion, because he has to check it anyway.

So the system needs to be allowed to say nothing. Routing a low-confidence case to a human is not a failure of the model, it is the feature that makes the rest of the output usable.

The threshold is a product decision with a measurable consequence, and it belongs in the charter, not in a constant somebody picked. Choosing it means deciding what a wrong routing costs compared to a human glance.

Example

if confidence >= THRESHOLD and queue in QUEUES:
    return "route", queue
return "human", "below the threshold agreed in the charter"

The reason travels with the decision. "Warranty, 87%" told Tom nothing; "below the threshold" tells him what happened.

Your task

Write decide(case, threshold) returning a tuple (action, detail). Route only when the queue is known AND the confidence is at or above the threshold; otherwise hand to a human with a reason. Then print the decisions at a threshold of 0.75, and the share of cases routed, as a percentage with no decimals.

Stuck?

Explain it

The sponsor wants the routed share higher. What do you need to know before lowering the threshold?

Not graded — this is for you.

Where this goes

D4 requires the threshold to be stated in the charter and justified with measured numbers, and D7 produces the curve that justifies it.