TICKET MANAGEMENT
Flag Multi-Account Outages by Aggregated ARR to Slack
Scans open Zendesk tickets on a schedule, clusters them by shared symptom and CRM-linked account.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires every N minutes
- ActionFetch open Zendesk tickets with tags and subjectsZendesk
- ActionResolve each account and attach ARR from SalesforceSalesforce
- LogicCluster tickets by symptom and sum affected ARR
- LogicKeep clusters above ARR threshold, rank descending
- OutputPost ranked blast-radius brief to SlackSlack
What it does
Individual tickets hide systemic outages. This workflow periodically pulls open Zendesk tickets, links each to its Salesforce account ARR, then groups tickets that share an error signature or product area. When the summed ARR across a cluster exceeds a configured ceiling, it emits a single incident brief ranking clusters by total revenue at risk.
When to use it
Run it when scattered tickets about the same root cause are being worked in isolation and nobody sees the aggregate revenue exposure. Useful for support leads and on-call managers who need an at-a-glance view of which simultaneous issues hurt the most ARR.
How it works
- 1A schedule fires every few minutes.
- 2Open Zendesk tickets are fetched along with their tags and subjects.
- 3Each ticket's account is resolved in Salesforce and its ARR attached.
- 4A clustering step groups tickets by shared symptom and sums affected ARR per cluster.
- 5A threshold check keeps only clusters above the ARR ceiling, ranked descending.
- 6A formatted blast-radius brief is posted to a Slack incident channel.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.