> ## Documentation Index
> Fetch the complete documentation index at: https://formbricks.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Feature Chaser

> Ask about one feature, immediately after it has been used.

A feature chaser asks about a single feature the moment someone finishes using it.

## Purpose

Feedback about a feature collected days later is feedback about the memory of it. Asked on the spot, you get the friction while it is still fresh — and only from people who actually used the thing.

## 1. Start from the template

Open **Surveys**, click **New Survey** and choose **Choose a template**. Search for **Feature Chaser**, then click the card to create the survey.

![The Feature Chaser template in the template picker](https://mintcdn.com/formbricks/5gmPPlpgcBxnNfUX/images/surveys/best-practices/feature-chaser/template.webp?fit=max\&auto=format\&n=5gmPPlpgcBxnNfUX\&q=85\&s=584107df4201740f173fe630a0b14041)

The template is deliberately short. One question about the feature is the point; a second question turns a quick answer into a form.

## 2. Trigger it at the right moment

Identify the click that means "finished using the feature" — usually the last button in the flow, such as **Export Report**. Match it with **Inner Text**, or with a **CSS Selector** such as `#export-report` if the same label appears elsewhere.

Open the **Settings** tab, find **Survey Trigger** and add the action.

![The Survey Trigger section with the action attached](https://mintcdn.com/formbricks/5gmPPlpgcBxnNfUX/images/surveys/best-practices/feature-chaser/trigger.webp?fit=max\&auto=format\&n=5gmPPlpgcBxnNfUX\&q=85\&s=9c056938841dcf0ce6ed37d1afddb080)

> [!TIP]
>
> Creating the action itself — Click versus Page View, Inner Text versus CSS Selector — is the same dialog
> in every recipe. It is walked through once on the [Feedback Box](https://formbricks.com/docs/surveys/best-practices/feedback-box.md)
> page, and the full reference is the [Actions manual](https://formbricks.com/docs/surveys/website-app-surveys/actions.md).

## 3. Decide how often it may appear

Still on **Settings**, open **Display & Recontact**. Choose **Show only once** for a one-off read on a new feature, or **Ask until they submit a response** if you want to keep asking until someone answers.

> [!NOTE]
>
> Recontact Options and the workspace-wide [Cooldown Period](https://formbricks.com/docs/surveys/website-app-surveys/cooldown-period.md)
> are two separate gates and a survey has to pass both — Recontact Options first, then the cooldown. If
> your workspace shows at most one survey a week, this survey inherits that unless you set **Ignore
> Cooldown Period**.

## 4. Activate

**Activate** starts it. The widget picks up the change within a minute.

> [!NOTE]
>
> This is an app survey, so it needs the Formbricks widget running in your product. If you have not
> installed it yet, follow [the quickstart](https://formbricks.com/docs/surveys/website-app-surveys/quickstart.md) first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.