Use an AI agent to draft help doc updates from customer meetings
Customers ask questions on calls that your help docs should already answer. A help docs updater reads each meeting, checks your Documentation.ai project and drafts page edits on a review branch. Bridge never publishes: a person reviews each draft and publishes it in Documentation.ai.
The job: spot the gap, draft the fix
When a customer asks how something works and nobody can point to a help page, that's a docs gap. Support and success teams hear these on calls, but the answers often stay in the meeting.
This agent turns those questions into draft edits. It finds questions the docs didn't answer, then drafts a page update or a new page on a review branch. A person decides what's true and what gets published.
- Collecting feature requests and bugs for the product team is a different job; see the customer feedback agent.
- Saving answers your team repeats inside Bridge is also different; see Memory FAQs.
Trigger, inputs, actions and output
| Part | In Bridge |
|---|---|
| Trigger | @mention on a recap to start; later, After every meeting, which runs against the recap and transcript as soon as a meeting ends |
| Meeting input | The meeting's recap and transcript; every agent can read transcripts |
| Docs context | From Documentation.ai: list and select projects, list pages, get a page, search and fetch content, list changes |
| Actions | Review branch only: create a branch, create a page, update a page |
| Output | Draft page edits on a branch in Documentation.ai, waiting for a person to review and publish |
What stays with people
Publishing and deletes stay in Documentation.ai. Bridge drafts on a branch for your team to review, but never publishes. So a wrong draft reaches a reviewer, not your readers.
- Whether the gap is real: a question asked once may not need a page.
- Whether the answer is right: something said on a call, even by your own team, isn't automatically correct.
- What gets published, merged or deleted: all of that happens in Documentation.ai.
Set it up
- Connect Documentation.ai from the Connectors page, under the Documentation category.
- Select Create Agent from the sidebar. In Identity, name the agent and write its instructions, up to 4,000 characters.
- In Tools, select Documentation.ai under Connectors. Unconnected tools can't be selected.
- In Triggers, keep @mention while you test. Turn on After every meeting once the drafts look right.
- Creating and using custom agents, including triggers, needs a paid Bridge plan.
An illustrative setup
This setup is illustrative, written for a fictional company, Northwind. It isn't a built-in template, so adapt it to how your team writes docs.
- "If this meeting wasn't with a customer or about a support topic, stop and change nothing."
- "List the questions people asked about how Northwind works."
- "Search our Documentation.ai project for each question. If a page already answers it, skip it."
- "If a page covers the topic but misses the answer, draft an update to that page. If no page covers it, draft a new page."
- "Put all drafts from one meeting on one new branch named after the meeting."
- "Write only what the meeting and the existing docs support. Mark anything unclear for the reviewer. Never include customer names."
| Step | Example choice |
|---|---|
| Identity | Name: Docs Gap Finder. Instructions: see the excerpt below |
| Abilities | Defaults only; reading transcripts is always on |
| Tools | Documentation.ai under Connectors |
| Trigger | @mention for the first two weeks, then After every meeting |
Example: one onboarding call
This example is illustrative. On a Northwind onboarding call, a customer asks whether reports can be exported to CSV. The support lead explains how, but the docs' export page only covers PDF.
After the call, the agent finds that page and drafts a CSV section on a new branch. The docs owner checks the steps with the product team, edits one line and publishes it in Documentation.ai.
Limits
- It only sees meetings captured in Bridge. Calls nobody captured or imported never reach it.
- On Zoom, Google Meet and Teams calls it works from the transcript. Agents can't hear or see through those platforms.
- After every meeting means every meeting, internal ones included. Keep the first instruction that tells it which meetings to skip.
- It drafts from what was said. Check each draft against the product before you publish.
