Skip to content
Service & spare partsPumps & ValvesElectronics & SensorsMachinery & Plant EngineeringPlastics & Packaging+3

Video support that documents itself

The customer shows the machine on a phone camera, your expert guides them remotely, and demi records findings, steps and result.

Today

A video call saves the expert the trip: the customer or a colleague at the machine shows what is wrong on a phone and is guided step by step. Afterwards the ticket says little more than "solved by phone". What was shown, measured and replaced only the expert knows, and the next identical case starts from zero with someone else.

An example

Night shift at Tarvina: the cup filler for 250 g dips, a special machine from Ebert & Lorenz Maschinenbau, rejects more and more cups for leaking seals. The shift lead video-calls Ebert & Lorenz's on-call service expert and shows him the dosing and sealing stations on the phone. After 25 minutes the cause is clear: the nozzle drips after each shot, and dip lands on the cup rim where the lid film should seal. demi records the finding, the seven steps up to resetting the suck-back and the result with still images, and puts the hygiene release before restart on the list. Tarvina receives the report that same night, without internal notes, and once approved, the entry "Leaking seal" is in the knowledge base, also for customers with this machine. Three weeks later the late shift on line 2 fixes the same fault itself with that entry, without calling anyone.
Fictional company, typical workflow.

Your data, wherever it lives

Today video calls are not saved at all or vanish into the video tool, photos sit in phones and chats, the case note in the ticket, manuals as PDFs in folders and the maintenance history in the CMMS. demi reads these sources, understands what was shown and said on the call, and links it with the unit, the ticket and earlier cases, with your rights. AI writes the report and the knowledge entry in minutes instead of in the evening, and your expert approves what counts.

Where the data lives today

  • Photos, video & audio
  • Chats
  • Tickets
  • Wiki & intranet
  • PDFs
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 video call, chat, ticket system, CMMS and wiki. demi replaces nothing and links the call's audio, images and chat messages with the unit, serial number, maintenance history and earlier cases. Every finding is tied to a time stamp and a still image.

  2. 2 · PermitPermission Layer

    Recording happens only when everyone on the call agrees, and you set how long recordings are kept. The customer receives the report for their unit but never sees internal notes on cost or warranty. A knowledge base entry becomes visible only after the expert approves it, and only to the roles you choose.

  3. 3 · ActIntelligence Layer

    The agent transcribes the call, picks out findings, actions, readings and result, and keeps a still image for every step. It takes a reading only when it is clear in the picture or the conversation and flags the spot otherwise. From the solved case it drafts a knowledge base entry with symptom, cause and fix, and checks whether a similar one already exists.

How it runs

  1. 1

    The customer or operator starts the video call from a link in the ticket and shows the machine on the phone camera.

  2. 2

    demi identifies the unit from its nameplate or code and puts its history and similar cases next to the picture for the expert.

  3. 3

    While the expert guides, demi records findings, steps, readings and result, each with a time stamp and a still image.

  4. 4

    After the call the report is in the ticket; the expert reviews it, adds to it and approves it.

  5. 5

    If wanted, it becomes a knowledge base entry, and the next identical case starts with the solution.

What changes

  • Every remote session documented, with no writing afterwards

  • The next identical case starts with the fix, not from zero

  • More cases solved remotely, fewer trips

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

+120 hfreed per year

Assumptions and calculation

demi records findings, steps and result of the call; your expert checks and approves.

25 min → 15 min per case

How does it run today?

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

How we calculate

60 video support calls × 25 min × 40% × 1.0 (manual) × 12 months = 7,200 min = 120 h

Value per year, before demi costs

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

+€7,800

gained per year

120 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

Do we need a special app or smart glasses?

No. A phone with a camera is enough; the call starts from a link in the ticket or in the video tool you already use. How recordings and chat get from that tool to demi, we clarify in a conversation. The expert can use smart glasses if you have them, but they are not needed.

Can the video call be recorded?

Yes, if everyone on the call agrees beforehand. The recording is announced at the start, and you decide how long it is kept. What should stay out of the picture, such as recipes or other equipment, the customer keeps off camera; the report then holds only findings, steps and result.

When does a solved case become a knowledge base entry?

Only once the expert has reviewed the report and approved the draft. demi proposes symptom, cause, fix, parts needed and the key still images. If a similar entry already exists, demi adds to it instead of creating a second one.

What does the customer see of the report?

What you release: findings, steps and result for their unit, with still images if you like. Internal notes, for example on cost, goodwill or a possible warranty claim, stay in the ticket. The report goes out in the language the customer needs.

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