In-app surveys and NPS for your product.

An in-app survey asks a question inside your product while the experience is fresh. In Gleap it runs in the widget as a small survey in the corner or a large survey, is triggered by an event, page or audience rule, and identified answers are tied to the contact.

Yes. Net Promoter Score is a question type with three scales: classic 0 to 10, a 0 to 5 scale and an emoji scale. The report shows the score with promoters, passives and detractors and each response with its contact.

Net Promoter Score, numeric scale, smiley rating, single choice, multiple choice, priority selection, short text, long text and file upload. Questions and answer options can be localized per language.

Trigger it with an event your product sends, a page rule or a session condition, narrow the audience with filters on contact data, and set how often it shows, from once to a repeat interval with start and stop dates. The audience preview shows who matches before it goes live.

Yes. Each survey has a hosted link you can send in an email campaign or embed in a page, so people can answer without opening the widget.

NPS asks how likely someone is to recommend your product; CSAT asks how satisfied they were with one experience. In Gleap, NPS is a survey question type, a rating question covers CSAT for a moment like onboarding, and conversation ratings in the inbox cover support satisfaction. See the support platform.

Yes. The survey overview includes an AI summary of the responses as a starting point; the individual answers stay next to it so you can verify the reading.

Yes. Export the responses of a survey as CSV or JSON from the Responses tab, filtered by date range.

Identified responses link to the contact, so a teammate opens the contact and replies from the inbox. A detractor's comment can become a support ticket and a repeated ask a feature request. See product feedback software.

Your team turns a pattern in the answers into a feature request with votes and subscribers, moves it through the public roadmap, and publishes a changelog when it ships. A low score alone does not approve or ship a change.

They are the follow-up measurement in closing the loop: after a fix or feature ships, a survey after the release tells you how it landed, and the answers feed the next request. The wider approach is described on self-driving development.

Surveys are included from the Team plan, together with outbound messaging. See pricing.