Armillaire, the full simulation.
A manufacturer of air quality sensors whose two technicians answer installers in five languages. The case followed on this page, an installer stuck in front of a sensor that stays amber.
A manufacturer of air quality sensors whose two technicians answer installers in five languages.
Every installer guided through to the green light.
- Armillaire designs and assembles air quality sensors in Grenoble for schools and office buildings. They measure carbon dioxide and fine particles, then send their readings over the building network. The company has sixty people, with two sales offices in Munich and Milan.
- Sensors are installed by electricians and integrators, who call support whenever an indicator stays amber. Two technicians answer in French, German, Italian, English and Spanish, with colleagues’ help when they struggle with a language. Most calls are about the same settings and delay work on actual faults.
- European rules add further requirements. Since 1 August 2025, connected sensors sold in the EU have been required to meet cybersecurity requirements, and the Cyber Resilience Act has required since 11 September 2026 that actively exploited vulnerabilities be reported.
- An agent replies to installers on WhatsApp and by chat, in their language, and introduces itself as an AI. It asks for a photo of the indicator and the serial number, then guides troubleshooting using the model’s datasheet.
- When the diagnosis goes beyond the datasheets, or when a sensor seems faulty, it passes a complete file to the technician, with the photos, serial number, firmware version and latest readings.
What remains with the technical team
Technicians alone decide on a warranty exchange and on each firmware update. The security lead rules on each vulnerability report, and the agent triggers no remote update.
- Calls handled without a technician
- Time to complete a diagnosis
- Sensors returned with no fault found
- Technicians’ time on real faults
Vulnerability reports
Researchers and clients reporting a vulnerability use a dedicated address. The agent acknowledges receipt and immediately alerts the security officer, reminding them of the 24 and 72-hour deadlines under the Cyber Resilience Act.
The security officer qualifies each vulnerability and handles the notifications personally.
The technical file
For each firmware version, the agent maintains the list of software components and the evidence of compliance with radio requirements. It thus prepares for the Cyber Resilience Act obligations that will apply on 11 December 2027.
The quality manager signs each declaration of conformity.
Warranty returns
Each replacement request arrives with its diagnostic and sensor history. The agent then tracks the dispatch of the replacement sensor and the return of the old unit to the workshop.
The technician accepts or rejects each replacement.
Reports to managers
Every month, building managers receive a report on the air quality in their rooms, indicating which spaces to ventilate as a priority.
The product team sets the alert thresholds, and the agent does not provide any medical advice.
an installer stuck in front of a sensor that stays amber
An amber sensor, before and after.
- The call
- The installer calls support and reaches voicemail. He calls back an hour later.
- He messages the agent on WhatsApp in his own language and receives an immediate reply.
- First workstream
- The diagnostic
- The technician asks the usual questions over the phone for twenty minutes.
- The agent asks for a photo of the indicator light and the serial number, then follows the model guide step by step.
- First workstream
- The resolution
- The adjustment took a single line, yet still tied up a technician.
- The sensor turns green, and the agent records the intervention in the site file.
- First workstream
- The genuine fault
- A faulty sensor waits in line behind simple adjustments.
- The agent hands over a complete file to the technician, and the breakdown moves to the front of the queue.
- First workstream
- Vulnerability reporting
- A researcher reports a vulnerability via the contact form, and the message sits for a week.
- The report reaches a dedicated inbox, and the agent immediately alerts the security lead.
- Workstream 2
- Warranty replacement
- The sensor is returned to the workshop without a diagnostic, and the workshop restarts from scratch.
- The replacement request arrives with its diagnostic and the sensor history.
- Workstream 4
- Welcome
- It replies on WhatsApp and webchat in the installer's language, introducing itself as an AI.
- Identify
- It asks for the serial number and a photo of the indicator light, then retrieves the model and its firmware version.
- Diagnose
- It follows the model technical sheet step by step and checks each answer from the installer.
- Read telemetry
- It checks the latest readings and connection status of the sensor in read-only mode.
- Close
- When the sensor turns green again, it records the intervention in the site file.
- Hand over
- Outside documented procedures, or when facing a seemingly faulty sensor, it passes a complete file to the technician.
- The technician decides on a warranty replacement.
- Report
- Anything resembling a security vulnerability is immediately forwarded to the security lead.
- The security lead qualifies each vulnerability.
- Improve documentation
- It flags questions every week that the guides do not cover.
- The technical team updates the guides.
- WhatsApp Business and webchat
- The channels installers already use to message support.
- Support messages
- Technical guides
- Diagnostic procedures for each model in five languages.
- Read-only
- Sensor platform
- Connection status and readings for each sensor.
- Read-only
- Ticketing tool
- Site files and intervention history.
- File creation and viewing
- Reporting inbox
- The inbox receiving vulnerability reports.
- Acknowledgement of receipt and escalation to the security lead
- Support technicians
- Take over diagnostics outside documented procedures and decide on warranty replacements.
- The security lead
- Qualifies each vulnerability and handles notifications under the Cyber Resilience Act.
- The product team
- Keeps technical guides up to date and decides on every firmware update.
- The Munich and Milan offices
- Review answers in German and Italian, and support their local installers.
- The FDE
- Leads the engagement and writes agent rules alongside the team. He is accountable for every agent.
- Support agent
- Guides installers through the diagnostic.
- Case agent
- Prepares files handed over to technicians.
- Vulnerability triage agent
- Logs vulnerability reports and alerts the security lead.
- Supervisory agent
- Reviews diagnostics and reports any deviation from the guides to the FDE.
- The agent gives hazardous instructions.
- It only follows guides validated by the technical team. Any electrical work remains the installer's responsibility, and the agent never instructs on it.
- A vulnerability is left unanswered.
- Every report is immediately routed to the security lead, complying with the 24-hour and 72-hour deadlines under the Cyber Resilience Act.
- A sensor receives an unplanned update.
- The agent has no access to remote updates.
- An installer believes they are speaking to a human.
- The agent introduces itself as an AI from the very first message, as required by the AI Act since 2 August 2026.
- A translation distorts an instruction.
- Guides already exist in all five languages, and the Munich and Milan offices review German and Italian.
- We benchmark the baseline over the previous quarter, including inbound calls, their duration, diagnostics resolved on first contact, and sensors returned with no fault found. The technical team writes the diagnostic guides with us.
- The agent assists participating French installers, and a technician reviews every interaction.
- German and Italian installers switch to the agent, supported by the Munich and Milan offices.
- All languages are opened. We compare results against the baseline and decide on the next workstream with leadership.
- Calls resolved without a technician
- Share of requests closed by the agent without technician intervention, tracked in the ticketing tool.
- Diagnostic resolution time
- Time elapsed between the installer's initial message and the sensor returning to green.
- Sensors returned with no fault found
- Sensors returned to the workshop where no defect is found, compared against the baseline quarter.
- Technician time spent on genuine faults
- Share of technician time spent on faults and replacements, logged by them weekly.
Council of the EU, radio equipment cybersecurity
European Commission, Cyber Resilience Act, 11 Sept 2026