|
1 | 1 | name: intercom-conversations |
2 | 2 | title: Intercom Connector |
3 | 3 | icon: ./assets/icon.png |
4 | | -description: Ingest Intercom support conversations into GitBook for auto-improvements. |
| 4 | +description: Automatically sync Intercom tickets to docs updates in GitBook. |
5 | 5 | visibility: public |
6 | 6 | script: ./src/index.ts |
7 | 7 | summary: | |
8 | 8 | # Overview |
9 | 9 |
|
10 | | - Automatically get AI-suggested change requests for your docs based on Intercom support conversations. |
| 10 | + By connecting Intercom to GitBook, you turn every resolved ticket into a source of documentation intelligence. The integration continuously ingests conversation data, detects recurring issues, and identifies where your docs can be clearer, more accurate, or more complete. |
| 11 | +
|
| 12 | + ## How it works |
| 13 | +
|
| 14 | + GitBook's Docs Agent analyzes the conversation data, detects recurring issues, and identifies where your docs can be clearer, more accurate, or more complete. It then opens proactive change requests based on this insight—suggesting edits, drafting improvements, and helping you keep content fresh as your product evolves. You can also @mention the AI agent or chat with it directly to accelerate reviews and edits inside any change request. |
| 15 | +
|
| 16 | + ## Configure |
| 17 | +
|
| 18 | + 1. Authorize GitBook to access Intercom |
| 19 | + After installing the app in Intercom, make sure you install the GitBook integration in your GitBook account to continue set up. After installing the GitBook integration, open the integration settings and click Connect Account. This enables GitBook to pull closed tickets and their full conversation history while automatically stripping sensitive data. |
| 20 | +
|
| 21 | + 2. Select what customer conversations to use as context |
| 22 | + Choose the inboxes, tags, or teams that best represent the voice of your customers. |
| 23 | + GitBook uses these conversations to understand issues, trends, and documentation gaps. |
| 24 | +
|
| 25 | + 3. Let the Docs Agent learn from your tickets |
| 26 | + Behind the scenes, GitBook classifies and analyzes each conversation to identify: |
| 27 | + - Frequently asked questions |
| 28 | + - Outdated or unclear documentation |
| 29 | + - Missing troubleshooting steps |
| 30 | + - Opportunities to improve explanations |
| 31 | + 4. Watch GitBook open proactive change requests |
| 32 | + Once patterns emerge, GitBook will automatically open change requests with suggested content updates. |
| 33 | + Each change request includes: |
| 34 | + - A proposed doc edit or improvement |
| 35 | + - Conversation context explaining why |
| 36 | + - A working draft written by the AI agent |
| 37 | + 5. Use the AI agent to refine and finalize |
| 38 | + Inside any change request, @mention the GitBook agent or open its chat panel to request rewrites, edits, clarifications, or additions. |
| 39 | + You stay in control while the agent accelerates the entire documentation update cycle. |
| 40 | +
|
11 | 41 | scopes: |
12 | 42 | - conversations:ingest |
13 | 43 | organization: gitbook |
|
0 commit comments