Login
Start free trial

Customer engagement

In-app messaging for web and mobile.

Sent in the moment. Answered in the inbox. Send a chat message from a teammate to a defined audience while they use your product. The reply opens a normal conversation in the Gleap inbox, with Kai Support and your team behind it.

4.6/5 on G2
Trusted by 4,500+ teams worldwide
Start free trial
Book a demo
Pick the audience, pick the sender, send.
Start free trial
Trusted by 4,500+ teams
A message from a teammate. Trigger on page load or an event, once or on a schedule, on web, iOS and Android. Replies land in the inbox.
Choose the audienceChoose the button actionAnswer the replies

Choose who sees it.

Users or guests, filtered by attributes and events, limited to pages of your web app. Trigger on page load or a custom event, or send once to a one-off audience or a CSV list.

Choose the button action.

Pick the sender. A click opens a conversation with them, or just the messenger. Sound and push are optional.

Kai Support · Follow-up answers

Replies land in the inbox.

A reply opens a conversation in the inbox and runs your conversation workflow, like a new chat, with the message and the customer's context. Kai Support answers the routine follow-ups.

Kai Support answers the follow-ups.

Your message, the customer's questions.
A message invites questions. Kai Support answers the routine ones from your help center and brings your team in when a reply needs a person.
Meet Kai Support

Built for AI agents.

In-app messages your agent can set up.
Through the Gleap MCP, an AI agent writes the message, picks the sender, and targets it by page, event and contact attribute. If the event it needs is not tracked yet, it gets the tracking code for your SDK.
See the MCP server
User engagement without per-seat limits.
Partfox moved from per-seat tooling to Gleap, integrated custom data in 10 days, and now runs live chat, AI support, bug reporting, feature requests, tours, checklists and surveys on one platform.
Maic Fankhauser
Product Manager, Partfox
About in-app messaging
What is in-app messaging?
In-app messaging is a chat message shown to a customer inside your website or app while they use it, sent from a named teammate to a defined audience at a defined moment. In Gleap the message appears above the widget launcher, and a reply opens a conversation in the inbox.
Who sees an in-app message?
The audience you define: all contacts, signed-in users or guests, filtered by attributes such as plan or signup date and by events your app sends. Page rules limit a message to parts of your web app. The editor shows how many contacts match. A one-off audience or a CSV upload of user IDs sends it once to a fixed list.
When is the message shown?
On page load, after a delay, or when a custom event fires. Frequency is once, once per period or every time, with an optional start and stop date. Preview it before it goes live.
Does every in-app message create a conversation?
No. The click action decides: "Open conversation" starts a chat with the sender, "Open messenger" only opens the widget. A conversation can also start a published workflow with Kai Support.
Where do replies go?
To the Gleap inbox, as a conversation that starts with your message and carries the customer's attributes and history. The reply runs your conversation workflow like any new chat and is routed by your normal rules, not automatically to the sender. Kai Support answers routine follow-ups; a teammate takes the rest.
Does in-app messaging work in mobile apps?
Yes. The iOS, Android, React Native and Flutter SDKs show the same chat message in the app. Page rules apply to web; on mobile you target by attributes and events, with an optional push notification.
How is this different from push notifications, banners and news?
An in-app chat message is a conversation starter from a person. Push notifications reach users outside the app, banners announce something on a page, news collects product updates in the widget, and email campaigns reach the customer's inbox. All are outbound messages in Gleap with the same audience rules.
Can Kai Support answer replies to a message?
Yes. When a reply is a question Kai Support can answer from your help center and sources, it does, labeled as AI. When the reply needs a person, Kai Support hands it to your team with the thread attached.
Which plan includes in-app messaging?
Outbound messaging, including in-app chat messages, is included from Team ($149 per month, billed annually), with unlimited seats. Starter includes live chat and Kai Support without outbound. See pricing.
Is customer data safe with in-app messages?
Audience rules run on the attributes and events you send to Gleap. Gleap is SOC 2 Type II audited and GDPR compliant, with EU or US hosting chosen at signup. See the trust center.
Can AI agents create in-app messages?
Yes. Connect Claude, ChatGPT, Codex, Cursor or another MCP client to the Gleap MCP server and the agent can draft chat messages, choose the teammate they come from, target them by page, trigger, events and contact attributes, and check how many people match. One-off messages need the recipient count you approved. Drafts wait for your review.
How does in-app messaging fit into the support platform?
It is the outbound side of Gleap's AI customer support platform. The same widget carries live chat, help center and bug reporting, and the same inbox answers what comes back, including replies to WhatsApp messages.
Kai Support First level support
A message inside the product.
The reply in your inbox.
Start free trial
See pricing
4.6/5
on G2