The five routines for teilAuto. Each follows fixed rules, and you decide per workflow how far it goes: suggest, ask first, or run independently. During the pilot, one person approves every action.
Every Friday at 10:00, Lanterne checks in with every workshop. By 14:00, two action lists are ready – while there's still time to provide a replacement vehicle. Asks first
How it works
Reads the workshop bookings via Casix, finds every vehicle with a customer booking waiting over the weekend, and sends each workshop a status request that covers every vehicle sitting there – one request per workshop, one reply for any number of vehicles: Will they be ready as booked – and if not, when?
Reads the replies through the morning and sorts them into two lists by 14:00: not ready in time (needs rebooking, with a replacement suggestion attached) and no response (call). Anything confirmed on time needs no one.
Prevents a workshop from being pinged for every single vehicle: either the next-due vehicles are flagged and confirmed at the same time, or it waits until at least five are overdue before following up – whichever keeps the workshop from getting three emails in a week.
Never decides the vehicle swap on its own. The decision stays with the fleet department – Lanterne makes sure it's made by 14:00, not 18:00.
KFZ-Service Lindemann, Dresden · L-CF 1954 · part missing, ready MondayCustomer booking Sun 10:30 · no direct replacement at the station · options attached
View optionsYour decision
Autohaus Vetter, Chemnitz · 3 vehicles · new commitment: WednesdayL-TA 8126, L-CF 6402, L-TA 2255 · one status request, one reply covers all three
22 of 26 vehicles confirmed as bookedall replies in the logbook · no action needed
13:40Done · automatically
Live · watching only – nothing to do right now
L-TA 6602 · pickup booked tomorrow 09:00Workshop confirmed on schedule · Lanterne is watching, and will only surface again if that changes
Being watched
Recent runs
Last Friday: 31 vehicles requested · 3 rebookings, 1 callall three weekend bookings held
last weekApproved by you
Task allocation
The morning's daily plan: an ordered list, assignment suggestions by proximity and travel time, sent in one step. About an hour of planning becomes a five-minute review. Asks first
How it works
Gathers every due task into one list: cleaning by interval, charging and telematics from INVERS, damage and complaint tasks from the Cantamen reports. Grouped by proximity and travel time, with an eye on upcoming bookings.
The lead for the service vehicles reviews the suggestion, adjusts what needs judgment, and sends all personal lists in one step. The process is the same across every city – and measurable.
Never rates any individual's performance. Assignment is by location and availability, not a performance rating – technicians already plan their routes well today; Lanterne just takes the work of assembling the plan off their hands.
After sending, Lanterne reads the "task completed" notifications from Cantamen and resets the intervals – nothing runs twice.
The breakdown by city – check duration, checks per technician, overdue checks – is under Analytics.
Bulk inspection booking
100+ individual bookings in a small calendar become one batch decision. Asks first
How it works
Takes in the vehicle list, checks each vehicle's existing customer bookings, and suggests appointments in the slots the workshops have pre-confirmed.
After your approval, Lanterne books the whole batch via Casix and sends each workshop an email with what they need: plate number, reason for the visit, pickup location. No back and forth.
Never books over a customer booking. Conflicts come back as options, not surprises.
L-TA 728E → Reifen & Service Moll, Magdeburg · Thu 23 Jul, 07:30Charging target of 80% scheduled before departure
Suggestion
Recent runs
Spring cycle: 96 appointments booked · 0 conflicts with customer bookings2 vehicles rescheduled, workshops notified automatically
MayApproved by you
Damage reports
Around 8,000 reports come in continuously every month – Lanterne reads each one the moment it arrives, and about 10 percent need a decision. It filters out the relevant new reports and enriches them with context. The decision stays with your team. Prepares
271Reports read live, since midnighteach read the moment it arrives, with photos and vehicle history
24Relevant cases preparedgrouped and enriched
189Duplicates linkedsame damage from multiple angles
58Already documented · closedflagged, logged, no new case
How it works
Reads every report the moment it arrives, along with photos, describes the damage, and groups it by vehicle, time and location on the vehicle. Already-documented damage is flagged and closed; multiple photos of the same damage are merged into one case.
Relevant new cases reach your team with context: the vehicle's damage history, the booking timeline, whether the ignition was on before the report. The groundwork is done right up to the decision point.
Never decides who caused a damage — it never assigns fault. Whether a case is pursued further is teilAuto's call – the final 10 percent stays deliberately with your team.
Flagged as they arrive
L-CF 6402 · Scratch, front bumper · just flaggedReport arrived 2 minutes ago · photo and history already attached
L-TA 5087 · Rim, front right · reported right after booking end~52% match, worth a lookContext: history shows a similar entry from 2024, different location · photos compared side by side
L-TA 2044 · reported stone chip already documented in Marchflagged and closed · traceable in the logbook
06:22Done · automatically
On average per month: around 8,000 reports become around 800 cases for your team – roughly 112 hours of review effort become roughly 11. Accuracy is measured offline beforehand against your April and May data.
Checklists into EBuS
The technician fills out the checklist once – at the vehicle, on their phone. Lanterne takes care of the rest. Asks first
How it works
Takes in the mobile checklist with its required fields and photos and enters it into the existing EBuS forms – via a dedicated, controlled account with exactly the permissions needed for data entry. No one types anything twice.
Checks before every entry that the form and fields are present as expected. If anything deviates or a required value is missing, the workflow stops and flags an exception instead of guessing.
Never overwrites existing entries. Every entry is logged with vehicle, time and account, and retained in the EU – during the pilot, one person approves every entry.
This week: 148 entries · 3 exceptions, all resolved same day · 0 overwritesevery entry in the logbook with vehicle, time and account
WeekLogged
Logbook
Every action with vehicle, time and approval – retained for at least six months, in the EU. One person can override any automated step. Click a row: the receipt shows what was read and what was done.
Today
Workshop status requests sent · 26 vehicles, 9 workshopsWorkshop monitoring · replies come in until 14:00
10:00Done · automatically
Read from Casix: 26 workshop bookings with weekend bookings9 workshops
26 status requests sent, one per vehiclePlate, booked return, 14:00 deadline
Reminder at 11:30 to 1 workshop with no responseKranz & Sohn, Halle
Daily plan suggested · 79 stops, 7 lists, 6 citiesTask allocation · waiting for approval from the service-vehicle lead
07:05Prepared
38 due tasks gatheredIntervals, INVERS, Cantamen reports
7 lists suggested by location and availabilitynot a performance rating
Waiting for approvalthe service-vehicle lead
24 relevant damage cases prepared · 189 duplicates linked, 58 closedDamage reports · context attached per case
06:30Prepared
271 reports read along with photosCantamen notifications
189 duplicates linked · 58 documented damages closedgrouped by vehicle, time, location
24 cases enriched and handed to the teamHistory, timeline, ignition
31 checklists entered into EBuS · all clearChecklists · account teilauto-lanterne, every entry logged individually
06:12Done · logged
31 entries via account teilauto-lanterneForm and required fields checked before every entry
0 exceptionsevery submission matched the EBuS form on the first try
This week
112 inspection appointments suggested · batch waiting for approvalBulk booking · workshop emails attached as drafts
ThuPrepared
Due list imported: 112 vehiclesfrom the fleet department, nothing retyped
Slots checked against customer bookings0 conflicts · 8 workshops
Batch waiting for approvalEmail drafts ready per workshop
Checklist exception resolved: required photo submitted, L-TA 348E enteredChecklists · returned to the technician, entry logged automatically afterward
TueApproved by you
Checklist returned to the technicianYour approval · required photo was missing
Entry logged automatically as soon as the photo arrivedAccount teilauto-lanterne · 09:41
1,912 damage reports processed · 176 cases handed off for reviewDamage reports · weekly total, all decisions with the team
WeekFiltered
1,912 reports read and groupedWeekly total, ~273 per night
176 cases enriched and handed to the team~9% relevant
Every decision loggedwith vehicle, time and approval
Analytics
What Lanterne handles for teilAuto – and the city-by-city view that didn't exist before. July, month to date.
8,000→ 800Damage reports per month, filteredTarget per validation · ~10% need a decision
112 h→ 11 hDamage review effort per monthmeasured offline, against April and May data
60→ 5 minDaily planning per morningone review instead of individual emails
0Booking conflicts in the batch112 inspection appointments, all built around customer bookings
Damage reports per weekdone automaticallyfor team review
15 Jun22 Jun29 Jun6 Julthis week
Checks per city · July
CityChecksAvg. durationper technician
Leipzig21418 min43
Dresden17621 min44
Halle9819 min49
Chemnitz6424 min32
Magdeburg4120 min41
Erfurt3722 min37
Overdue checks appear per city in the daily plan. Assignment is by location and availability, not a performance rating – the analytics measure the process, not individual staff.
Integrations
Lanterne builds on what teilAuto already uses. Nothing gets migrated, and Cantamen stays the source of truth. Write actions go through the same approvals as everything else.
Ca
CantamenSource of truth
Secure account
The record of every vehicle – and it stays that way. Lanterne reads the notifications (damage, complaints, "task completed"); actions run through a dedicated, controlled account and are logged individually.
EB
EBuSCentral work platform
Secure account
No API needed and no migration: Lanterne works in the same forms as your team, with the permissions needed for data entry. Checklists and inspection data land in the vehicle record, every entry in the logbook.
Cx
CasixFront-end bookings
Connected
Customer and workshop bookings, read and booked via the Casix API. The workshop runs, rebookings, and bulk inspection booking all run through here.
IN
INVERSTelematics
Connected
Charge status, ignition, status and position. Feeds the charging and telematics tasks in the daily plan and the context for damage cases.
@
EmailWorkshops & team
Connected
Status requests to workshops, their replies – free text included –, the personal task lists, and the 14:00 overview to the fleet department.
Rebooked. The customer booking now sits on L-TA 3980, and the workshop booking is extended to Tuesday. Everything's in the logbook.
L-TA 4127 won't be ready in time. L-TA 3980 can take over the booking.
Autohaus Brenner reports: the replacement part won't arrive until Monday, so the vehicle will be ready Tuesday. L-TA 4127 has a customer booking waiting from Saturday 09:00. L-TA 3980 is at the same station, free until Monday, and the same vehicle class – the customer keeps the same station and class and won't notice the swap.
Workshop booking read via CasixWorkshop reply at 11:52Customer booking Sat 09:00 checkedL-TA 3980 free until Monday
What changes on approval
Customer booking Sat 09:00→ L-TA 3980
Workshop booking L-TA 4127→ extended to Tue
For the customerno change
MKYour decision
How Lanterne got here· Step 2 of ~8 in the swap workflow, not the whole process
10:00: Status request sent to all 9 workshops with vehicles that have a weekend booking waiting.
11:52: Reply from Autohaus Brenner: "Replacement part won't arrive until Monday, vehicle ready Tuesday morning."
Receipt · what Lanterne read
Vehicle
L-TA 4127
Workshop booking
scheduled until Fri · new commitment Tue
Customer booking
Sat 09:00 – Sun 18:00
L-TA 3980: same class, no booking until Monday – suggested.
L-TA 2044: free, but an interior check is open · L-CF 3702: different vehicle class.
The vehicle swap stays your decision – Lanterne makes sure it's made by 14:00, not 18:00.
After approval, Lanterne rebooks via Casix, extends the workshop booking, and logs the decision and approval in the logbook.
All seven lists sent. Completion notifications from Cantamen reset the intervals automatically.
79 stops · 7 lists · 6 cities~5 min review
Friday across the fleet: six cities, ready to send in one review.
Cleaning falls due on a 14-day cadence, charging targets have to be met before the next booking, and damage and complaint tasks arrive from Cantamen overnight. Lanterne groups every task by region and orders each round by travel time, not task count. Leipzig runs two technicians, so a stop can move between them, or a cleaning that is still inside its window can wait for tomorrow. Review, adjust, and send them all in one step.
MKYour decisionReassign or skip anything that needs judgment, then send.
Friday · today's plan across the fleet
How Lanterne got here
Cleaning by interval, charging and telematics from INVERS, damage and complaint tasks from the Cantamen reports – all in one list per technician.
Each technician gets one round, ordered by travel time. Time-critical charging targets and complaints come first; cleanings follow by interval.
Receipt · assignment
Grouping
By region — technicians work their own area
Criteria
Location and availability – not a performance rating
Balancing
Where a region has two technicians, load is levelled
Whatever needs judgment is flagged. The rest is a five-minute review instead of an hour of assembly.
Everyone gets their list. Lanterne reads the "task completed" notifications from Cantamen and keeps the plans in sync – nothing runs twice.
112 appointments booked via Casix, 8 workshops emailed with plate, reason and pickup. Every booking is in the log.
112 inspection appointments, planned around every customer booking.
The due-list came from the fleet department. For each vehicle Lanterne checked the existing bookings and placed the appointment in a slot the workshop had confirmed in advance, spread across three weeks. Review the rows below, reschedule or drop anything, then one approval books exactly what is left on screen.
Customer bookings checked per vehicleCapacity from workshop pre-confirmationsSpread across 3 weeksOne email draft ready per workshop
Drop this month's due-list (CSV) here to start a new batch
Books on approval:112appointments·8workshops·8emailsOnly the rows left in below get booked.
112 appointments · 0 collisions with a customer bookingnothing needs review before approval
Every appointment sits in a booking-free window, in a pre-confirmed workshop slotSwitch to L2 or L3 for the breakdown
0 conflicts
By workshopshift a whole workshop's run if a window changes
+106 more, same ruleseach in a booking-free window, each in a pre-confirmed workshop slot
0 conflicts
Workshop emails · 8 drafts
Autohaus Brenner, Leipzig · 26 vehicles
Hello, for the coming weeks we have booked inspection appointments with you: L-TA 4890 (Tue 21 Jul, 08:00), L-TA 1276 (Tue 21 Jul, 10:00), L-CF 2907 (Wed 22 Jul, 08:30) and 23 more. Reason: scheduled inspection. Pickup at the Karl-Liebknecht-Straße station each time. Thank you.
KFZ-Service Lindemann, Dresden · 21 vehicles
Hello, we have booked 21 inspection appointments with you between 24 Jul and 06 Aug, including L-CF 5140 (Thu 24 Jul, 09:00). Reason: scheduled inspection. Pickup at the listed stations. Thank you.
Autohaus Vetter, Chemnitz · 17 vehicles
Hello, 17 inspection appointments are booked with you across three weeks, including L-CF 3312 (Wed 22 Jul, 10:30). Reason: scheduled inspection. Thank you.
Reifen & Service Moll, Magdeburg · 12 vehicles
Hello, 12 inspection appointments are booked with you, including L-TA 728E (Thu 23 Jul, 07:30). Reason: scheduled inspection. Thank you.
18 appointments at Kranz & Sohn and 18 across three further workshops, each with plate, reason and pickup. Drafts ready to send on approval.
MKYour decision
Booking via Casix
109 of 112 booked
109 booked straight through. 3 need a look.
Three vehicles picked up a customer booking after the batch was planned. Casix caught it before anything was double-booked — those three sit below, ready and waiting for a new slot.
Couldn't be booked · needs rescheduling
How Lanterne got here
Nothing is retyped: the list arrives as a file or straight from the plan.
Every slot sits in a booking-free window for the vehicle and a pre-confirmed window for the workshop.
Receipt · distribution
Period
21 Jul – 07 Aug
Workshops
Brenner 26 · Lindemann 21 · Kranz & Sohn 18 · Vetter 17 · Moll 12 · three more 18
Conflicts
0
Booking happens only after your approval — the whole batch, or the adjusted set you leave on screen.
Bookings via Casix, one email per workshop with plate, reason and pickup, every booking in the log.
Logged in Cantamen as a new damage — via the secure account, with vehicle, time and approval recorded. No cause recorded.
Scratch, rear left, on L-CF 2381 — new, and with the context to decide.
Three reports came in within seven minutes, all showing the same spot, so Lanterne merged them into one case. Nothing is documented at this spot in the vehicle's history. The ignition was on from 07:12 to 07:31; the first report arrived at 07:34, right after the booking ended. Lanterne supplies this context and never assigns fault. That decision stays with your team.
3 reports linked into 1 casePhotos described and comparedHistory: no prior damage at this spotIgnition timeline attached
3reports merged into one case — separate any that does not belong
Anchor
Photo · rear left
Report 1 · 07:34rear left, wide angle
97% match
Photo · rear left
Report 2 · 07:36rear left, close-up
94% match
Photo · rear left
Report 3 · 07:41rear left, angled
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 — rear left isn't visible in either photo
Cause
Not recorded. Lanterne works with what's available; who's responsible stays your team's decision.
Create as a new damage in CantamenRear left, documented here for the first time.
Link to an existing documented damageOnly if this is the same as the 2024 right door or 2023 front bumper entry.
Close · no actionLogged with your decision, nothing created.
What gets written to Cantamen
VehicleL-CF 2381
Locationrear left
Reportedtoday · 07:34
Photos3 attached
Accountteilauto-lanterne
Cause: not recorded. Lanterne never fills this field; who's responsible stays your team's decision.
MKYour decision
How Lanterne got here
189 duplicates merged, 58 already-documented damages marked and closed. Remaining: 24 relevant cases, and this is one of them.
Photos from the three reports show the same spot from different angles — one case, not three.
History: right door (2024) and front bumper (2023) are documented — rear left is new.
Receipt · history
Right door
documented 2024
Front bumper
documented 2023
Rear left
nothing on record
Lanterne delivers the work up to the decision point — the last 10 percent stays with teilAuto by design.
After your choice Lanterne creates the damage in Cantamen or closes the case — both logged, with decision and time.
The scratch on L-TA 3374's rear bumper was already reported six minutes earlier.
Two reports came in within six minutes, from two different renters at the same station – same spot, same angle, same light. Lanterne compared the photos and merged the second report into the first case. Nothing new was created; no one had to look twice.
2 reports compared96% photo matchSame vehicle, same 6-minute windowFiltered automatically · no new case
2reports compared — newest shown first, both viewable in detail
96% match
Photo · rear bumper
Report 2 · 07:41 (newest)rear bumper, wide angle — the one kept
Anchor
Photo · rear bumper
Report 1 · 07:35rear bumper, close-up — captured first
Receipt · why it was filtered
Report 1
07:35 · rear bumper, close-up
Report 2
07:41 · rear bumper, wide angle — same scratch, same edge, same light
Every checklist submitted overnight synced itself into EBuS.
Twelve technicians submitted 31 checklists between 05:40 and 06:50 – interior checks, cleanings, handovers. Every one matched the EBuS form on the first try: required fields present, photos attached, vehicle record correct. Nothing needed a second look.
31 checklists synced0 exceptions today12 technicians · 6 citiesEvery entry logged with vehicle, time, account
Received from phone at the vehicle12 of 12 fields, 1 photo
Checked against the EBuS formRequired fields + photo present
Entered into EBuSAccount teilauto-lanterne · 06:04
L-CF 309E · Cleaning · T. WeberLeipzig · submitted 06:10
06:10Synced
Received from phone at the vehicle8 of 8 fields, 2 photos
Checked against the EBuS formRequired fields + photos present
Entered into EBuSAccount teilauto-lanterne · 06:10
L-TA 2044 · Handover · M. RothErfurt · submitted 05:52
05:52Synced
Received from phone at the vehicle10 of 10 fields, 3 photos
Checked against the EBuS formRequired fields + photos present
Entered into EBuSAccount teilauto-lanterne · 05:52
L-CF 1873 · Cleaning · S. KaiserDresden · submitted 06:22
06:22Synced
Received from phone at the vehicle8 of 8 fields, 2 photos
Checked against the EBuS formRequired fields + photos present
Entered into EBuSAccount teilauto-lanterne · 06:22
+27 more, same checks, all cleareach logged with vehicle, time and account
Logged
This week
148 entries · 3 exceptions, all resolved same day · 0 overwritesevery entry in the logbook with vehicle, time and account
WeekLogged
Lanterne checks the form and required fields before every entry – if something is missing, it stops and flags an exception instead of guessing, instead of entering it. That's what would show up here; today there was none of that.