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. When people should point at a spot on the page instead, use the website feedback tool.

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. A one-off audience or a CSV upload sends it once to a fixed list of people.

Yes. Share a survey by link, or create an email campaign for it from the survey's share options, so people can answer without opening the widget. The SDK can also open a survey from your own code.

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 multichannel 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 Gleap's customer feedback software.

Yes, when your team acts on them: a pattern in the answers becomes a feature request with votes and subscribers, moves through the public roadmap, and a changelog goes out when it ships. A low score alone does not approve or ship a change.

Yes. Connect Claude, ChatGPT, Codex, Cursor or another MCP client to the Gleap MCP server and the agent can draft surveys with their questions, target them by trigger, page, events and contact attributes, preview how many people match, and read responses and AI summaries. When the audience needs an event your app does not track yet, the agent gets the tracking code for your SDK instead of guessing. Drafts wait for your review, and the agent works with the role of the person who connected it.

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.

Gleap fits when you want to ask inside your product and follow up in the same workspace as support. For long research questionnaires, a dedicated form tool can fit better. Compare Gleap vs SurveyMonkey, Gleap vs Typeform and Gleap vs GetFeedback.

Surveys are included from Team ($149 per month, billed annually), together with outbound messaging. See pricing.