Skip to content
Service & spare partsPumps & ValvesElectronics & SensorsMachinery & Plant EngineeringConveying & Intralogistics+3

Live help on support calls, ticket written for you

When a customer calls, you see their machines, contracts and open cases at once. AI suggests fixes and writes the ticket afterwards.

Today

A customer calls, and while they wait, the hotline searches the CRM, ticket system, maintenance system and file share for their machine, the contract that applies and what happened last time. Often only one colleague knows the fix, and that colleague is on another call. What was agreed on the phone reaches the ticket incomplete or not at all.

An example

At Valbrecht, the clinical engineering team of a hospital calls: three VZ 248 infusion pumps raise occlusion alarms although the line is clear. Before the greeting is over, the hotline sees the customer's 140 pumps, the service contract with next-working-day response and two open repairs. The agent shows four earlier cases with the same fault; in three of them an infusion set not approved for the pump was the cause. The hotline asks about the set, the pattern holds, and when the call ends the ticket is ready with serial numbers, set lot and a note for quality assurance, which checks whether the case must be reported under the MDR.
Fictional company, typical workflow.

Your data, wherever it lives

What the hotline needs during a call is scattered today: customers and contracts in the CRM, open and solved cases in the ticket system, machines and maintenance in the maintenance system, spare parts in the ERP, manuals as PDFs in the DMS. demi reads, understands and links all of it per caller and device, with your rights. When the phone rings, AI shows what belongs to this customer, suggests fixes during the call and writes the ticket; your employee decides what is promised.

Where the data lives today

  • Phone & voice
  • CRM
  • Tickets
  • ERP
  • DMS & archive
  • 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

    Data sources in this case: phone system, CRM, ticket system, maintenance system, ERP and DMS. demi replaces nothing; it recognises the caller by number and links them to their machines with serial numbers, contracts, open tickets, spare part orders and manuals. Solved cases with a similar fault sit alongside, each linked to the case.

  2. 2 · PermitPermission Layer

    The call is transcribed only if the caller agrees at the start; without consent the hotline types keywords and gets the same suggestions. Everyone sees only the customers and contracts they may see in the CRM. demi creates the ticket only after the employee has checked it, and every commitment is recorded with name and time.

  3. 3 · ActIntelligence Layer

    The agent picks out device, fault and request during the call and shows matching fixes from past cases, each with its case and the page in the manual. Response time and warranty come from the contract, never from an estimate. After the call it sums up fault, checks done and agreements in a draft ticket.

How it runs

  1. 1

    The customer calls; demi recognises the number and opens their machines, contracts and open cases before the first word.

  2. 2

    If the caller agrees, demi transcribes and picks out serial number, fault and request.

  3. 3

    Next to the call, fixes from similar cases, manual pages and spare part status appear, each with its source.

  4. 4

    When the call ends, a draft ticket with fault, checks done and commitments is ready.

  5. 5

    The hotline checks and completes the draft and creates the ticket; a site visit or part goes to the responsible team.

What changes

  • Shorter calls, because nobody has to search

  • More cases solved on the first call

  • Every commitment made on the phone is in the ticket

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

+360 hfreed per year

Assumptions and calculation

demi shows machines, contracts and past fixes during the call and drafts the ticket; you check and release it.

12 min → 8.4 min per case

How does it run today?

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

How we calculate

500 support calls × 12 min × 30% × 1.0 (manual) × 12 months = 21,600 min = 360 h

Value per year, before demi costs

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

+€23,400

gained per year

360 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 package

Questions about this use case

Is every support call recorded?

No. demi transcribes only if the caller agrees at the start, for example by pressing a key after an announcement, or when the employee asks. What is kept is the ticket with summary and commitments; the transcript is deleted after the period your company sets. Without consent the hotline types keywords and gets the same suggestions.

Which phone system do we need for this?

No new one. demi is connected to your existing phone system or cloud telephony and so receives the caller's number and the call audio. We set up the connection to your system together. The hotline takes calls as usual and sees demi in a window alongside.

Where do the suggestions during the call come from?

From your own cases and documents: solved tickets, service reports, manuals and fault code lists for this customer's devices. Every suggestion names the case or manual page it comes from. If the agent finds nothing that fits, it says so instead of guessing.

Who decides what the customer is promised?

The person on the phone. The agent shows contract, response time and spare part stock; the commitment is made by a human. Only after that check is the ticket created and a site visit or delivery triggered.

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