TICKET MANAGEMENT
Weekly audit of duplicate-merge accuracy from Front
On a weekly schedule, it reviews merges performed in Front against customer reopens, scores how often merges were correct.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch merged duplicates + reopen activityFront
- LogicLabel each merge good or suspect
- ActionJoin outcomes with similarity scoresPostgres
- ActionSummarize patterns + recommend thresholdOpenAI
- OutputPublish accuracy report to NotionNotion
What it does
This workflow keeps your auto-merge logic honest. Each week it pulls the conversations that were merged as duplicates, checks whether any were reopened or disputed by the customer, computes a merge-accuracy score, and publishes a Notion report highlighting where merges went wrong.
When to use it
Run it once duplicate merging is live and you need ongoing evidence that it isn't burying distinct customer issues. The report tells you whether to loosen or tighten your similarity threshold.
How it works
- 1A weekly scheduled trigger starts the run.
- 2The workflow fetches conversations merged as duplicates in the past week from Front, along with their reopen and reply activity.
- 3A logic step labels each merge as confirmed-good (no reopen) or suspect (reopened or customer pushback).
- 4A Postgres query joins these outcomes with the original similarity scores to find the threshold where accuracy degrades.
- 5OpenAI summarizes the patterns and recommends a threshold adjustment.
- 6The workflow writes a dated accuracy report to Notion with the score, suspect-merge list, and the recommendation.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 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 Ticket Management workflows
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
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.