---
title: "Microsurvey"
description: "A short 1-3 question survey triggered in-context at a specific moment in your product."
category: "Feedback & Sentiment"
canonical: https://featureos.com/glossary/microsurvey
markdown: https://featureos.com/glossary/microsurvey.md
source: FeatureOS (https://featureos.com)
---

A **microsurvey** is a 1-3 question survey shown inside your product at a specific moment, triggered by a user action rather than a scheduled email blast. It's designed to capture feedback when the experience is fresh, not a week later.

The contrast is a traditional 20-question survey sent on the first of the month. It gets a 4% open rate, answered mostly by people at the extremes. The normal users stay quiet.

## How microsurveys work

Instead of pulling people out of your product to fill out a form, you catch them mid-session. Just finished onboarding? One question. Just exported a report? One question. Just cancelled? Three questions max.

**Response rates are dramatically higher**, sometimes 10x compared to email surveys, because you're asking when the experience is vivid.

## When to use them

They work best for transactional moments: NPS after a milestone, CSAT after a support interaction, quick sentiment checks after a new feature launch. If you need deep qualitative insight, a longer interview is still better. Microsurveys are for high-frequency, low-friction signal.

The trigger is everything. A microsurvey shown at the wrong time is just annoying. Shown right after a key action, it feels natural.

Set them up with [FeatureOS Forms and Surveys](/forms-and-surveys) wired to your product events, and you'll start learning from moments that used to be invisible.

---
Source: FeatureOS — https://featureos.com/glossary/microsurvey
FeatureOS: product feedback, roadmaps & changelogs — https://featureos.com