Today
Warranty claims are decided case by case, and the result depends on who happens to check. Delivery date, contract and findings sit in different systems. Costs caused by a purchased part are rarely recovered from the supplier.
An example
At Talwerk Antriebstechnik, a customer's GM-2040 gear motor fails after 14 months; it was delivered on 12 March 2025 with a 24-month warranty. The findings show damage to the purchased output bearing. The agent proposes warranty, points to two identical cases from last year and drafts the recovery claim to the bearing supplier.
Your data, wherever it lives
Today warranty claims arrive by e-mail, through a portal or in the CRM, delivery date and serial number sit in the ERP, contract terms and supplier quality agreements as PDFs, and findings and photos of returned parts in the QMS. demi reads, understands and links them per unit and customer, with your rights. The AI puts a reasoned proposal with similar past cases on every claim in minutes, no matter who is checking, and drafts the recovery claim for purchased parts; service decides.
Where the data lives today
- E-mails
- Web & portals
- CRM
- ERP
- PDFs
- Photos, video & audio
- QM system
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
Data sources in this case: the ERP, CRM, QMS and e-mail. demi replaces nothing and links every claim to delivery date, serial number, contract terms, service history, findings on returned parts and supplier quality agreements. Every claim is tied to its unit and customer.
- 2 · PermitPermission Layer
Service sees the claims of its own customers and decides; above a set value, management approves as well. Purchasing handles supplier recovery, and every decision is recorded with its reason.
- 3 · ActIntelligence Layer
The agent checks eligibility by fixed rules against delivery date and contract term and proposes a decision alongside similar past ones, every reason with its source. If a purchased part caused the failure, it drafts the recovery claim.
How it runs
- 1
The claim arrives by e-mail, through the portal or from the CRM.
- 2
demi links it to unit, serial number, delivery and contract.
- 3
The agent checks the warranty period and terms and shows similar past cases.
- 4
It proposes warranty, goodwill or rejection, with reasons and sources.
- 5
Service decides; for purchased parts, the recovery draft goes to purchasing.
What changes
Similar cases get the same decision
Costs from purchased parts go back to the supplier
Customers get a reasoned answer sooner
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.
Your numbers
Result
+192 hfreed per year
Assumptions and calculation
demi checks each claim against contract, delivery date and history and proposes a decision; you decide.
40 min → 24 min per case
How we calculate
60 warranty claims × 40 min × 40% × 1.0 (manual) × 12 months = 11,520 min = 192 h
Value per year, before demi costs
Freed per year+192 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
+€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 packageQuestions about this use case
How do goodwill decisions become consistent?
For every claim, the agent shows similar past cases with their decision and reasons. You set rules for goodwill, for example by unit age, contract type or customer status. If someone deviates, the reason is recorded.
Can demi recover costs from suppliers?
demi prepares the recovery: findings, part number and batch, costs from the ERP and the matching clause of the quality agreement. The agent drafts the claim, and purchasing reviews and sends it. Open claims stay visible until they are settled.
Who makes the decision?
Always a person. The agent proposes and gives reasons; service decides. Above a value limit you set, management approves as well, and every decision is recorded with its reason.
What if the delivery date in the ERP is wrong?
The agent uses the date from your data and shows its source. If it conflicts with other records, such as the delivery note or commissioning date, it flags the conflict instead of deciding. Corrections are written back only after approval.
