Lanterne
This demo is private. Enter the password from the message.
Home

Home

Home

Ask

Lanterne

How can I help?

Ask about Flinkster bookings, damage or work Lanterne has handled.

Demo · simulated actions

Workflows

WorkflowStarts whenNeeds attentionRecent activityModeOpen workflow

Re-booking

Starts on every MOQO car-without-assignment ticket. Called booking protection in the offer. Autonomous

How it runs
Links the ticket, the car and every affected booking, then checks MOQO and INVERS.
Ends a trip left open, or removes a wrong maintenance block, when the evidence supports it. Re-reads first and changes once.
If the car is really out, re-books by your order: Deutsche Bahn colleagues first, then the longer booking.
Conflicting evidence, undefined cancellation rules and failed notification come to your team.
Confirms every allocation or cancellation in MOQO and verifies customer email delivery separately. Never moves a customer to another station without agreement.
To agree with you
Idle time before ending an open trip2 hours to agree
Early-start window10 or 15 minutes to agree
Automatic cancellation deadlineProduction rule to agree
Priority orderDeutsche Bahn colleagues, then the longer booking to confirm
Cancellation email and delivery-failure routingNotification rules to agree
Recent runs
The 11:15 booking was cancelled. Alternatives were emailed.Booking 2091417 · HAM-119 · Hauptbahnhof
email delivered Your call
A 10:00 booking has no car available. Decide whether to re-book it.SPR-336 · breakdown report conflicts with vehicle data
review the case Your call
KRT-482 · maintenance block removed09:00 booking has the car
07:09Auto
HAM-119 · re-booked by priority2 protected allocations · 1 cancelled and notified
06:24Auto
BER-207 · open trip ended09:30 booking has the car
01:00Auto
WDN-118 · covered by MOQOflat tyre · maintenance kept
Sun 11:37Auto
TGL-845 · covered by MOQO17:00 booking moved to FRD-512
Sat 16:14Auto
MRZ-310 · covered by MOQOlate return
Fri 21:52Auto
Fixed by Lanterne · 07:09 Re-booking

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.

Ticket and booking linked Customer got in at 06:50 Immobiliser never released No fault codes, battery 12.6 V
What changed in MOQO
Maintenance block M-5521Removed
09:00 booking 2091203Has KRT-482
Rule applied: a maintenance block comes off when the evidence shows no fault. Agreed in validation.

How Lanterne got here

  1. 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.
  2. Any new event on the car would have stopped the change and sent the case to you.
  3. 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
Fixed by Lanterne · 01:00 Re-booking

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.

At its station since 22:54 Doors locked, key inside, engine off No movement, mileage unchanged Waited 2 hours · idle time to agree
What changed in MOQO
Trip 2090877Ended at 22:58
09:30 booking 2091310Has BER-207
Rule applied: end an open trip after the agreed idle time at the return station. Any new movement restarts the wait.

How Lanterne got here

  1. 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.
  2. Lanterne never shortens the wait because a booking is coming up.
  3. 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

    Handled automaticallyRe-booking

    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.

    Booking 2091417Cancellation confirmed in MOQO · 06:25
    Customer emailDelivery confirmed · 06:26

    Illustrative automatic run under a configured demo policy. The production cancellation deadline and notification rules still need agreement.

    View all checks in Logbook →

    Try a delivery failure

    This demo control shows the same cancelled booking when email delivery fails. It does not cancel the booking again.

    Vehicle status unclear Re-booking

    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.

    Ticket: "broken down" at 07:38 Moved 07:31 to 07:40, now at Pankow KTB-218 free at Gesundbrunnen
    If you re-book
    10:00 booking 2091502Moves to KTB-218, same station
    SPR-336 and its open tripLeft for your team
    OPYour call, before 10:00

    How Lanterne got here

    1. 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

    How it runs
    Checks outside, interior and other, whatever category the customer picked, and corrects it.
    Known damage and photos that aren't damage are set to Ready, so the next customer doesn't see them.
    Litter becomes a cleaning task. Warning lights and service messages become service tasks.
    New damage, unclear photos, mixed reports and safety concerns come to you.
    Never deletes a photo, charges a customer or says a car is safe to drive.
    To agree with you
    How long original photos are kept12 months to agree
    Who gets safety flagsOperations, by email and Inbox to agree
    New damage waits asReady until you confirm to agree
    Recent runs
    A cracked mirror may be unsafe. Decide whether to take the car off the road.NVK-356 · next booking 10:15
    review the case Your call
    KTB-218 · known damage, set to Readymatches D-2107 from 12 Sep
    07:52Auto
    BLM-652 · category correctedInterior to Outside · known D-1988
    07:31Auto
    SPN-409 · oil service warningservice task S-3380 · hidden from customers
    06:58Auto
    A scratch appears to be new. Review the photos.PLD-771 · front right · 3 reports
    review the photos Your call
    FRD-512 · litter in the footwellcleaning task C-2204
    Sun 19:12Auto
    A damage photo is too blurred to assess. Request a clearer one.OPK-340 · rear left
    review the case Your call
    September backlog · 214 reports151 handled · 63 for you
    Sun 02:10Auto
    0 photos deleted Damage triage

    214 open September reports sorted: 151 handled, 63 for you.

    88 known damage 34 cleaning tasks 29 service or not damage 27 categories corrected
    For you: 38new or changed ·19unclear ·6mixed or safety Validation starts here.
    For you · 5 of 63
    WLT-915 → tyre sidewall bulgesafety · 24 Sep
    HRB-733 → dent on the driver doornew · 28 Sep
    GRV-280 → bumper crack longer than D-1874changed · 26 Sep
    OPK-340 → photo blurredunclear · 19 Sep
    MRZ-310 → boot scratch plus a known dentmixed · 11 Sep
    Handled · 5 of 151, all set to Ready
    KTB-218 → known damage D-210729 Sep
    FRD-512 → litter, cleaning task27 Sep
    BLM-652 → moved to Outside, known D-198822 Sep
    SPN-409 → tyre pressure warning, service task16 Sep
    TGL-845 → photo of a person, not the car3 Sep
    Relevant · new damage Damage triage

    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.

    3 reports merged Moved from Interior to Outside No damage on file at this spot
    3Reports merged into one case

    Damage photos · illustrative demo images · select to enlarge

    Anchor
    Report 1 · 18:31filed under Interior
    96% match
    Report 2 · 18:36close-up
    93% match
    Report 3 · 18:40angled
    Receipt · earlier photos
    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

    1. Report 1 was filed under Interior; the photo shows the outside front right.
    2. No mark in the Sunday 14:20 check-in photos. No repair on this panel since June.
    Relevant · mixed report Damage triage

    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.

    Safety · mirror glass loose Scratch matches D-2231 Mirror not on file
    If you block it
    NVK-356Maintenance booking + repair task
    10:15 bookingGoes to re-booking

    How Lanterne got here

    1. 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.
    Unclear · can't compare Damage triage

    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.

    Photo out of focus D-1840 on file, rear left Next cleaning visit Tue 09:00
    What's missing
    A clear photo of the rear leftTaken by someone at the car

    How Lanterne got here

    1. 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.

    Logbook

    Home