CUSTOMER SUPPORT
Detect bug reports in Intercom and open a Linear issue
Reads new Intercom conversations, uses an LLM to decide if it's a real bug, and for confirmed bugs creates a triaged Linear issue and replies to the customer with the tracking…
How it runs
The automated pipeline, trigger to output.
- TriggerNew Intercom conversationIntercom
- ActionClassify + extract bug details with OpenAIOpenAI
- LogicConfirmed bug report?
- ActionCreate labeled Linear issueLinear
- OutputAdd issue link as internal note in IntercomIntercom
What it does
This watches inbound Intercom conversations and uses an LLM to separate genuine bug reports from how-to questions, feature requests, and billing chatter. When it identifies a bug, it drafts a clean reproduction summary, opens a Linear issue with a severity label, and posts an internal note back on the Intercom conversation linking the two so support can track resolution.
When to use it
Use it when bug reports get lost in a shared inbox and engineering only hears about them days later. It turns customer language into a structured, labeled engineering ticket the moment the report lands.
How it works
- 1A new Intercom conversation triggers the flow.
- 2OpenAI classifies the message and, if it's a bug, extracts a title, repro steps, and severity.
- 3A branch routes only confirmed bugs forward; everything else exits.
- 4A Linear issue is created with the title, body, and a severity label.
- 5An internal note with the Linear issue link is added back to the Intercom conversation for the support agent.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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 Customer Support workflows
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
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.