AI & RAG

Flag help articles whose RAG keeps missing real user phrasings

Pulls recent Intercom conversations where the AI answer bot scored low or got a thumbs-down, clusters the unmatched user phrasings against your help center.

CategoryAI & RAG
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly audit schedule
  • ActionFetch recent answer-bot conversations + CSATIntercomIntercom
  • LogicKeep low-confidence or thumbs-down replies
  • ActionCluster missed phrasings, map to articlesOpenAI
  • ActionStore article-to-phrasing mapPostgreSQLPostgres
  • OutputOpen a Linear ticket per weak articleLinearLinear

What it does

It audits which help-center articles your retrieval layer should have surfaced but didn't. It reads recent answer-bot conversations, isolates the questions where retrieval missed or the customer rated the reply unhelpful, then maps each miss to the article that *should* have answered it and the exact phrasing the user actually typed. Each weak article becomes a Linear ticket with the missed phrasings attached.

When to use it

Run it weekly when your Intercom answer bot deflection rate is plateauing and you suspect the content is right but the wording doesn't match how customers ask. Ideal for support-content and knowledge-ops teams who own article quality.

How it works

  1. 1A weekly schedule fires the audit.
  2. 2Fetch the last 7 days of Intercom answer-bot conversations plus their resolution and CSAT signals.
  3. 3Filter to conversations with a low retrieval-confidence score or a thumbs-down rating.
  4. 4An OpenAI step clusters the unmatched user phrasings and matches each cluster to the closest existing article.
  5. 5Persist the article-to-missed-phrasing map in Postgres for trend tracking.
  6. 6Open one Linear ticket per under-performing article listing the phrasings to add as synonyms or headings.

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
    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.