Skip to main content
The Feedback Box gives your users a direct channel to share what is on their mind, in two clicks, without leaving your app.

​
Purpose

A low-friction channel catches the small frustrations that never make it into a support ticket. Because it is always available rather than scheduled, it also tells you when something broke.

​
What you will build

A survey that opens whenever someone clicks your Feedback button, and that keeps working every time they click it — not once per person. Two settings get you there, and both are needed: the recontact option, and an exemption from the workspace cooldown.
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 first.

​
1. Start from the template

Open Surveys, click New Survey and choose Choose a template. Search for Feedback Box. The Feedback Box template in the template picker Click the card to create the survey. The template opens with a “What is on your mind, boss?” choice — bug report or feature request — and branches into a follow-up question for each answer.

​
2. Make it yours

Edit the questions on the Questions tab. The wording matters more than it looks: “What is on your mind, boss?” sets a casual tone that suits some products and not others. Keep it short. Every extra question costs you responses, and the value of a feedback box is that answering it is nearly free.

​
3. Trigger it on your Feedback button

Open the Settings tab and find Survey Trigger. Click Add action, then Capture new action. The Add action dialog, on its Capture new action tab Name the action, leave the type on Click, and identify your button in one of two ways:
  • Inner Text — matches the visible text of the element that was clicked. Switch it on and enter Feedback if that is what your button says.
  • CSS Selector — matches a class or id, such as #feedback-button. Use this when the label is translated, or when several elements share the text.
Switch on both and the click has to match both to count. Once created, the action appears under the trigger: The Survey Trigger section with the Feedback action attached
Reusing a button that already exists? Select saved action lists every action in the workspace, so you do not have to define the same click twice.

​
4. Let it open every time

By default a survey is shown to each person once. That is wrong for a feedback box — someone who reports a bug on Monday should still be able to request a feature on Tuesday. Still on Settings, open Visibility & Recontact and choose Keep showing while conditions match. Recontact options, set to keep showing while conditions match Then, in the same section, choose Ignore Cooldown Period. This second setting is not optional if you want the box to open on every click. Recontact Options and the Cooldown Period are two separate gates and a survey has to pass both: Recontact Options are evaluated first, then the workspace-wide cooldown. So a box set to “keep showing” but left on Use Cooldown Period still goes quiet for a week after any other survey has appeared — which looks exactly like the feature being broken.
Ignoring the cooldown is the right call here and not in general. It is defensible because the user opened this survey deliberately; a survey that interrupts them uninvited should stay inside the workspace budget.

​
5. Publish

Publish puts it live. The widget picks up the change within a minute.

​
Where the feedback goes

Responses land in the survey’s Responses tab like any other. Two things worth setting up on day one:
  • A Workflow that emails whoever triages feedback, so nobody has to remember to check.
  • Tags on the responses, so “bug” and “feature request” stay separable once there are hundreds of them.