The responses console

Every submission lands here first. The Sliick Responses tab is the working surface for staged submissions: find them, read them, check what they will write, and export them. Open it from the app, or from a form’s Submissions row action on the dashboard.

Nothing has been written to your Salesforce records yet. A submission stages in this console, and processing is the separate step that maps it onto records. See Processing responses onto records.

Filter the list

Filter with the status picker (All statuses, Received, Processing, Completed, Failed), the form picker, a from and to date range, and an Include test checkbox. Test-respondent submissions are hidden until you tick it.

There is no free-text search here: searching happens on the dashboard, across forms rather than responses.

See the answers in the list

Filtered to one form, each row’s own questions become the table’s columns, up to five, in field order. Without a form filter, or with a status or date filter spanning several forms, each row instead shows a short summary line: up to three answers, an email-looking one first if there is one, each capped at 60 characters.

Either way this reads straight off what the respondent submitted, so an answer shows whether or not its field is mapped to a Salesforce field: mapping decides what processing writes onto target records, not what you can see here.

File uploads, signatures, and payment fields are never shown in either view; open the row for those.

Preview what processing will do

Click the row. The panel that opens is a dry run, titled What processing would do. It shows every record processing would touch: Create, Update existing, or Create child row, the object, the field values it would write, and, where the form has matching fields, whether this submission matches an existing record or would insert a new one.

Nothing is written at this stage. Click the row again to close the panel. If the form maps no fields at all, the panel says so rather than showing an empty plan.

Any files a respondent uploaded are attached to the submission record as soon as it is received, so you can open them while reviewing, before you process anything. See File uploads.

A response from a public form can take a few seconds to appear. Answers from an anonymous visitor are staged through a background step rather than written on the spot, which is what keeps visitors away from the response records themselves.

Export CSV

Export CSV downloads every submission matching your current filters, including status, form, date range and Include test, across all pages rather than just the page on screen. Each row carries the answers as a JSON cell and an IsTest column, so test-respondent rows stay identifiable once you include them.

The export stops at 2000 rows without saying so, while the count above the table keeps showing the true total. If those two numbers disagree, narrow the date range and export in slices.