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.

CategoryTicket Management
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires after hours
  • ActionFetch conversations closed in last 24hIntercomIntercom
  • ActionEmbed each conversation complaintOpenAI
  • LogicCluster embeddings and label themes
  • LogicDrop clusters below min-size threshold
  • OutputUpsert ranked themes by fingerprintPostgreSQLPostgres

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

  1. 1A nightly schedule fires after business hours.
  2. 2The flow fetches Intercom conversations closed in the last 24 hours, including transcript text and tags.
  3. 3OpenAI generates an embedding for each conversation's core complaint.
  4. 4A clustering step groups embeddings by cosine similarity and labels each cluster with a plain-language theme and severity.
  5. 5Clusters below a minimum-size threshold are dropped as noise.
  6. 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.

  1. 1
    Connect IntercomConversations, contacts, articles.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.