Automatic status escalation rules
Automatically notify or change a Team message's status when it sits too long without moving.
Watch this step in the video · My tasks, reminders and daily digest
What status auto-escalation rules do
Escalation rules watch the statuses of a Team space and act on their own when a message has been sitting too long without moving. They keep important cards from being forgotten in a column: once an hour threshold is reached, Omnifox can notify the space (mentioning its admins) or move the message to another status.
This is an advanced feature and is only available to space admins.
Requirements
- The space must have statuses created (the Statuses tab of the settings panel). With none you'll see "Create statuses in this space to configure escalations."
- You need permission to manage the space (admin/moderator). The Escalation tab is hidden for everyone else.
Steps to create a rule
- Open the space in Team and go to its settings panel (gear icon in the space header).
- Open the Escalation tab.
- Click Add rule and complete the sentence: If it has been X hours in [source status], then…
- Pick the action:
- Notify the space: posts a system card mentioning the admins and sends an "⏱ Team escalation" push.
- Move to another status: choose a target status (it must differ from the source).
- Save. The rule is enabled right away; you can Disable or Delete it anytime.
How they run
A background sweep checks the rules every 15 minutes. Only top-level messages (cards) are evaluated, not replies inside a thread. Each message + rule pair fires exactly once (it's idempotent), so the same card never escalates twice.
Verify it works
- Create a short rule (e.g. 1 hour in a test status) and leave a card in that status.
- On the next sweep you'll see the system card "⏱ … has been X h in …" (Notify action) or the card moved to the new column (Move action).
If it doesn't work
- No Escalation tab: you aren't an admin of that space.
- "Create statuses…": create statuses in the Statuses tab first.
- A move rule does nothing: a Move rule needs a valid target status; if the target was deleted it becomes a no-op.
- Nothing fires yet: the sweep runs every 15 minutes and only counts top-level cards.
Tips
- Chain two rules: at 24 h notify, at 48 h move to "At risk".
- Use a dedicated "Awaiting reply" target status so escalations stay visible and filterable.
Related articles
Related articles
-
Internal communication with Team
Create spaces and direct messages, use mentions, notes, reminders and polls, turn a message into a task, and get alerts from your workflows.
-
Team complete guide
Team in depth, in 28 chapters: spaces, direct messages, threads, polls, scheduled messages, statuses, assignees and tasks, board, inbox, AI, calls, notifications and shortcuts.
-
Start here: Team in 4 minutes
Team essentials in a short video: spaces, creating a space, messages and mentions, threads, tasks and board, direct messages, saved items and Discuss in Team.
-
Spaces and direct messages in Team
Organize internal communication by topic with spaces, and talk 1-on-1 with direct messages.
-
Turn a message into a task or a deal
Turn any Team message into a board task or a CRM deal, with no copy-paste.