TICKET MANAGEMENT
Detect duplicate-ticket spikes and open one incident
On a short interval, scan recently created tickets for a sudden cluster sharing a topic, and when the count crosses a spike threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerShort-interval schedule
- ActionFetch recent tickets + embeddingsPostgres
- LogicCluster exceeds spike threshold?
- ActionDedup against open incidentsPostgres
- ActionOpen one PagerDuty incidentPagerDuty
- OutputPost incident + ticket list to on-call SlackSlack
What it does
Turns a flood of duplicate tickets into a single signal. Rather than one alert per ticket, it watches for a rapid cluster of similar tickets — the fingerprint of an outage — and raises exactly one incident with the full list attached.
When to use it
Use it when incidents reveal themselves first in support volume: a payment provider goes down and tickets spike before monitoring catches it. This gives on-call an early, deduplicated heads-up.
How it works
- 1A short-interval schedule triggers the scan.
- 2Postgres returns tickets created in the trailing window with their precomputed embeddings.
- 3A logic step clusters them and checks whether any single cluster exceeds the spike threshold over the baseline rate.
- 4If no spike, the flow exits quietly.
- 5On a spike, it deduplicates against open incidents in Postgres so it never double-pages, then opens one PagerDuty incident describing the cluster.
- 6It posts the incident link and the list of affected ticket ids to the on-call Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.