> For the complete documentation index, see [llms.txt](https://uni.fotello.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uni.fotello.co/orders/intake-questions.md).
# Intake Questions
Use Intake Questions to collect the details you need before a customer books a shoot.
When customers book through your booking page, they can answer custom questions as part of the booking flow. This helps you gather access details, special requests, and anything else your team should know in advance.
Submitted answers are saved with the customer's order and appointment.
To get there, go to **Order Form** and click the **Intake Questions** tab, or use [this link](https://app.fotello.co/dashboard/order-form).
### Add or edit intake questions
Fotello includes some suggested questions by default. You can edit them, remove them, or add your own.
{% stepper %}
{% step %}
**Enter your question**
Type the question you want customers to answer during booking.
{% endstep %}
{% step %}
**Choose the field type**
Select the format that fits your question:
* Short Text
* Long Text
* Checkbox
* Dropdown
* Radio Button
* Numerical
* Date Picker
* Yes / No Toggle
{% endstep %}
{% step %}
**Add answer options if needed**
If you choose **Checkbox**, **Dropdown**, or **Radio Button**, enter the answer choices your customer can select.
{% endstep %}
{% step %}
**Make it required**
Turn on **Required** if customers must answer the question before submitting the booking. Customers can skip questions that are not required.
{% endstep %}
{% step %}
**Save your changes**
Click **Save** when you're done.
{% endstep %}
{% endstepper %}
### See answers on the schedule
Once a customer books, their intake answers travel with the appointment so your team has everything they need before arriving on-site.
* **Open the Schedule**
Click **Schedule** in the left navigation.
* **Open the appointment**
Click the appointment to open its details.
You’ll see the property area alongside the address, products, and assigned team members.
* **Expand Intake questions**
Click **Intake questions** to expand the section and read every answer the customer provided during booking.
### Common questions to add
Here are a few questions photographers often use:
* **How will the photographer access the property?**
* Examples: lock box code, SUPRA, gate code, or other access notes
* **Who will be present?**
* Examples: agent, homeowner, or tenant
* **Finished basement?**
* Good fit for a **Yes / No Toggle**
* **Neighborhood or community requests?**
* **Any special notes for the photographer?**
* Examples: special requests, standout features, or anything else to know before arrival
### Example setup
You can create a **Checkbox** question for optional spaces or features.
**Question:** Want photos of these additional areas?
**Options:**
* Utility Room
* Attached Garage
This is useful when customers may want extra coverage but not every property includes the same spaces.
{% hint style="info" %}
Use short, specific questions. This makes the booking flow faster and improves response quality.
{% 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://uni.fotello.co/orders/intake-questions.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.
