NounDesk alerts fire on rules you can tune: device offline beyond a threshold, non-compliant, security risk, lost mode, wipe started or completed, app install failed, storage almost full, blocked app installed, and enrollment code expired. Alerts are grouped into Security, Compliance, Device, Application, Command and Enrollment categories, can be acknowledged and resolved, resolve themselves when the problem clears, and are delivered as email digests to the people you choose plus an in-app bell.
The point of managing your phones is not to stare at a dashboard. Alerts fire on rules you can tune and leave you alone the rest of the time.
Alerts belong to one of six categories, so the owner and whoever handles the job app do not have to wade through each other's noise.
Route Security to the owner and Application to whoever handles the job app.
Open an alert, acknowledge it to show you are on it, and resolve it when it is fixed. Better still, most resolve themselves.
Alerts reach you where you already are, without you having to remember to go and look.
The point of managing your phones is not to stare at a dashboard. It's to be told when something needs you, and left alone the rest of the time.
Every alert becomes part of the history your reports draw on. The pattern you spot in a report often started as an alert you resolved three weeks ago.
The problems that come up most, ranked.
Which security policy has the most trouble.
Which team or site needs attention.
Every rule can be tuned or turned off. Open one to see when it fires.
Fires when a device has not checked in for longer than your threshold, 24 hours by default. Resolves itself when the device reappears. Raise the threshold for sites with poor signal.
The device does not meet its policy, for example "Screen lock does not meet policy" or "Required app Jobber is missing". Written as a sentence, never a code.
Play Protect turned off, storage not encrypted, or a security patch far older than the rest of the fleet.
So the owner always knows when a device is in lost mode and who changed it.
Two alerts, because the gap between them is the answer to "did it actually happen?"
A required app could not install, with the reason the device reported, most often not enough storage.
Before apps start failing to update.
An app you blocked appeared on a device anyway.
A batch you planned did not finish before its code ran out.
An Android device dashboard and inventory for small fleets: see which phones are online, offline or need attention, and filter by group, employee, policy.
Android fleet compliance reports: top issues, policy and group breakdowns, Android version and patch age, CSV export and an audit log of admin actions.
Android security policies in plain English: pick a template, set screen lock, updates, camera, Wi-Fi and encryption, and preview changes before publishing.
The trades that lean on this feature most, each with its own scenario and recommended policy.
Driver phones running navigation and proof of delivery all day. Keep the dispatch app on the version you tested, get told when a phone goes quiet, and lock it the moment it is lost.
Read more →Order screens and check-in tablets that should show one app and nothing else. Kiosk mode blocks the settings menu, keeps the screen awake, and tells you before the lunch rush if a tablet dies.
Read more →By email digest to the recipients you choose, and in the bell icon inside NounDesk. You pick who receives which categories.
No. The offline rule has a threshold you set, 24 hours by default. Short gaps in coverage do not raise alerts.
Acknowledge means "I've seen it and I'm on it." Resolve means it is fixed. Many alerts resolve themselves when the device reports that the problem has cleared.
Yes. Each rule can be disabled or have its threshold changed.
Start a 14-day free trial, no card required. Or load a sample fleet in demo mode first.
NounDesk