TICKET MANAGEMENT
Dedupe Intercom conversations and alert support with a cluster digest in Slack
Groups newly opened Intercom conversations that describe the same issue into clusters and posts a live Slack digest showing each cluster, its size, and every requester.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Intercom conversation openedIntercom
- ActionEmbed message and match against active clustersOpenAI
- LogicAttach to existing cluster or create new
- ActionUpdate cluster membership and count in PostgresPostgres
- OutputCreate or edit the cluster digest in SlackSlack
What it does
Watches incoming Intercom conversations, clusters the ones reporting the same underlying issue, and surfaces those clusters to the support team in Slack so a single agent can own each cluster instead of many agents touching duplicates.
When to use it
When your inbox spikes with lookalike messages and you want humans, not automation, to send the final reply, but you still need duplicates grouped and assigned in one place.
How it works
- 1A new Intercom conversation opens and triggers the flow.
- 2The message body is embedded with OpenAI and matched against active clusters tracked in Postgres.
- 3A branch decides whether to attach the conversation to an existing cluster or open a new one.
- 4The cluster row in Postgres is updated with the conversation id and the running requester count.
- 5A Slack digest message for that cluster is created or edited in place, listing size and affected users for an agent to claim.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect OpenAIModels, embeddings, files.
- 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 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.