A button press. A sensor reading. A missed call. A device going offline. NocTel can use any of them to start the response you define.
Something happens.
NocTel recognizes the event and starts the next step.
One event can begin a simple notification, or a larger response across your organization.
Type it:
For more involved systems, start with a whiteboard sketch. Take a picture. NocTel turns it into an editable action map and asks questions where it needs more information.
NocTel can respond to events from anything that can report one.
Each one gives NocTel something useful to act on.
You don’t have to connect everything at once.
Start with the event that matters now. Add more when it becomes useful.
Events reach NocTel on their own radio, not your WiFi, not a cell signal.
A reading from the basement still gets through.
The same place you manage your phones shows every device you’ve connected.
The response is already moving.
Every action leaves a record.
NocTel Desk keeps the full path in one place.
An event isn’t off in its own app. Because it runs in the same Desk as the rest of NocTel, a single signal can ring a phone, page the halls, or change a screen the moment it happens.
Anything that can report an event: buttons, sensors, phones, screens, gateways, doors, queues, network connections, connected devices, and other systems. If it can signal that something happened, NocTel can act on it.
Not for the core. Buttons and sensors run on the same 900MHz and LoRa radio as the Now devices, through walls to a gateway that bridges to NocTel. WiFi can be one of the connected things, but the signal doesn’t depend on it.
Describe it in plain language, or sketch it on a whiteboard and take a picture. NocTel turns it into an editable action map and asks questions where it needs more. You set the rule once, and it runs on its own.
Now is for a person who presses a button to signal for help. Connected Devices is the wider idea: any event from any source becoming any response. Same radio network, same Desk.