Today
At night and at weekends, a customer with a stopped machine reaches a voicemail or wakes the on-call technician, often for a question the manual answers. Half asleep, the technician has to work out which unit, which contract and which fault it is, without the file in front of him. Meanwhile real emergencies wait as long as trivial ones.
An example
At 3:10 a.m. the shift leader of a paper mill calls Conveyra Fördertechnik: the 10-tonne overhead crane in the roll store will not lift any more. demi recognizes the number, matches crane BK-17-0291 and the maintenance contract with night cover and asks what the radio remote control shows: overload, although only a 6-tonne paper roll hangs on the hook. From two earlier cases on identical cranes demi knows the approved operator steps: set the load down, acknowledge the fault with the reset button, test lift without load. The crane lifts again, but the message returns on the next lift. demi wakes the on-call technician with a summary naming the load measuring device as the likely cause; he is on site at 4:45 a.m. with the right spare part.
Your data, wherever it lives
What a customer with a stopped machine needs at night is spread out today: contracts and response times in the CRM, manuals as PDFs in the DMS, earlier faults and their fixes in the ticket system, spare parts in the ERP, fault codes in the controller. demi reads, understands and links it per unit, with your rights. The AI settles in minutes what would otherwise get the technician out of bed, and your on-call team decides when to drive out.
Where the data lives today
- Phone & voice
- CRM
- Tickets
- DMS & archive
- PDFs
- ERP
- Machines & sensors
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: phone, CRM, ticket system, DMS, PDF manuals, ERP and, where connected, machine data. demi replaces nothing and links caller, customer, contract and response time with the unit, its manuals, earlier faults and the fixes your service team has approved. If the unit is connected, demi sees the fault code and latest messages itself.
- 2 · PermitPermission Layer
demi gives information on a unit only once the caller is recognized as the customer's contact, by the stored number and the unit or customer number. On the phone demi passes on only steps your service team has approved for operators; work on safety devices or inside the control cabinet stays with specialists. Whatever the contract does not cover, demi says openly, and a chargeable call-out is created only with the caller's consent.
- 3 · ActIntelligence Layer
The agent holds the conversation in natural language, recognizes unit and contract and asks the diagnostic questions your service team has set for this fault. It helps with approved fixes from the manual and earlier cases and decides by your rules whether to wake the on-call technician. The technician gets a summary with unit, fault, steps taken and likely cause.
How it runs
- 1
Outside service hours demi answers the service number and says that a digital assistant is speaking.
- 2
demi recognizes customer, unit and contract from the phone number and unit number and asks about the fault.
- 3
The agent asks the set diagnostic questions and guides the caller through approved fix steps.
- 4
If that does not help and the contract covers a call-out, demi wakes the on-call technician with a summary; otherwise it opens a ticket for the morning.
- 5
In the morning your service team sees every night call with conversation, steps and outcome in the ticket.
What changes
Customers reach someone at night who knows their unit
On-call technicians are woken only when it is needed
Every night call is documented by the morning
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
+108 hfreed per year
Assumptions and calculation
demi takes night calls, helps with approved fixes and wakes the technician only when needed.
30 min → 21 min per case
How we calculate
60 calls outside service hours × 30 min × 30% × 1.0 (manual) × 12 months = 6,480 min = 108 h
Value per year, before demi costs
Freed per year+108 h
Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.
= Value per year, before demi costs
+$7,020
gained per year
108 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 packageQuestions about this use case
Does demi give instructions on the phone that could be dangerous?
No. demi only passes on steps your service team has approved for operators, word for word from the manual or the solution database. Work on safety devices, brakes or inside the control cabinet is not part of that; a technician comes for those.
When does demi wake the on-call technician?
By rules you set: contract and response time, type of fault, whether the unit is down, danger to people or the environment. If there is danger, demi calls through at once; if people are at risk, it first tells the caller to call the emergency services. Everything else becomes a ticket for the morning, and the customer hears when someone will get back to them.
What does the technician have in hand when woken?
A short summary as a message, read out on request: customer, unit, contract, fault, steps taken and the likely cause from earlier cases, plus the relevant manual pages. He does not need to ask anything and can decide right away whether to drive out.
Does the hotline understand customers who speak another language?
Yes. demi holds the conversation in the caller's language and writes the ticket in your service team's language. Fix steps come from the approved language version of the manual where there is one; otherwise demi hands over to the technician.
