Today
Customers ask for delivery dates every day. Sales has to check with planning, purchasing and the warehouse. Answers take hours and often stay vague.
An example
A customer asks Talwerk Antriebstechnik about order 45-2290. The agent sees that assembly is waiting for a gearbox housing the supplier has confirmed for Thursday. It drafts the answer: shipping on Tuesday of the following week, with exactly that reason.
Your data, wherever it lives
Today delivery-date requests come by e-mail, phone or the customer portal, while the customer order, purchase orders and shipping data sit in the ERP and production confirmations in the MES. demi reads, understands and links them into one order chain per customer order, with your rights. The AI finds the bottleneck and works out the date from confirmations and confirmed supplier dates in minutes instead of hours of asking around, and your sales team confirms it to the customer.
Where the data lives today
- E-mails
- Phone & voice
- Web & portals
- ERP
- MES
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, MES and e-mail. demi replaces nothing and joins the sales order, production orders, confirmations, purchase orders for critical parts and shipping data into one order chain.
- 2 · PermitPermission Layer
The customer sees date and status, never internal capacity. Production planning approves a changed date before sales promises it, and this is recorded.
- 3 · ActIntelligence Layer
The agent follows the order across all sources of the case, finds the current bottleneck and drafts an answer with the date and the reason. It derives the date from confirmations and confirmed supplier dates, not from an estimate, citing the order number.
How it runs
- 1
The date request arrives by e-mail, phone note or portal.
- 2
demi finds the order and every production and purchase step linked to it.
- 3
The agent checks confirmations, open operations, purchased parts and shipping.
- 4
It names the bottleneck and derives a realistic date from it.
- 5
Sales sends the answer; a new date goes to planning first.
What changes
Answers without asking three departments
Fewer internal calls and follow-ups
Realistic dates with reasons
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
+300 hfreed per year
Assumptions and calculation
demi links order, shop-floor status and shipping into a date with evidence; you confirm it to the customer.
15 min → 9 min per case
How we calculate
250 delivery date requests × 15 min × 40% × 1.0 (manual) × 12 months = 18,000 min = 300 h
Value per year, before demi costs
Freed per year+300 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
+€19,500
gained per year
300 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 packageQuestions about this use case
Where does the date come from if production is behind?
From the actual status: confirmations from the MES, open operations in the ERP and confirmed dates for critical purchased parts. The agent names the bottleneck with its order number, so the answer can be traced. If a date is uncertain, it says so instead of naming a hopeful one.
Can customers ask through a portal themselves?
Yes, if you want that. In the portal customers see only their own orders with status and date. You can also start with answers through inside sales and open the portal later.
Who confirms a new date?
Production planning. When a date moves, the agent proposes the new commitment, and it reaches the customer only after planning has confirmed it. Every commitment is recorded on the order with person and time.
How much of our internal data does the customer see?
Only the date, the status and a plain reason, such as “waiting for a purchased part”. Capacities, suppliers and internal priorities stay inside. The Permission Layer only passes on the fields you have released for customers.
