Email marketing automation for SaaS.

Email marketing automation in Gleap sends customer emails from rules instead of by hand. An email has a trigger, an audience, a frequency and a sender; dynamic emails go out when a tracked event or property change matches, one-off emails go to everyone who matches right now. It runs on the same contacts and events as your support inbox, and contacts who unsubscribe are skipped on later sends.

An event-triggered email is dynamic: it waits for its trigger and sends to each person who matches, once or every time. A newsletter is a one-off send to the audience that matches at that moment. People who match later do not receive an already-sent one-off email.

Send from a team member or from a custom sender name and address. A custom address uses a domain you verified in Gleap, for example lukas@mail.acme.com. Choose an email template for the appearance, and add attachments if needed.

The reply becomes a ticket in the Gleap inbox, assigned to the teammate you set as the reply assignee. It carries the customer's record and history, and Kai Support can answer the simple ones from your knowledge base.

Yes. Send preview mails the email to you as it will render. Publishing a dynamic email turns it live; publishing a one-off email sends it to the current audience, and Gleap refuses to publish a dynamic email that has no trigger so a forgotten setting cannot turn into a blast.

Yes. The editor inserts variables such as the first name and custom attributes from the contact record, and supports images, buttons, links and multiple languages per project.

Emails sent, opens and unique opens, clicks and unique clicks, click-through rate, bounces and bounce rate, spam complaints and SMTP errors, plus the email clients used and each link's clicks. Recipients and their delivery status are listed per email.

Yes. A one-off email can go to a CSV upload or to a saved contact list. Rules from a contact list can also be imported as the audience of a dynamic email.

An outbound email is a message your team prepares and Gleap sends by rule. Kai Support answers incoming questions, including replies to your campaigns, from your knowledge base and brings the team in when needed. One inbox holds both.

Yes. Publish the release note, then send a one-off email to the audience you choose, for example by plan, attribute or a CSV list. Customers who voted on a feature request get the update you post in that request. From Team, when a bug travels from report to pull request with Kai Resolve and Kai Code, the customer on the ticket hears back once a teammate confirms the fix is live; see how Gleap closes the loop.

Gleap fits when campaign replies should land in the same inbox as support, with the customer's history attached. Teams that need a full marketing suite may keep a dedicated tool. Compare Gleap vs Customer.io and Gleap vs HubSpot.

Yes. Through the Gleap MCP server, an agent drafts newsletters and lifecycle emails, sets the event trigger, delay, frequency and audience from your events and contact attributes, previews the recipients, and publishes or pauses an email once you approve. A one-off email is refused unless its audience has rules, and a one-off that would reach everyone is never sent. If the trigger event is not tracked yet, the agent gets the tracking code for your SDK or backend.

Outbound email 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.