CUSTOMER SUPPORT
Weekly bug-report repro quality report from logged ticket scores
On a weekly schedule, reads all bug-ticket repro scores logged to Postgres, computes completeness trends and the most common missing fields.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery past week's repro scoresPostgres
- ActionSummarize trends and top gaps (LLM)OpenAI
- ActionPost quality report to SlackSlack
- OutputFile Linear issue with recommendationsLinear
What it does
This workflow turns individual repro scores into a team-level signal. It queries a Postgres table where each bug ticket's repro score and missing-field list were logged, aggregates the week's data, and produces an LLM-written report covering average completeness, week-over-week trend, and the fields customers most often leave out. The report goes to Slack and is filed as a Linear issue so improvements get owned.
When to use it
Use it when you already score incoming bugs and want a recurring read on whether report quality is improving and which prompts or form fields to fix.
How it works
- 1A weekly schedule triggers the run.
- 2A Postgres query pulls the past week's repro scores and missing-field records.
- 3An LLM summarizes the aggregates into trends, top missing fields, and concrete recommendations.
- 4The narrative report is posted to the support leadership Slack channel.
- 5A Linear issue is created capturing the recommendations so process changes get tracked to completion.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect OpenAIModels, embeddings, files.
- 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
Flag Live Intercom Chats With No Help Article and Alert Slack
When an Intercom conversation closes, checks whether the customer's question is already covered by a help article.
Negative VIP CSAT to Owner Callback Scheduler
When a VIP submits a low Intercom CSAT rating, drafts a recovery note with an LLM and books a callback on the account owner's Google Calendar within their working hours.
CEO Agent: Mine Last Month's Tickets and Publish a Deflection Plan
Monthly, an agent investigates the top recurring Zendesk ticket themes, drafts and publishes the highest-confidence help articles to ReadMe.
Mine a Discord Support Channel for Recurring Questions to Document
On a daily schedule, scans a Discord support channel for questions the community keeps asking, deduplicates against existing ReadMe docs.
Daily VIP Sentiment Digest for Account Owners
Each morning, pulls the prior day's Intercom conversations for VIP accounts, summarizes the overall mood per account with an LLM.
VIP Reply Sentiment Watcher with Account-Owner Escalation
Scores every inbound Intercom reply from a VIP customer for frustration and, when it crosses the anger threshold, pings the account owner in Slack with the conversation link…
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.