CUSTOMER SUPPORT
Enrich repro score with Sentry data before filing a Linear bug
When a bug ticket clears a repro-completeness check, it pulls the matching Sentry event (stack trace, release.
How it runs
The automated pipeline, trigger to output.
- TriggerTicket marked ready-for-engineering
- ActionScore repro completeness (LLM)OpenAI
- LogicBranch: search Sentry for matching eventSentry
- ActionAttach stack trace, release, breadcrumbsSentry
- OutputFile Linear issue labeled repro-confirmedLinear
What it does
This workflow gates the support-to-engineering handoff. It scores a bug ticket for repro completeness, searches Sentry for an event matching the reported error or release, and merges that telemetry into the report. Only reports that are both customer-complete and corroborated by real Sentry data become Linear issues; the rest bounce back for more detail.
When to use it
Use it when engineering complains that support files vague or unreproducible bugs. It enforces that a Linear ticket carries a stack trace and a real Sentry link, not just a customer's guess.
How it works
- 1A support ticket marked ready for engineering triggers the run.
- 2An LLM scores repro completeness from the ticket text.
- 3A branch checks the score, then searches Sentry for a matching issue by error message or release.
- 4If a Sentry event is found, its stack trace, release, and breadcrumbs are attached to the report.
- 5A Linear issue is created with the merged customer report plus Sentry context, labeled `repro-confirmed`.
- 6If no Sentry match or score is low, the run posts the gaps back to support instead of filing.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect OpenAIModels, embeddings, files.
- 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.