Judge

When someone says the answer was wrong, something has to decide — on the record.

What a ruling
actually rests on.

Three things, and a dispute needs all three: the evidence it is measured against, both sides being heard, and a consequence that follows.

What it stood on

AnswerDeposit is refundable up to 14 days before
CitedTerms of engagement · §4
Versionthe one live at 09:12

Not „the AI said so" — the passage it read, in the version it read.

It is judged on evidence, not on vibes

Every answer carries what it stood on: the passage from your own documents, in the version that was live at that moment. A dispute is decided against that record — not against what anyone remembers afterwards.

Who gets a say

The customersays the answer was wrong
Your teamsays the answer was fine
The judgereads both against the evidence

Both sides can object

A customer can say the answer was wrong. Your team can say it was right. Neither of them decides it alone, and neither of them has to argue with a support queue to be heard.

What follows

Receipt retracted
Removed from the solved count
Source corrected once
Never answered that way again

A ruling that changes nothing is an opinion. This one changes the count and the source.

A ruling has consequences

When an answer does not hold, it is retracted, it drops out of the solved count, and the document that caused it gets corrected — once, for every conversation that would have hit it next.

Every answer can be called into question.

Most systems make you take their word for it. This one hands over the evidence, lets either side object, and acts on what comes out of it.

Receipt #4192

„Deposit is refundable up to 14 days before the appointment."

based on Terms of engagement · §4

This is wrongLooks right

Anyone on the thread can object — no ticket, no queue.

Ready when the next call comes in.

Hear Klarium answer calls for your own business. Enter your website — Klarium reads it, sets up a phone assistant, and you call it a minute later.