An AI support agent for your website.

Create a Gleap project, install the web widget or an app SDK, connect the knowledge Kai Support should answer from, and set its tone and scope. Test representative questions and the handoff to your team before opening it to all customers.

Kai Support answers from the sources you connect: your website, snippets and files on every plan, and from Team also help center articles and connected sources such as Notion or API data. It does not guess from public information about your product. Meet Kai Support.

No. Connecting knowledge gives Kai Support the context it answers from; you are not training a foundation model. The quality of your sources and instructions decides the quality of the answers.

The conversation goes to your team in the Gleap inbox or, on Team and up when enabled, to Kai Resolve, which investigates with the logs and your code and returns its finding with evidence. The customer stays in the same conversation.

Yes, with the tools your team adds. On Team and up, Kai Support can use API calls, MCP servers including Composio apps, web search and frontend tools. From Team, custom agents get their own tools, and approval controls cover actions that need review. See custom agents.

Gleap combines a platform subscription with two AI prices: Kai Support is $0.29 per resolution on every plan, and the agents that work for your team bill for the work they do. Kai Support is on every plan, and tools for Kai Support and custom agents come with Team and up. See pricing.

Yes. Every conversation stays in the Gleap inbox, so a teammate can take over at any point. Make the handoff part of your setup and check it alongside Kai Support's answers.

Kai Support is the first step: it answers what your knowledge covers. From Team, hard tickets go to Kai Resolve, confirmed bugs become coding tasks for Kai Code, your engineers review and ship, and the customer hears back. See how the loop closes.