TICKET MANAGEMENT
Notify Intercom customers when their reported Linear bug ships
When a Linear bug moves to Done, this finds every Intercom conversation linked to it and sends each affected customer a notification that the fix has shipped.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue moved to DoneLinear
- LogicHas support-origin label?
- ActionResolve linked Intercom conversation IDsIntercom
- ActionDraft plain-language resolution message
- ActionReply to each linked Intercom conversationIntercom
- OutputPost notified-customers summary to SlackSlack
What it does
Closes the support loop automatically. When a Linear issue that originated from support is marked Done, the workflow finds all the Intercom conversations linked to that issue and sends each customer a clear, friendly message that their reported bug is now fixed, including a short summary of what changed.
When to use it
Use when customers report bugs and then never hear back, even after the fix ships. Proactive resolution notices reduce repeat tickets and improve CSAT without support staff manually tracking which tickets a Linear issue resolved.
How it works
- 1A Linear issue transitions to the Done state, firing the trigger.
- 2A logic step confirms the issue carries a support-origin label so internal-only bugs are skipped.
- 3The agent reads the issue description and links to find the associated Intercom conversation IDs.
- 4It drafts a per-customer resolution message summarizing the fix in plain language.
- 5It reopens and replies to each linked Intercom conversation with the message.
- 6It posts a summary to the team Slack channel listing which customers were notified.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect IntercomConversations, contacts, articles.
- 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.