Accepting responses
You open or close a form with one switch in the builder.
In the builder’s top bar, click the pill that reads Accepting responses or Not accepting responses. The change saves straight away. There is no separate Save.

Publish a form before you open it. Respondents only ever see a published version, so the builder will not open a form that has never been published. You rarely meet this: publishing a form for the first time opens it for you.
What a respondent sees
Section titled “What a respondent sees”| Form state | What a respondent sees |
|---|---|
| Accepting responses | The form |
| Not accepting responses, and it has been published | Form closed: This form is not accepting responses right now |
| Never published | Form not available, as though the form does not exist |

An unpublished form shows as “not available” rather than “closed”, so nobody guessing links can tell that it exists.
If a respondent already had the form open when you closed it, they are told it is closed when they submit.
A closed form also refuses file uploads, and so does a form that has reached its response limit. Nobody can leave files behind for a response that will not be accepted.
Scheduled windows and response limits
Section titled “Scheduled windows and response limits”A form can also close on its own:
- Open from and Close at set a time window. Outside it, respondents see This form is not open yet or This form is no longer accepting responses.
- Close after this many responses sets a limit. Once it is reached, respondents see This form has reached its response limit.
Set both under Availability in Form settings.
Forms at or near their limit, and forms closing within seven days, are listed in the dashboard’s Needs attention panel.
When a form reaches its response limit, everyone on the notify list gets one email. Notification and confirmation emails arrive shortly after a response, not instantly.
Responses that share a link id
Section titled “Responses that share a link id”A form link can carry an id for each respondent, as the sliickCid value in an emailed link. If two responses to the same form arrive with the same id:
- Same answers (for example a double click or a retry): the response is recorded once.
- Different answers: the second response is kept and marked Suspected duplicate. It counts toward the response limit. It is not processed, and its webhook is held, until someone marks it genuine. The notify list gets one Suspected duplicate summary instead of a New submission email. The respondent still gets their confirmation email.
The same id on two different forms is never a duplicate. Ids that differ only by upper and lower case count as the same id, so use 18-character Salesforce record Ids, not 15-character ones. The placeholder in the email snippet, REPLACE_WITH_RECIPIENT_ID, counts as no id. See The responses console for what to do with a flagged response.
Give each recipient their own random id, never an email address. If everyone gets the same id, for example because a merge tag in the email did not fill in, identical answers are dropped as repeats and different answers are all flagged.
Where the flag shows: on a new install, the Form Submission page layout shows it. An upgrade does not change your existing page layout, so on an upgraded org, look in Sliick Responses.
Where the state is shown
Section titled “Where the state is shown”The dashboard shows a read-only Accepting or Paused badge. Change the state in the builder.
Public forms on Experience Cloud: a closed form only shows as closed if the site’s guest sharing rule still shares it. That rule needs both of its criteria. See Guest access for public forms.