Use case

Hear from visitors before they leave

Every number you have is a description of behaviour. None of it is a reason. The cheapest way to get a reason is to let somebody type one on the page where it went wrong.

The situation

You can see that a page loses people and you cannot see what stopped them. Asking is the obvious answer and the usual attempts fail: almost nobody starts a survey, and the ones who do are not the ones who left.

An emailed questionnaire arrives a day later, when the specific frustration has become a vague impression.

How it is done

1. Put the widget on the pages that matter. It has six positions and an opt-out, so it can sit where it will be seen without covering what somebody is reading.

2. Let the context come with it. A comment left on your pricing page arrives attached to that page. The same sentence in a survey response arrives attached to nothing.

3. Publish the ones worth discussing. A submission is never published on its own. Only a topic somebody chose to open becomes public, so a person writing privately stays private. Votes on a public topic are kept for the life of the board.

4. Get it out of the dashboard. Feedback can be pushed to a webhook as it arrives, or exported, so it reaches wherever your team decides things.

Where this stops

It is not a survey builder. No targeting, no branching, no quotas, no recruiting participants. If the job is asking a defined set of questions to a defined audience, buy a survey tool. This is a smaller thing wearing a similar name.

It is not a support inbox. There is no ticketing, no assignment, no reply threads with a customer. What arrives is a comment, not a conversation.

You get who volunteers. People who take the trouble to write are not a sample of your visitors. Treat it as a source of hypotheses, and confirm them with the numbers.