Say what the machine showed and the unit, the hour meter, the parts and the estimate are written standing next to it. The estimate waits for approval, on every plan.
30 days free. No card to start.
Forklift and equipment dealers, and the service teams that keep the fleet running.
Ray walked the Vantage yard with Dana, unit 214 reads 8,240 hours with a hydraulic weep, quote steer tires and a load wheel, and book the PM for 14 October.
Pick who you are. The workspace opens as that person, on this trade, with data that looks like a Tuesday rather than a slide.
How many people will actually open Rillo? Everyone who does needs a seat. Somebody you give a view of one record is a collaborator and is not billed.
No hour meter arrives on its own and no truck shows on a map: meters come off scans and walks, and the ledger stays in your accounting package.
What is due today, and in what order?
What changes for somebody else: The second tech works from the same four stops instead of re-reading a calendar.
The call says unit 214 is down again, and everything the tech needs on the way there is somewhere else: the last work order in a paper file at the branch, the hour meter in a spreadsheet from the March fleet walk, the parts that fixed it last time on a van nobody counted, and the approval to do the work in a voicemail from a man on vacation. The truck rolls anyway, because trucks do, and the store finds out what the visit cost when the paperwork surfaces Thursday.
Serial or barcode on the machine, and everything Rillo knows about it comes back: hours, last PM, open work, what was fitted and by whom.
Units counted where they stand, with hours, model and condition. A fleet walk is a record afterwards rather than a notebook nobody types up.
The estimate is drafted from what the tech said and the parts your stock actually holds, and it sits in an approval queue until a person releases it.
Scheduled maintenance tracked against the unit rather than the calendar, so a machine is due because of what it did, not because of the month.
PMs due by hours, the two units that went down overnight, and the fleet walk promised to the Vantage account, in an order that makes geographic sense. The dispatcher is choosing between jobs rather than discovering them, and the vans roll with the parts the day will actually use.
The tech scans the serial and reads the unit’s story standing next to it: 8,200 hours, steer tires at the last PM, the hydraulic weep that was watched and not fixed in March. The diagnosis starts where the last visit ended instead of starting over in the dark.
What the tech found becomes a priced estimate from the store’s own parts and labour rates, and it sits in the approval queue under the customer’s name. Nobody buys anything in a voicemail anymore; the yes, when it comes, is written down where the work order can see it.
Hours, condition, and what comes due inside ninety days, recorded walking the customer’s floor. The walk used to be a notebook that died in a truck cab. Now it is next quarter’s PM schedule, and the replacement conversation the salesman gets to have before the competitor does.
Rillo Fleet understands these as things, not as text in a note. Your company can call them whatever it calls them and Rillo will follow, because the name is a label and the meaning underneath it does not move.
Rillo knows the difference between the jobs people do here. What somebody is allowed to see and change is a separate question, set by whoever runs the company.
Thirty days free and no card to start. If you have not added one by day 31 the workspace pauses rather than billing you, and nothing is deleted.
Best for a service team operating from one shared workflow. Units, work orders, quotes and a parts list everybody can see.
Start on Service TeamTeam on your invoice
Best for coordinated teams needing shared records, manager oversight and permissions across more than one team or location.
Start on OperationsBusiness on your invoice
Best for multi location operations, complex migration, identity, security, custom integrations or a configured deployment.
Rillo prepares customer facing work and holds it. It does not loosen on a bigger plan, and there is no setting that turns it off.
Every action the assistant takes is written down with what was said, so a record that looks wrong can be traced to the sentence it came from.
Your browser does the transcription. Rillo never receives the recording, only the text you can see.
Export what is in there whenever you want. A workspace you cannot leave is a workspace you cannot properly try.
No screen yet for the work order, the unit, the inspection or the tool. No telematics feed. Not an accounting ledger. No matching on equipment.
Hour meters come from scans, walks and work orders, not from a live feed off the truck. If your fleet is already wired and you need meters arriving on their own, that integration does not exist yet, and this page will not pretend it does.
Work orders, parts used and estimates live here. The ledger, invoicing terms and statements live in your accounting package, and the QuickBooks connection is being built rather than live. The handoff today is export, not sync.
Work waits for a person to say yes, in writing, every time. That is the trust boundary the whole workspace is built around, and no plan tier loosens it.
If one of these is the reason you need a CRM, Rillo is not ready for you yet, and it is cheaper for everyone that this page says so instead of the demo.
No. Invoicing and the ledger stay in accounting, and live location and machine hours stay in whatever streams them. Rillo holds the work order closed at the machine, the unit found by serial, and what was actually fitted.
They say what they did. The work order, the parts off the truck and the estimate are written from that, and the estimate waits for a person before it goes anywhere. That hold is on every plan and there is no setting that removes it.
There is no screen yet for the work order, the unit, the inspection or the tool: they are records the assistant writes and reads. No telematics feed, and no matching on equipment.
Dictation runs in the browser, so it wants a connection. What it does not want is a laptop or a desk, which is why the work order gets written at the machine instead of from memory at six o clock.
Yes. Units are found by serial and carry what was fitted to them, so the fourth call on the same machine reads as a pattern rather than as a fourth call.
Yes, whenever you want. Units, work orders and what was fitted to each come out together, so the service history stays a history rather than a list of dates.
Open the workspace and look at it first. If it does not look like your work, nothing further down this page will change that.
30 days free. No card to start.