> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/booking/booking-experiences/resource-selection.md).

# Resource Selection

Let customers pick a specific resource — a team member, room, or equipment — as part of their booking flow, or have Sesami assign one automatically.

{% hint style="info" %}
"Resources" is the new term in the Sesami Admin Portal. In the Shopify app, this is still labeled "Team". A team member is one type of resource — rooms and equipment are others.
{% endhint %}

## When to Use Resource Selection

Resource selection works well when the choice of resource matters to the customer:

* **Personal services** — hair, massage, coaching, tattoo, training
* **Provider loyalty** — customers rebooking with the same person
* **Room or equipment preference** — specific treatment rooms, studios, or gear
* **Expertise matching** — customers choosing a specialist for their needs

## Configure Resource Selection

Resource selection is configured per service and per service **per location**, with fine-grained control over how each resource group behaves in the booking experience.

1. Go to **Services** and open a service
2. Click **Manage resources** for the location you want to configure
3. In the **Resources** dialog, you'll see one or more resource groups (e.g., "One of these resources")
4. For each group, toggle:
   * **Selectable in Experience** — when on, customers can pick from this group during booking. When off, Sesami auto-assigns from the group.
   * **Blocks during booking** — reserves the resource for the duration of the booking so it can't be double-booked
   * **"Any Available"** — if two or more resources are available at the same time, Sesami assigns one randomly. There isn't a way to prioritize specific resources for auto-assignment.
5. Use **Add a resource** to add more resources or resource groups
6. Click **Confirm**, then **Save**

{% hint style="info" %}
To remove “Any available” or a specific resource, place the cursor over the resource and click the X to remove it.
{% endhint %}

<figure><img src="https://934599958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnDgiM1CWSLWRIbhORANO%2Fuploads%2FQMHIh1AA6qDZrhyIlUt7%2FScreenshot%202026-09-09%20at%2018.35.13.png?alt=media&amp;token=ad262d12-8873-4071-b52f-395340a272f4" alt=""><figcaption></figcaption></figure>

## Recommendations

{% hint style="success" %}
Showing both **"Choose a resource"** and **"Any available"** typically converts better — customers who care about the choice can make it, and everyone else takes the fastest path.
{% endhint %}

* Make sure every resource has availability configured; otherwise, they won't appear as options
* Keep resources assigned to the right services under **Sesami > Services**
* For multi-resource services (e.g., a stylist **and** a room), Sesami handles the combined assignment automatically

## Related

* [Resources](https://help.sesami.co/admin/resources.md) — set up team members, rooms, and equipment
* [Resource Availability](https://help.sesami.co/booking/availability/resource-availability.md) — configure each resource's schedule
* [Services](https://help.sesami.co/admin/services.md) — assign resources to services
* [Assigned to No One - Invalid Order](https://help.sesami.co/get-started/onboarding/troubleshooting/troubleshooting-assigned-to-no-one-caused-by-invalid-order.md) — resource assignment troubleshooting


---

# 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.sesami.co/booking/booking-experiences/resource-selection.md?ask=<question>&goal=<user_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.
