Communication channels
Seven notification channels, with routing based on who owns the response.
InfiIoT supports email, SMS, Telegram, WhatsApp, Slack, Discord, and webhooks. Rules can fire on state changes, schedules, thresholds, or individual messages. Each event can follow a different route for operators, managers, and external systems.
The data path, including the hand-offs that usually cause trouble.
Define the trigger
Configure threshold crossings, state changes, schedules, or every-event rules for one device or an entire fleet.
Route by role
The operator can receive WhatsApp, the manager email, and the ticketing system a webhook from the same event.
Template the message
Messages include the asset, value, threshold, and timestamp so the recipient can judge the condition before opening the dashboard.
Escalate
Unacknowledged alerts re-route according to the escalation policy and remain visible until someone takes ownership.
Where teams use this integration.
Night-shift alarms that reach the duty operator
A 2 AM threshold breach can go to the duty operator's WhatsApp and escalate if it remains unacknowledged.
Tickets with the evidence attached
A webhook opens the ticket with the triggering telemetry, asset identity, and timestamp instead of relying on a forwarded screenshot.
One incident, several useful routes
The operator gets the immediate message, management receives a summary, and the ERP receives the structured event.
Want this wired into your stack?
Bring the source system, target system, and security constraints. An engineer will map the interface and the unresolved questions.