What is answerLoops?
Prepare and review answers from your documentation across connected support channels.
answerLoops collects support questions from connected channels, drafts answers from workspace knowledge, and runs a separate AI review. Your team controls which channels can send qualifying replies automatically.
It works with developer, art, crypto, course, membership, and general-interest communities. You can also add the chat widget to any website or documentation site that supports custom JavaScript.
How it works
- Receive the question. A message in a connected channel becomes a ticket with its source attached.
- Retrieve knowledge. answerLoops searches relevant sources for material to answer the question. The public widget uses published knowledge.
- Draft and review. One AI step prepares the answer; another checks it against the available evidence.
- Send or review manually. Automatic replies must be enabled and meet the configured confidence threshold. Other drafts remain available to your team.
- Maintain knowledge. Promote useful resolved answers and update articles as your product changes.
A confidence score is an AI assessment, not a guarantee that an answer is correct. Test representative questions before enabling automatic replies.
Capabilities
| Feature | What it does |
|---|---|
| AI deflection | Sends qualifying answers automatically when enabled for a channel. |
| Multi-channel ingest | Collects questions from Discord, Slack, Discourse, Circle, GitHub, Telegram, email, Google Chat, and a website widget. |
| Knowledge base | Imports URLs, files, GitHub content, Notion pages, and promoted resolutions. |
| Knowledge gaps | Identifies questions that may need better documentation; Pro and Enterprise. |
| Human escalation | Routes follow-up notifications to configured recipients; Pro and Enterprise. |
| CSAT scoring | Records customer ratings on supported channels; Pro and Enterprise. |
| Simulation mode | Tests the answer workflow without sending live replies; Pro and Enterprise. |
| Ticket list | Collects requests, drafts, replies, and status in one queue. |
| Multi-provider AI | Uses your supported provider account; custom endpoints require Enterprise or self-hosting. |
| Website widget | Adds support chat and lead capture to your site. |
| Billing | Hosted plans with monthly answer allowances, or a self-hosted edition without subscription fees. |
Ingest channels
| Channel | How it connects | What it ingests |
|---|---|---|
| Discord | OAuth installation (cloud) or bot token (self-host) | Text channel messages, forum thread posts, and replies |
| Slack | OAuth installation or polling mode | Channel messages |
| Discourse | REST API + webhook | Topics and posts in watched categories |
| Circle | API token | Space posts and comments |
| GitHub | GitHub App webhook | Issues, issue comments, Discussions, discussion comments |
| Telegram | Webhook via bot token | Messages in configured chats |
| Provider-agnostic inbound webhook | Any inbound email forwarded to the webhook URL | |
| Website widget | Embeddable <script> tag | Widget chat sessions |
| Google Chat | Connect-code space pairing | Messages in the paired space |
Choose a deployment
Cloud: choose a plan, sign in with Google, and complete checkout for a 14-day trial. A card is required. Model-provider costs are separate after the five-ticket introductory allowance.
Self-hosted: operate the application and channel services on your infrastructure under AGPL-3.0. Your team manages setup, backups, updates, and the services you connect. External model and channel providers still process relevant content.
For a machine-readable overview, use /llms.txt. The full documentation is available at /llms-full.txt.