FleetPro plan
Every machine you service, on file.
Fleet is the record behind the work: one page per machine, its readings, its manuals, its chats, and one timeline holding the faults, the repairs and the services. Plan the maintenance by months, kilometres or engine hours, and Lyxter mails you before the work comes due.
An illustration of the Fleet list: four machines, each with its make, model and year, its latest odometer or engine-hours reading, and its service status - overdue, due soon, or waiting on a reading - above a short history for one of them.
What Fleet does.
Six things, all of them the ordinary work of keeping other people's machines running.
- A page per machine
- Make, model, year and specs, the odometer or the engine hours, the machine's own manuals, its chats, and one timeline holding the faults, the repairs and the services with what they cost.
- Plans on the axis that matters
- Set an interval in months, in kilometres, in engine hours, or all three on one plan. The tightest axis wins, so the truck that stands still all winter and the one that never stops both come up when they actually should.
- A reminder before it is a problem
- Lyxter checks the plans through the day and emails the address you set under Company the first time a service crosses into due soon, and again the first time it crosses into overdue. Finish the work and it stops. The same crossing never mails you twice.
- A list that counts what needs you
- How many machines are down, how many need attention, how many have a service due. Every machine carries its latest reading and its worst plan status, so the list is the morning briefing.
- The machine behind every answer
- Link a chat to a machine and the AI works with that record open: what the machine is, what your workshop already found on it, and any service that is due or overdue, even when you are asking about something else.
- Who can change what
- Any mechanic can upload a manual to a machine and work in its chats. Adding or editing a machine is the owner's or an admin's; deleting one is the owner's alone.
Fleet is part of Pro, with up to 25 of your own machines included. A customer's vehicle created inside a service job does not count against that. Bigger fleet? Tell us the size at hello@lyxter.ai.
Service status
Four states, and the rule behind each.
A status is only worth reading if you know what makes it change. These are the rules Lyxter actually applies, on every plan, every time it looks.
- Overdue
The interval has run out on at least one axis: the date has passed, the kilometres are up, or the engine hours are.
- Due soon
Inside the last tenth of the interval, and never a shorter warning than 14 days, 500 km or 25 engine hours, so a short interval still warns you a useful distance out.
- On plan
Nothing to do. A machine that is on plan carries no badge at all, so the list only shows you what is asking for something.
- Needs a reading
The plan cannot be worked out, because the odometer or the hours have not been logged. Lyxter says so rather than showing the machine as healthy.
A plan can run on several axes at once. The worst one wins, so a machine is never reported as fine because one of its three intervals still has room.
In a linked chat
The machine turns up in the answer.
A record nobody reads is filing. The point of keeping the machine on file is that the diagnosis changes when the AI knows which machine it is looking at.
It knows what the machine is.
Register it once with its make, model and year and Lyxter works out what that machine is a single time: electronically managed or not, the engine and emissions options for that year, and what varies between units. Every later chat on it starts from that.
It knows what you already found.
The AI searches your own earlier chats and your own recorded cases on that machine, and answers with what your workshop found before. Only ever your company's work, never another workshop's.
It knows what is due.
A service that is due soon or overdue on the machine sits in front of the AI while it works an unrelated fault, so it can tell you the oil service is 2 000 km past while you are chasing a sensor.
A chat with no machine on it gets the answers a stranger would. Linking one is a tap, at the start of the chat or halfway through.
One loop
Three products, one record per machine.
What one records, the next already knows.
- DiagnosticsLyxter reads the fault and names the likely cause.Open Diagnostics →
- FleetLyxter holds the machine, its history and its schedule.You are here
- ServiceBetaLyxter runs the work and produces the document.Open Service →
Finish a service on one of your own machines and it lands on that machine's timeline in Fleet. Open a chat on the same machine and the AI answers with that timeline behind it.
Fleet and Service both come with Pro, per seat and per month, with no long contract.
Stop guessing. Start fixing.
Set your workshop up today, or book a demo with our team.