Home / In-house dispute teams
On your own rulebook
Settle customer and counterparty disputes in-house
Disputes with customers and business counterparties arrive in volume, through the channels your teams already work in. SpyroLex opens the case where the request lands and reads it against your own rulebook, so a named person can settle it before it reaches court or an outside forum. Most of this work never needed a lawyer.
Based on our research
Most disputes were never going to need a courtroom
We studied a large body of public dispute records. The same pattern holds across them: most disputes settle, few are ever heard, and the ones that reach an outside forum take the best part of a year, and a lawyer, to get there.
- of disputes end in a settlement, not a ruling
- 6 in 10
- resolve without ever reaching a hearing
- 9 in 10
- median time to resolve once a dispute reaches an outside forum
- 11 months
- of claimants arrive already represented by a lawyer
- 87%
Based on our analysis of public dispute records, 2013 to 2026. Figures are directional.
How it helps
The judgment stays in the building, and the record stays with the case
Your rulebook is the ground
SpyroLex runs each dispute on your own positions: the terms and the steps your team already settles these cases by. It reads the dispute against that rulebook and drafts where you stand.
The decision comes ready for a named owner
The case reaches one named person with the position drafted and the next step proposed. They approve it or change it, and the decision is theirs. SpyroLex never sends anything by itself.
A record of what was decided
What SpyroLex proposed and what the person decided are kept as separate entries, attributed and timestamped. If a customer escalates or a counterparty challenges the outcome, the whole case is there to show.
Where the dispute arrives
Pick up the case where the work already lands
A dispute arrives through Slack, Teams, Outlook or Gmail, and SpyroLex opens the case with whatever came attached. Your team works where it already works, and nothing has to be re-entered in another window.
- Slack
- Teams
- Outlook
- Gmail
One case, one record
Every dispute connects back to one record
The case is read against your rulebook and both sides, and a named owner decides. All of it stays on one record you can produce.
Where it runs in-house
The desks that resolve disputes in-house
Airlines and travel
Flight disruption and baggage claims arrive in volume and against the clock. SpyroLex reads each one against your conditions of carriage, and the owner on the desk decides what to pay.
E-commerce and marketplaces
Buyer and seller disputes and payment claims pile up across a marketplace. Your trust-and-safety team gets each case opened on your marketplace policy, with the call between the two sides already drafted.
Universities and education
Student appeals and conduct cases run on procedures you publish and deadlines you have to keep. SpyroLex prepares each one against your own regulations, and a named person in your office signs it.
B2B platforms and suppliers
Contract and SaaS disputes between businesses turn on the agreement and the service terms. The account or legal owner gets the claim read against your contract and a position drafted, ready to decide what to offer.
Some of these we have built against and some are ahead of us, and a working session is the honest place to find out which is which for your own case types.
If it escalates
The dispute handled in-house is the one nobody has to rebuild later
See what the record keepsConfidentiality
Your data terms, in writing, before any agreement
The full security architecture goes to your team in writing before go-live, and the terms are settled with your counsel rather than presented on a slide.
Restricted per organisation
Each organisation sees only its own cases, and traffic is encrypted in transit.
The model has no write path
The model suggests and never writes the record. Anything that enters the file is entered by a named person.
An append-only record
Case actions are logged with the user and the time, in an append-only record, so later changes are detectable.
Yours to export
Export any case, or all of them, in open formats, as a term of your contract.
Hosting, residency, source code in escrow, and how your cases may be used, by any AI model or anyone else, are written into the contract.
Questions in-house teams ask first
How does a dispute get into SpyroLex?
It arrives where your team already works. A dispute comes in through Slack, Teams, Outlook or Gmail, and SpyroLex opens the case with whatever came attached. Your people do not move to another window to start it.
Does SpyroLex decide the dispute?
No. It prepares the case and brings it to a named owner with the position drafted and the next step proposed. That person approves it or changes it, and the decision is theirs. What SpyroLex proposed and what the person decided are kept as separate entries on the record.
How is this different from our CRM or ticketing system?
A CRM or a ticket queue holds the case and moves it along. SpyroLex runs your own rulebook on the case and drafts the position from the file. It keeps a record that shows a named person decided. The difference shows when the outcome is challenged and someone asks to see how it was handled.
Is this only for the legal team?
No. SpyroLex runs wherever disputes are resolved: the customer-care desk, the grievance or conduct team, trust-and-safety, and in-house counsel. The rulebook is configured to how each team already decides, so the right owner keeps the case.
Further readingHow courts and lawyers use AI, and how the law regulates itChoosing AI legal tools: what the rules requireWhat the record keeps, and why it holds
See alsoCatch disputes before they escalateSectors we work inHow a first session works
See it run on your own disputes
Book a working sessionBring your own rulebook and the disputes you handle today, and we will run SpyroLex on your own cases.