Reading out of range
Incident detected
A fridge, freezer, room, or transport reading moves outside the configured range long enough to count as a real incident.
Product feature
Temperature alerts and alarms with clear ownership.
KRYOS turns an out-of-range reading into a temperature alert, shipment temperature alert, or temperature alarm with fast routing, timed escalation, and one traceable record.
- Thresholds and delay rules are set per fridge, freezer, room, or transport unit.
- Acknowledgement, escalation, notes, and review history stay on one incident.
- SMS, push and email support the response path; WhatsApp is on demand and sound alarms come only from the device.
Live alert path
The system evaluates the threshold, routes the alert, escalates when needed, and closes with a clean incident record.
Policy applied
Threshold evaluated
Thresholds, delay windows, and severity logic decide whether this becomes a temperature alert or temperature alarm.
Delivery started
Alert routed
The incident is sent through the configured channels and ownership rules for that asset, team, and site.
No response timeout
Escalation triggered
If the alert is not acknowledged in time, reminders and escalation tiers move it to the next responsible person.
Record trail closed
Acknowledged and logged
Acknowledgement, notes, timestamps, and follow-up remain attached to the same incident record for review later.
SMSWhatsApp (on demand)PushEmailDevice sound alarm
One incident record keeps delivery, escalation, acknowledgement, and follow-up connected.
Alert operating model
Temperature alarms need asset-level thresholds, environment-specific alarm profiles, channel routing, escalation ownership, and one record that survives from first alert to final review.
Roles and permissions keep alert ownership clear
Clear alert response starts with clear boundaries: who sets policy, who works the incident, who escalates across teams, and who reviews the final record.
Alert delivery that matches how teams actually respond
Urgency, location and response ownership guide SMS, push and email routing. WhatsApp is available on demand; local sound alarms come only from the device, not the browser or app.
SMS
Immediate reach Immediate route for urgent incidents
SMS suits an urgent out-of-range alert where the responsible person needs a fridge temperature alarm or freezer temperature alarm on the phone immediately.
Push
In-app workflow Keep the response inside KRYOS
Push works when acknowledgement, investigation, or escalation should start directly in the product, not in a standalone message thread.
WhatsApp (on demand)
Shift and group visibility Route incidents to the on-duty team
When arranged on demand, WhatsApp helps surface incidents to the on-duty team across shift handoff, transport or field coordination. It is not included by default.
Email
Review distribution Share review-ready incident context
Email fits incident summaries, escalation context, and review-ready details for QA, supervisors, or stakeholders who need more than a short alert.
Device sound alarm
Device only Warn staff near the monitored unit
The device provides a local audible warning for nearby staff at the monitored fridge, freezer, room or storage area. The browser and app do not produce this sound alarm.
One incident screen keeps the response moving
When an alert fires, teams need current value, threshold breach, delivery status, ownership, acknowledgement, and next action in one place.
- The incident view keeps the monitored unit, breached threshold, and excursion window visible from the first alert.
- Current status, latest reading, and threshold context stay on screen so teams can judge severity before they react.
- Delivery status, acknowledgement, and escalation timing remain attached to the same incident instead of being split across separate tools.
- Notes and follow-up stay on the incident, so the team can continue the response without rebuilding context.
Live incident viewThreshold breachResponse state
Ongoing incident view
Align alert logic to the environments you monitor
Request a demo if you need help defining thresholds, escalation, or delivery channels. If your alert setup is already decided, you can go straight to order.
- Thresholds tuned by environment
- Escalation paths that match response teams
- Traceable incident history
