Page the channel the crew actually watches.

Ignition already covers email, SMS, voice and WhatsApp notification profiles. Plenty of plants still page people somewhere else: a Teams channel the shift actually watches, a Slack workspace, or a webhook into an on-call tool. Those usually end up as one-off scripts with no acknowledgement path and no proof the page was delivered.

Mustry Alarm Notifications adds Teams, Slack and generic webhooks as native alarm notification profiles. They show up under Config → Alarming like any other profile, sit in pipelines beside the built-in channels, and inherit rosters, schedules and throttling from the platform. Inductive’s Email / SMS / Voice / WhatsApp modules stay where they are. This covers the channels they leave open, and hands off when you want fallback.

Ack that matches the channel

• Teams. Adaptive Card via a Teams Workflows webhook. No Azure app, no bot. Optional acknowledge link.
• Slack. Block Kit with real buttons. Interactions verified with your app’s signing secret.
• Webhook. Any HTTP endpoint, fully templated, with a signed callback for acknowledge.

Per-profile rate limiting, a Test Send button and a status page come with it. When the licence lapses the module stops delivering and says so loudly. No silent grace period: a plant that thinks it is being paged and is not is worse than one that knows.

Where it belongs

Not a full alarm management suite. Not a substitute for Email / SMS / Voice / WhatsApp. Use those when they fit. Use this when the page has to land where the crew already lives. The product page on mustrysolutions.com is still catching up; the module itself is real and licensable through Mustry.