CUSTOMER SUPPORT
Daily cluster recurring support bugs and file consolidated Linear reports
Once a day, this scans the last 24 hours of bug-tagged Zendesk tickets, clusters them by the Sentry issue they map.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull last 24h of bug-tagged Zendesk ticketsZendesk
- ActionResolve each ticket's Sentry issue and fingerprintSentry
- LogicCluster by fingerprint and count impact
- ActionCreate or update consolidated Linear issuesLinear
- OutputPost daily cluster digest to SlackSlack
What it does
Replaces noisy one-ticket-per-bug filing with a daily roll-up. It collects yesterday's bug-tagged Zendesk tickets, maps each to its underlying Sentry issue, groups tickets that share the same root issue, and files a single Linear report per cluster showing how many customers were affected and how often it recurred.
When to use it
Use when high ticket volume creates duplicate bug reports and you want engineering to prioritize by real frequency and customer reach rather than first-come order. Runs unattended on a schedule.
How it works
- 1A daily schedule fires (trigger).
- 2The flow pulls all Zendesk tickets tagged `bug` from the last 24 hours.
- 3For each, it resolves the matching Sentry issue and its fingerprint and environment metadata.
- 4A logic step clusters tickets by Sentry fingerprint and computes affected-customer and occurrence counts.
- 5For each cluster it creates or updates a Linear issue with the consolidated repro report, counts, and ticket links.
- 6It posts a daily digest of the top clusters to Slack for the support and engineering leads.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SentryErrors, performance, releases.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.