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

Handle returns and repair quotes

The return opened with serial number and history, the repair scope proposed and the quote or credit note drafted.

Today

Returned units arrive with a short note and no history. Repair quotes are written from scratch every time, and the same no-fault-found cases keep coming back. What repair learns about the product rarely reaches engineering.

An example

An FU-24 frequency inverter from Wallner+Hardt Sensortechnik, serial number FU24-118207, comes back for the third time. The agent shows two earlier test bench runs with no fault found, suggests checking the firmware on the EtherCAT interface and drafts the quote without the part still covered by warranty.
Fictional company, typical workflow.

Your data, wherever it lives

Today returns arrive with a short note by e-mail or through the customer portal, delivery dates, warranty terms and spare-part prices sit in the ERP, past repairs in the CRM and test bench results in the MES. demi reads, understands and links them per unit and serial number, with your rights. The AI opens the case with its full history in minutes, proposes scope, parts and time from similar repairs and drafts the quote or credit note, and service approves.

Where the data lives today

  • E-mails
  • Web & portals
  • ERP
  • CRM
  • MES
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 ERP, CRM, MES and e-mail. demi replaces nothing and ties every return to the unit by serial number, its repair history, test bench results, warranty terms and spare-part prices. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Service sees its own cases, and customers see only released quotes. Service approves quotes, management also approves credit notes above a set limit, and every approval is recorded in the case.

  3. 3 · ActIntelligence Layer

    The agent checks the warranty status by fixed rules from delivery date and terms and proposes scope, parts and time from similar past repairs, each with its source. It reports recurring no-fault-found cases to quality and engineering in one batch.

How it runs

  1. 1

    The customer registers the return by e-mail or portal; demi opens the case with the serial number.

  2. 2

    The agent shows warranty status, past repairs and test results for this unit.

  3. 3

    After the incoming inspection, it proposes repair scope, parts and time.

  4. 4

    It drafts the repair quote or credit note; service reviews and releases it.

  5. 5

    Recurring patterns go to quality and engineering in one summary.

What changes

  • Repair quotes based on real repair data

  • Fewer repeat returns

  • Engineering learns what fails in the field

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

+192 hfreed per year

Assumptions and calculation

demi opens the return with its history and drafts the repair scope and quote; you approve.

30 min → 18 min per case

How does it run today?

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

How we calculate

80 returns × 30 min × 40% × 1.0 (manual) × 12 months = 11,520 min = 192 h

Value per year, before demi costs

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

+$12,480

gained per year

192 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

Can customers register returns themselves?

Yes, through a portal form or by e-mail. demi reads the serial number and fault description and opens the case. If something is missing, the agent asks the customer before the unit is shipped.

How does demi decide between warranty and paid repair?

By delivery date, warranty terms and findings as recorded in the contract and the ERP. The agent applies these rules and shows them in the case. Service makes the decision, and management approves credit notes above the limit.

Can demi read our test bench results?

Yes, if the test bench stores its results as files, in the MES or in a database. demi links every result to the serial number. We work out with you how the test bench data reaches demi. The next time the unit comes back, its full test history is in the case.

Where do the repair times in the quote come from?

From past repairs of the same series with the same fault pattern, with the source shown in the quote. Parts and prices come from the BOM and the ERP. If there is no comparable repair, the agent says so and leaves the time open.

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