The responses console
Every response lands in the Sliick Responses tab first. Here you find responses, read them, check what they will write to Salesforce, and export them. Open it from the app, or from a form’s Submissions row action on the dashboard.
You can use it with the Sliick Forms Admin permission set, or with Sliick Forms Operator, the set for staff who work on responses but do not build forms. See Install and permission sets.
Nothing is on your Salesforce records yet. A response waits here until it is processed. Processing is a separate step. See Processing responses onto records.
Filter the list
Section titled “Filter the list”Use the filters at the top:
- Status: All statuses, Received, Processing, Completed, Failed, Suspected duplicate, Failed validation.
- Form: one form, or all.
- From and to dates.
- Include test: test responses are hidden until you tick this.
There is no text search in the console. To search, use the dashboard, which searches across forms.
See the answers in the list
Section titled “See the answers in the list”
When you filter to one form, its questions become the table’s columns, up to five, in the order they appear on the form.
When the list covers several forms, each row shows a short summary instead: up to three answers, an email address first if there is one, each cut to 60 characters.
Either way, you see what the respondent sent, whether or not the question is mapped to a Salesforce field.
File uploads, signatures and payments are not shown in the list. Open the row to see them.
Records and forms are named, not shown as Ids. The Result / Error column and the match line name each record, such as Contact Daniel Reyes or Case 00001027, as a link you can open. Forms are shown by name in the Form column, the form filter and the results title. A record you cannot read still shows its Id. Times follow your Salesforce locale and time zone.
With many answer columns, the table scrolls sideways. The Process, Retry, Accept and Mark as genuine buttons stay in view.
Preview what processing will do
Section titled “Preview what processing will do”
Click a row. A panel opens titled What processing would do. It lists every record processing would touch, and for each one:
- the action: Create, Update existing or Create child row,
- the object and the values it would write,
- if the form uses matching, whether this response matches an existing record or would create a new one.
Nothing is written yet. Click the row again to close the panel. If the form maps no fields, the panel says so.
Files a respondent uploaded are attached to the response as soon as it arrives, so you can open them before you process anything. See File uploads.
A response from a public form can take a few seconds to appear. This is normal.
Suspected duplicates
Section titled “Suspected duplicates”
A Suspected duplicate badge means another response to the same form already arrived with the same link id, but with different answers. The response is kept, not thrown away. See Accepting responses for how this happens.
To list only these, choose Suspected duplicate in the status filter. They also show, with the badge, under Received, because their status stays Received.
To deal with one:
- Open the row to see why it was flagged. The panel lists the other responses with the same link id, each named by respondent and the time it was received, earliest first (up to ten, then a count of the rest). The earliest one has no badge, because it arrived first and was treated as normal. The processing preview is still shown.
- If it is genuine, click Mark as genuine. This button replaces Process on a flagged row. It clears the flag and sends the form’s webhook, which was held back. It does not process the response, change its status, send any email, or recheck the response limit (the response already counted). Afterwards, Process appears as normal.
- If it is not genuine, delete its Form Submission record. That also frees its place under the response limit. If it is actually the earliest response you do not want, check the records it created first, then delete it.
Good to know:
- The webhook sends the answers as the respondent sent them, so a correction you saved first does not change what the webhook sends.
- If someone else marked the response genuine a moment before you, Mark as genuine says so and does nothing.
- Sliick Forms Admin and Sliick Forms Operator can mark a response genuine.
Responses that failed validation
Section titled “Responses that failed validation”A Failed validation badge means the response did not pass the form’s checks, but was kept anyway. This only happens when the system sending the response asks for it, using the keepIfInvalid option. Responses from an Experience Cloud page are never kept this way: the respondent sees the errors and fixes them on the page.
To list only these, choose Failed validation in the status filter. The dashboard’s Needs attention list also shows each form that has any.
To deal with one:
- Open the row to see why. The panel lists the checks it failed, then checks it again with any correction you have saved. It either now passes, or still fails and says why.
- Fix it with Edit answers, then open the row again to see the new result. A required answer that never arrived is listed under Not answered in this response, so you can add it.
- Click Accept for processing. This button replaces Process on the row. It clears the flag and sends the form’s webhook, which was held back. It does not process the response or send any email. Afterwards, Process appears as normal.
Good to know:
- If the response still fails, Accept for processing asks you to confirm first, because sometimes the check itself is what is wrong. It also asks if the check could not be run again.
- The webhook sends the answers as they arrived. Your saved correction reaches your records when the response is processed.
- The original reasons stay on the response in its Validation Errors field, as a record of what was overridden.
- A response can be both a suspected duplicate and failed validation. It then shows both buttons. Each clears its own flag, and Process appears only when both are cleared.
- Sliick Forms Admin and Sliick Forms Operator can accept a response for processing.
Export CSV
Section titled “Export CSV”Export CSV downloads every response that matches your current filters (status, form, dates and Include test), across all pages, not only the page on screen. The file is named after the form and the date.
What is in the file:
- One column per question, headed with your question labels, in form order.
- IsTest, so you can spot test responses.
- SuspectedDuplicate, FailedValidation and ValidationErrors. These three were added in version 0.9.0. If another tool reads the file by column position, check it still works after upgrading to 0.9.0.
- A last column with the full raw response.
- Questions you have since removed from the form, headed “(no longer asked)”, so old responses keep all their answers.
Headings, paragraphs, images and other blocks nobody answers are left out.
There is no row limit. A large export runs in the background with a progress bar and a Cancel button.
The file is safe to open in Excel. An answer that looks like a spreadsheet formula will not run, and accented characters display correctly. The translations export works the same way, and re-importing an exported translations file restores it exactly.