The AI-native customer support platform.
Kai and your team, one workspace. Answer customers, investigate bugs and review fixes in one workspace. Your team stays in control.
Trusted by 4,500+ teams
Kai · Inbox
Every channel in one inbox.
Widget chat, email, WhatsApp and connected tools land as tickets with the customer's history. Kai answers from your knowledge and brings the team in when needed.
InboxOpen 3
Florian SteinerSurvey alerts failnow
Tobias KellerSafari export fails2m
Mara LindqvistExport team reports?14m
Kai Resolve · Technical context
Evidence comes with the report.
SDK reports can include session replay, console and network logs, device data and events, depending on your setup. Kai Resolve reads them before anyone asks the customer a question.
13:24:30 Feedback received
13:24:03 cart.items undefined
13:24:02 500 POST /api/orders
{
"status": 500,
"duration": 1840,
"response": { "error": "cart_expired" }
}
13:23:54 pageView
{
"page": "/checkout",
"referrer": "/cart"
}
13:23:50 Retrying (2/3)
13:23:43 sessionStarted
{
"userId": "u_84s2k",
"plan": "growth"
}
13:23:39 User logged in.
No entries match the selected filters.
Kai Resolve → Kai Code · Ticket
Agents work on the same record.
The investigation, the coding session and the pull request live in the ticket next to the conversation. Your engineers review and merge; the customer hears back after the release.
Kai Code picked up this ticket GleapSDK/Desktop
Specialist agents on the shared context.
Each agent has one job. Your team sets direction and reviews what ships.
Kai
Answers customers
Replies from your help center, snippets, websites and files. Escalates to a teammate or Kai Resolve when a question needs more.
Kai Resolve
Investigates hard tickets
Reads the session, logs and code read-only, returns a verdict with evidence and starts coding tasks for confirmed bugs.
Kai Code
Builds the fix
Plans the change, edits the code, runs the tests and opens a pull request linked to the ticket. Engineers review and merge.
Kai PM
Plans
Feature request triage and prioritization from your feature requests. Available on Pro.
Where customers reach you.
Bug reports, help content and surveys share the same workspace.
Report an issue
Hey 👋 Found a bug? Please describe the issue below. You can also mark the bug.
Checkout does nothing after I add a coupon.
Mark the bugRecord screen
Submit
Reports arrive with replay and logs. With bug triage on, Kai Resolve investigates before the team sees them.
AllLiveDraft
TitleStatus
Exporting your dataPublished
Inviting teammatesPublished
Survey notificationsUnpublished
Help articles for customers and the source Kai answers from. Drafts stay unpublished until you approve them.
Would you recommend Lumen?
012345678910
Not likelyVery likely
NPS, CSAT and custom surveys in the widget, with responses next to the customer's tickets.
Where the product changes.
Requests, pull requests and release notes stay linked to the customers who asked.
Planned2 CSV export23Dark mode41
In progress1 Team hours18
Done1 Surveys12
Requests with votes and subscribers on a public roadmap. Duplicates are linked, not lost.
3 changed files +84 −12 PR #412
- Notifications.tsx +61−9
- useNotificationSocket.ts +19−3
- Notifications.test.tsx +4−0
src/drawer/Notifications.tsx
@@ -42,7 +42,15 @@ NotificationsDrawer const { items } = useNotifications();− useEffect(() => { if (open) refetch(); });+ const socket = useNotificationSocket();+ useEffect(() => {+ if (!open) return;+ return socket.on('notification:new',+ (n) => setItems((p) => [n, ...p]));+ }, [open, socket]); return <Drawer open={open}>
@@ -8,6 +8,18 @@ useNotificationSocket const socket = useSocket();+ const on = useCallback((evt, fn) => {+ socket.on(evt, fn);+ return () => socket.off(evt, fn);+ }, [socket]);− return socket;+ return { on };
@@ -0,0 +1,4 @@+ it('appends a pushed notification',+ async () => {+ render(<NotificationsDrawer open />);+ socket.emit('notification:new', n);+ expect(await findByText(n.title))+ .toBeVisible();
Kai Code opens the pull request from the ticket. The diff, checks and preview are ready for review.
Survey notifications for visitors
Surveys now reach visitors who are not logged in.
Publish what changed in the widget and by email. Subscribers to a request hear when it ships.
Close the loop.
A confirmed bug becomes a coding task in the ticket.
Kai Resolve attaches the evidence, your team picks the fix up with Kai Code or opens it in Claude Code, Codex or Cursor. The customer is notified after the release.
Kai Resolve prepared a coding task
Found a likely bug
Survey pushes skip anonymous visitors:
sendSurveyPush returns early without a contact email, but delivery only needs the session's subscription. Remove the guard and add a regression test. Ask for changes Fix with Kai Code
Handed to Kai Code
Your team stays in control.
Read-only investigation, reviewed changes, verified releases.
Access for this investigation
- GleapSDK/ServerRepository Read-only
- GleapSDK/WidgetRepository Read-only
- Postgres via MCPData Read-only
- Writes, deletes, billingAny tool Blocked
Kai Resolve investigates repositories read-only in a sandbox and blocks destructive tool operations.
Fix with Kai Code
Resolve coding tasks are picked up or sent back by a person. Pull requests are reviewed and merged by your team.
Fix merged. Is it live?
Confirm before Rami hears back.
#412GleapSDK/Desktop Not fixed Confirm & reply
By default a teammate confirms the merged fix is live before the customer reply goes out.
What teams run on Gleap.
Inbound support handled by Kai at Commonplace
Commonplace uses Gleap for support, feedback, its knowledge base and roadmap. The team reports Kai handling 50 to 60% of inbound support.
Read the Commonplace story Setup and migration at Salesforge
Salesforge brought support, roadmap requests, product news and Slack collaboration into one workspace. Its reported setup took less than a day.
Read the Salesforge story 
To full integration at Partfox
Partfox connected custom data and brought live chat, AI support, feedback, tours, checklists and surveys into Gleap. Its integration took 10 days.
Read the Partfox story “Switching from Intercom to Gleap was a win-win.”
“It's elevated our user feedback and customer support experience immensely.”