AI & RAG

Turn recurring un-answerable Intercom questions into Confluence doc stubs

Clusters resolved Intercom conversations that had no matching answer-bank entry, identifies recurring knowledge gaps with an LLM.

CategoryAI & RAG
EngineSim + Paperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule: weekly
  • ActionPull low-confidence resolved Intercom conversationsIntercomIntercom
  • ActionCluster gaps into recurring topics with LLMOpenAI
  • LogicKeep clusters above frequency threshold
  • ActionDraft Confluence page outline per clusterConfluenceConfluence
  • OutputOpen Linear ticket linking the draftLinearLinear

What it does

Finds the questions your answer bank keeps missing and routes them to be written up. The workflow looks at recently resolved conversations that were tagged as having no confident retrieval match, clusters them by topic, and for each recurring gap generates a draft Confluence page outline and a tracking ticket so a writer can fill it in.

When to use it

When retrieval coverage is plateauing and you want a data-driven backlog of what to document next, instead of guessing which help articles are missing.

How it works

  1. 1A weekly schedule kicks off the gap analysis.
  2. 2The workflow pulls resolved Intercom conversations from the past week tagged `needs-human` or low-confidence.
  3. 3An LLM clusters them into recurring topics and ranks clusters by volume.
  4. 4A logic step keeps only clusters above a minimum frequency to suppress one-off noise.
  5. 5For each qualifying cluster, an LLM drafts a Confluence page outline with the common question and a suggested answer skeleton.
  6. 6A draft Confluence page is created and a Linear issue is opened linking to it for an owner to complete.

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 ConfluenceSpaces, pages, blueprints.
  4. 4
    Connect LinearIssues, projects, cycles, triage.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.