Good afternoon, Adam.
Support Desk
Disputed charges and billing. Advises you
Licence Check
Validations and renewals. Advises you
The A$20 late fee was applied in error.
Jack returned the Tesla Model 3 at 3:42 PM on Sunday, well before the 6:00 PM booking end, so the delayed-return penalty shouldn't have been charged. The A$140 weekend booking fee is correct and stays. Lanterne recommends refunding the A$20 and has drafted the reply for you to relay on the call.
Hi Jack, I've had a proper look at your booking. You returned the Tesla at 3:42 PM on Sunday, well before your 6:00 PM end time, so that A$20 late fee shouldn't have been there. I'm waiving it now; the A$140 weekend booking stands. You'll see the A$20 back on your card in a few days.
How Lanterne got here
-
Read Adam's case note: "returned the Tesla early, still hit with a late fee."Pulled booking 2047106877 from MOQO: planned end 6:00 PM Sunday, actual return logged 3:42 PM.Compared the charge lines: weekend booking A$140 is per the rate card; the A$20 delayed-return penalty conflicts with the 3:42 PM return.Checked the front-line playbook: first dispute from this customer, goodwill-first applies, amount is under Adam's A$50 authority.Receipt · what Lanterne read
- Booking
- 2047106877
- Return logged
- Sun 3:42 PM (due 6:00 PM)
- Playbook rule
- Goodwill-first · cap A$50
-
Moving money and messaging the customer are yours. The decision is laid out above.
-
Once you decide, Lanterne records what happened and who decided, and the case closes with a receipt.
Mia's card was renewed; the record on file wasn't.
Mia Clarke's licence failed validation, and the expiry on file falls inside this month: the classic sign of a licence renewed while the old card details stayed on the account. Lanterne recommends the standard retest first. About nine in ten of these clear right here.
- On the DoT site, test the same licence number with the expiry moved +12 months.
- No luck? Test it again at +5 years.
- One of them validates for most renewed cards; clear Mia and she can book straight away.
Hi Mia, we couldn't confirm your licence against the current record. If you've renewed it recently, could you send us the new valid-to date shown on your card? We'll update it and you'll be able to book right away.
How Lanterne got here 2 steps
-
Picked the failed validation off the portal queue: licence number, expiry, date of birth.Expiry on file falls inside the current month, matching the renewed-card pattern that clears on retest ~90% of the time.Checked the playbook: licences are never cleared by Lanterne; the retest guidance and the customer email are prepared instead.
-
If a retest validates, mark Mia cleared. If neither does, the drafted email asks Mia for the new valid-to date on her card.
New case
New check
Dan is the booked driver; the app lost sync with the car.
Dan Foster is standing at the Mini in Southgate with an active booking, and his app won't unlock it. The failed attempts in the log fit a sync error. The lock-then-unlock reset didn't take, so the remote unlock is staged. It is sent only when you approve, and the customer is waiting with the car.
How Lanterne got here
-
Matched the caller to the active booking on the Mini at Southgate.The app log shows three failed unlocks in four minutes: the sync-error signature.Walked the playbook reset: press Lock first, then Unlock. It didn't take.Receipt · what Lanterne read
- Driver
- Dan Foster · booking active now
- Vehicle
- Mini · Southgate
- Playbook rule
- Approval-first · lockout, escalate if unfixed
-
The unlock is staged, not sent. If it fails, the playbook says escalate; the case keeps its log.
The car is back and checks out; the booking never closed.
Jules Bennett left the car in a basement car park, where it has no signal to close the booking on its own. The car reads locked, keys in, ignition off, right where he said he left it. The next driver's booking starts at 6 PM. Closing it frees the car; both customer messages are drafted.
Hi, good news: the car for your 6 PM booking is confirmed back and ready at the Southgate basement, level 2. The app will unlock it as usual from your start time.
How Lanterne got here
-
Pulled Jules Bennett's booking: due back 1 PM, no close signal since.Checked the car remotely: locked, keys in, ignition off, parked at Southgate basement level 2.Read the return photos: no damage flags.Receipt · what Lanterne read
- Booking
- Jules Bennett · due back 1 PM
- Car state
- Locked · keys in · ignition off
- Next booking
- Today 6 PM
-
Closing ends Jules's booking at the verified return time and frees the car for the 6 PM driver.
New unlock
New return
Good afternoon, Adam.
How can I help with your fleet?
Workflows
What Lanterne runs for you. Each one carries its own playbook, and you set how far it goes: advise, ask first, or run on its own.
Logbook
Every run and every decision, with its receipt. Click a row to see exactly what was read and what was done.
Analytics
What Lanterne is carrying for you. June, month to date.
End to end means no operator touch. Handle time runs from a case opening to its close, receipts included.
Integrations
Lanterne plugs into what you already run. Reads flow continuously; writes go through the same gates as everything else.
Bookings, vehicles, customers and charges, read continuously. Writes only ever go through your approval gates.
Lock state, ignition, keys and location. It's how a return gets verified before anything closes.
The rate card, the idle list, the cleaning roster. Lanterne reads and updates the sheets you already keep.
Supplier invoices and customer mail land here and become runs on their own.
Drivers just text. A lockout at the car opens a case before they finish typing.
Service schedules, inspections and odometer readings feed straight into upkeep and Damage Triage.
Location, engine health and driver behaviour, alongside INVERS for lock and ignition state.
Nothing to migrate and no API to build. Lanterne works the same screens your team does. The licensing portal and the insurer's claim portal already run this way, and every click lands in the Logbook.
Reservation Swap
Bookings whose car won't be ready, swapped before the driver notices. Autonomous
Inspections
The TÜV cycle run from your fleet sheet: workshops emailed, replies parsed, bookings staged. Asks you first
Battery Watch
Charge watched across the fleet, with the noise muted. Autonomous
How Lanterne got here
Teach Lanterne something new
Damage Triage
Return photos graded against the damage guide. Asks you first
Invoice Ingest
Supplier bills parsed, matched, reconciled. Autonomous