TICKET MANAGEMENT
Cluster Intercom Conversations into Recurring-Issue Themes Nightly
Each night, pulls the day's resolved Intercom conversations, embeds and clusters them into recurring-issue themes.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires after hours
- ActionFetch conversations closed in last 24hIntercom
- ActionEmbed each conversation complaintOpenAI
- LogicCluster embeddings and label themes
- LogicDrop clusters below min-size threshold
- OutputUpsert ranked themes by fingerprintPostgres
What it does
Turns a flood of individual Intercom conversations into a short, ranked list of recurring issue themes so your support and product teams see the real patterns instead of one-off tickets.
When to use it
Run it when conversation volume is too high to read manually and you want a nightly digest of what customers actually struggled with — grouped by theme, with counts, not 400 separate threads.
How it works
- 1A nightly schedule fires after business hours.
- 2The flow fetches Intercom conversations closed in the last 24 hours, including transcript text and tags.
- 3OpenAI generates an embedding for each conversation's core complaint.
- 4A clustering step groups embeddings by cosine similarity and labels each cluster with a plain-language theme and severity.
- 5Clusters below a minimum-size threshold are dropped as noise.
- 6The remaining themes, with example conversation IDs and volume counts, are upserted into a Postgres `issue_themes` table keyed by theme fingerprint so recurring themes accumulate over time.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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 Ticket Management workflows
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
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.
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…
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.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
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.
