The customer's email, read at zero latency

The problem

The rating changes by email, and the email is read after the batch has started.

A chemical customer emails to say the next order needs a different packing group — a more demanding rating. The email lands in an inbox checked hours later, by which point a batch is already scheduled to start that afternoon with the old rating. Critical customer alerts arrive by email to one person who can't watch the inbox in real time, so by the time they're read, production decisions already in motion have to be broken.

• A chemical customer writes to say the next order needs a different packing group: a more demanding rating, with different closure, hoop or wall requirements. For a fiber drum that can mean another closure, a steel hoop where there was none, or a liner the old order did not need.
• The message lands in an inbox checked hours later. By then a batch is scheduled to start that afternoon with the old rating. Nobody did anything wrong: the information simply arrived through a channel nobody watches continuously.
• Critical alerts reach one person who cannot watch the inbox in real time, competing with quotes, invoices and routine delivery questions. A change of packing group looks like any other customer email until someone reads it carefully.
• So by the time it is read, production decisions already in motion have to be broken: drums wound for the wrong group, closures already ordered, a delivery date at risk. In dangerous-goods packaging, a drum made for the wrong group cannot be relabeled and sold as the right one.

How it fits the IRIS system

Connect in silent copy on the order mailbox — the alert arrives as an action.

iLEAN Connect sits in silent copy on the mailbox 24/7. At zero latency it extracts the message's intent, the affected order and the new packing group, cross-checks the ERP, and alerts the production lead with a concrete action — not just "you've got an email".

Reading the email sooner is only half of it. What matters is that the production lead receives the affected order, the new packing group and what has to change on the line, so the decision takes seconds instead of a phone call to find out what the email meant. And if the batch has not started yet, the change costs a reschedule instead of a pallet of drums.

See the full IRIS architecture →

Before and after

Today's customer alert versus the alert crossed with the order

Aspect	Today, in the inbox	With iLEAN Connect
When a packing group change is read	Hours later	At zero latency
Link to the affected order	Someone looks it up	Identified in the ERP automatically
Batch scheduled with the old rating	Often already running	Flagged before startup
What the production lead gets	A forwarded email	A concrete action on the order
Routine messages	Mixed in with the critical ones	Kept out of the alert
Final decision	Whoever reads it first	The production lead, with context

Before: hours of human latency and decisions based on what was read hours earlier. After: replanning in seconds, based on the live order.

Impact estimate

Impact estimate — to be validated with your numbers.

The block below is an estimate to be validated against your plant's actual data. We put it forward so the committee has an order of magnitude; we refine it during the assessment.

• Estimated payback 3-7 months, depending on how often critical alerts arrive.
• It comes from avoiding batches made with the wrong rating, which in dangerous-goods packaging cannot simply be relabeled. Each one is kraft paper, adhesive, hoops and closures turned into stock nobody ordered.
• From hours of human latency to replanning in seconds, based on the live order rather than on what was read hours earlier.
• And the customer sees a supplier that reacted the same day to a change in specification. For a chemical customer, that responsiveness is part of what keeps the supplier on the approved list.

Estimated payback 3-7 months depending on how often critical alerts arrive, from avoiding batches made with the wrong rating. Estimate to be validated.

And the fair question from the production manager

“How does it know an email is about the rating and not a routine question?” — classifying the intent of a message and pulling out the order and the packing group is an anchored task, where the best models drop below 1.5% error [1]. And it never changes anything on its own: it proposes the action and the production lead decides. Nothing in the schedule moves without a person.

^[1] OpenAI paper "Why Language Models Hallucinate", 2025 — on the reliability of AI in anchored tasks.