Book with your AI assistant.

From a conversation to a visit.

Copy the instructions
Paste them into your AI assistant. It will need the ability to submit a website request.
Choose your visit
Share your store, treatment, date, time, room preference and contact email. Authorize the assistant to send those details.
Look out for our reply
Keep your request number. Our team usually replies by email within 1 hour; late-night requests may take longer. Your time and room are confirmed by that 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, 10:00–21:59; the session must finish by 22:00). 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” is a menu version, not a light-pressure setting. A 60-minute warm treatment may be head-and-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.

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 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 authorized 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.

A successful submit means we have received the request. It is not a locked appointment, not an automatic confirmation email, and not a promise that the store will phone you. Staff usually reply within 1 hour; late-night requests may take longer. The confirmation email is the appointment record.

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

The ordinary request form is the backup when an assistant cannot submit. It is the same request: email required, phone optional, confirmation 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. Unknown keys are ignored. Missing store/service become not-sure.
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.

Book with your AI assistant.

From a conversation to a visit.

Copy the instructions

Choose your visit

Look out for our reply