> 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/analytics/bookings-report.md).

# 预订报告

将您的预约和预订数据导出为报告，并直接发送到您的商店管理员邮箱。

## 套餐可用性

报告导出适用于 **Pro** 和 **Premium** 套餐。

## 如何导出

{% stepper %}
{% step %}

#### 打开即将到来的预约

前往 **Sesami > 即将到来的预约** 在您的商店后台中。
{% endstep %}

{% step %}

#### 点击“查看全部”

打开完整的预约列表。
{% endstep %}

{% step %}

#### 选择筛选条件

选择以下之一： **即将到来的**, **全部**, **过去的**，或 **日期范围**.
{% endstep %}

{% step %}

#### 点击“导出”

报告将在几分钟内通过电子邮件发送到您的商店邮箱。
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**频率限制：** 大约每隔 **10分钟**.
{% endhint %}

{% hint style="info" %}
**注意：** 报告日期范围按 UTC 处理。若要导出某一天的所有预约，请将所需日期设为开始日期，并将次日设为结束日期。

**示例：** 若要导出11月3日的预约，请将11月3日设为开始日期，将11月4日设为结束日期。
{% endhint %}

<figure><img src="https://1798155128-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnDgiM1CWSLWRIbhORANO%2Fuploads%2FSTdR5KAVUzEPHCnlpSuz%2FScreenshot%202026-11-04%20at%2012.09.46.png?alt=media&amp;token=44311292-1c94-4ac2-98ad-d078c59b39fa" alt=""><figcaption></figcaption></figure>

## 包含内容

导出的报告包括：

* 预约 ID / 订单 ID
* 团队成员（资源）
* 产品 / 变体
* 时长 / 日期 / 时间
* 客户姓名和电子邮件
* 付款状态
* 改期链接
* 签到 / 未到场状态
* 数量（适用于团体预约）
* 位置
* 资源

{% hint style="info" %}
在 Sesami 中， **团队成员属于资源类型** （资源也可以是房间、设备等）。管理后台导出的报告包含完整的资源和位置字段。
{% endhint %}

## 相关

* [分析](https://help.sesami.co/zh-cn/analytics/analytics.md) — 预订指标和洞察
* [团体预约](https://help.sesami.co/zh-cn/yu-ding/booking-features/group-appointments.md) — 了解导出中的数量
* [位置](https://help.sesami.co/zh-cn/guan-li/locations.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/analytics/bookings-report.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.
