> 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/availability-and-scheduling/service-area.md).
# Service Area
Service Areas control **where** customers can book you or your team members.
If you don’t add a service area, booking is available for **all locations**.
### Add a service area
{% stepper %}
{% step %}
#### Open Service Area
Go to **Studio Manager → Availability → Service Area** or use [this link](https://app.fotello.co/dashboard/availability/service-area).
{% endstep %}
{% step %}
#### Click **Add Service Area**
This opens the service area panel.
{% endstep %}
{% step %}
#### Choose an area type
Pick how you want to define the area using the **Type** dropdown:
* **Radius** — a circle around one location. Everything within the distance you set is covered. Best for quick, even coverage.
* **Geofence** — a custom shape you draw yourself. Trace exact neighborhoods, city limits, or any irregular area you serve.
{% endstep %}
{% step %}
#### Set your area
**If you chose Radius:** search for your city in the search bar to set the home base location, then set the distance you want to cover by moving the radius slider.
**If you chose Geofence:** search a location to jump the map there, then click on the map to drop points around the area you serve. Press **Enter** or double-click to close the shape. Drag any point to fine-tune the outline, or use **Reset** to start over.
{% endstep %}
{% step %}
#### Assign team members
Assign one or more team members to that service area by selecting the relevant ones from the dropdown.
{% endstep %}
{% step %}
#### Save
Click **Add** to save that service area. You can create multiple service areas if your team members operate in different locations.
{% endstep %}
{% endstepper %}
---
# 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/availability-and-scheduling/service-area.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.
