TICKET MANAGEMENT
Alert Slack When an Intercom Issue Theme Spikes
Hourly, recounts conversations per recurring theme and posts a Slack alert to the on-call channel whenever any theme's volume jumps sharply above its rolling baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule triggers check
- ActionRead last hour's conversations and assign themesIntercom
- ActionUpdate counts vs rolling baselinePostgres
- LogicFlag themes exceeding spike multiplier
- OutputPost deduped alert to on-call SlackSlack
What it does
Watches your clustered Intercom themes for sudden volume spikes and pings the right Slack channel the moment a known issue starts trending, so you catch incidents from support signal before they escalate.
When to use it
Use it when a backend regression or outage shows up first as a wave of similar tickets. This turns that wave into a single, timely alert instead of a slow trickle of duplicate reports.
How it works
- 1An hourly schedule triggers the check.
- 2The flow reads the last hour's Intercom conversations and assigns each to its nearest existing theme using stored fingerprints in Postgres.
- 3It updates per-theme hourly counts and compares each against that theme's rolling 7-day baseline.
- 4A logic step flags themes whose current rate exceeds the baseline by the configured spike multiplier.
- 5For each flagged theme it composes a message with the theme label, current vs. baseline volume, and sample conversation links.
- 6The alert posts to the on-call Slack channel, deduped so the same spike isn't re-alerted within the cooldown window.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
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.