> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/ja/feature-templates/browse-purchase-and-manage-classes/congrats-screen.md).
# おめでとうスクリーン
ブラウズ、購入、およびクラス管理機能テンプレートのおめでとう画面は、クラスの購入体験を完了させます。
シームレスな顧客体験を作るために、常にUXのベストプラクティスを使用し、「成功状態」と呼ばれるものを含めることをお勧めします。これにより、ユーザーがすべてが予想通りに機能したことを認識しやすくなります。この場合、支払いが完了し、クラスの予約が確定したことを示します。
あなたのビジネスを表す画像とテキストでこの画面をカスタマイズしてください。
---
# 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://help.adalo.com/ja/feature-templates/browse-purchase-and-manage-classes/congrats-screen.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.
