> For the complete documentation index, see [llms.txt](https://docs.simplebooth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplebooth.com/customization-guide/experience-designer/experience-designer-overview.md).
# Experience Designer Overview
The Experience Designer is your hub for customizing the guest journey. While the Layout Designer focuses on the final photo output, the Experience Designer controls the booth’s interface and the overall flow of your event.
These settings manage the visual aesthetic of the booth and the interactive elements participants encounter, such as on-screen prompts, editing tools, and sharing methods. To make navigation easy, settings are organized into three sections based on when they appear in the guest experience.
Customize the experience from your [Preset](https://app.simplebooth.com/presets) settings.
***
To make setup easier, settings are organized chronologically into three sections. Each section includes a set of cards, and each card customizes a different aspect of the experience.
#### [Pre-Capture](/customization-guide/experience-designer/pre-capture.md)
Focuses on the first impression, including the Tap to Start screen and any branding or prompts guests see before they begin.
#### [During Capture](/customization-guide/experience-designer/capture.md)
Controls the camera interface, countdowns, and on-screen guidance while photos are being taken.
#### [Post-Capture](/customization-guide/experience-designer/post-capture.md)
Manages the post-capture experience, including editing tools and sharing methods.
{% hint style="info" %}
The online gallery, where picture are sent after capture, is customized separately. [Learn more](https://docs.simplebooth.com/gallery-design/).
{% endhint %}
---
# 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.simplebooth.com/customization-guide/experience-designer/experience-designer-overview.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.
