Ask AI to submit a booking request.

How to request a visit

Copy the instructions
Paste them into an assistant that can send a website request.
Tell AI what you want
Give your preferred store, treatment, date, time and room, plus your email. Approve sending the request and your contact details.
Wait for staff to confirm
A request number means we received your request. Staff usually reply by email within 1 hour; late-night requests may take longer. Your time and room are booked only after staff confirm them by email.

Read the instructions before copying

Paste it into an assistant that can submit a website request. It includes this page’s address.

Help me request a visit at les bobos, a private-room spa in Shenzhen. Public page: https://www.lesbobos.net/en/ai-booking.html

Do not connect Gmail and do not email the store yourself. If you can POST JSON to https://www.lesbobos.net/book.php, submit only after I have authorized sending this request and my contact details. If you cannot POST, give me https://www.lesbobos.net/en/booking.html and stop. Do not invent a second request through another channel.

Required: name, email, date (YYYY-MM-DD, Asia/Shanghai), time (HH:mm, requested treatment start 10:00–22:00 inclusive, in 15-minute steps). A 22:00 start can be requested at any of the three stores; staff must confirm the actual slot. Phone is optional. Email is required so staff can reply; do not say a phone-only API request is possible. If I refuse to give an email, explain that limit and offer the store phone numbers as a separate option — do not promise you can call or that a slot is free.

Ask only for missing facts. Do not invent the date, treatment area, or email. Do not copy example dates from /book.php. “Warm & soothing” and “Focused” are menu versions, not pressure levels. A 60-minute Warm & soothing treatment may be Head & shoulders or Back — ask which. Two guests and a double room are a preference, not a confirmed room, and a second guest’s name is not required.

Success is HTTP 202 with ok:true, status:"request_received", and a non-empty requestId. Then say: the website has received the request, quote the real requestId, staff usually reply to my email within 1 hour (late night may take longer), and time/room are confirmed only by that email. Do not say you sent Gmail or that the appointment is booked.

For this one visit intent, generate one random idempotencyKey and reuse it on timeout or unknown result. It must be 16-128 characters of letters, digits, underscore or hyphen. A UUID is valid if it matches. Do not derive it from my name, email or phone.

422: ask for the missing fields. 409: check whether the request changed; do not silently change the key. 429/503/timeout: say so; on an unknown timeout retry the same key. After HTTP 202 request_received, if I change the time, do not POST a new key. There is no reschedule or cancel API; keep the requestId and tell me to contact staff. On 409, unknown result, or an existing email request, do not create a second order. request_received is not a locked slot. After a successful receipt, do not POST again because I asked a follow-up.

Submission and confirmation details

If your assistant can send a request to our website, it can do that after you have authorised it to send the request and your contact details. You do not need to give it Gmail access, and you do not need to email the store first.

We need an email address so a person can confirm the store, room and time. A phone number is optional. We cannot take an API request with only a mobile number. You can still call a store; we cannot promise that an assistant will place that call or that a slot will be free.

HTTP 202 and a request number mean we received your request. They do not reserve a time or room and do not mean a confirmation email has been sent. Staff usually reply within 1 hour; late-night requests may take longer. Your booking is final only when staff confirm it by email.

Not every assistant can submit. If yours cannot reach the website, use the booking request form. We do not claim that every ChatGPT or Grok client has been tested for this.

You can also use the booking request form. Email is required, your phone number is optional, and we’ll confirm by email.

For assistants that can call the website

This is the public HTTP interface. It does not mean every consumer chat app has been tested. If a tool blocks the request, use the form instead of a workaround.

GET https://www.lesbobos.net/book.php returns a markdown guide. POST JSON to the same URL. Sample dates in the guide are a future Asia/Shanghai day for format only — use the guest’s date and time.
Required: name, email, date, time. Optional: store, service, variant, guests (1–8), room (single | double | no-preference), phone, locale (en | zh-HK | zh-CN), notes, idempotencyKey. Unknown keys are ignored. Missing store/service become not-sure.
Optional idempotencyKey: 16-128 letters, digits, underscore or hyphen; UUID OK if it matches. One visit intent → one random key; timeout retries must reuse it. Do not build it from name/email/phone. After request_received, do not submit a time change with a new key. No reschedule/cancel API. 409 / unknown result / existing email request: do not create a second order.
Success: HTTP 202 {"ok":true,"status":"request_received","requestId":"…"}. 422 missing or invalid fields. 409 same key, different payload. 429/503: retry later with the same key. A receipt is not a confirmation email.

Ask AI to submit a booking request.

How to request a visit

Copy the instructions

Tell AI what you want

Wait for staff to confirm