Skip to content
Service & spare partsFor every industry

Sort and route service requests

Fault reports from e-mail, phone and portal: AI links them to the unit, sets priority by contract and routes them to the right team.

Today

Fault reports arrive by e-mail, phone and portal and are sorted by hand. The serial number is often missing, and nobody sees at a glance which contract applies. Simple cases tie up experts while urgent ones wait in the queue.

An example

A customer writes to Talwerk Antriebstechnik: "Gearbox on conveyor line 3 is leaking oil, line still running." From serial number 21-0388 the agent identifies a GM-2040 gear motor under a premium contract with a four-hour response time. It sets the priority to high and routes the ticket to the southern service team, which specializes in gearboxes.
Fictional company, typical workflow.

Your data, wherever it lives

Today fault reports arrive by e-mail, as phone notes or through the customer portal; customers and service contracts sit in the CRM, and units, service history and past fixes in the ticket system. demi reads, understands and links them per report, unit and contract, with your rights. The AI routes each report in seconds and sets the priority by the contractual response time instead of someone sorting by hand, and service approves the reply to the customer.

Where the data lives today

  • E-mails
  • Phone & voice
  • Web & portals
  • CRM
  • Tickets
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 inbox, CRM, portal and CMMS. demi replaces nothing and relates every report to its unit, customer, contract, service history and the solution database. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Requests go to the responsible team by region and skill, and the contract sets the priority. Service approves every reply to the customer, and each ticket shows the rule that routed it.

  3. 3 · ActIntelligence Layer

    The agent identifies unit and contract and sets the priority from the contracted response time, as a fixed rule rather than a guess. It routes the ticket and attaches matching fixes from past cases, each linked to its case.

How it runs

  1. 1

    The report arrives by e-mail, through the portal or as a phone note.

  2. 2

    demi identifies serial number, unit, customer and contract; if something is missing, the agent asks.

  3. 3

    The agent sets the priority from the contracted response time and shows the rule.

  4. 4

    The ticket goes to the team for that region and skill, with history and similar cases.

  5. 5

    Service reviews the reply to the customer and releases it.

What changes

  • Customers get a first response sooner

  • Experts work on the hard cases

  • Contracted response times are kept

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

+256 hfreed per year

Assumptions and calculation

demi links each request to its machine, ranks it by contract and routes it; you solve the case.

8 min → 4.8 min per case

How does it run today?

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

How we calculate

400 service requests × 8 min × 40% × 1.0 (manual) × 12 months = 15,360 min = 256 h

Value per year, before demi costs

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

+$16,640

gained per year

256 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 channels can demi handle?

E-mail, customer portal forms, phone notes in the CRM and chat messages. demi replaces none of your systems, so you need no new ticket system. How the data from mailboxes and systems gets to demi, we clarify in a conversation. Tickets land where your service team already works.

How does the agent decide the priority?

By rules you define, mainly the contracted response time and whether the unit is down. The model does not guess the priority; it applies the rule and shows it in the ticket. Anyone who disagrees can override it with a reason.

What if the serial number is missing?

The agent searches the installed base by customer, site and description. If the result is not clear, it asks the customer or puts the candidates in front of service. It never assigns a unit on a guess.

Can demi also create a service quote?

Yes, when the case is not covered by contract or warranty. The agent drafts the quote with labor, spare parts and prices from the ERP. Service reviews and releases it before it goes to the customer.

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