Marketing automation for SaaS teams.

Gleap includes product tours, onboarding checklists, tooltips, info cards, banners, in-app chat messages, email automation, push notifications, WhatsApp messages, surveys and news and release notes. They live in one outreach list inside the support platform.

Use a checklist for a set of tasks, a tour for a guided sequence on the interface, a tooltip for one control, and an info card for a launch that needs a picture. A checklist task can start a tour, so start with the checklist and attach tours to its tasks.

Yes, for many formats: event or property triggers start them, with an optional delay. Audience targeting is shared; page rules and frequency controls depend on the format. Tooltips use audience and page targeting, and checklists have no frequency setting. Your app sends the events through the Gleap SDK or API.

A dynamic audience keeps matching: each person who meets the rules after the trigger receives the message. A one-off send goes once to everyone who matches at that moment and shows the count before you publish. Email, push, WhatsApp, in-app chat messages, surveys, info cards and banners support both, and a one-off send can also go to a CSV upload. Tours, tooltips, checklists and news use rules.

Publish the release note in news, then point the right audience at it: a banner or info card for people in the product, an email or push for those who are not. All of them can open the news item directly.

No. Your team writes, targets and publishes every message. Kai Support comes in when customers reply or ask questions: it answers from your knowledge base, can suggest a product tour, and brings the team in when needed.

Yes. WhatsApp messages are an outreach format with a one-off or dynamic audience, sent through your connected WhatsApp channel, and replies arrive in the same inbox.

Partly. Banners, info cards and checklists run in the JavaScript SDK and in the native iOS and Android SDKs. Tours and tooltips are web only. Native apps also get news, surveys, in-app chat messages and push notifications.

The contact record, events, inbox and knowledge base are the same ones support uses, so a reply to a campaign is a ticket with history, not a new lead in another tool. Gleap fits teams that want onboarding, announcements and re-engagement next to support. Compare reporting and integration needs before replacing a dedicated marketing suite, for example with Gleap vs Customer.io, Gleap vs HubSpot or Gleap vs Userpilot.

It shares the customer with support and product. A reply goes to Kai Support or a teammate, and a reported problem becomes a ticket with session replay. From Team, Kai Support investigates it, Kai Code opens a pull request your team reviews, and the customer hears back once a teammate confirms the fix is live. See how Gleap closes the loop and what self-driving development means.

They can prepare them. Connect Claude, ChatGPT, Codex, Cursor or another MCP client to the Gleap MCP server and the agent drafts any outbound format, reads the events and contact attributes your project tracks, sets triggers, page rules, audiences and schedules, previews the reach and publishes or pauses once you approve. When the audience needs an event that is not tracked yet, the agent gets the tracking code for your SDK or backend. One-off sends need the recipient count you approved, and one-off emails and push never go to every contact.

Outbound messaging is included from Team ($149 per month, billed annually), with unlimited seats. The plan includes 1,000 emails to customers a month, then $2 per 1,000. See pricing.

Yes. The platform overview shows how the inbox, AI agents, feedback tools and outreach share one workspace and one customer record. For software companies, see AI customer support for SaaS.