Part 3 ended on the trade still sitting in the remaining cases. Magnitude and Pattern protect the money. Value at risk protects the relationship. When they fire together, they point in opposite directions. Here is a case of that shape.
Today the human exception owner weighs the two sides and picks one. On the morning shift she refunds. On the afternoon shift a colleague declines a case that looks the same. Nobody records which side won, or at what price.
Expert judgment drifts this way everywhere it has been measured. In Noise (2021), Daniel Kahneman, Olivier Sibony and Cass Sunstein describe an audit at an insurer: underwriters priced the same policies, and the median gap between two underwriters was 55%. Asked how much variation they expected, 828 senior executives gave a median answer of 10% (strategy+business). In the refund queue, the trade between margin and goodwill has no written rule at all.
Imagine the Monday review. The finance lead opens last week's goodwill credits and asks why so many were paid. The CX lead opens last week's detractors and asks why so many were refused. They are looking at the same queue, and neither has a record of the trade the exception owners actually made. That argument is the work. It is happening too late, and without the cases in front of them.
The human should keep this call. She needs a design that shows her the trade, records her answer, and keeps every other case away from her.
Split the triggers by what they protect
Part 2's five triggers fed one queue. Sort them by what each one protects and they fall into three groups.
Two AI managers, built to disagree
The AI money manager and the AI experience manager are AI models, but narrow ones. Each is a scoring model that reads tables, and neither reads the customer's message. Version one of each can be a set of rules on the Part 2 fields. What the design needs from them is separation.
The AI money manager reads order, billing and payment data: amounts, credits issued, chargebacks, device and card links, goodwill budget left. Its only goal is to lose less money to refunds, credits and abuse. It returns an objection or none, and the euros at stake if the company refunds.
The AI experience manager reads CRM and survey data: tenure, lifetime value, renewal date, recent NPS, open complaints. Its only goal is to lose fewer customers and create fewer detractors. It returns an objection or none, and the revenue at risk if the company declines.
Each has a human owner. Part 1's parameter owner splits in two. A finance owner sets the AI money manager's thresholds. A CX owner sets the AI experience manager's thresholds. Neither can change the other's.
The AI agent from Parts 1 to 3 still reads the message, does the plumbing, and applies the SOP when both managers are silent. It does not settle the money-versus-relationship trade.
Case B changes most. In Part 2 the Pattern trigger sent it to the human exception owner. Now nothing on the relationship side argues for the refund, so the decline is a lookup.
That lookup is the risk, and it is not limited to Case B. A decline leaves the money where it is, so a payment can still be reversed if the customer contests. Many refused customers do not contest. They leave. The reversibility of the cash is not the reversibility of the relationship. Case A from Part 2 can land in the same quiet cell: a first forgotten trial, no Pattern, no Value at risk, and an SOP that says the annual plan is non-refundable. Correct by policy, and gone from the queue. Part 2's audit sample has to watch the auto-declines, not only the refunds — a random sample of declined cases, read by a human, and whether those customers renew or churn. A decline the audit would have reversed is a trigger you do not have yet.
A case needs a human when two legitimate goals point in opposite directions. When only one goal has a stake, the answer is a lookup.
This is also the cleanest way to apply Part 3's yield rule. Cases flagged by one side with nothing on the other no longer reach the human. The queue holds only cases where a careful human could go either way.
You can measure the cut before you make it. Take a sample of cases that today reach the human exception owner, and tag each one: money trigger only, relationship trigger only, both, or a hard stop. The share that is both, plus the hard stops, is the queue this design would leave you. If that share is small, the human's time is already being spent on lookups. If it is large, the trade was already the job, and it was invisible.
Why these two do not share the AI supervisor's blind spot
Part 2 rejected the AI supervisor because it read the same message and lacked the same history as the AI agent, so their errors lined up. The evidence for that has grown. Elliot Kim, Avi Garg, Kenny Peng and Nikhil Garg compared more than 350 language models on two public leaderboards (ICML 2025). On one leaderboard dataset, when two models both got a question wrong, they gave the same wrong answer 60% of the time. Shared providers and architectures raised the overlap, and so did larger, more accurate models, even across providers. A stronger AI supervisor does not escape the problem.
The two AI managers differ from that AI supervisor in three ways. First, they read different data. The AI money manager never sees lifetime value or NPS, and the AI experience manager never sees chargebacks. A missing fact in one set of tables does not repeat in the other. Second, they want opposite outcomes. One looks for reasons to decline, the other for reasons to refund. A check that wants the same result as the thing it checks will tend to confirm it. Third, neither one judges the other. The design asks only where they split, and sends the split to a human.
That changes what agreement means. When the manager hunting for reasons to decline finds none, and the one hunting for reasons to refund finds none, the case is ordinary for two separate reasons.
When they would share it
Independence is a property of the build. Four shortcuts destroy it, and each one is tempting.
Part 2's random audit sample now has a sharper target. Disagreements already reach a human. Shared blind spots show up only where the managers agree — the auto-refunds and, especially, the auto-declines.
The screen and the numbers
Both prices appear in euros, so the trade is explicit. No button is pre-filled, because a default side is a vote. Every answer becomes a data point: this human, on this case, gave up this much margin to protect this much revenue.
The finance owner and the CX owner read that log together every week. When finance wants a tighter threshold after a loss, the log shows how many disagreements the change adds.
A low disagreement rate is a prompt to investigate, not a verdict. Shared fields can suppress it, and so can two loose thresholds, or a week with fewer customers who are both expensive and valuable.
What this costs you
First, you get two owners who will argue, every week. That argument used to happen silently in one human's head. Now it happens in a meeting, with cases and prices, where someone can check it.
Second, the data split is real work. Lifetime value often includes refund history, and fraud scores often include tenure. Untangling them is a data project before it is an AI project.
Third, finance usually outranks CX. If the finance owner can tighten after every loss and the CX owner needs a business case to loosen, the AI money manager slowly becomes a veto with a human signature on it. Give both owners the same rule: no threshold change without the disagreement-rate effect on the table.
What comes next
Every time a human exception owner refunds €420 to protect a €1,200 renewal, she puts a price on that customer's goodwill. Another owner on another shift puts a different price on it. After a quarter, the log will hold those prices. Whether they settle into a rate you can trust is another matter. Disagreement cases are few, and they are not all the same trade. A handful of mixed cases is a start, not an exchange rate.
The thresholds were a price all along. The finance owner says a refund is worth an objection above some amount. The CX owner says a decline is worth an objection above some revenue at risk. The ratio between the two thresholds is an exchange rate between euros and the relationship. Change either one and you reprice your customers.
Write that rate down, and lopsided disagreements can start to resolve themselves. A quarter of mixed cases may not be enough to set it. Gathering that number, and being honest about when you do not have it yet, is the work this series has been circling since the intro: how many euros one unhappy customer is worth.
That is Part 5.