Skip to main content
Intake & Triage

Request Intake & Triage: Real Enforced SLA-Breach Flag

Every team that takes requests from other teams — IT, facilities, design, legal, marketing ops — eve

Key Features

  • SLA_Breach Flag
  • Resolution Time Calculation
  • Event-Triggered Breach Alert
  • Priority-Based SLA Assignment
  • Daily Breach Digest
  • Triage Queue View

Request Intake & Triage: Real Enforced SLA-Breach Flag — Not Just a Report a Human Has to Check

Target Keyword: helpdesk template Secondary Keywords: request intake template, triage template, SLA tracking template, helpdesk ticketing template, service desk template Vertical: Intake & Triage Word Count: ~1,050


Every team that takes requests from other teams — IT, facilities, design, legal, marketing ops — eventually builds a spreadsheet to track them. The spreadsheet has columns for requester, date, priority, status, and maybe an SLA target. What it does not have is enforcement. The SLA column is a number someone typed in. Nobody checks whether the request actually breached that SLA until someone complains or a manager runs a report.

The OpenSource AI Pro Request Intake & Triage template replaces that passive tracking with active monitoring. An SLA_Breach formula flag evaluates every open request in real time: if the request's age exceeds its SLA target and the status is not "Resolved," the flag fires. Not in a weekly report. Not when someone filters the spreadsheet. Right now, on every page load. An event-triggered alert emails the assigned agent and their manager the instant a breach occurs. A daily digest summarizes all breached and at-risk requests for the team lead. The SLA becomes a real boundary, not a suggestion.


Key Features

  • SLA_Breach Flag — A formula field compares the request's creation date, SLA target (in hours or days), and current status: if(and(field('Status') != 'Resolved', field('Hours_Open') > field('SLA_Hours')), true, false). The flag evaluates live. Breach by one hour? Flagged.

  • Resolution Time Calculation — A formula field calculates the elapsed time between request creation and resolution. For resolved requests, this is the final resolution time. For open requests, it shows how long the request has been waiting — a live clock that drives urgency.

  • Event-Triggered Breach Alert — When a request transitions to SLA_Breach = true, an automation sends one email to the assigned agent and CCs the team lead. The alert includes request ID, requester name, priority, SLA target, and time elapsed. Fires once, re-arms automatically.

  • Priority-Based SLA Assignment — Each priority level (Critical, High, Medium, Low) has a default SLA target in hours. When a request is created and prioritized, the SLA target populates automatically. No manual entry, no inconsistency.

  • Daily Breach Digest — A scheduled automation sends the team lead a morning summary of all currently-breached requests and all requests within 2 hours of breaching. Proactive, not reactive.

  • Triage Queue View — A filtered, sorted view shows unassigned requests ordered by priority and age. The oldest, highest-priority unassigned request is always at the top.


How It Works

  1. Requests come in. A requester creates a row in the Requests table (or submits via Baserow's form view, which creates the row automatically). They fill in the description, category, and urgency. The priority field determines the SLA target.

  2. Triage assigns and prioritizes. The triage agent reviews the queue, confirms the priority, and assigns the request to a team member. The SLA clock started when the request was created — assignment does not reset it.

  3. Formulas monitor continuously. The Hours_Open formula calculates elapsed time from creation. The SLA_Breach formula compares that against the SLA target. The At_Risk formula flags requests within a configurable warning window (e.g., 80% of SLA consumed).

  4. Alerts catch breaches instantly. The event-triggered automation fires the moment SLA_Breach transitions to true. The daily digest provides a summary for management. Resolved requests stop appearing in active views but retain their resolution time data for reporting.


Who It's For

  • Internal IT helpdesks managing hardware requests, access provisioning, and troubleshooting with SLA commitments to the business.
  • Facilities and operations teams handling maintenance requests, office moves, and vendor coordination.
  • Design and marketing ops teams receiving creative requests from stakeholders and needing to manage turnaround expectations.
  • Legal and compliance teams tracking contract review requests, approval requests, and regulatory inquiries.
  • Any internal service team that currently uses a shared inbox or spreadsheet and has no automated SLA enforcement.

vs the Alternatives

| Feature | OpenSource AI Pro | Zendesk | Freshdesk | Google Sheets | |---|---|---|---|---| | SLA breach detection | Formula flag, live | Built-in | Built-in | Manual | | Email alerts on breach | Event-triggered, auto re-arm | Included | Included | Not available | | Pricing | Free, self-hosted, unlimited users | $19-55/agent/month | $15-49/agent/month | Free, no automation | | Customization | Full schema, open source | Configuration limits | Configuration limits | Unlimited, manual |

Zendesk and Freshdesk are purpose-built helpdesk platforms — and they are excellent for external customer support at scale. But for internal request management, they are often over-engineered and over-priced. A 10-person IT team does not need a $55/agent/month platform. This template delivers the critical feature — automated SLA enforcement — on a self-hosted, zero-cost foundation you can customize completely.


What's Included

  • Tables: Requests, Agents, Categories, SLA Targets, Activity Log
  • Key Fields: SLA_Breach (formula flag), Hours_Open (formula), Resolution_Time (formula), At_Risk (formula), Priority (single select), SLA_Hours (lookup from priority)
  • Automations: (1) Event-triggered breach alert to assigned agent and team lead, (2) Scheduled daily breach and at-risk digest
  • Views: Triage Queue, Breached Requests, At-Risk Requests, By Category, By Agent, Resolved Archive

Get Started Free

Download the Request Intake & Triage template and deploy it on your own Baserow instance. No per-agent fees. No ticket volume limits. Self-hosted, open source, and fully customizable.

Download Free Template | View Live Demo | Self-Hosting Guide


Related Templates

Download Request Intake & Triage: Real Enforced SLA-Breach Flag

Enter your email and we will send you the template link.