> 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/zh-cn/yu-ding/availability/flexible-slots.md).

# 灵活时间段

灵活时段可让你控制时间段在预订日历上的显示间隔——独立于服务时长。

## 灵活时段的作用

默认情况下，Sesami 会根据服务时长生成时间段。使用灵活时段后，你可以选择可用时间的显示方式——每 15、30、45 或 60 分钟显示一次——为你和你的客户提供更多灵活性。

**示例：** 一个 60 分钟的服务，如果设置为 15 分钟的灵活时段，将显示：

* 上午 9:00、上午 9:15、上午 9:30、上午 9:45、上午 10:00……

如果没有灵活时段，则只会显示：

* 上午 9:00、上午 10:00、上午 11:00……

## 设置灵活时段

1. 前往 **Sesami > 服务 > \[选择一项服务]**
2. 滚动到 **灵活时段**
3. 选择你的间隔： **15**, **30**, **45**，或 **60 分钟**
4. 点击 **保存**

新的间隔适用于 **管理门户** 预订视图和 **在线商店** 日历。

{% hint style="info" %}
如需在你的账户中启用灵活时段，请联系 Sesami 团队，邮箱： <help@sesami.co>.
{% endhint %}

## 何时使用灵活时段

* **更多预订选项** — 较短的间隔可为客户提供更多选择，减少错过预订的情况
* **优化排班** — 通过提供错开的开始时间来填补日历中的空档
* **服务重叠控制** — 结合缓冲时间使用，以管理预约之间的过渡

## 相关

* [缓冲时间](/zh-cn/yu-ding/availability/buffer-times.md) — 在预约之间增加时间
* [当日预订](/zh-cn/yu-ding/availability/same-day-bookings.md) — 控制当天预订的可用性
* [资源可用性](/zh-cn/yu-ding/availability/resource-availability.md) — 设置可用性时间表


---

# 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/zh-cn/yu-ding/availability/flexible-slots.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.