TICKET MANAGEMENT
Daily SLA breach digest from Snowflake to Microsoft Teams
Each morning it queries yesterday's SLA breaches from your Snowflake support warehouse, summarizes counts by team, severity, and repeat offenders.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionQuery prior-day SLA breaches from SnowflakeSnowflake
- LogicAggregate by team, severity, repeat offenders
- LogicFormat leadership digest
- OutputPost digest to Microsoft Teams channelMicrosoft Teams
What it does
It gives support and engineering leads a single daily read on where SLAs are slipping, without anyone building a dashboard query by hand. It rolls up the prior day's breaches by owning team, severity, and which accounts breached more than once, then delivers it where leadership already reads.
When to use it
Use it when breach events already land in a Snowflake warehouse and you want a recurring management-level summary rather than per-incident noise. Ideal for weekly ops reviews and accountability tracking.
How it works
- 1A scheduled trigger runs each morning.
- 2The flow queries Snowflake for all SLA breaches in the prior 24 hours.
- 3A logic step aggregates them by team, severity tier, and repeat-offender account.
- 4It formats a digest highlighting the worst categories and any account with multiple breaches.
- 5It posts the digest to the operations Microsoft Teams channel for the leads.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect Microsoft TeamsChannels, chats, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.