CHATBOTS

Onboarding coach that logs doc gaps for the docs team

Answers in-app onboarding questions from docs and records every question, the doc used, and the confidence into Postgres so you can find which features are under-documented.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew in-app onboarding messageIntercomIntercom
  • ActionRetrieve matching doc from CodaCodaCoda
  • ActionDraft answer with topic and confidenceOpenAI
  • ActionLog question and match to PostgresPostgreSQLPostgres
  • OutputReply to the user in IntercomIntercomIntercom

What it does

Every answer the coach gives becomes data. Alongside replying to the user, this workflow writes a structured row to Postgres for each question: the user's text, which feature doc was matched, the confidence, and whether an answer was sent. Over a week you get a ranked list of the topics your docs fail to cover.

When to use it

Use it when you want the onboarding bot to also drive your documentation roadmap. The accumulating table tells your docs team exactly which features generate the most unanswered or low-confidence questions, so they fix the gaps that hurt activation most.

How it works

  1. 1The Intercom trigger fires on each new in-app onboarding message.
  2. 2The closest feature doc is retrieved from Coda.
  3. 3OpenAI drafts the answer and returns the matched topic and a confidence score.
  4. 4A row capturing question, matched doc, confidence, and timestamp is inserted into Postgres.
  5. 5The grounded answer is delivered back to the user in Intercom.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect IntercomConversations, contacts, articles.
  2. 2
    Connect CodaDocs, packs, automations.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect PostgresAny Postgres URL — query, write, migrate.
  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.