AI & RAG

Find documentation gaps from tickets the knowledge base can't answer

Weekly, scans recently resolved Zendesk tickets, tests each against the knowledge base.

CategoryAI & RAG
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly gap-analysis run
  • ActionPull recently resolved tickets from ZendeskZendeskZendesk
  • LogicKeep tickets with low knowledge-base retrieval scoresSupabaseSupabase
  • ActionCluster gaps and propose article outlines with OpenAIOpenAI
  • OutputPublish ranked doc-gap report to ConfluenceConfluenceConfluence

What it does

Turns support history into a documentation backlog. It looks back over recently resolved tickets, checks which ones the knowledge base could not have answered confidently, clusters those misses by topic, and delivers a ranked list of missing or weak articles for the docs team to fix.

When to use it

For knowledge and content teams who want to prioritize doc work by real customer demand instead of guesswork. A perfect monthly or weekly companion to any RAG answering workflow — it tells you why deflection is leaking.

How it works

  1. 1A weekly schedule fires the trigger.
  2. 2Recently resolved tickets are pulled from Zendesk.
  3. 3Each ticket question is run against the Supabase index; low-retrieval-score tickets are kept as likely doc gaps.
  4. 4OpenAI clusters the gap tickets into themes and proposes article titles and outlines.
  5. 5The ranked gap report is posted to a Confluence page for the docs team to action.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZendeskTickets, queues, knowledge base.
  2. 2
    Connect SupabaseTables, auth, storage, edge functions.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect ConfluenceSpaces, pages, blueprints.
  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.