Review and manage form responses
Filter and export submissions, open responses with contact and ticket, check files and delete responses
Every form has the Responses tab in its detail area. There you see the submissions of this one form. The list uses a server-side data table: sorting and filters are sent to the API instead of only searching the page already loaded in the browser.
For the form overview and individual responses you need forms.view. Deleting responses – individually or in bulk – requires forms.delete. A missing permission hides the page or the delete action.
Open responses
Select the form
Open Forms and click the form you want. Then open the Responses tab or go directly to the Form responses page at /dashboard/forms/[formId]/submissions.
Open a response
Click a table row or Open response. The detail page is at /dashboard/forms/[formId]/submission/[submissionId]. With Back to responses you get back to the filtered form view.
Interpret an empty list
An empty list means there are no matching submissions for this form. First check the mode and date filters, then whether the form has been published.
Filter and sort the list
The default sort is Received at, descending, so the newest responses are on top. Every column can be shown or hidden, and the table supports the usual table functions for sorting, filtering and exporting the visible data.
Fixed columns
The list can show, among others, the following information. Via the table actions you can also export matching records as JSON, CSV, XLSX or PDF and choose the export columns:
- Submission: internal ID of the response.
- Received at: time of submission.
- Mode: Production or Preview.
- Status: currently mostly Submitted.
- Submitted by and Respondent: if SimpliServ knows these details.
- Source, Device, Browser and Country: visitor signals from the detected session, if available.
With the column filters you can search by ID, date or the available text values. Mode and status have multi-select filters, so for mode you can choose production, preview or both.
Form fields as columns
All named form fields that are not pure layout elements are additionally shown as columns. The first four field columns are visible by default; you can enable more field columns in the table settings.
Layout fields such as divider, page break and text section create no response column. Values are displayed readably depending on the field type:
- Choice values are shown with their field label instead of only the technical value.
- Country and vehicle values are resolved when the corresponding name is known.
- Yes/no fields appear as Yes or No and can be filtered with a boolean filter.
- Date fields are formatted as date and time and have a date filter.
- Selection fields such as select, radio, multi-select and checkbox group offer an option filter.
- Signatures can be displayed but not meaningfully filtered or exported as a sortable text value.
Use unique field names. Certain technical names such as id, status, country, city, browser or source_label already belong to the fixed response or visitor columns. SimpliServ protects against such collisions internally; clear field names of your own still make filters and exports much easier to read.
Tell production and preview responses apart
A submission from the published public version has the mode Production. Submissions from the builder preview have Preview. Preview responses are useful for testing validation, conditions, file uploads and mappings; they should not be confused with real leads or customer requests.
If you only want to work on real submissions, filter the mode to Production. Before deleting a test response, always check the mode in the table row or on the detail page.
Read the detail page
The detail page shows the time of receipt at the top and – if known – who submitted the response. Preview submissions carry the Preview badge.
Below are the answers in the order of the form fields. Choice values appear with their label, countries and vehicles resolved, ratings as stars, signatures as an image. You open images and videos in a preview, other files via their file link.
If a contact or ticket was created from the submission (via the form's mappings), you jump there directly at the top with Open ticket or Open contact. The page then also shows the contact details and the conversation with the customer, from which you can write a new email directly.
Files and signatures
File answers are shown as attachments in the field value. Images can be enlarged, videos played directly in the shared preview, and other files opened in a new tab, provided a valid file link is available. The detail view shows the file type and – if available – the file size.
Signature fields are deliberately not normal text columns. In the list they appear as a preview without a filter or export value; on the detail page the signature is shown visually.
Delete responses
You can delete a response via the action menu on the detail page with Delete response. In the list you can also select several rows and delete them in bulk. Both actions require confirmation; deletion is permanent.
Only delete preview responses after checking the mode. For a production response the stored field values are lost. Save any information you need beforehand via the table export.
Practical review routine
- First filter to Production if you want to work on real submissions.
- Sort by Received at to review the latest responses.
- Show the form fields and visitor columns you need.
- Open a response and jump to the linked ticket or contact if needed.
- Open attachments directly from the field and check that they are fully accessible.
- Delete test data only after the review and confirm only the rows you really selected.
Responses, analytics and tracking
The Insights tab of the same form shows key figures, trends and breakdowns by source, device, country and browser. The Responses tab is the operational list of individual submissions. For website conversions you can also set up form tracking with GTM. Tracking reports successful submissions to your website; it does not replace the response stored in SimpliServ.
Related topics
How is this guide?