Skip to content
Warehouse, shipping & traceabilityMachinery & Plant EngineeringAutomotive SuppliersLogistics & Ports

Report delays before the customer asks

Arrival is recalculated, the customer is informed and you get solutions proposed.

Today

Delays, damage and failed deliveries are often discovered when the customer calls. Dispatchers spend the day chasing carriers for status updates. That leaves little time to actually solve the problem.

An example

At Nordhanse a truck carrying a 40 ft container for a just-in-time delivery reports a 5-hour delay. The agent re-estimates arrival, drafts the message to the customer's goods receipt and proposes a partial delivery of 12 pallets (1,200 × 800) from the Hamburg warehouse. The dispatcher approves both.
Fictional company, typical workflow.

Your data, wherever it lives

Today transport orders sit in the TMS, customer orders in the ERP and each customer's contact rules in the CRM, carrier status messages arrive by e-mail and through carrier portals, and tracking events come from the trucks' telematics. demi reads, understands and links them per shipment and customer order, with your rights. The AI spots a delay as soon as it is reported rather than when the customer calls, recalculates the arrival and drafts the customer notice, and your dispatcher decides on the fix.

Where the data lives today

  • ERP
  • CRM
  • E-mails
  • Web & portals
  • Telematics
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the TMS, ERP, e-mail and portals. demi replaces nothing and links transport orders, carrier status messages and tracking events with customer orders and each customer's contact rules. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    The dispatcher chooses the solution, such as rerouting or a partial delivery, and approves the message to the customer. Customers see only their own shipments, and every message is recorded.

  3. 3 · ActIntelligence Layer

    The agent detects exceptions in the status messages and re-estimates arrival traceably from recorded events and the lane's history. It drafts the customer notice and proposes options, every detail citing its status message.

How it runs

  1. 1

    Status messages and tracking events come in continuously.

  2. 2

    The agent spots deviations from the plan and re-estimates arrival.

  3. 3

    It drafts the customer notice and proposes solutions.

  4. 4

    The dispatcher picks the solution and approves the message.

  5. 5

    The updates are ready to write back after approval, and the customer is informed.

What changes

  • Customers informed before they ask

  • Less status chasing

  • Exceptions resolved faster

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.

Assumption, editable

Your numbers

Result

+240 hfreed per year

Assumptions and calculation

demi spots delays, recalculates arrival and drafts the customer notice; you decide the fix.

15 min → 9 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

200 delivery exceptions × 15 min × 40% × 1.0 (manual) × 12 months = 14,400 min = 240 h

Value per year, before demi costs

Freed per year+240 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

+€15,600

gained per year

240 h ÷ 1,760 h per role = 0.1 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 package

Questions about this use case

Which carrier messages can demi read?

Status messages via EDI and interfaces, tracking events from portals and plain e-mails such as "truck stuck in traffic". demi matches every message to the right transport order. If a carrier sends nothing at all, that itself shows up as an exception.

How is the new arrival time estimated?

From the recorded status events and the lane's history, meaning how long comparable trips from this point actually took. The agent names the events the estimate rests on. An estimate is still an estimate, so you also see how certain it is.

Does a message go to the customer without approval?

Only if you allow it for simple cases, such as a shift within the agreed time window. Everything else goes to the dispatcher as a draft. Every message sent is recorded.

Can customers track their shipments themselves?

Yes, if you give them a view. Each customer sees only their own shipments; the rights come from the Permission Layer. New arrival times appear as soon as the dispatcher has approved them.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases