The customer support platform for SaaS.

Customer support software for SaaS is a shared inbox for the channels software customers use (in-app chat, email, WhatsApp, Slack, social messaging), with assignment, SLAs and a knowledge base, connected to the product itself. Gleap adds the AI agent Kai to answer first and Kai Resolve to investigate hard tickets in the session, logs and code, so a support question can end in a shipped fix.

Seven: the Gleap widget on websites and in iOS, Android, React Native and Flutter apps, email, WhatsApp through the Meta Cloud API, Slack, Instagram direct messages, Facebook Messenger and Telegram. Each channel is connected in the project settings and creates tickets in the same inbox. See live chat and WhatsApp support for the channel pages.

Yes. A multichannel customer support platform keeps every channel's conversation in one inbox with one customer record. In Gleap a WhatsApp thread, an email and a widget chat from the same customer sit in the same contact, are assigned with the same rules and can be answered by Kai or a teammate from the same composer.

Tickets are assigned to a teammate or a team. A team routes its tickets manually, at random, balanced by open tickets or in circular order, optionally to online members only and with a ticket limit per person. Teams have their own operating hours and SLA. When nobody is available, assignment is queued until someone is.

Yes. Kai runs on the widget, email, WhatsApp, Slack, Instagram, Messenger and Telegram. It answers from your help center, snippets and connected sources in the customer's language, and brings the team in when a question needs a person.

The conversation goes to a second level. Kai Resolve investigates the session, the logs and your code and returns a verdict with evidence; what it cannot settle reaches your team as a "Handed to the team" card in the ticket with the whole thread. You set the policy per project, from full second level to safety net only.

No. Conversations stay separate tickets per channel and thread. Email keeps its message references, Slack follows threads, WhatsApp and the other messengers have their own ticket-creation rules, for example a new ticket after a pause. What is shared is the contact and their history in the sidebar.

Intercom and Zendesk are strong inboxes; Gleap connects the inbox to the product. Tickets from the SDK carry session replay, console and network logs, Kai Resolve can read your code to investigate, and Kai Code turns confirmed bugs into pull requests. Pricing is per plan with unlimited seats on Team and above, and AI usage is billed by tokens. Compare in detail: Gleap vs Intercom and Gleap vs Zendesk.

Plans start at $49 per month for a solo builder. Team ($149 per month, billed annually) includes unlimited seats and projects, the multichannel inbox, knowledge base and outbound messaging. Pro adds Kai Resolve and Kai Code. AI usage is separate and billed by tokens and model. See pricing.

Gleap is SOC 2 Type II audited and GDPR compliant, hosted in the EU (Frankfurt) with US data residency on Enterprise. Data processing terms, sub-processors and the security report are documented in the trust center.

Yes. The knowledge base is the help center your customers search in the widget and the source Kai answers from. Published articles are picked up automatically; snippets, files, websites, Notion pages and code repositories can be added as further sources.

Through the ticket. A confirmed bug becomes a coding task in the same ticket, Kai Code opens a pull request, your engineers review and merge, and the customer is notified after the release. This is the loop Gleap calls close the loop, part of self-driving development.

Yes. The Gleap SDK for iOS, Android, React Native and Flutter adds the chat widget, bug reporting and help center to your app. Conversations from the app land in the same inbox as web, email and messaging channels.

Native integrations for Jira, Linear, GitHub, Slack, HubSpot, Zapier and more, plus 1,000+ tools through Composio. Tickets can be sent to an integration from the sidebar, and replies from a Slack thread sync back. See integrations.