Response detail

Click any row in Responses to open a single submission.

Response data

The raw answers, one row per field, in the order they appear on the form — question label on the left, the visitor's answer on the right.

Status and Assignee

Status starts as New. Use Change status to move it through your own workflow (e.g. in progress, resolved) — this is manual, nothing sets it automatically. Assignee lets you hand the response to a specific teammate; Assign to me is a shortcut for claiming it yourself.

Overview

A quick-glance card:

• Rating — the response's satisfaction score on the app-wide 1–5 scale (the same number shown in the Responses table and used by the 1–5 filter slider), computed by the backend from the raw answer to whichever question is flagged as the survey's main evaluation question — see "General satisfaction and default feedback text" below.
• Starred — whether you've flagged this response (toggle from the Responses table or this page).
• Submitted — the exact timestamp.
• Device, Browser / OS, Viewport — the summarized version of the full details further down the page.

General satisfaction and default feedback text

Every survey has exactly one field flagged as its main evaluation question and one flagged as its main feedback question (set per field in the survey editor's Meta tab):

• General satisfaction is whichever question is flagged as the main evaluation question — a response's overall satisfaction score (the number shown throughout the app, including the 1-5 filter range) always comes from that question's answer, not from averaging every question on the form.
• Default feedback text is whichever question is flagged as the main feedback question — it's the text shown as "the" response in places (like the Responses table) that only have room for one line, even if the survey has several free-text fields.

Popup surveys require both flags to publish; inline surveys only warn if they're missing.

Page context

Where the widget was embedded when this response was submitted: the page URL (opens in a new tab), the average satisfaction score across all responses collected on that exact URL, and a short list of other recent feedback from that same page — useful for spotting whether a low score is a one-off or part of a pattern tied to a specific page.

Page snapshot

View snapshot opens a rendered screenshot of the page as it looked at submission time — handy for reproducing a layout-specific bug report without needing the visitor to describe what they saw. If the survey has element selection turned on and the visitor pointed at something, that part of the page is outlined directly on the screenshot, in the color set under Attributes.

Selected element

Only shown when the survey has element selection turned on and this particular visitor chose to point at something rather than give general feedback. A small, always-visible card — separate from Page snapshot above — showing just that one part of the page on its own, cropped and fully styled, so you don't have to open the full snapshot to see what they meant.

Browser & device data

Collected automatically at submission time, no extra config needed: platform, browser language, widget version, CPU core count, device memory, whether cookies are enabled, whether the visitor looks like an automated browser, PDF-viewer support, and the full user-agent string. Useful for reproducing a bug a specific visitor hit, or for the browser/OS/device dashboard breakdowns.

Technical details

The identifiers behind this response: its own Response ID (copyable, useful when referencing a specific submission in support conversations), which domain and survey it belongs to, and the exact page URL again.

Activity log

A running history of what's happened to this response: starred/unstarred, status changes (with an optional comment explaining why), and manual notes added by your team (Add comment). Newest first.