For claims and compliance teams
An AI tool handled the claim. Who is responsible if it got it wrong?
When AI reads a complaint, summarises a document or routes a case, you carry the liability for what it did. Your own system logs are written by the system being questioned. Metrecept gives you a record that a regulator, an Ombudsman or a customer can check for themselves, without asking you and without an account.
Things that go wrong, and what you can show
A complaint misread
What went wrong
An AI tool summarised a customer complaint and left out the amount in dispute. The handler acted on the summary. Weeks later the customer says you ignored them.
What your auditor sees with Metrecept
A signed record of the complaint that arrived, the summary produced, and the time. You can show exactly what the handler was given.
A figure that did not match
What went wrong
An AI tool read a repair estimate and the figure did not match the claim form. Nobody can say which one the tool actually saw.
What your auditor sees with Metrecept
A signed record of the document that was read and what came out. The mismatch can be traced to its source in minutes.
An out-of-date source
What went wrong
An AI tool pulled guidance from a web page that had since changed. A decision was made on it.
What your auditor sees with Metrecept
A signed record of the page fetched, when, and what it said at that moment. The page can change; the record cannot.
A log that disappeared
What went wrong
An old database script was reused and wiped most of the record of who had viewed sensitive customer files. Nobody could say who had seen what, and the regulator had to be told.
What your auditor sees with Metrecept
A signed record of each access, made when it happened and kept outside the system. A wiped database cannot erase it.
A reported figure nobody could trace
What went wrong
A regulator asked where a reported number came from. The data had been pulled, adjusted and checked by different tools, and nobody could show which version fed the report.
What your auditor sees with Metrecept
A signed record of each step from source data to the submitted figure, so the number can be traced back and checked by anyone.
Carve: every complaint, sorted on arrival
Carve turns each complaint, in any length and six languages, into the facts a handler needs: who, what happened, how much, by when. It then sends the case to the right desk. On 1,039 test tickets it chose the right desk 83.7% of the time, in about 2 milliseconds per complaint. If a complaint is too vague to route, Carve asks the customer for more detail before it reaches a person. If the customer is angry, it sends a message of understanding while routing the case to a person at the same time. Every decision gets a signed record, so you can show what arrived and where it went.
The Paid Enterprise Pilot: £3,500 fixed, four weeks, 1,000 Case Envelopes
On your own complaints. Each case is opened as a £3.50 envelope at Bias and carried: the carve, up to five documents, ten custody receipts and two fetches bill 0p inside the allowance. The charge is the charge of the crossing. There is no second price.
Week 1
Connect
We point your complaints inbox or form at Carve and map it to your desks. A data-processing agreement is signed first.
Weeks 2 and 3
Run live
Every real complaint is restructured into a short set of facts and sent to the right desk. Each one gets a signed record.
Week 4
Decide
We report accuracy by desk and the time saved per case. Keep it running, or stop and receive a signed record of deletion.
Verifiable evidence, or your money back.
If a single record fails to check against our published keys, you get every penny of your Enterprise fee back. Hosted in the UK.