Team alerts: post to a Space when something important happens

The problems that hurt most are the ones nobody catches in time: an SLA that broke, the quality of your WhatsApp number that cratered, a channel that disconnected at 3 a.m. By the time you find out, you've already lost customers. The fix is to turn those events into automatic internal team alerts with the Omnifox workflow engine: the system tells you itself, in the right Space, the moment it happens.

In this guide we build operational alerts using the workflow editor (chat/omnichannel) and its Team module.

The big idea

Each critical event is a separate trigger, so we'll build several small workflows, one per alert. The pattern repeats:

Trigger (critical event) → Post to Team (or Send DM / Create reminder)

Remember: one trigger per workflow. You can't cram SLA breached and Channel disconnected into the same flow; that's two workflows.

Alert 1: SLA breached

The SLA breached trigger fires when a conversation exceeds the committed response time. The flow:

SLA breached → Post to Team in the "Operations" Space.

In the Post to Team node you write the message with conversation variables:

SLA breached on {{$conversation.channel_name}} — assigned to {{$conversation.assignee}}. Status: {{$conversation.status}}.

If you want a specific lead to get the heads-up privately, swap in (or add in parallel) a Send DM node aimed at that person.

Alert 2: WABA quality changed

Meta rates the quality of your WhatsApp Business number. If it drops, your templates and messaging limit are at risk. The WABA quality changed trigger alerts you the moment Meta reclassifies the number.

WABA quality changed → Post to Team in "WhatsApp Alerts".

This is one of those alerts that saves the operation: learning that quality fell to "Red" the same day gives you time to fix the behavior before Meta throttles your sending.

Alert 3: channel disconnected

A downed channel is silent and lethal: customers write and nobody receives it. The Channel disconnected trigger fires when Omnifox loses the connection to a channel (expired token, dropped session).

Channel disconnected → Post to Team + Create reminder.

Here it pays to double up: Post to Team for the immediate heads-up and Create reminder so someone checks in 15 minutes whether it reconnected. That way the alert doesn't get lost in the scroll.

Routing the alert to the right person

Not every alert goes to the same place. You have three nodes to choose from:

You can combine them with Run in parallel to, say, post to the Space and DM the on-call person at once.

Add context and priority

Inside the Post to Team node, lean on conversation variables ({{$conversation.channel_name}}, {{$conversation.assignee}}) so the message is actionable, not a vague "something happened." An alert with a name, channel, and owner gets resolved much faster than a generic one.

If the alert is a must-handle, add a Notify team by email node as a backup, in case the Team isn't open at that moment.

Common mistakes

• Cramming several events into one workflow. You can't: each workflow has a single trigger. Build one per event.
• Posting without context. A bare "SLA breached" forces investigation. Always include channel, assignee, and status via variables.
• Ownerless alerts. Posting to a Space nobody watches is the same as not alerting. Pick active Spaces or combine with Send DM to an owner.
• Not planning the bounce-back. For disconnected channels, add Create reminder; otherwise the reconnection may be forgotten.

A daily digest, not just alerts on the fly

Real-time alerts are for the urgent stuff, but a periodic pulse helps too. With the Scheduled trigger (cron) you can build a workflow that runs each morning and uses Post to Team to drop a status summary in the "Operations" Space: connected channels, pending conversations, SLAs at risk. That way the team starts the day with context instead of waiting for something to break.

Test every alert before you trust it

Don't assume an alert works until you've watched it fire. The simplest way is to provoke the event in a controlled setting: disconnect and reconnect a test channel to confirm Channel disconnected posts to the Team. Check that the message lands in the right Space and that the variables ({{$conversation.channel_name}}, {{$conversation.assignee}}) fill in. An alert you never tested is a false sense of security: the day a channel actually goes down, you don't want to discover the workflow was pointing at an archived Space.

Put it to work

Internal alerts are the difference between putting out a fire and finding out the next day. In Omnifox you build these workflows in minutes and your team learns what matters without relying on anyone staring at a dashboard. Start with the event that hurt most last time.