FLEETX · AI FLEET MANAGEMENT OS
Contracts become rules. Rules govern every case, clock and approval, with every decision on the record.
Download the product overview (PDF)A fleet contract fixes service intervals, response times and who pays for what. It then goes into a folder, and the operation runs on what people remember of it. An agent takes a breakdown call without knowing which contract governs the vehicle. A repair gets authorised above the limit that applies. An SLA clock runs over a weekend nobody agreed to count, and the breach only surfaces in the monthly report, when the argument is already lost.
What the contract commits you to sits in a document. What the call centre does sits in a case tool. Nothing reconciles the two while the case is still open.
Whether this person can approve this amount is a question answered by whoever is on the phone, and it is answered again from scratch every time.
Elapsed time and working time are not the same. Measured against the wrong calendar, a two-hour response target quietly consumes a weekend.
Service intervals, SLA targets and authorisation limits are extracted from the signed agreement with citations back to the clause they came from, so the rule can be traced to the paper.
Nothing extracted governs a live case until someone reviews and activates it. Rules are versioned and carry effective periods and precedence, so you can see which one applied on the day.
Customers, contracts, vehicles and rate cards in one place, so a call-centre agent finds any vehicle by registration, VIN or customer in seconds and sees the contract and rate card that apply to it.
Working hours and public holidays, pause segments and threshold alerts. Turnaround time and SLA time are tracked separately, because a customer who waited over a weekend waited over a weekend.
Ownership transfers on handover as a record rather than an edited field, and a resolution is proposed by the owner and then accepted or disputed by the requester. A disputed resolution keeps both versions.
Customer approval limits tied to each role, with the authority above them named. Supplier work inside the agreed threshold authorises straight through, and partial cover always shows what the customer is being asked to pay.
All three sit inside one FleetX tenant and see different things, enforced at the database rather than by hiding fields on a screen. Every material action any of them takes is written to a record none of them can edit.
Internal staff see every customer, contract, vehicle, case and supplier in their organisation, because somebody has to hold the whole picture.
Their vehicles, their contracts, their approval limit and the name of the authority above it, and one decision to approve or dispute a resolution.
A governed portal instead of an inbox: vehicle verification, rate lookup and authorisation, with the minimum operational detail needed. Never the contract, never the margin.
Approvals and material actions are recorded for oversight, and the party being audited cannot read the trail back. Fail closed in both directions.
Personal and operational data handled lawfully
Every capability mapped to a specified requirement
Material actions recorded and not editable
Information Security Management
Asset Management
Isolation enforced at the database, in both directions
FleetX runs on the same rails as every other module: single sign-on, per-tenant isolation enforced at the database, and the shared audit and notification services. Every capability traces back to the functional and business requirements it was specified against.
The same contract intelligence that reviews an agreement before signature feeds the rules that govern the operation after it.
Slipping SLA clocks, exceptions and authorisation patterns join the operating picture, where they can be read against everything else the business runs.
Breakdown calls, driver contact and customer approval requests reach people on the channel they actually answer.
Any vehicle and its obligations found in seconds, with the contract that governs it already on the screen.
Which clocks are running, which are breached, which cases need a manager today, and what the month actually looks like.
Their own fleet, their own limit, and an approval or dispute that takes one decision rather than a phone call.
A governed quote and straight-through authorisation for work inside threshold, instead of waiting on somebody to answer an email.
We take a signed fleet contract through extraction and review, activate the rules it implies, and run one depot's cases against them. From there you can see, on your own paper, what the contract commits you to and where the operation is drifting from it.
Contracts become rules. Rules become governed action.
Service intervals, SLA targets and authorisation limits extracted with citations, then reviewed and activated by your people.
Customers, contracts, vehicles and rate cards imported, so a lookup answers with the right contract from day one.
Cases on working-calendar SLA clocks, with approvals and supplier authorisation inside the limits the contract set.
FLEETX · AI FLEET MANAGEMENT OS