TICKET MANAGEMENT
Daily digest of top deduplicated bug clusters from Intercom to Slack and Notion
Once a day this scans the last 24 hours of bug-tagged Intercom conversations, clusters them into deduplicated groups by symptom.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionPull last 24h of bug-tagged Intercom conversationsIntercom
- ActionCluster and rank by symptom with OpenAIOpenAI
- ActionLink clusters to Linear issuesLinear
- OutputPost digest to Slack and log to NotionSlack
What it does
Gives leadership a once-a-day view of which bugs are hurting the most customers, without anyone manually counting tickets. It clusters the day's reports into deduplicated groups, ranks them by how many customers hit each one, and publishes a clean summary.
When to use it
Use it for a morning standup or weekly review where you want a count-ranked picture of bug pain rather than a real-time per-ticket firehose. Pairs well with the live escalation workflows for the at-a-glance layer.
How it works
- 1A daily schedule triggers the run.
- 2The flow pulls all Intercom conversations tagged `bug` from the last 24 hours.
- 3OpenAI clusters them by symptom fingerprint and writes a one-line summary plus reporter count for each cluster, ranked largest first.
- 4It links each cluster to its existing Linear issue where one exists.
- 5It posts the ranked digest to a Slack channel and appends the full write-up to a running Notion page for history.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Connect NotionPages, databases, comments.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
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…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.