Today
For every traffic jam, busy ramp and closed goods receipt, the driver calls dispatch, often while driving and often in another language. The dispatcher then calls the customer, takes notes on the side and looks up the next order. At the end of the month there is no proof of how long the truck waited at the customer, and detention is not charged.
An example
At Nordhanse a driver calls the driver line at 14:10 and says in Polish: “Jam before the Elbe tunnel, about 40 minutes late.” The agent recognises trip and container, calculates from position and the driving times on that route an arrival at the customer in Neumünster of 15:45 instead of 15:05 and sees that the customer's time window ends at 15:30. It proposes moving the window to 16:00 and drafts the message to goods receipt. At the next stop the driver reports “ramp busy, I'm waiting”; the agent records arrival and departure from telematics, 1 hour 50 minutes, and prepares the waiting time for invoicing under the agreed terms. The dispatcher releases both.
Your data, wherever it lives
What happens on the road is scattered today: drivers' updates reach dispatch as phone calls, positions sit in telematics, trips and time windows in the TMS and ERP, waiting-time rules in contracts as PDF and arrangements with customers in e-mails. demi reads, understands and links it per trip and order, with your rights. The AI turns one sentence from the driver into a new arrival time and a customer message within seconds, and dispatch decides.
Where the data lives today
- Phone & voice
- Telematics
- ERP
- E-mails
- PDFs
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: voice updates by call or voice message, telematics, trips and orders from the TMS and ERP, customer contacts and contracts from e-mails and PDFs. demi replaces nothing and links every update with driver, vehicle, trip and order, with position and driving times from telematics, with customers' time windows and with the agreed waiting time.
- 2 · PermitPermission Layer
Drivers see only their own trips, customers only their own shipments, dispatch sees everything. demi uses tracking for trips and arrival times, not to monitor drivers' performance, as your works agreement sets out. Customer messages and waiting-time invoices go out only after an authorised person releases them, and every release is recorded.
- 3 · ActIntelligence Layer
The agent understands updates in Polish, Romanian or Turkish too, recognises trip and order and classifies the update: delay, busy ramp, damage, missing papers. It calculates the new arrival from position, remaining route and the measured driving times on that route, and checks the time windows of the following stops and the remaining driving time. It takes waiting times from telematics data, not from memory, and drafts the customer message and the invoice.
How it runs
- 1
The driver calls a fixed number or sends a voice message, in their own language and hands-free.
- 2
demi recognises driver, trip and order and understands what has happened.
- 3
The agent recalculates the arrival, checks time windows and driving time and shows the effect on the next stops.
- 4
It drafts the message to the customer and records waiting times with arrival and departure from telematics.
- 5
Dispatch releases the message and the waiting-time invoice or replans the trip.
What changes
Fewer phone calls to dispatch
Customers hear about delays before they ask
Waiting times documented and charged
What does it bring you?
Check it with your own numbers
Every starting value is an assumption you can change. The calculation sits right below, step by step.
Your numbers
Result
+320 hfreed per year
Assumptions and calculation
demi understands the voice update, recalculates arrival and drafts the customer message; dispatch releases it.
8 min → 4.8 min per case
How we calculate
500 driver updates × 8 min × 40% × 1.0 (manual) × 12 months = 19,200 min = 320 h
Value per year, before demi costs
Freed per year+320 h
Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.
= Value per year, before demi costs
+€20,800
gained per year
320 h ÷ 1,760 h per role = 0.2 full-time roles
An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.
Combine with more cases and get the packageQuestions about this use case
How does a driver report while driving?
Hands-free: drivers call a fixed number through the hands-free kit or send a voice message. demi recognises them by their number and the order they are driving. How the updates reach demi, we clarify in conversation.
What if demi does not understand an update clearly?
Then the agent asks once, briefly, for example which stop is meant. If it stays unclear, the update goes straight to dispatch with recording and transcript instead of demi guessing an arrival time.
How reliable is the new arrival time?
The agent calculates it from the telematics position, the remaining route and measured driving times on that route at the same time of day. It treats the driver's estimate as a hint, not as the result, and shows both side by side. Without a position, the time is marked as the driver's estimate.
Is every waiting time charged automatically?
No. The agent prepares the invoice with arrival, departure, free time and the contract clause. Dispatch or the account manager decides whether it goes to the customer, and the release is recorded.
