Home
Since Friday 18:00
7 tickets affected 10 bookings
Waiting for you
Nothing waiting. Every affected booking has a car or a confirmed cancellation. Customer notification is complete.
Settled on its own
Home
Since Friday 18:00
New and changed MOQO damage reports
Lanterne corrected the category on 4 of these reports. No photo was deleted. 0 reviews completed by your team.
Waiting for you
Handled on its own
September backlog
214 reports still Open
Ask
How can I help?
Ask about Flinkster bookings, damage or work Lanterne has handled.
Workflows
| Workflow | Starts when | Needs attention | Recent activity | Mode | Open workflow |
|---|
No matching workflows
Try another search or clear your filters.
Re-booking
Starts on every MOQO car-without-assignment ticket. Called booking protection in the offer. Autonomous
KRT-482 is back in service. The 09:00 booking has it.
Support set a maintenance block at 07:05 because the car wouldn't start. The customer got in but never released the immobiliser. There's no fault, so Lanterne removed the block.
How Lanterne got here
-
Ticket 363307: "car won't start". Maintenance block placed 07:05.Trip started 06:48. Doors opened 06:49, key out 06:50.Immobiliser never released, including after support reopened the doors at 07:01.No fault codes or warning lights.
-
Any new event on the car would have stopped the change and sent the case to you.
-
Receipt
- Ticket
- 363307
- Before
- M-5521 active · 09:00 booking without a car
- After
- M-5521 removed · 09:00 booking has KRT-482
- Events read
- INVERS, 06:48 to 07:09
BER-207's trip was left open. Lanterne ended it.
The car was parked at Ostkreuz at 22:54 and nobody ended the trip. Once it had been still for the agreed time, Lanterne ended the trip at 22:58, when the doors locked. The 09:30 booking has the car.
How Lanterne got here
-
Booking 2090877 was due to end Sunday 23:00.Engine off 22:54, key in 22:57, doors locked 22:58.Odometer unchanged at 38,214 km.
-
Lanterne never shortens the wait because a booking is coming up.
-
Receipt
- Before
- Trip 2090877 open · 09:30 booking without a car
- After
- Trip ended 22:58 · 09:30 booking has BER-207
- Events read
- INVERS, 22:40 to 01:00
How Lanterne got here
The 11:15 booking was cancelled. The customer received nearby alternatives.
HAM-119 has a confirmed brake fault. The maintenance block stays in place. The 08:30 Deutsche Bahn booking keeps ODR-415 and the longer 09:00 booking keeps PKW-238. No car remains at Hauptbahnhof for booking 2091417.
Illustrative automatic run under a configured demo policy. The production cancellation deadline and notification rules still need agreement.
Cancellation email
- To
- Customer on booking 2091417
- Subject
- Your 11:15 booking has been cancelled
Unfortunately, a technical fault means we cannot provide a car for your booking at Hauptbahnhof from Monday 11:15 to Wednesday 11:15. We have cancelled booking 2091417.
These cars in the same Compact class were available for your full booking period when we checked at 06:25:
- BRZ-205 · Alexanderplatz
1.4 km from your original station · Compact · Mon 11:15 to Wed 11:15 - WST-620 · Friedrichstraße
2.1 km from your original station · Compact · Mon 11:15 to Wed 11:15
You can choose an alternative in the booking app. These cars have not been reserved for you, and availability may change.
Try a delivery failure
This demo control shows the same cancelled booking when email delivery fails. It does not cancel the booking again.
A 10:00 booking has no car available. Decide whether to re-book it.
The customer told support the car broke down at Gesundbrunnen. INVERS shows it drove 3.2 km to Pankow afterwards, and the trip is still open. Lanterne can't tell which is right, so it changed nothing.
How Lanterne got here
-
Ticket 363412, 07:38: "Auto springt nicht an, Gesundbrunnen."Trip 2091188 open since 06:55. Engine on 07:31, off 07:40 at Pankow.No fault codes. The 10:00 booking at Gesundbrunnen has no car.
Damage triage
Starts on every new or changed MOQO damage report. Autonomous
214 open September reports sorted: 151 handled, 63 for you.
A scratch appears to be new. Review the photos.
Three reports show the same spot, so Lanterne merged them. The Sunday 14:20 check-in photos show no mark there. Lanterne doesn't assign fault. It stays Ready until you decide, so the next customer doesn't see it yet.
Damage photos · illustrative demo images · select to enlarge
- Check-in
- Sun 14:20 · front right visible, no mark
- Damage on file
- 2, other spots
- Cause
- Not recorded. Your team decides.
How Lanterne got here
-
Report 1 was filed under Interior; the photo shows the outside front right.
-
No mark in the Sunday 14:20 check-in photos. No repair on this panel since June.
A cracked mirror may be unsafe. Decide whether to take the car off the road.
The same report shows a scratch that's already on file. The mirror appears new and may not be safe. Lanterne hasn't blocked the car. The next booking is at 10:15.
How Lanterne got here
-
Rear bumper scratch: same as D-2231 from 3 September.Left mirror housing cracked, glass moved. Not in Saturday's check-in photos.Kept as one report and flagged for safety.
A damage photo is too blurred to assess. Request a clearer one.
The customer reported a scratch on the rear left. The photo is out of focus, so Lanterne can't tell if it matches D-1840 from August. It hasn't classified the report.
How Lanterne got here
-
Plate visible: OPK-340. Category Outside, correct.Photo too blurred to see the edge of the mark.D-1840, 14 August: scratch on the rear left door. No repair since.