Skip to content
Management & reportingLogistics & Ports

Measure and report service levels per customer

On-time rate, damage and response times computed per customer, outliers explained for the customer review.

Today

Logistics customers expect a regular service-level report. It is assembled by hand from transport management, ERP and spreadsheets, and it shows percentages but no reasons. In the customer review, the answer to the first follow-up question is missing.

An example

For a retail customer, Nordhanse's monthly report shows on-time delivery below target in week 3. The agent explains: 14 of 52 container moves (40 ft) out of Hamburg arrived late, 9 because of a full motorway closure and 5 with one subcontractor. The account manager reviews the draft before it is sent.
Fictional company, typical workflow.

Your data, wherever it lives

Today shipments and status events sit in the TMS and telematics, orders in the ERP, damage claims arrive by e-mail with photos, the agreed service levels are in contract PDFs and the last report in a spreadsheet. demi reads, understands and links them per customer and shipment, with your rights. The figures follow the contract's definitions exactly, the AI explains every miss with the events behind it and drafts the report in minutes instead of an hour, and the account manager approves it.

Where the data lives today

  • Telematics
  • ERP
  • E-mails
  • Photos, video & audio
  • PDFs
  • Office files
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

    Data sources in this case: TMS, ERP, spreadsheets and e-mail. demi replaces nothing and links shipments, status events, damage claims and the service levels agreed per customer, each shipment with its events from pickup to delivery.

  2. 2 · PermitPermission Layer

    Account managers see their customers; branch management sees all. No report goes to a customer without the account manager's approval, and the sending is recorded.

  3. 3 · ActIntelligence Layer

    demi computes the key figures exactly as the contract defines them, from the recorded events; the language model only writes the text. The agent explains every miss with the events behind it.

How it runs

  1. 1

    The contractual service levels per customer are set up once.

  2. 2

    demi continuously reads shipments, status events and damage claims.

  3. 3

    The agent computes key figures per customer, week and lane.

  4. 4

    Each miss gets an explanation with the events behind it.

  5. 5

    The account manager reviews the draft and releases the report.

What changes

  • Reports without manual collecting

  • Every miss explained before the customer asks

  • Customer reviews built on facts

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

+144 hfreed per year

Assumptions and calculation

demi computes on-time rate, damage and response times per customer and explains outliers; you lead the review.

60 min → 36 min per case

How does it run today?

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

How we calculate

30 customer reports × 60 min × 40% × 1.0 (manual) × 12 months = 8,640 min = 144 h

Value per year, before demi costs

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

+€9,360

gained per year

144 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 key figures are supported?

The ones in your contracts, for example on-time pickup and delivery, damage rate, response time to enquiries or completeness of documents. New key figures can be added as long as the events behind them are recorded. If they are not, demi shows the gap.

Can we use the definitions from our contracts?

Yes, that is how it is meant to work. What counts as on time, which time window applies and which exceptions are excluded is set per customer according to the contract. The agent computes by that, not by a generic formula.

Can customers access the reports themselves?

If you want them to, for example through a customer portal with released reports. The customer then sees only their own shipments and only what has been released. Internal notes and other customers' data stay out.

What about delays that were not our fault?

The agent assigns every miss to its cause, such as a road closure, waiting time at the terminal or a subcontractor. Whether a cause is excluded from the score is set by your contract, and demi computes accordingly. The report shows both: the figure and the reason.

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