> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/surveys/question-configuration/terminating-a-survey.md). # Terminating a Survey Navigate to the Survey Termination options by clicking in the Details panel, choose Terminate Survey as Question Type. Click Save Navigate to the Survey Termination options by clicking in the Details panel, choose **Terminate Survey** as Question Type. Click **Save** **Tip:** Surveys do not display text written in a terminate survey question box. To enter text to terminate a survey, the user must first put a break question with desired text then an empty **Terminate Survey** question. **Note:** Skip patterns skip to pages, not questions. When you have a skip to a terminate survey question, it skips to the top of the page that holds the terminate survey button. A survey participant will have to view every question on that page before the survey terminates. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.shiftiq.com/help/surveys/question-configuration/terminating-a-survey.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.