Skip to content
Service & spare partsPumps & ValvesElectronics & SensorsWater & EnvironmentMachinery & Plant Engineering+3

The right technician for every job

Each proposal weighs skills, parts and contract deadlines, so fewer second visits are needed.

Today

Dispatch lives in one planner's head and on a wall board. Technicians arrive without the right part or certificate, so a second visit is needed. Emergency deadlines in service contracts slip through.

An example

At Conveyra Fördertechnik an emergency call comes in at 9:00: a B 800 belt conveyor in an ATEX area has stopped. The agent proposes the second-nearest technician, because only she holds the explosion-protection certificate and carries the right gear motor on her van. The 4-hour response time in the contract is met.
Fictional company, typical workflow.

Your data, wherever it lives

Today service tickets sit in the ticket system, installed base, maintenance contracts and van stock in the ERP and CRM, technicians' skills and certificates in spreadsheets or the HR system, and the plan on a wall board and in calendars. demi reads, understands and links them per job, with your rights. The AI proposes the right technician in seconds, giving skill, part in the van and contract deadline as reasons, instead of one planner matching it all in their head, and dispatch confirms the job.

Where the data lives today

  • Tickets
  • ERP
  • CRM
  • Office files
  • HR system
  • Calendars
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 ERP, CRM, field service app and calendars. demi replaces nothing and joins service tickets, installed base, maintenance contracts, technician skills and certificates and van stock into one record per job. demi writes back only after approval.

  2. 2 · PermitPermission Layer

    Dispatchers see every job in their region; technicians see their own plan and customer data only for jobs assigned to them. Dispatch confirms every plan before the technician receives it, and this is recorded.

  3. 3 · ActIntelligence Layer

    The agent ranks technicians by skill, certificate, location and contract deadline and checks that the parts are on the van or in stock; required qualifications and deadlines are hard rules. It backs every proposal with the ticket and contract and replans when a job runs over.

How it runs

  1. 1

    A ticket comes in; demi links the unit and the contract

  2. 2

    Determine required qualification, deadline and parts

  3. 3

    Rank technicians by fit, with reasons

  4. 4

    Dispatch confirms, the technician accepts

  5. 5

    When a job runs late, demi proposes a new plan

What changes

  • Fewer second visits

  • Contract deadlines checked on every assignment

  • Planning knowledge no longer in one head

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

+180 hfreed per year

Assumptions and calculation

demi proposes the right technician by skills, parts and deadlines; you schedule the job.

10 min → 7 min per case

How does it run today?

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

How we calculate

300 service jobs × 10 min × 30% × 1.0 (manual) × 12 months = 10,800 min = 180 h

Value per year, before demi costs

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

+€11,700

gained per year

180 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

Does demi replace our scheduling software?

No. demi works with your existing data and writes the confirmed plan back only after approval. What is new is a reasoned proposal that weighs ticket, contract, qualification and parts together.

How are skills and certificates kept up to date?

Where they already live today, for example in HR records or a spreadsheet. demi reads them with their expiry dates. When a certificate expires, the technician is no longer proposed for those jobs and dispatch gets an early warning.

Can technicians accept or decline jobs?

Yes. The technician sees the job on their phone and accepts, or declines with a reason. If they decline, demi proposes the next-best technician.

Who makes the final call?

Dispatch, always. demi proposes and explains; nothing is scheduled until it is confirmed. Every decision is recorded.

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