IT Service Desk with Automatic Escalation

Overview

IT support teams drown in tickets. The critical server issue sits in the same queue as a password reset, escalation depends on someone remembering to flag it, and the person who submitted the request has no idea whether anyone is even looking at it.

This template fixes the three biggest IT service desk problems: urgent tickets get flagged automatically based on priority and wait time, problem statuses trigger the right notifications without manual escalation, and resolved tickets push their status back to the requesting department's board so people know their issue is fixed.

Who This Template Is For

• IT support teams handling internal help desk tickets
• Managed service providers tracking client support requests
• DevOps teams managing infrastructure incidents alongside feature requests
• Any team with an internal ticketing workflow that needs automatic escalation

Board Structure

Groups

• Incoming — new tickets awaiting triage
• In Progress — actively being worked on
• Waiting on User — need information from the requester
• Escalated — elevated to senior support or management
• Resolved — completed tickets (archive weekly)

Columns

Setting Up the Automations

Automation 1: Auto-Escalate Problem Tickets

This uses the OR Status Trigger.

What it does: When any ticket hits "Escalated", "Critical" priority, or gets stuck in "Waiting on User" for too long, a single automation notifies the IT manager. One trigger covers multiple escalation scenarios.

How to set it up:

1. Open the Automations Centre on your Service Desk board
2. Search for Community Cookbook recipes
3. Select: When a column matches any of these values
4. On the Priority column, set values to: Critical, High
5. Set the action to notify the IT Manager and change Ticket Status to Escalated

Set up a second OR trigger on the Ticket Status column for: Escalated, Waiting on User — this notifies the team lead when tickets need attention.

Automation 2: Queue Time Alerts

This uses the Formula Column Threshold Trigger.

What it does: The Hours in Queue formula calculates how long a ticket has been open. When it exceeds your SLA threshold (e.g., 24 hours for High priority, 4 hours for Critical), the trigger fires.

How to set it up:

1. Open the Automations Centre
2. Search for Community Cookbook recipes
3. Select: When a numeric formula column goes above or below a number
4. Choose the Hours in Queue column
5. Set threshold to 24 (hours) for standard SLA
6. Set the action to change Priority to High and notify the team

Create a second trigger at 4 hours for Critical tickets. This ensures no ticket sits unattended past your SLA commitment.

Automation 3: Auto-Update Requester Board

This uses the Update Status in Connected Board.

What it does: When a ticket's status changes to "Resolved", the connected item on the department's request board automatically updates. The requester sees their issue is fixed without anyone sending a manual update.

How to set it up:

1. Open the Automations Centre
2. Select: When a status changes here, update the matching item in a connected board
3. Set trigger status to Resolved
4. Set target status on the department board to Completed
5. Activate

Tips and Variations

• SLA dashboard: Create a dashboard view showing tickets grouped by Priority with the Hours in Queue column visible. Use chart widgets to show SLA compliance rates.
• Knowledge base link: Add a Link column to resolved tickets pointing to the relevant knowledge base article. Over time, this builds a searchable resolution database.
• Recurring issues: Add a "Recurrence" checkbox column. When triaging, mark tickets that are repeat issues. Review monthly to identify systemic problems worth a permanent fix.
• Client-facing SLA: For managed service providers, add a "Client" column and set different threshold triggers per client tier (e.g., 2 hours for Premium, 8 hours for Standard).
• On-call rotation: Add a "On-Call" people column that auto-assigns based on a schedule. Use native monday.com automations to rotate the assignment weekly.

What You Will Need

• A monday.com account (Standard plan or above)
• Community Cookbook installed from the monday.com marketplace
• About 15 minutes for initial setup

Frequently Asked Questions

How does the Hours in Queue formula work?+

Can I set different SLAs for different priority levels?+

What if multiple departments use this board?+