> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/strona-podziekowania.md). # Thank-you page A thank-you page is the last page of a form/process, displayed after the application save point. Such a page may contain: a thank-you for the completed action (e.g. "Thank you for completing the application"), the application/request number, information about next steps, and links (e.g. an invitation to use other services).

Figure 1. Example appearance of a thank-you page

### There are 2 thank-you page options: * Platform thank-you page - that is, a situation where the application contains no page after **the application save point** ([Application save point - last pages mechanism](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/punkt-zapisu-wniosku-i-mechanizm-ostatnich-stron.md#mechanizm-ostatnich-stron)).

Figure 2. Example application structure (Steps tab), after which the client will see the platform thank-you page

* Dedicated thank-you page - that is, the page/pages that were added by the designer and are displayed after **the application save point** ([Application save point - last pages mechanism](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/punkt-zapisu-wniosku-i-mechanizm-ostatnich-stron.md#mechanizm-ostatnich-stron)).

Figure 3. Example application structure (Steps tab), after which the client will see the dedicated thank-you page.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/strona-podziekowania.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.