Workflow details· Step 2 of ~8 in the swap workflow

1. Request & reply10:00 status request · 11:52 workshop replyLanterne
   10:00: Status request sent to all 9 workshops for vehicles with weekend customer bookings.

   11:52: Reply from Autohaus Brenner: "Replacement part won't arrive until Monday, vehicle ready Tuesday morning."

   Receipt · input data

   Vehicle

   L-TA 4127

   Workshop booking

   scheduled until Fri · new commitment Tue

   Customer booking

   Sat 09:00 – Sun 18:00

2. Replacement sought3 comparable vehicles checked at the stationLanterne
   L-TA 3980: same class, no booking until Monday · suggested.

   L-TA 2044: available, but an interior check is open · L-CF 3702: different vehicle class.
3. Your decisionThe proposed swap is waiting for your approvalYou
   You decide whether to swap the vehicle. Lanterne presents the case by 14:00, rather than 18:00.
4. Wrap-upRebook, extend, logLanterne
   After approval, Lanterne rebooks through Casix, extends the workshop booking and logs the decision and approval.

Needs your decision· 7 vehicles at 4 workshops

Workflow details· one run, four steps

1. Asked every workshop10:00 · 12 requests for 26 vehiclesLanterne
   One request per workshop covers every vehicle it holds, not one request per vehicle. The request asks whether each vehicle will be ready as booked and, if not, when.

   11:30: reminder sent to the three workshops that had not answered.
2. Applied the rulesby 13:50 · 19 of 26 settledLanterne
   15 confirmed ready as booked. 4 rebooked at the same station in the same class under your rules, with each change logged.

   7 could not be resolved. Reasons included one within the 48-hour window, three with no same-class vehicle available, and two at a workshop that did not reply.
3. Your decisions7 vehicles at 4 workshops, waiting aboveYou
   The rules resolved all eligible cases. The remaining cases require a choice between swapping or deferring the booking.
4. Workshop emailsdrafted once you approveLanterne
   After all vehicles are resolved, Lanterne drafts one email per workshop covering every vehicle. A workshop holding three vehicles receives one message, not three.

Relevant · new damage All 24 cases today

New rear-left scratch on L-CF 2381 with supporting context.

Lanterne merged three reports submitted within seven minutes into one case because they show the same location. The vehicle history contains no damage at this location. The ignition was on from 07:12 to 07:31 and the first report arrived at 07:34, after the booking ended. Lanterne provides this context but does not assign fault. The team decides what happens next.

3 reports linked into 1 case Photos described and compared History: no prior damage at this spot Ignition timeline attached

3Reports merged into one case · separate any report that does not belong

Anchor

Report 1 · 07:34rear left, wide angle

Separate

97% match

Report 2 · 07:36rear left, close-up

Separate

94% match

Report 3 · 07:41rear left, angled

Separate

Receipt · timeline

07:12 – 07:31

Ignition on (INVERS)

07:34

Report 1 · photo rear left

07:36 / 07:41

Reports 2 and 3 · same spot

Receipt · previous booking

Renter

K. Feldmann · booking ended 07:12

Photos on return

2 uploaded at check-in · neither shows rear left

Visible in renter photos?

No. The rear left is not visible in either photo.

Cause

Not recorded. Lanterne uses the available evidence. Your team decides responsibility.

Create the damage in EBuSRear left, documented here for the first time. Opens the pre-filled create-damage form in EBuS via a deep link.

Link to an existing documented damageOnly use this option if the damage matches the 2024 right door or 2023 front bumper entry.

Close · no actionThe decision is logged, and no damage is created.

What opens in the EBuS create-damage form

VehicleL-CF 2381

Locationrear left

Reportedtoday · 07:34

Photos3 attached

Accountteilauto-lanterne

Deep linkEBuS · create-damage · case ID from the report email

Cause is not recorded. Lanterne leaves this field empty, and your team decides responsibility.

Hand off to claims team

MKYour decision

Open in EBuS · create damage Decide later

Workflow details

1. Read & grouped271 reports overnight, grouped by vehicle, time and spotLanterne
   189 duplicates were merged, and 58 previously documented damages were marked and closed. The remaining 24 relevant cases include this one.
2. EnrichedHistory, timeline, photo comparisonLanterne
   The three reports show the same location from different angles and are grouped into one case rather than three.

   The vehicle history includes right door damage from 2024 and front bumper damage from 2023; the rear-left damage is new.

   Receipt · history

   Right door

   documented 2024

   Front bumper

   documented 2023

   Rear left

   nothing on record

3. Your decisionCreate, link or close · the team makes the decisionYou
   Lanterne prepares each case up to the decision point. teilAuto reviews the final 10 percent.
4. CompletionCreated in EBuS via a deep linkLanterne
   After your decision, Lanterne opens the pre-filled create-damage form in EBuS via the deep link, or closes the case, and logs the outcome and time.

Workflow details· Step 3 of 4 in the check

1. Feed matched412 charges against bookings · 06:10Lanterne
   411 charges sit inside a booking. One does not.

   Receipt · input data

   Charge

   €68.40 · Aral Leipzig-Plagwitz · 22:41

   Booking window

   none on L-TA 1204, 18:00–06:00

   Position

   4.1 km from the pump at 22:41

2. Plausibility checkedvolume and consumption against the vehicle typeLanterne
   38.2 l charged against a 40 l tank on file, and the vehicle's own tank level did not move.
3. Your decisionsend to the team, or close as legitimateYou
   The case reaches you 9 hours after the charge, not two weeks later.
4. Wrap-upsend or close · either way it is loggedLanterne
   The decision, the evidence and the outcome land in the logbook.

Workflow details· Step 3 of 4 in the buyout

1. Buyout recordeddecision and purchase data captured · 18 JulLanterne
   The invoice was uploaded and read; date, price and contract reference were extracted and confirmed against the lease.

   Receipt · input data

   Purchase date

   18 Jul 2026

   Price

   €9,300 · invoice SKF-2026-0114

   Provision held

   €2,140

2. Posting draftedamount, date and vehicle referenceLanterne
   Release of €2,140 drafted for the provision fund, referenced to L-TA 1877 and dated on approval.
3. Your decisionthe posting waits for your approvalYou
   Nothing posts and no status changes until you approve.
4. Wrap-uppost, change status, logLanterne
   The release posts, the status changes with its history kept, and both land in the logbook and the year-end export.

Workflow details· Step 3 of 4 in the watch

1. Indexes recomputed2,487 vehicles · 03:10Lanterne
   30 vehicles sit outside the 80–120% band. One is far enough out for a proposal.

   Receipt · input data

   L-TA 2431

   164% · 33,412 km in 16 months · plan 45,000 km

   L-TA 0642

   71% · same class · Leipzig Grünau

   Band

   80–120% of plan

2. Candidates checked3 under-plan cars at nearby stationsLanterne
   L-TA 0642: same class, 71%, free from Friday · suggested.

   L-TA 1130: different class · L-CF 2210: an interior check is open.
3. Your decisionthe swap waits for your approvalYou
   No car moves until you approve. The excess-mileage clock on L-TA 2431 keeps running at €0.09 per km over.
4. Wrap-uptasks created · decision loggedLanterne
   On approval, two relocation tasks go to the service team's list, and the watch keeps recomputing nightly.