TICKET MANAGEMENT
Daily digest of unscoped Intercom bugs into a Linear triage queue
Each morning this scans the last day of Intercom conversations for un-triaged bug signals, scopes each into reproduction steps, and files them as a batched.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionFetch + classify last 24h Intercom threadsIntercom
- LogicFilter out already-filed and non-bugs
- ActionExtract repro steps + severity per bug
- ActionBatch-create prioritized Linear issuesLinear
- OutputPost ranked digest to SlackSlack
What it does
Runs a scheduled sweep instead of reacting per-ticket. Once a day it pulls Intercom conversations from the last 24 hours that look like bug reports but were never filed, scopes each into reproduction steps and severity, and creates a tidy batch of Linear triage issues. It then posts a ranked digest to Slack so the team starts the day with a clear queue.
When to use it
Use when bugs slip through because support is busy and forgets to tag or file them. A daily backstop catches unscoped reports and gives engineering a single prioritized list rather than a trickle of interruptions.
How it works
- 1A daily schedule fires the trigger.
- 2The agent fetches the prior day's Intercom conversations and classifies which are likely bugs.
- 3A logic step filters out already-linked conversations and non-bugs.
- 4For each remaining bug it extracts reproduction steps and assigns a severity.
- 5It creates one Linear triage issue per distinct bug, ordered by severity.
- 6It posts a ranked Slack digest summarizing the new issues and their links.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.