Also lives in WhatsApp · message it, send photos, it files the rest
You
Which cars are off road and which inspections are due?
Lanterne
Seven cars are off road: five in for repair at Current Works, one awaiting a shipped part (CV‑118, three weeks), one flagged for a low battery. Six annual inspections are due this month, two are already overdue. All of it read straight from Vulog and the service log, no scrolling the sheet.
photo · rear bumper, CV‑089 · Damage on return, log it.
Lanterne
Filed to CV‑089's log with the photo and opened the case: quote requested from Current Works, tonight's booking unaffected. Works the same from WhatsApp, so your techs send photos where they already talk and nothing new gets installed.
Service board
Repairs, annual inspections and fluid checks, from Shop-Ware and the service log. Advises you
2
Need a person
a shop gone quiet, and an inspection with no booking on record
5
Chased under your rules
past their expected date · a firm date asked for, replies filed to the car
31
On track
booked, in for repair, or back on the road · nothing needed
Live from Shop-Ware · repair-order status across the fleet, updated just now. The service schedule is read from your Google Sheet, and every booking, date and sign-off is written back to it.
Needs a person
CV‑118 · off road 3 weeks, waiting on a partCurrent Works · silent 4 days · inspection now overdue too
open case
CV‑044 · annual inspection overdueDockyard · no record it was booked
book it
Cleaning, raised from the booking calendar
19 cleaning tasks raised for tomorrow’s collectionsone per car with a booking starting before noon · sent to the technician covering that location
21:00Done · auto
CV‑151 cleaned ahead of the 09:00 collectionraised from booking 4471 the evening before · photo filed to the car
05:12Done · auto
CV‑089 turned around between two same-day bookingsreturned 13:40, next collection 16:00 · cleaning task raised on the gap
13:41Done · auto
CV‑244 booking cancelled · cleaning task withdrawnthe task follows the booking, so nobody drives out for a car nobody collects
YesterdayWithdrawn
142 cleaning tasks raised in July · 138 done before collection4 ran late · each one logged against the person and the booking
JulyLogged
Chased under your rules · no action needed
CV‑258 · at Current Works 5 days, past the expected datechased Monday · firm date given: back Thursday
MondayDate agreed
CV‑133 · waiting on a part 10 dayschased Monday · part shipped, tracking filed to the car
MondayDate agreed
CV‑322 · fluid check flagged lowbooked into Current Works for Friday · no booking clash
TuesdayBooked
CV‑201 · annual inspection due this weekbooked around the Thursday rental · sheet updated
TuesdayBooked
CV‑162 · battery flagged from Battery watchhanded to the service board, slot booked with the next inspection
YesterdayBooked
On track · nothing needed
CV‑190 · booked into Current Worksservice · Thursday, inside a booking gap
Booked
CV‑305 · booked into Current Worksannual inspection · Friday
Booked
CV‑077 · at Current Works, 1 dayon the expected date, nothing to chase
In repair
CV‑088 and CV‑019 · back on the roadmoved into rotation in Vulog, records closed
Back on road
27 more · on the road, nothing dueno repair, inspection or fluid check outstanding
A drive-motor fault took CV‑118 off the road on the 1st. Current Works ordered a part that had to be shipped in. It has now been three weeks, the part landed two days ago, and the shop has gone quiet on when it goes back on. On top of that, the car's annual inspection fell due while it sat. It is a Hamilton car in peak season, so every day off road is a lost rental. Getting a straight answer needs a person.
Read across Vulog, the service log and Current Works Off road since 1 Jul · part shipped, landed 2 days ago Annual inspection now overdue · bundle it in
Message prepared · for you to send
Who
Current Works service desk
Channel
WhatsApp thread on file
Hi, the part for CV‑118 landed two days ago and it has now been off the road three weeks. When does it go back on? While it is in, please run the annual inspection that is now due so it does not go off road again next week. Let me know a firm date.
PCYour call, Piers
Reason for closing
How Lanterne got here
Read CV‑118 across Vulog, the service log and the Current Works thread.
Off road since 1 Jul with a drive-motor fault. Part shipped in, landed two days ago.
Annual inspection fell due while it sat. Bundle it into the same visit.
Receipt · what Lanterne read
Vehicle
CV‑118
Location
Hamilton
Off road
3 weeks · part landed
Lanterne has the message prepared, with the inspection bundled in so the car does not go off road again next week.
Once it is back, Lanterne logs what happened, marks the inspection done, and returns the car to rotation in Vulog.
Breakdown cover
Matches faults from Vulog against forward bookings and puts a replacement car on the booking before the customer arrives. Asks you first
CV‑134 will not start, and it is on the 09:00 booking.
Vulog recorded an ignition fault on CV‑134 at 04:12, on the forecourt at Hamilton. The car has two bookings ahead of it. The first collects at 09:00 today and runs three days. Lanterne moves a booking on its own when collection is more than eight hours away. This one is not, so it comes to you.
Vulog · ignition fault on CV‑134 at 04:12 Booking 4471 · collects 09:00 today · runs 3 days Booking 4488 · Thursday · same car 5 cars on the Hamilton forecourt, checked against both bookings
Recommended
CV‑151
Charged to 94%, cleaned at 21:40, and nothing booked on it this week. It covers booking 4471 and booking 4488, so one move settles both.
What Lanterne will do if you approve
Move bookings 4471 and 4488onto CV‑151 in Vulog
Send the taskWhatsApp to the technician on shift at Hamilton
Take CV‑134 off roadcause recorded as no-start
Book the repairCurrent Works · next open slot
PCYour call, Piers
Done
Approved. CV‑151 is on booking 4471.
To the technician on shift · Hamilton
CV‑134 on the Hamilton forecourt will not start. Bring CV‑151 out front for booking 4471, collecting at 09:00. Keys are in the Hamilton box. Reply DONE when it is out.04:14
Done, CV‑151 out front, keys back in the box05:38
CV‑134 off road from 04:12 · cause recorded as no-start Bookings 4471 and 4488 moved to CV‑151 in Vulog Assigned 04:14 · confirmed 05:38 · Hamilton technician CV‑134 booked into Current Works · Thursday slot
How Lanterne got here
Ignition fault recorded on CV‑134 at 04:12, parked on the Hamilton forecourt, last trip ended 23:41.
Receipt · what Lanterne read
Vehicle
CV‑134
Location
Hamilton
Signal
ignition_fault · 04:12
Two bookings sit on CV‑134. Booking 4471 collects at 09:00 today and runs three days. Booking 4488 is Thursday.
Five cars are on the Hamilton forecourt. Each was checked for charge, cleaning and its own forward bookings.
Lanterne moves a booking on its own when collection is more than eight hours out. Collection is at 09:00, so this one waits for you.
On approval the bookings move in Vulog, the task goes to the technician on shift over WhatsApp, and the reply closes it against a person and a time.
Recent runs
CV‑171 power train fault · 11:00 booking coveredCV‑145 put on the booking, collection more than 8 hours out · ran on its own
03:26Done · auto
CV‑092 power train fault · Dockyard, two bookings coveredCV‑188 put on both · ran on its own
02:51Done · auto
No spare at Southampton for a 10:00 collectioncame to you · customer moved to the 11:30 with a free upgrade
TuesdayYou approved
47 faults read this month · 9 put a booking at riskthe rest recovered on their own and raised nothing
JulyFiltered
How it runs
Reads every fault from Vulog against the bookings on that car, and checks the forecourt for a car that is charged, cleaned and free for the whole booking.
Comes to you when collection is inside eight hours, or when no car covers every affected booking.
Never cancels a booking, and never closes a task on a promise. A technician confirms the car is out front.
Battery watch
Monitors state of charge, 12 V battery level and charging state, and raises a task when a car is returned low or a battery goes flat. Autonomous
Recent runs
CV‑188 returned at 12% · charge task raised on the returnnext booking 17:30 · on charge 9 minutes after the trip ended, ready in time
12:04Done · auto
CV‑093 returned at 18% with no booking behind itcharged on the normal rota, nobody sent out · a low return is not always urgent
YesterdayFiltered
CV‑162 put on charge before a booking · caught overnighttechnician notified · charging completed before the booking
YesterdayDone · auto
CV‑089 flagged for a battery check · 4th event4th low-voltage event · battery inspection requested. Prior check
TuesdayYou approved
CV‑061 parked at Hamilton, not charging · outlet trippedcaught 22:40, tech sent, on charge by 23:05 · ready for its 09:00 booking
22:40Done · auto
Unnoticed return at Hamilton · cleaning and charge tasks raisedtrip ended from the customer's phone · car back to ready 41 minutes later
CV‑207 is on a long-term rental at Hamilton and has been parked for 11 days. Vulog records a falling starter-battery level across that period. No alert is currently configured for this pattern.
Vulog · CV‑207 falling across 11 days Long-term rental · parked for 11 days Hamilton technician · on shift
What Lanterne will do if you approve
Raise a high-priority taskget CV‑207 on charge before it fails to start
Notify the nearest techone-tap WhatsApp link, no app to open
Attach the how-to12 V boost steps · photo at completion
Flag it for a battery check3rd low-voltage event this month
PCYour call, Piers
Done
Task out. Here's what Lanterne did.
High-priority task raised for CV‑207 Nearest tech notified · one-tap WhatsApp link How-to attached · 12 V boost steps Flagged for a battery check · 3rd event this month
Tech notified
Task
Boost and check CV‑207 at Hamilton
Sent to
Nearest tech at Hamilton · via WhatsApp
Priority
High · before next booking
How it runs
Watches every car's 12 V level and state of charge in Vulog, including cars sitting on long rentals.
Reads the charge the moment a trip ends, and raises a charge task when a car comes back low with a booking behind it.
Raises a task, notifies the nearest tech, and flags vehicles with repeated low-voltage events for inspection.
Never touches the car itself. It alerts and tasks; a tech does the boost.
Availability
What is on the road, what is out of service, and an alert when it crosses your line. Advises you
65%on the roadright now
18%out of servicealert line 18%
17%available to rent13 cars free
71%fleet utilisationJuly · up from 64% in May
July · out-of-service % by location
Utilisation · share of the fleet on rent, by month
By location · July
Hamilton81%
Dockyard74%
Southampton58%
By vehicle · July ·
Days on rent as a share of the month, read from Vulog booking records. Time off road counts against a car, because a car in the workshop earns nothing: the three lowest here are the same cars sitting on the service board.
Can I take this booking?a real week-long check against forward bookings
Dockyard · XEV Yoyo · 12-19 Augclear · no clash
Hamilton · XEV Yoyo · 12-19 Augclash on the 16th
Southampton · XEV Yoyo · 12-19 Augclear · 2 free
Alerts
Hamilton crossed 18% out of service4 cars at Current Works · pulled forward the two closest to done
02:10Done · auto
Deploy & rebalance
Raises a rebalancing task when a location falls below its configured supply target. Autonomous
How it runs
Watches each location's supply against a target you set, with the cruise-ship schedule and hotel demand in view.
Raises a deploy task with how many cars to move, from where, and by when, and assigns the driver.
A driver completes and confirms each vehicle movement. Lanterne sizes and assigns the cars.
Recent runs
Southampton onboarding · 20 of 60 new cars in-fleetedTCD inspection booked per car · service schedule enrolled · charge points mapped
This weekOn track · auto
4 cars moved Hamilton → Dockyard for two cruise arrivals8,000 passengers in · driver assigned · supply restored
06:30Done · auto
Southampton topped up ahead of the weekend2 cars from the Current Works store · before demand peaked
YesterdayDone · auto
No spare for a third arrival · came to youevery car committed · you decided which booking to move
SundayYou approved
Handled · auto
4 cars moved to Dockyard.
How Lanterne got here
Team & tasks
Task completion by team member. Each task records an assignee. Advisory
57tasks completedJuly to date
6team membersacross both hubs
11open tasks2 need a person
100%logged to a personassignee recorded
July · work by person
Accountability playbook
Each task records the assignee, completion time and a completion photo, submitted through a WhatsApp link.
Each task can carry approved steps, photos and a reference video for new starters.
Summarises daily task activity by team member across both hubs.
Records completed work. Performance decisions stay with you.
Workflows
Describe a process in plain language and Lanterne builds and runs it across Vulog and your service log.
Lanterne read your description and turned it into a four-step workflow across Vulog and your service log, with the three-strikes battery-check rule you asked for. Review the playbook, then approve it to run across your fleet.
Steps
Detect12 V below 12.2, or idle 5 days on a long rental
Lanterne
Raise taskhigh priority, nearest location
Lanterne
Notify techWhatsApp, one-tap link to the car
Tech
Flag repeats3 events → proper battery check
Lanterne
Battery watch playbook
Watches every car's 12 V and idle time and raises a task the moment one crosses the line.
Notifies the nearest tech by WhatsApp and flags a three-time offender for a proper check.
Never touches the car itself. It alerts and tasks; a tech does the work.
Every run and every decision, with its receipt. Click a row to see what was read and what was done.
Analytics
Workflow activity for the period shown. Figures throughout this demo are sample data.
32 hops time savedJuly
186actions handled142 without you touching them
76%handled end to endup from 61% in June
2.4 daysavg off roadfrom Shop-Ware · down from 3.6
Actions by week ran on its own with your call
1 Jul8 Jul15 Jul22 Julthis week
WorkflowRunsEnd to endMedian handle
Battery watch4495%40 s
Deploy & rebalance2186%2 min
Service board6172%4 min
Availability30100%1 min
Fleet sizing · sold-out days
1 Jul8 Jul15 Jul22 Julthis week
No cars availableCars back, not ready
13 sold-out days in July41 bookings turned away
5 of the 13vehicles on site but not ready to book
At 260 cars11 of 13 clear · the remaining 2 are turnaround, not fleet size
Data required
✗Vulog records booked and not booked. It does not record readiness.
✗The service spreadsheet records service dates. It does not record readiness.
✗Readiness is currently captured in operational messages, not structured records.
Sourcereadiness records · each vehicle marked not ready and ready again, with assignee and time
Integrations
Lanterne plugs into what you already run. Reads flow continuously; writes go through the same gates as everything else.
VU
VulogBookings & telematics
Connected
Bookings, vehicle status, 12 V level, location and availability, read continuously through the Vulog APIs. The alerts the dashboard does not give you.
GS
Service logout of Google Sheets
Connected
Your maintenance history and inspection schedule, lifted off the spreadsheet into a live board. The sheet stays readable; the tracking stops being manual.
SW
Shop-WareCurrent Works repair orders
Connected
Every repair order at Current Works, read from the Shop-Ware you already run: how often each car is in the shop and how long, with a chase when one sits too long waiting on parts. The shop history you already have, put to work.
WA
WhatsAppTech comms
Connected
Tasks reach the techs where they already are, with a one-tap link to the exact car and checklist, so nobody has to adopt a new app.
@
EmailAlerts & reports
Connected
Threshold alerts on availability and the scheduled fleet reports, to you.
