🔔Alerts & Notifications
Configure how Myncel reaches you when something needs attention — in-app, email, SMS, mobile push, Slack, Microsoft Teams, PagerDuty, or any external system via Webhooks.
Notification channels
Each user configures their own preferences from the user menu → Notifications. You can choose a different channel — or several channels — for each event type. Admins can set defaults for the organization and choose which defaults can be overridden by individual users.
- In-app — always on; appears in the bell icon at the top right and is shown in real time on web and mobile.
- Email — default for most events; granular per event type. Branded with your organization's logo on Professional and above.
- SMS — for urgent alerts. Available on the Growth plan and above. Worldwide coverage via Twilio with E.164-formatted numbers.
- Mobile push — to the iOS or Android app via APNs and FCM. Banner on lock screen, badge on icon, optional sound, and tap-to-deep-link straight to the work order or alert.
- Slack — post to a channel of your choice. Configure in /settings/integrations → Slack.
- Microsoft Teams — adaptive-card alerts to any Teams channel via Incoming Webhook. Configure in /settings/integrations → Microsoft Teams. See the Integrations chapter.
- PagerDuty — page on-call engineers via PagerDuty Events API v2 with severity-aware routing and auto-resolve. Configure in /settings/integrations → PagerDuty. See the Integrations chapter.
- Webhooks — POST a JSON payload to any URL you control. Useful for piping into custom dashboards or any tool not covered by the native integrations above (e.g. Opsgenie until its native integration ships).
Mobile push notifications
After installing the Myncel mobile app and signing in, push notifications are enabled by default. The app uses Apple Push Notification service (APNs) on iOS and Firebase Cloud Messaging (FCM) on Android. Both are end-to-end encrypted in transit.
You will receive a notification banner on the lock screen, an icon badge with unread count, and (if enabled in your phone's settings) a sound for events like new work-order assignments, predictive alerts, and emergency broadcasts. Tapping the notification jumps you straight to the relevant screen in the app — even when the app was previously closed.
If a teammate is not receiving push notifications, ask them to: (1) make sure the app is installed and signed in; (2) check iOS Settings → Notifications → Myncel is set to Allow Notifications; on Android, Settings → Apps → Myncel → Notifications must be on; and (3) confirm the channel is toggled on under user-menu → Notifications inside the app.
Quiet hours
Nobody wants a "low-priority work order created" SMS at 2 AM. Quiet hours let each user silence non-critical notifications between configurable times, optionally per day of week. Critical alerts (Priority = Critical, or emergency broadcasts) always break through quiet hours by default — you can change this per user, but we strongly recommend leaving it on.
Alert rules and thresholds
Rules-based alerts are the simpler cousin of AI predictive alerts. They fire when a sensor value crosses a fixed threshold you define — for example "alert me if any chiller goes above 12 °C return temperature for more than 5 minutes". Use them when the threshold is well-known and stable; use AI predictive alerts when you want the system to find anomalies you have not thought of.
AI predictive alerts (anomalies the engine flagged statistically, plus failure forecasts based on linear-trend regression) are configured separately in Settings → AI & Predictive — see the AI & Predictive Maintenance chapter for the full walkthrough. The two systems coexist: a sensor can have a rule-based threshold AND be watched by the AI engine, and they will publish independently.
- Go to Equipment → [machine] → Alerts → "+ New Rule".
- Pick the sensor / data point.
- Choose the comparison (>, <, =, ≠, between, outside).
- Set the threshold and the dwell time (how long must the condition hold before firing? Prevents flapping).
- Choose severity (Info / Warning / Critical) — drives which channels and which user list receives it.
- Optionally enable auto-create-work-order on fire.
- Save.
Emergency broadcasts
Admins can send an emergency broadcast to every user in the organization with one click — useful for facility-wide events like power outages, evacuations, severe weather, or production halts. Broadcasts go to every channel a user has configured (in-app, email, SMS, push) regardless of quiet hours, and are logged in the audit trail with the sender, the recipients, and the delivery status per channel.
Use broadcasts sparingly. They are intentionally noisy. We recommend reserving them for events that genuinely require simultaneous attention from the entire team.