LOW / CODEBlueprints
customer-support

SLA Breach Alert System

Monitor support ticket response times against SLA thresholds. Escalates breached tickets via Slack alerts and sends email notifications to managers before deadlines are missed.

Advanced~35 minn8nMake.com 164 downloads 371 views

Setup Instructions

1. Ensure your ticket tracking Google Sheet has columns: Ticket ID, Created At (ISO timestamp), Priority, SLA Hours (e.g., 4 for high, 8 for medium, 24 for low), Status, Assigned To, Last Response At. 2. In your automation platform, create a Schedule trigger that runs every 30 minutes. 3. Add a Google Sheets node to read all rows where Status is "Open" or "In Progress". 4. Add a Code/Function node that calculates hours elapsed since Created At (or Last Response At) and compares against the SLA Hours column. Flag each ticket as "OK", "Warning" (>75% of SLA), or "Breached" (>100% of SLA). 5. Add a Filter node to separate Warning and Breached tickets from OK tickets. 6. For Warning tickets, add a Slack node that posts to #support-escalations with a yellow warning and time remaining. 7. For Breached tickets, add a Slack node with a red alert and a Gmail node that emails the assigned agent's manager with the ticket details and breach duration. 8. Add a Google Sheets update node to mark breached tickets with a "Breached" flag so they are not re-alerted every cycle (or track last alert time).
Troubleshooting
**False SLA breaches on weekends:** The elapsed time calculation does not account for business hours by default. Add logic to exclude weekends and holidays from the hour count, or adjust SLA Hours for non-business-day tickets. **Duplicate alerts firing every 30 minutes:** Add a "Last Alerted At" column to the sheet. Only send alerts if Last Alerted At is empty or more than 2 hours ago. Update this column after each alert. **Timezone mismatches:** Ensure Created At timestamps and the schedule trigger use the same timezone. Google Sheets may store dates in the sheet owner's timezone while the automation server uses UTC. **Gmail rate limiting on mass breaches:** If many tickets breach simultaneously, batch the emails into a single summary rather than one email per ticket. Use an Aggregate node before the Gmail step.

Need a custom version?

We can build a tailored automation workflow for your specific needs.

New blueprints weekly

Get notified when we publish new automation workflows.