Forms and their responses
A form is how a visitor says something to you that is not an order: a contact inquiry, a newsletter signup, a wholesale application, a returns request.
CIQRA builds these without code — you add fields, set validation on each, and publish.
The fields, and what validation is actually for
Section titled “The fields, and what validation is actually for”A form is a list of fields, each with a label (what the visitor reads) and a key (how the response is recorded). The available shapes are:
short text · long text · email · phone · number · dropdown · checkbox · date · file upload
Each field can be marked required and given bounds — a minimum and maximum length for text, a minimum and maximum value for numbers, and a pattern for anything with a fixed shape.
Validation here is not about data hygiene for its own sake. Every rule you add is a rule the visitor has to satisfy before the response reaches you, which means it is also a rule you are imposing on a customer who is trying to reach you. A required field that is merely nice to have is a customer who gave up.
The editor shows a preview of how the form reads to a visitor. Use it — a form is a piece of writing before it is a data structure.
Responses arrive in two places, and only one of them is durable
Section titled “Responses arrive in two places, and only one of them is durable”| Where | What it is |
|---|---|
| The responses screen | Every submission to this form, kept in CIQRA, paged and searchable by response. |
| The notification email | A copy of each response emailed to one address, as it arrives. |
The notification email is a convenience, not a record. Leave it blank and nothing is lost — the responses screen still holds everything. Set it and you get a nudge, but an inbox rule that archives those mails does not archive the responses.
🔴 Deleting a response deletes it. It is removed from the inbox permanently, and deleting the whole form removes the form and every response it ever collected. If responses matter to your business, export or copy what you need before you tidy up.
Two switches decide who actually reaches you
Section titled “Two switches decide who actually reaches you”Accepting responses pauses the form without deleting it. A paused form stays on the page it was placed on and stops accepting submissions — the right move for a seasonal application window, and much better than deleting the form and losing its responses with it.
Require CAPTCHA adds a bot check before a response is accepted. Turn it on for any form that is reachable from a public page. A contact form without it does not fill with spam gradually; it fills all at once, on the day it is found, and the real inquiries are then buried in it.
After a visitor submits
Section titled “After a visitor submits”The success message is what they see. It has a default, and the default is a placeholder — “Thanks — we’ll be in touch!” is fine for a contact form and wrong for a wholesale application where the honest answer is “we reply within three working days”.
This is the one line of a form most worth writing yourself, because it is the only part of the exchange where you set the customer’s expectation of what happens next.
What this page does not say
Section titled “What this page does not say”- It does not describe placing a form on a page. That is the content editor’s job; a form is built here and referenced there.
- It does not cover what happens to uploaded files. A file-upload field accepts a file; where that file is stored and for how long is a media question, not a forms one.
- It does not describe exporting responses. Data export under Settings covers selected store data; whether form responses are inside that selection is stated on that screen, not here.