TICKET MANAGEMENT
Weight Intercom bugs by customer impact before setting Linear priority
On a new bug-tagged conversation, this looks up the customer's plan and account value, counts how many other open conversations mention the same issue.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Intercom conversation tagged 'bug'Intercom
- ActionRead customer plan, MRR, seatsIntercom
- ActionCount matching open conversationsIntercom
- LogicCompute impact score to priority band
- ActionCreate Linear issue at weighted priorityLinear
- OutputWrite priority + impact note to IntercomIntercom
What it does
Files a Linear bug whose priority reflects real customer impact rather than whoever shouted loudest. It pulls the reporting customer's plan tier and MRR from Intercom attributes, searches open Intercom conversations for the same symptom to gauge blast radius, computes an impact score, and creates the Linear issue at a matching priority with a labeled rationale.
When to use it
When your Linear backlog priorities don't track business impact, and enterprise-blocking bugs sit at the same level as cosmetic complaints from free accounts.
How it works
- 1A new Intercom conversation tagged "bug" fires the trigger.
- 2The flow reads the customer's plan, MRR, and seat count from Intercom contact attributes.
- 3It searches Intercom for other open conversations matching the symptom keywords to count affected customers.
- 4A logic step computes a weighted impact score from plan tier, dollar value, and conversation count, mapping it to a Linear priority band.
- 5A Linear issue is created at that priority with impact labels and a one-line rationale in the description.
- 6The flow writes the assigned priority and affected-account count back as an Intercom note.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.