# VibeBooking Docs

The VibeBooking console is where you publish your property's details in a form AI agents can read. New here? Start with [Getting started](https://docs.vibebooking.ai/en/getting-started).

## Reading these docs from an AI agent

Add `.md` to any page's URL to get it as Markdown, or request the page with `Accept: text/markdown`.

```sh
curl https://docs.vibebooking.ai/en/getting-started.md
```

| URL | What it holds |
| --- | --- |
| [/llms.txt](https://docs.vibebooking.ai/llms.txt) | A list of every page, Japanese and English |
| [/llms-full.txt](https://docs.vibebooking.ai/llms-full.txt) | The text of every page, Japanese and English |
| [/llms-full.en.txt](https://docs.vibebooking.ai/llms-full.en.txt) | The English pages only |
| [/llms-full.ja.txt](https://docs.vibebooking.ai/llms-full.ja.txt) | The Japanese pages only |

What an assistant can do for you, and what stays with you, is in [What AI assistants can and cannot do](https://docs.vibebooking.ai/en/ai-assistants).

# Getting started

> **Plans**
>
> Everything on this page is available on every plan.

## What the console is for

The console is where you publish your property's details for AI agents to read. In it you:

- add your property's website (**Add a property**)
- connect your reservation system so rates and availability can be read (**Connect a reservation system**; see [Beds24](https://docs.vibebooking.ai/en/connect-beds24) or [Channex](https://docs.vibebooking.ai/en/connect-channex))
- check what will be listed on the **Facts** and **Preview** tabs, then press **Go live** (see [Go live](https://docs.vibebooking.ai/en/go-live#go-live))
- once live, see on **Home** how often AI read your pages (see [Read the report](https://docs.vibebooking.ai/en/report))

## Sign in

![The console sign in screen, with Continue with LINE and Continue with Google buttons.](https://docs.vibebooking.ai/screenshots/en/sign-in-desktop.webp)
*The sign in screen. Only an invited account can sign in.*

1. **Open the console**

   Go to [console.vibebooking.ai/en](https://console.vibebooking.ai/en). You land on **Sign in**. There is no password.

2. **Choose an account**

   Press **Continue with LINE** or **Continue with Google** and sign in with the account you already use.

3. **Your account is created**

   The first time you sign in, the console creates your account and opens **Home**. You are its **Owner**. If you came from an invitation link, you see **Invitation to VibeBooking** instead (see [If you were invited](https://docs.vibebooking.ai/en/getting-started#accept)).

## Invite someone

Invite the people you work with by email. Only the **Owner** can invite. Anyone else who opens **People** sees "The owner manages people."

1. **Open People**

   Press **People** in the menu.

2. **Enter an address and a role**

   Under **Invite someone**, fill in their **Email address** and pick a **Role**.

3. **Send the invitation**

   Press **Send the invitation**. They receive an email with the subject "You're invited to VibeBooking". The invitation works for 7 days. Right after sending, **Revoke** on the same screen takes it back.

![The invite someone form, with fields for an email address and a role.](https://docs.vibebooking.ai/screenshots/en/people-invite-desktop.webp)
*The invite someone form.*

What each role can do is below. An invitation offers **Manager** or **Viewer**.

| Role | What it can do |
| --- | --- |
| **Owner** | Everything, including paying, people and deleting the account. |
| **Manager** | Connect, go live, edit facts. Not people, not deleting the account. |
| **Viewer** | Sees everything, changes nothing. |

### If you were invited

1. **Open the link in the invitation email**

   Sign in, and **Invitation to VibeBooking** opens with the account and the role you are invited as.

2. **Press Accept**

   You join the account. To say no, press **Decline** instead.

![The invitation screen opened from the email link, with the role explained and Accept and Decline buttons.](https://docs.vibebooking.ai/screenshots/en/invitation-accept-desktop.webp)
*What the link in the invitation opens.*

A link older than 7 days no longer works. Ask the person who invited you to send a new one.

# What AI assistants can and cannot do

> **Plans**
>
> Everything on this page is available on every plan.

## What works today

Connect VibeBooking to ChatGPT or Claude and your assistant can help with these. [Connect an AI assistant](https://docs.vibebooking.ai/en/connect-assistant) has the steps.

- Check your site and find what AI cannot read on it
- Add your property's website, and link it to the reservation system you have connected
- Draft your property's details from your site, your reservation system or text you paste, and ask you to check them
- Draft details shared by all your properties
- Add room types by hand and match them to your reservation system's
- Set up a custom domain until its record takes effect. You choose the properties it serves
- Read your report, your connections and what to do next
- Read these docs and walk you through a task

Every page is also plain Markdown: add `.md` to its URL. [/llms.txt](https://docs.vibebooking.ai/llms.txt) lists every page.

```sh
curl https://docs.vibebooking.ai/en/connect-beds24.md
```

### An assistant only ever drafts

Anything an assistant writes about your property is saved as a draft, next to what is listed now. Nothing it writes is listed until you say so.

An assistant never publishes, approves or goes live. No setting changes that.

### The three things you do yourself

These three steps stay yours:

1. Create your account and allow the assistant to connect.
2. Connect your reservation system ([Beds24](https://docs.vibebooking.ai/en/connect-beds24), [Channex](https://docs.vibebooking.ai/en/connect-channex)).
3. Check the assistant's drafts, and publish them.

### Checking the drafts

When an assistant asks you to check its drafts, a notice arrives in your inbox and by email. However often it asks, you hear at most once an hour.

1. **Press Review them**

   **Review before publishing** opens, one draft to a card, each next to what is listed now.

2. **Choose the drafts to publish**

   Tick **Publish** on each draft that is right. Press **Edit** to change one first, or **Reject** to drop it.

3. **Press the publish button**

   The button names how many drafts go live, such as **Approve and publish 2**. Check the number, then press it.

![The Review before publishing screen, with each suggestion from an assistant beside what is live now.](https://docs.vibebooking.ai/screenshots/en/review-drafts-desktop.webp)
*Review before publishing: each suggestion sits beside what is live now.*

What you approve counts as your own words.

## An assistant should never guess

Your prices, cancellation terms, capacity and check-in times come from you or from your reservation system, nowhere else. These docs tell AI assistants not to guess anything they do not say.

If an answer does not look right, check it on the console's screens.

# Connect an AI assistant

> **Plans**
>
> Everything on this page is available on every plan.

Add VibeBooking's address to ChatGPT or Claude and your assistant can check your site and draft your property's details. You check the drafts and publish them yourself.

## Before you start

- No account yet? You do not need to make one first. When the assistant asks you to sign in, sign in with Google: the account is created with you as its **Owner**, and you go straight on to allow the connection. While the console is invitation-only, this works only for an email address we have contacted (see [Sign in](https://docs.vibebooking.ai/en/getting-started#sign-in)).
- Already in an account? Your role there is **Owner** or **Manager**. A **Viewer** cannot connect an assistant.

## Find the address

Open **Settings** and choose **Connected assistants**. **Set up with an AI assistant** shows the address to add, and **Copy the address** copies it.

```text
https://mcp.vibebooking.ai/mcp
```

![The Connected assistants tab, showing the address to add to an assistant and a Copy the address button.](https://docs.vibebooking.ai/screenshots/en/assistant-address-desktop.webp)
*The Connected assistants tab.*

## Add it to Claude

Any plan can add it: Free, Pro or Max. Free allows one custom connector.

1. **Open the connector settings**

   In Claude, open Settings and choose Connectors. Press Add, then Add custom connector.

2. **Enter the address**

   Enter a name (such as VibeBooking) and the address, and press Continue. Claude shows two sign-in options: leave both as they are and press Add.

3. **Connect**

   Press Connect. The console's confirmation page opens. Check it and press **Allow** (see [What to check before you allow it](https://docs.vibebooking.ai/en/connect-assistant#consent)).

## Add it to Claude Code

Add it from the terminal. No key is needed.

1. **Add it with a command**

   Run the command below. It adds the server to the project you are in; add `--scope user` to use it in every project.

   ```sh
   claude mcp add --transport http vibebooking \
     https://mcp.vibebooking.ai/mcp
   ```

2. **Sign in**

   In Claude Code, type `/mcp`, choose vibebooking and press Authenticate. The console's confirmation page opens in your browser. Check it and press **Allow** (see [What to check before you allow it](https://docs.vibebooking.ai/en/connect-assistant#consent)).

## Add it to ChatGPT

Plus, Pro, Business, Enterprise and Edu plans can add it, on the web. ChatGPT calls this developer mode.

1. **Turn on developer mode**

   In Settings, open Security and login and turn on Developer mode.

2. **Create the app**

   In the list of apps, press the plus button and create one with a name and the address.

3. **Allow the connection**

   The console's confirmation page opens. Check it and press **Allow** (see [What to check before you allow it](https://docs.vibebooking.ai/en/connect-assistant#consent)).

ChatGPT asks you to confirm each time before it drafts anything.

> **Note**
>
> Claude and ChatGPT rename their screens from time to time. If you cannot find one, check their help pages: [Claude](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), [ChatGPT](https://help.openai.com/en/articles/12584461-developer-mode-apps-and-full-mcp-connectors-in-chatgpt-beta).

## What to check before you allow it

The page asks "Let claude.ai connect to your account?", with the name of your assistant. Before you press **Allow**, check three things:

![The consent screen for connecting an assistant, listing where it connects, what it can do and which accounts.](https://docs.vibebooking.ai/screenshots/en/assistant-consent-desktop.webp)
*The confirmation page, opened from Claude.*

| On the page | What to check |
| --- | --- |
| **Connecting to** | You recognise the address. If not, press **Deny**. |
| **What it may do** | **Read and draft** is chosen to start with, and lets it draft your property's details. **Read only** reads and changes nothing. |
| **Accounts** | It can reach only the accounts ticked here. |

Whatever you choose, an assistant can only draft. Publishing and approving stay with you.

## After you connect

When your assistant drafts something and asks you to check it, a notice arrives in your inbox and by email. **Review them** shows the drafts, and you choose which ones go live. The steps are in [Checking the drafts](https://docs.vibebooking.ai/en/ai-assistants#review).

An assistant cannot connect your reservation system. Connect it yourself in the console, as [Beds24](https://docs.vibebooking.ai/en/connect-beds24) and [Channex](https://docs.vibebooking.ai/en/connect-channex) describe.

## API keys, for scripts

An assistant needs no key. Make one only for a script or an agency's tool.

1. **Open Developer**

   Open **Settings** in the menu and choose **Developer**.

2. **Fill in Create an API key**

   Enter a **Name**, pick when it **Expires after**, and choose read or write.

3. **Press Create**

   The key appears. It starts `vbk_` and is shown only this once: copy it and keep it somewhere safe.

![The Create an API key form, with name, access, accounts and expiry.](https://docs.vibebooking.ai/screenshots/en/api-key-create-desktop.webp)
*The Create an API key form.*

**Revoke** on a key stops it at once.

## Disconnect

In **Settings**, under **Connected assistants**, press **Disconnect** beside the assistant, or **Disconnect all** to remove every one. From that moment it can no longer act on this account.

# Connect Beds24

> **Plans**
>
> Everything on this page is available on every plan.

Once Beds24 is connected, VibeBooking can read your property list, rates and availability from it. You move between the console and Beds24's control panel to set it up.

## Before you start

Check two things:

- Your role in the console is **Owner** or **Manager**. A **Viewer** cannot connect.
- You can sign in to Beds24's control panel. The console notes: "It may ask for two-factor authentication. The owner should be the one at the keyboard."

### Add the website first

You enter each Beds24 property's website after connecting. You can also add it beforehand.

1. **Open Add a property**

   Press **Properties** in the menu and open **Add a property** on **All**. With no properties yet, it is already open.

2. **Enter the domain**

   Under **The property's website**, enter your site's domain, without `https://` or a path (for example `hana-kyoto.jp`).

3. **Press Add**

   The property joins the list. Its state is **Not connected**.

![The Add a property form, with a field for the property website and an Add button.](https://docs.vibebooking.ai/screenshots/en/add-property-desktop.webp)
*The Add a property form.*

## Connect

On **Properties** › **All**, press **Connect a reservation system** to open the **Integrations** tab. Under **Your reservation system**, press **Connect Beds24** to open the connect screen.

![The Connect Beds24 screen, with a field to paste the invite code and a Connect button.](https://docs.vibebooking.ai/screenshots/en/connect-wizard-desktop.webp)
*The connect screen, with a field to paste the invite code.*

1. **Open Beds24**

   Press **Make an invite code in Beds24**. Beds24's control panel opens in a new tab. The link already carries the three read permissions VibeBooking asks for.

2. **Make an invite code in Beds24**

   On the Beds24 screen, do this (the console shows the same two steps):

   1. In “Name for this token”, type a name you will recognise (e.g. VibeBooking)
   2. Press “Generate invite code”

   Copy the invite code you get. Beds24 explains invite codes in its own documentation, under [API V2](https://wiki.beds24.com/index.php/Category:API_V2).

3. **Paste the invite code**

   Go back to the console tab, paste it into **Invite code** and press **Connect**.

Once the code is confirmed, you land on **Beds24 is connected**. Link your properties to their websites there next: see [Link a property](https://docs.vibebooking.ai/en/go-live#link).

![The table for linking Beds24 properties to their websites.](https://docs.vibebooking.ai/screenshots/en/connect-linking-desktop.webp)
*The table for linking Beds24 properties to their websites.*

## What VibeBooking can read

VibeBooking asks for these three read permissions and nothing else. It never changes anything in Beds24.

| Permission | What it reads | What it is used for |
| --- | --- | --- |
| Properties | Your properties and room types in Beds24 | Linking them to your websites |
| Rates and availability | The rate for given dates and guests, and which rooms are free | Filling **What does a night cost for my dates and party?** on a property's **Facts** tab |
| Bookings | Basic booking records only | Counting **Bookings we could measure** in the report |

VibeBooking does not ask for permission to read guest names, contact details or payment details. Beds24 defines the permissions in its [API reference](https://beds24.com/api/v2).

Only the properties you take live with **Go live** are published for AI agents (see [Go live](https://docs.vibebooking.ai/en/go-live#go-live)).

## When it does not work

### The invite code is not accepted

If, after you press **Connect**, the console says "That code is wrong or already used. Make a new one in Beds24 and paste it here.", check these in order:

1. Is there a space inside the code? Spaces around it are removed, but a space in the middle stays.
2. Have you used this code before? A used code does not work again. Make a new one in Beds24.
3. Wait a moment, then press **Connect** again.

### A permission is missing

"This invite code cannot read everything we need. Make the invite code again in Beds24." means the code is missing one of the permissions VibeBooking asks for. Open Beds24 again from **Make an invite code in Beds24** and make a new invite code. Beds24's documentation on permissions is under [API V2](https://wiki.beds24.com/index.php/Category:API_V2).

## Disconnect

An **Owner** or a **Manager** can disconnect.

1. **Open the Integrations tab**

   Press **Properties** in the menu, then the **Integrations** tab.

2. **Press Disconnect**

   On the **Beds24** card, press **Disconnect**.

3. **Confirm**

   The console asks **Disconnect Beds24?** Press **Disconnect**. The card then says "Disconnected."

![The Beds24 card on the Integrations tab, with Review the links and Disconnect buttons.](https://docs.vibebooking.ai/screenshots/en/connection-beds24-desktop.webp)
*The Beds24 card on the Integrations tab.*

When you disconnect:

- Reading rates and availability stops. VibeBooking also revokes the access it was given, at Beds24 itself, and reads nothing more from it.
- Live pages stay up, but no longer show rates. To take a property off, see [Stop being live](https://docs.vibebooking.ai/en/go-live#back-to-preview).
- Nothing is deleted.

If the console says "That did not work. Try again.", the connection is still in place. Start again from **Disconnect**.

### When the connection's details are not there

The **Beds24** card may show only how many properties are linked, with no **Disconnect** button. The connection is remembered by the browser that made it. Sign in on the same device and browser, and **Disconnect** appears. Clearing that browser's data has the same effect.

### Revoke it in Beds24

Without the device that made the connection, you can revoke VibeBooking's access in Beds24's control panel. Beds24's documentation, under [API V2](https://wiki.beds24.com/index.php/Category:API_V2), says where.

# Connect Channex

> **Plans**
>
> Everything on this page is available on every plan.

Once Channex is connected, VibeBooking can read your properties, rates and availability from it. You make one API key in Channex and paste it into the console. It takes about two minutes.

## Before you start

Check two things:

- Your role in the console is **Owner** or **Manager**. A **Viewer** cannot connect.
- You can sign in to Channex and make an API key there.

Channex does not tell us the address of the page where guests book. If you use a booking engine, have its booking page's address ready. You can also add it later ([Add your booking page](https://docs.vibebooking.ai/en/connect-channex#booking-page)).

## Connect

On **Properties** › **All**, press **Connect a reservation system** to open the **Integrations** tab. Under **Your reservation system**, press **Connect Channex**.

![The Connect Channex screen, with fields for the API key and the booking page URL and a Connect button.](https://docs.vibebooking.ai/screenshots/en/connect-channex-wizard-desktop.webp)
*Paste the API key here, and your booking page if you have one.*

1. **Open the API key settings in Channex**

   Press **Open the API key settings in Channex**. Channex's API key settings open in a new tab.

2. **Make an API key in Channex**

   Follow what the console lists:

   1. "Name the key something you will recognise (e.g. VibeBooking)"
   2. "Copy the key it shows you"

3. **Paste the API key**

   Go back to the console tab and paste it into **API key**. Spaces before or after it are fine.

4. **Enter your booking page**

   In **Your booking page (recommended)**, enter the address of your booking engine's page. You can connect with it empty.

5. **Press Connect**

   Once the key checks out, the screen moves on to "Channex is connected".

On that screen, link each Channex property to your website next. The steps are in [Link a property](https://docs.vibebooking.ai/en/go-live#link). If you did not enter a booking page, the screen says "No booking page yet. Agents have no booking link to give guests."

## Add your booking page

Agents send guests to the page you enter here. You can take a property live without one, but agents then have no booking link to give guests.

1. **Open the Integrations tab**

   Press **Properties** in the menu, then the **Integrations** tab.

2. **Enter the address**

   Under **Booking page** on the Channex card, enter the address of your booking engine's page.

3. **Press Save**

   The screen says "Booking page saved."

![The Channex card on the Integrations tab, with a field for the booking page URL and a Save button.](https://docs.vibebooking.ai/screenshots/en/connection-channex-desktop.webp)
*The Channex card on the Integrations tab, where the booking page goes.*

The address has to start with `https://` and be your own booking engine's page. A booking site's page, such as Rakuten Travel or Booking.com, cannot be used. To remove it, empty the field and press **Save**: the screen says "Booking page removed."

If your booking engine is on a different domain from your property's website, the screen says "This is not on your website's domain. That is fine if your booking engine lives on another one." If it is your booking engine's page, leave it as it is.

## Choose your VibeBooking channel

This is how bookings that come in through VibeBooking links get counted. You create one booking page (a channel) in Channex just for VibeBooking, then choose it under **VibeBooking channel** on the Channex card. Bookings made on that channel count as bookings through VibeBooking. They are counted for the channel as a whole, not per AI.

Until you set it, the card says "Not set, so bookings through VibeBooking are not counted yet."

1. **Create the channel in Channex**

   In Channex, create one channel just for VibeBooking. Put "VibeBooking" in its name and the console selects it for you. Until you have one, the card shows **Create the booking page in Channex**, which opens Channex's channels page.

2. **Choose it**

   Back on the **Integrations** tab, choose your channel from the **VibeBooking channel** list. If its name has "VibeBooking" in it, the card says "The channel named VibeBooking is selected. Save to confirm it." Channels for booking sites such as Booking.com are left out of the list.

3. **Press Save**

   The screen says "Channel ID saved."

If your channel is not in the list, open **Not in the list? Paste its ID**, open the channel in Channex, paste the address from your browser's address bar, and press **Save**. If the console could not read your channels, the field is called **Your VibeBooking channel ID** instead; paste the address there the same way.

Only an **Owner** or a **Manager** can change it.

## What VibeBooking reads

With the API key, VibeBooking reads your properties, rates and availability from Channex. It never changes anything in Channex.

Only the properties you take live are published for AI agents ([Go live](https://docs.vibebooking.ai/en/go-live#go-live)).

## When it does not work

### The key is not confirmed

If, after you press **Connect**, you see "Not confirmed. The key may be mistyped, or Channex could not be reached just now. Paste it again, or try again in a moment.", check these in order:

1. You copied the whole key. It is a long string, and copying can cut it short. Copy it again from Channex.
2. You did not paste a different key.
3. Wait a moment and press **Connect** again.

### A permission is missing

If you see "This key cannot read everything we need. Make the API key again in Channex.", open Channex again from **Open the API key settings in Channex**, make a new key and paste it.

### The booking page address is refused

A refused address shows one of these:

| Message | Why, and what to do |
| --- | --- |
| "Use an address that starts with https://." | An `http://` address cannot be used. Enter your booking engine's `https://` page. |
| "A booking site cannot be your booking page. Enter your own booking engine's address." | It is a page on a booking site such as Rakuten Travel or Booking.com. Enter the page of the booking engine your property uses. |
| "That is a VibeBooking address. Enter your own booking page." | Enter your booking engine's page instead. |
| "Take the user name and password out of the address." | The address contains a sign-in name or password. Remove them and enter it again. |
| "Check the address, for example https://book.example.jp/" | It could not be read as an address. Copy it again from your browser's address bar. |

## Disconnect

Only an **Owner** or a **Manager** can disconnect.

1. **Open the Integrations tab**

   Press **Properties** in the menu, then the **Integrations** tab.

2. **Press Disconnect**

   Press **Disconnect** on the Channex card.

3. **Confirm**

   You are asked "Disconnect Channex?". Press **Disconnect**, and the screen says "Disconnected."

4. **Delete the API key in Channex**

   Channex is not told when you disconnect. In Channex's API key settings, delete the key you made for VibeBooking.

When you disconnect:

- Reading rates and availability stops.
- Live pages stay up, but no longer show rates. To take a property off, see [Stop being live](https://docs.vibebooking.ai/en/go-live#back-to-preview).
- Nothing is deleted.

If you see "That did not work. Try again.", the connection is still there. Start again from **Disconnect**.

# The traveller connector

> **Plans**
>
> Everything on this page is available on every plan.

Travellers' assistants find your property through a second MCP server, vibebook. It is not the one you add to your own assistant ([Connect an AI assistant](https://docs.vibebooking.ai/en/connect-assistant)): that one manages your account and needs you to sign in. vibebook only reads what you have published, and anyone can add it.

## The two addresses

| Address | For | Sign-in |
| --- | --- | --- |
| `https://vibebook.vibebooking.ai/mcp` | A traveller's assistant: find a stay, read rates, get the booking link | None |
| `https://mcp.vibebooking.ai/mcp` | You and your assistant: check your site, draft your property's details | Yes, see [Connect an AI assistant](https://docs.vibebooking.ai/en/connect-assistant) |

vibebook is listed in the official MCP Registry as `ai.vibebooking/vibebook`. Its server card is at `https://vibebook.vibebooking.ai/.well-known/mcp/server-card.json`.

## What it can do

| Tool | What it answers |
| --- | --- |
| `search_hotels` | Live properties in an area, such as 京都市東山区 or Gion |
| `resolve_hotel` | Whether a website is a VibeBooking property, from its domain |
| `get_hotel` | A property's published details and room types |
| `get_rates` | Live rates for a stay, each with its total, cancellation terms and a booking link |
| `book_link` | The link to your booking page for a stay, or for one offer from `get_rates` |

Every tool only reads. Nothing is booked, held or paid through vibebook: the booking link opens your own booking page, checks the price again, and the traveller books and pays there.

## Which properties it shows

Only properties that are live. A property you have not put live (see [Go live](https://docs.vibebooking.ai/en/go-live)) is not in its answers. What it says about yours is what you published.

## Add it to an assistant

Claude Code:

```sh
claude mcp add --transport http vibebook \
  https://vibebook.vibebooking.ai/mcp
```

In Claude or ChatGPT, add the same address as a custom connector or app, as on [Connect an AI assistant](https://docs.vibebooking.ai/en/connect-assistant#claude), and skip the sign-in: there is none.

# Go live

> **Plans**
>
> Everything on this page is available on every plan.

A property's state shows in the list on **Properties** › **All**, and next to its name on its own screen.

| State | What it means |
| --- | --- |
| **Not connected** | Not linked to a property in your reservation system yet. |
| **Preview** | Linked, but not live yet. |
| **Live** | AI agents can read it. |
| **Demo (hidden from AI)** | Set as a demonstration on the **Settings** tab. Even when live, AI does not see it. |

## Link a property

Once your reservation system is confirmed, the console opens a screen such as **Beds24 is connected**. The **Properties in Beds24** table lists the properties in your reservation system.

1. **Enter the website**

   In the **Website** column of each property you want to publish, enter that property's website. Websites you have added are offered as you type. A website not linked yet may already be filled in.

2. **Press Prepare**

   The website is saved and the property's **Facts** tab opens. The property moves to **Preview**. Nothing goes live yet.

![The table for linking Beds24 properties to their websites.](https://docs.vibebooking.ai/screenshots/en/connect-linking-desktop.webp)
*The properties in your booking system, one row each, with a website to enter.*

**See your properties** takes you to **Properties** › **All**. To come back to this screen later, press **Review the links** on the integrations tab of **Properties**.

If you press **Prepare** with no website entered, the row says "Enter this property's website first." Entries with no room count are listed apart, under **Other entries**. A day-use plan or a test entry needs no link.

## Check the facts

In **Properties** › **All**, press a property to open it. It has three tabs, **Facts**, **Preview** and **Settings**, and opens on **Facts**. Above the tabs are the property's state and how many facts are left before it can go live.

Under **Required to be listed**, the **Facts** tab lists the six facts a property needs before it can go live. As the tab says, "Six facts are needed to go live. Agents see exactly what you save here."

### Let them fill in themselves

Most of the six fill in without typing. We recommend this order:

1. From your reservation system and your website: when you open the property, whatever we could read is already in, with a line such as "4 fields filled in from your website and booking system." A fact read from your site is marked **From your website**, with the page it came from.
2. With **Fill in from text or a file**: paste a brochure, a booking site's description or an email draft, or add a file (PDF, Word, Excel or text). AI reads it and fills the empty facts; where a fact already has a value, the one from your text is offered as a choice. What you paste is not kept.
3. From your AI assistant: once you [connect an assistant](https://docs.vibebooking.ai/en/connect-assistant), it can draft the facts for you. You check them before they go live (see [Checking the drafts](https://docs.vibebooking.ai/en/ai-assistants#review)).

Nothing is listed until you save it. Type in only what is left.

| Fact | Typing it in |
| --- | --- |
| **What does a night cost for my dates and party?** | From your reservation system. Nothing to enter. |
| **Check-in from / check-out by?** | Pick from a list. |
| **Can I cancel? Free until when, what penalty, no-show charge?** | Pick how many days before from a list, then enter the fee as a percentage. |
| **Where exactly is it? (postal address)** | Type it in. |
| **How far is it from the nearest station / airport, and how do I get there?** | Type it in. |
| **How many people can stay in a room (adults / children)?** | Type it in. |

Check-in and check-out, and the cancellation policy, can be entered once for every property. On the **Defaults** tab of **Properties**, fill in **Defaults for all properties** and press **Save for all properties**.

### Check and save

1. **Check what is there**

   Correct anything that is wrong.

2. **Save**

   While something is unsaved, a button such as **Save 7 changes** shows at the bottom of the screen. Press it. Once all six are in, the screen says "6 saved. All six facts are in.", with **Go live** beside it.

![A property's Facts tab: the items required to be listed, filled in from the booking system, and the save button.](https://docs.vibebooking.ai/screenshots/en/go-live-facts-desktop.webp)
*Required to be listed, on the Facts tab. Anything unsaved brings up the save button below.*

A saved fact says **Saved**. To change one, press **Edit**.

## Check the preview

The **Preview** tab shows what AI is told.

| On the tab | What it is |
| --- | --- |
| **What AI is told** | What AI uses to answer a traveller about this property. A fact not filled in yet says **Not filled in**. |
| **The page AI reads (English)** | The page AI actually reads. **Open in a new tab** opens it in a tab of its own. |

![A property's Preview tab, showing what AI is told and the Go live button.](https://docs.vibebooking.ai/screenshots/en/go-live-preview-desktop.webp)
*The Preview tab, with what AI is told.*

An **Owner** or a **Manager** also sees **Share a preview link**. That link opens without signing in, until the date shown. Use it to show the page to your web person or a partner.

## Go live

Only an **Owner** or a **Manager** can go live. **Go live** sits at the top of the property's screen, on every tab. The line beside it depends on the property:

| It says | What to do |
| --- | --- |
| "Connect a reservation system first." | The property is not linked yet. Connect your reservation system ([Beds24](https://docs.vibebooking.ai/en/connect-beds24), [Channex](https://docs.vibebooking.ai/en/connect-channex)). |
| A line such as "2 more to fill in before going live." | Fill in the missing facts on the **Facts** tab. |
| "Ready to go live: all six facts are in." | You can go live. |

1. **Press Go live**

   With all six facts in, press **Go live**.

2. **Check the result**

   The screen says "Live. AI can read this page now." and the property's state becomes **Live**. The address of the page agents read shows too.

### Stop being live

On the **Settings** tab, under **Stop serving it**, press **Back to preview**. The property goes back to **Preview**, and AI agents can no longer read it. Its facts and preview stay, so you can go live again at any time.

# Link from your site

> **Plans**
>
> Everything on this page is available on every plan.

A link from your property's site helps AI find your live page.

## Where the link points

The link points at the address your live page is served from, which is one of these:

| Served from | The link |
| --- | --- |
| Our domain | `https://vibebooking.ai/hotels/…`. Nothing to set up. |
| Your own domain | A subdomain of your property's site, such as `https://agents.hana-kyoto.jp/hotels/…`. Needs [Serve on your own domain](https://docs.vibebooking.ai/en/custom-domain). |

Once your own domain is ready, the snippets under **Link from your site** switch to it. If you already added a link with our domain, replace it.

## Add the link

Once the property is live, the **Preview** tab shows **Link from your site**. It says "Any of the three is enough. We check on the next scan." and lists three snippets:

- **A link for your site's footer**
- **A line for your site's robots.txt**
- **A line for your site's llms.txt**

![A live property's Preview tab, showing the Link from your site snippets.](https://docs.vibebooking.ai/screenshots/en/go-live-publish-desktop.webp)
*A live property's Preview tab, with the Link from your site snippets.*

1. **Press Copy**

   Press **Copy** under the snippet you want, and add it to your property's site.

2. **Press I've added it**

   Open **Getting found by AI** on the **Facts** tab and press **I've added it**.

# Take bookings on your booking pages

> **Plans**
>
> Available on Standard and Pro. On Free the console shows that these are there, but you need Standard or higher to use them.

A guest who follows your booking link from an AI answer lands on your current booking page today. Finish the items on the **Booking pages** tab and you can send that link to VibeBooking's booking pages instead, in your logo and colour.

> **Note: Test mode for now**
>
> Card payments go through Stripe's test mode, so no real bookings or payments are made.

## Before you start

- It's for properties on Channex. [Connect Channex](https://docs.vibebooking.ai/en/connect-channex) first.
- An **Owner** or a **Manager** sets it up.
- On Free, the tab says **Available on Standard**.

## Open the setup

Open the property and its **Booking pages** tab. **Before you take bookings** is at the top, with a count such as "1 of 6 done".

![Before you take bookings on the Booking pages tab: the payment options, and the list of items still to do.](https://docs.vibebooking.ai/screenshots/en/engine-setup-desktop.webp)
*Before you take bookings, at the start. Items already done are ticked.*

## Choose how guests pay

Under **How guests pay**, choose one or both, then click **Save payment options**.

| Option | When guests pay | Stripe account |
| --- | --- | --- |
| **Pay by card when booking** | As they book, by card | Needed |
| **Pay at the property** | At check-in, to you | Not needed |

**Pay by card when booking** unlocks once you [set up Stripe](https://docs.vibebooking.ai/en/booking-engine#stripe).

![How guests pay: checkboxes for card payment when booking and payment at the property, and a save button.](https://docs.vibebooking.ai/screenshots/en/engine-modes-desktop.webp)
*Card payment chosen and saved.*

## Set up Stripe

Card payments go to your own Stripe account, and guests see your name on their statements. Your VibeBooking account has one Stripe account, shared by all its properties.

1. **Click Set up Stripe**

   A Stripe account is created for your property, and Stripe's sign up pages open.

2. **Sign up on Stripe**

   The business itself enters its details, its representative's identity and the bank account for payouts. Stripe receives them; VibeBooking never sees them.

3. **Come back**

   When you finish, Stripe sends you back to the **Booking pages** tab.

If Stripe still needs something, **Continue on Stripe** picks up where you left off. Stripe's review can take a few days.

## Work through the checklist

**Before you take bookings** has six items. Each one not yet done says what it's waiting for.

![The list of items before taking bookings, the finished ones ticked and the statement name still to check.](https://docs.vibebooking.ai/screenshots/en/engine-checklist-desktop.webp)
*Done up to the test booking. The statement name is left.*

| Item | How to finish it |
| --- | --- |
| Card payments on Stripe | Finish [Set up Stripe](https://docs.vibebooking.ai/en/booking-engine#stripe). Not needed for **Pay at the property** alone. |
| Bookings reach your reservation system | If you see "Your reservation system isn't answering. Check its connection settings.", check that Channex's Booking CRS application is installed and your API key is still valid. |
| Cancelled rooms go back on sale | Turn on both of Channex's availability settings (off by default). [How VibeBooking works with your system](https://docs.vibebooking.ai/en/inventory-systems#channex) names them. |
| A test booking, made and cancelled | **Run a test booking** writes one booking to Channex and cancels it. If it fails, check the two items above and run it again. |
| Your name on guests' card statements | See [Your statement name](https://docs.vibebooking.ai/en/booking-engine#descriptor). Not needed for **Pay at the property** alone. |
| The six facts filled in, and live | See [Go live](https://docs.vibebooking.ai/en/go-live). |

### Your statement name

Compare **On card statements (Stripe)** with **On your checkout**. A statement name that looks nothing like your property's can make a guest dispute the charge. You can change it in your Stripe dashboard. When it's right, click **This name is fine**.

![The name on card statements at Stripe beside the name on your checkout, with a This name is fine button.](https://docs.vibebooking.ai/screenshots/en/engine-descriptor-desktop.webp)
*Compare the name at Stripe with the name on your checkout.*

If you change the name at Stripe later, check it again.

## Switch your booking link

Once every item is done, click **Send guests to this checkout**. From then on, guests who follow your booking link book on your booking pages.

![Where your booking link goes, with every item done and the Send guests to this checkout button ready to press.](https://docs.vibebooking.ai/screenshots/en/engine-ready-desktop.webp)
*Every item done, ready to switch.*

After the switch, your logo and colour settings sit at the top of the tab ([Brand your booking pages](https://docs.vibebooking.ai/en/checkout-brand)). To undo, click **Go back to your current booking page**.

![The booking link switched to this checkout, with a button to go back to your current booking page.](https://docs.vibebooking.ai/screenshots/en/engine-switched-desktop.webp)
*Switched. You can go back to your current booking page.*

### When it won't switch

If something changed after you opened the page, such as the statement name at Stripe, the switch is refused and names the items still to do. Finish them and click again.

![The switch refused, with the items still to do listed by name.](https://docs.vibebooking.ai/screenshots/en/engine-not-ready-desktop.webp)
*The items still to do, by name.*

## If your plan changes

If the property moves to Free, guests go to your current booking page again. Back on a plan with booking pages, they book on them again, with nothing to set up.

# Brand your booking pages

> **Plans**
>
> Available on Standard and Pro. On Free the console shows that these are there, but you need Standard or higher to use them.

You can put your logo and one colour on the pages where guests book. Leave both unset and the pages stay plain black and white.

## Before you start

- On Free, the **Booking pages** tab says **Available on Standard**, and **I'd like to use it** lets us know.
- An **Owner** or a **Manager** can change it. A **Viewer** sees it read-only.

## Set your logo and colour

Open the property and its **Booking pages** tab. The settings are on the left, under **Logo and colour on your booking pages**, and a live preview of your booking pages is on the right.

1. **Choose a logo**

   Upload one with **Choose a logo image** (PNG, JPEG or WebP), or pick one of the property's photos under **Or use one of your photos**.

2. **Choose a colour**

   Click the swatch under **Colour** and pick one.

3. **Check the preview**

   The preview follows your changes before you save. Switch pages with **Details**, **Review**, **Confirmed** and **Manage**, and width with **Desktop** and **Phone**.

4. **Click Save**

   You see "Saved. Guests see it on your booking pages too."

![The booking page logo and colour settings, with the logo and colour on the left and a preview of the booking page on the right.](https://docs.vibebooking.ai/screenshots/en/checkout-brand-desktop.webp)
*The logo and colour settings, and the live preview.*

| Setting | Where guests see it |
| --- | --- |
| Logo | At the top of every page, left of your property's name. |
| Colour | The buttons, the confirm booking button among them, and the progress bar. |

![The guest details page, showing the property logo and colour.](https://docs.vibebooking.ai/screenshots/en/checkout-details-desktop.webp)
*The guest details page with your logo and colour.*

To undo, click **Remove the logo** or **Use the default colour**, then **Save**.

## Colours that are too light

White text sits on your colour. If white text would be hard to read on the one you pick, you see "This colour is too light: white text on it is hard to read. Choose a darker one." and cannot save it.

The bar is a contrast ratio of 4.5:1 against white text (WCAG AA). Darker colours pass.

![The colour field with a light yellow chosen, and the message that it is too light for white text.](https://docs.vibebooking.ai/screenshots/en/checkout-brand-too-light-desktop.webp)
*A light yellow is refused: white text on it is hard to read.*

## Try your booking pages

**Try your booking pages** opens your booking pages in a new tab, exactly as a guest sees them, and lets you book right through. Pay with Stripe's test card `4242 4242 4242 4242`, any future expiry date and any three-digit security code.

Nothing about it is real:

|  | When you try it |
| --- | --- |
| Charges | None. |
| Reservation system | Nothing is written to it. |
| Bookings | None is kept. |
| Emails | The confirmation and the receipt go to your own email address, with `[PREVIEW]` at the start of the subject. |

![The Confirm booking button, in the property colour.](https://docs.vibebooking.ai/screenshots/en/checkout-confirm-desktop.webp)
*The final button wears your colour too.*

![The booking confirmed page, showing the property logo and colour.](https://docs.vibebooking.ai/screenshots/en/checkout-done-desktop.webp)
*The booking confirmed page. A try's booking number starts with PREVIEW.*

## Let your AI assistant suggest one

With your AI assistant connected ([Connect an AI assistant](https://docs.vibebooking.ai/en/connect-assistant)), it can suggest a logo and colour (the `draft_brand` tool). The **Booking pages** tab then shows "Your AI assistant suggested a logo and colour".

![A logo and colour suggested by an AI assistant, with Try the suggestion and Not now buttons.](https://docs.vibebooking.ai/screenshots/en/checkout-proposal-desktop.webp)
*A suggestion from your AI assistant.*

**Try the suggestion** puts it in the preview. Guests see nothing new until you click **Save**. **Not now** sets it aside.

# Serve on your own domain

> **Plans**
>
> Everything on this page is available on every plan.

Live pages are normally served on our domain. With your own domain set up, they are served on a subdomain of your property's site instead (for example `agents.hana-kyoto.jp`). You do not have to set one up.

## Before you start

Check three things:

- Your role in the console is **Owner** or **Manager**. A **Viewer** sees "Read-only. An owner or manager changes the domain."
- The name is a subdomain of your property's site. For a site at `hana-kyoto.jp`, that is a name like `agents.hana-kyoto.jp`. The site's own domain cannot be used.
- You can change your domain's DNS. If someone else looks after it, see [Ask your web person](https://docs.vibebooking.ai/en/custom-domain#web-person).

## Set it up

1. **Open the Your domain tab**

   Press **Properties** in the menu, then the **Your domain** tab.

2. **Enter a subdomain**

   Under **Set up your domain**, enter the name in **Subdomain to use** and press **Use this name**.

3. **Add the DNS record**

   **The record to add** shows a **Type**, a **Name** and a **Value (points to)**. In your DNS panel, add this one line exactly as shown. **Copy** copies all three at once.

4. **Wait for it to take effect**

   The heading moves from "Waiting for DNS" to "Certificate pending". When everything is ready it reads like "Ready: served on agents.hana-kyoto.jp". While the page is open, it checks again by itself. To check straight away, press **Check again**.

5. **Choose the properties**

   Under **Properties served on this domain**, press **Serve on this domain** for each property. A property served there shows **Served here**. **Stop serving** takes one off.

![A custom domain card, showing the DNS record to add and the properties served on the domain.](https://docs.vibebooking.ai/screenshots/en/custom-domain-record-desktop.webp)
*A custom domain just after it is set: the record to add, and the properties it serves.*

On Cloudflare, set the record's proxy status to "DNS only". While it is "Proxied", we cannot see the record and the setup does not move on. The screen shows the same note under the record.

## Ask your web person

If someone else looks after your DNS, press **Send to your web person**. It opens a page with the record in Japanese and English. Only someone signed in as a member of your account can open that page, so [invite them](https://docs.vibebooking.ai/en/getting-started#invite) first.

An [AI assistant](https://docs.vibebooking.ai/en/ai-assistants) can also add the domain and check its record for you. Choosing the properties it serves stays with you.

On that page, **Check** tells them whether the record has taken effect: "The record is in place." once it has, "Not seen yet." until then.

## What the status means

The heading on the domain screen tells you how far the setup has got. At every stage your pages are served: on our domain until everything is ready, and on yours after.

| Heading | What it means | What to do |
| --- | --- | --- |
| "Waiting for DNS" | We cannot see the record yet. This can take minutes or hours. | Once you have added the record, just wait. |
| "Certificate pending" | The record is in place. It moves on once the HTTPS certificate is issued. | Nothing. |
| "Ready: served on agents.hana-kyoto.jp" | Your pages are served on your domain. | Nothing. |
| A heading like "Your domain stopped pointing at VibeBooking on 9/25/2026" | It was working, and then we could no longer see the record. | See [When the record is gone](https://docs.vibebooking.ai/en/custom-domain#lapsed). |
| "The certificate has not been issued" | The record is in place, but the HTTPS certificate could not be issued. Your pages are still served on our domain. | See [When the certificate has not been issued](https://docs.vibebooking.ai/en/custom-domain#certificate-failed). |

## When it does not work

### You entered the site's own domain

If you see "Use a subdomain, such as agents.hana-kyoto.jp.", the name you entered is the site's own domain (`hana-kyoto.jp`). Put a name such as `agents.` in front of it, as in `agents.hana-kyoto.jp`, and try again.

### The name is used by another account

"That name is already used by another account." means another VibeBooking account has already set up the same name. Check whether someone at your company set it up in a different account. If not, use another name (for example `ai.hana-kyoto.jp`), or [contact us](https://docs.vibebooking.ai/en/custom-domain#contact).

### It stays at "Waiting for DNS"

If nothing changes after a few hours, check the record in your DNS panel, in this order:

1. The name is not doubled. Some DNS services want only the `agents` part in the **Name** field. Typing `agents.hana-kyoto.jp` there makes a different name, `agents.hana-kyoto.jp.hana-kyoto.jp`.
2. The type is CNAME, and the value matches **Value (points to)** exactly. Copying it with **Copy** is the safest way.
3. On Cloudflare, the proxy status is "DNS only".
4. No other record (an A record, for example) is left on the same name. If one is, you may not be able to add the CNAME, or we may not see it correctly.

Then press **Check again**.

### DNS could not be checked

"We could not check DNS. This is the last known state; we retry automatically." means our side could not check DNS just now. Nothing is wrong with your setup. The screen keeps the last known state and checks again by itself. Nothing to do.

### When the record is gone

A heading like "Your domain stopped pointing at VibeBooking on 9/25/2026" appears when we can no longer see a record that used to work. Check in your DNS panel whether the record was deleted or its value changed. Meanwhile your pages are served on our domain. Add the record shown under **The record to add** again, and it recovers by itself.

### When the certificate has not been issued

"The certificate has not been issued" appears when we can see your record but could not issue the HTTPS certificate for your own domain. Meanwhile your pages are served on our domain. Check these in order:

1. The record in your DNS panel matches **The record to add** on the screen.
2. Your domain has no CAA record limiting who may issue its certificates. If it has one, that can be the cause. If a web person set up your DNS, ask them to check.

Once it is right, serving on your domain starts on its own. We keep trying to issue the certificate too. If that does not solve it, [contact us](https://docs.vibebooking.ai/en/custom-domain#contact).

### A property cannot be served here

A line like "agents.hana-kyoto.jp is not under yado-nara.jp, so it cannot serve this property." means the property's site is on a different domain from the one this name is under. For example, `agents.hana-kyoto.jp` can only serve properties whose site is `hana-kyoto.jp`. For a property on another site, set up that site's subdomain as [another domain of your own](https://docs.vibebooking.ai/en/custom-domain#set-up).

### Something did not finish

These mean the work stopped on our side. Wait a moment and do the same thing again. If it keeps happening, [contact us](https://docs.vibebooking.ai/en/custom-domain#contact).

- "That did not save. Try again."
- "That did not change. Try again."
- "That did not work, so the domain is unchanged. Try again."

## Remove your domain

Once removed, your pages are served on our domain again. Only an **Owner** or a **Manager** can remove it.

1. **Press Remove this domain**

   Press it on the card of the domain you want to remove.

2. **Press Remove**

   You are asked something like "Remove agents.hana-kyoto.jp?". Press **Remove**, and the screen shows "Removed agents.hana-kyoto.jp".

3. **Delete the DNS record**

   In your DNS panel, delete the record you added. Any time after removing is fine.

## Contact us

If none of this solves it, press **Still stuck? Contact us** under the error. The screen and the reference go with it, so we can see which step went wrong. How to reach us with no error on screen, and when we reply, are in [Contact us](https://docs.vibebooking.ai/en/troubleshooting#contact).

# Read the report

> **Plans**
>
> - Reads and bookings we could measure: Available on every plan.
> - The period before, handoffs to your booking page, and records older than 90 days: Available on Standard and Pro.
> - Which AI read your pages and what AI looked up: Available on Standard and Pro. On Free the console shows that these are there, but you need Standard or higher to use them.

## On Home

**Times AI read your pages** on **Home** shows how often AI read your pages. The screen explains: "How often ChatGPT, Perplexity and the like read your property's pages. Only visits we confirmed really came from that AI are counted." It shows:

- **Reads**, against the period before
- **Handoffs to your booking page**
- **Bookings we could measure**
- a chart of the count over time (**Show as a table** shows the same figures as a table)
- **Which AI read your pages** and **What AI looked up**

**Period** and **Counted per** change what you see. With two or more properties, **Property** narrows it to one. Each property's count also shows under **AI reads (7 days)** in **Properties** › **All**.

![The figures on Home, with how often AI read your pages and a chart of how that changed.](https://docs.vibebooking.ai/screenshots/en/go-live-report-desktop.webp)
*The figures on Home: how often AI read your pages, and how that changed.*

Depending on your plan, some figures show a lock and the name of the plan that shows them, in place of the figure.

## Week by week

Choose **Week** under **Counted per** to see the figures a week at a time. Narrowed to one property, that is the property's weekly report. The report link in a notice email opens the same screen.

## When nothing has been read yet

Until the first read, the screen says "Waiting for the first read" and explains: "It takes days to weeks before AI reads a newly live page for the first time. Once it does, the count shows here." Below that are the results of checking that the page is served correctly. A link from your property's site makes the page easier to find (see [Link from your site](https://docs.vibebooking.ai/en/link-from-site)).

# When something does not work

> **Plans**
>
> Everything on this page is available on every plan.

When the console shows an error, look for its message on this page. Errors about connecting and your own domain are on their own pages ([Beds24](https://docs.vibebooking.ai/en/connect-beds24#troubleshooting), [Channex](https://docs.vibebooking.ai/en/connect-channex#troubleshooting), [Your domain](https://docs.vibebooking.ai/en/custom-domain#troubleshooting)).

## The reference

When something stops on our side, the error shows a line like "Reference when you contact us: 8F3A-2B9C". With it, we can check which step went wrong and what happened.

Contact us from **Still stuck? Contact us** beside the reference, and the reference and the screen are sent along for you. If you email us instead, include it.

## Common errors

### Something went wrong on our side

"Something went wrong. Try again in a moment." means the work stopped on our side. Nothing is wrong with your setup. Wait a moment and press **Retry**, or do the same thing again. If it keeps happening, [contact us](https://docs.vibebooking.ai/en/troubleshooting#contact).

### The server could not be reached

"We could not reach the server." means the console could not reach our server. Check that other sites open, wait a moment and press **Retry**. If other sites open and the same message keeps appearing, the problem is on our side. Email us at hello@vibebooking.ai: the form in the console cannot reach us either.

### No permission

"You do not have permission to do that." means your role in the console does not allow what you tried. A **Viewer** cannot add properties, connect or go live. If it needs doing, ask your account's **Owner**. Opening another account's page shows it too.

### Page not found

"Not found." means the page does not exist. An old link to a property or domain that was removed shows it too. Open it again from the menu.

### The account was deleted

"This account was deleted." appears once the account has been closed. Its properties, connection and members are gone. **Make a new account** starts again.

## When you cannot sign in

### Sign-in stopped partway

"Sign-in did not complete. Try again." means signing in with Google or LINE stopped partway. Press **Continue with Google** or **Continue with LINE** again. If your browser is signed in to a different Google account, choose the one you use.

### Invitation-only

If you see "The console is invitation-only for now. Only people we have contacted can sign in.", check that you are signing in with the email address our invitation was sent to.

### Not yet available

"This account cannot use the console yet. We will be in touch." means the account you signed in with cannot start yet. We will contact you.

## Contact us

If none of this solves it, contact us from the console. We can see which screen you were on and what it showed, so there is no need to explain it again.

1. **Open Contact us**

   Press **Still stuck? Contact us** under the error. With no error on screen, press your account name at the bottom left, then open **Help** and choose **Contact us**.

2. **Write what happened**

   In **What happened**, write what you noticed and what you tried. The screen, the message shown and the reference are shown under **Sent along with it**, and reach us as they are.

3. **Press Send**

   The screen says "We received your message", and a confirmation email arrives.

![The Contact us screen, with a box for what happened and a Send button.](https://docs.vibebooking.ai/screenshots/en/help-form-desktop.webp)
*The Contact us screen.*

We read messages on weekdays, 10:00 to 18:00 Japan time, and reply by the next business day, to the email address of the account you signed in with. If your account has no email address, the form asks where to reply.

If you see "That did not send. Try again.", **Send from your email app** sends the same content by email. If you cannot sign in at all, email hello@vibebooking.ai.

# FAQ

> **Plans**
>
> Everything on this page is available on every plan.

## About VibeBooking

### What is VibeBooking?

A service that publishes your property's details in a form AI agents can read. Rates and availability come from your reservation system (Beds24 or Channex). You check what will be published in the console before it goes live (see [What the console is for](https://docs.vibebooking.ai/en/getting-started#what-the-console-is-for)).

### Which languages does it support?

Japanese and English, for both the console and these docs. The English console is at [console.vibebooking.ai/en](https://console.vibebooking.ai/en).

To switch the console's language, select your account name to open its menu, then choose **Language**.

![The account menu open, with Language offering 日本語 and English.](https://docs.vibebooking.ai/screenshots/en/language-menu-desktop.webp)
*The account menu, with Language open.*

### What happens to the data VibeBooking reads?

The rates read from your reservation system appear on the page of each property you take live, and AI agents read that page. The page is served on our domain, or on [your own domain](https://docs.vibebooking.ai/en/custom-domain) if you set one up.

## Signing in

### Can anyone sign in?

No. The console is invitation-only for now: only accounts with an email address we have contacted can sign in. Any other account sees "This account cannot use the console yet. We will be in touch." (see [Sign in](https://docs.vibebooking.ai/en/getting-started#sign-in)).

### Why can't I sign in with LINE?

LINE does not pass an email address to the console. While the console is invitation-only it checks that address, so with LINE it has nothing to check. Use Google (see [Sign in](https://docs.vibebooking.ai/en/getting-started#sign-in)).

## Connecting Beds24

### Does VibeBooking change anything in Beds24?

No. VibeBooking holds read permissions only, and cannot change anything in Beds24 (see [What VibeBooking can read](https://docs.vibebooking.ai/en/connect-beds24#what-vibebooking-reads)).

### What does VibeBooking read from Beds24?

Your properties and room types, rates and availability, and basic booking records. It does not read guest names, contact details or payment details (see [What VibeBooking can read](https://docs.vibebooking.ai/en/connect-beds24#what-vibebooking-reads)).

### How do I disconnect Beds24?

On the **Integrations** tab of **Properties**, on the **Beds24** card, press **Disconnect**. Reading rates stops, and VibeBooking's access is revoked at Beds24 as well. Live pages stay up, but no longer show rates. Do it on the device you connected from (see [Disconnect](https://docs.vibebooking.ai/en/connect-beds24#disconnect)).

## Going live and the report

### Does connecting make my property live straight away?

No. A linked property goes to **Preview** first. AI agents can read only the properties you take live with **Go live** (see [Go live](https://docs.vibebooking.ai/en/go-live#go-live)).

### How do I stop being live?

Press **Back to preview** on the property's **Settings** tab. The property goes back to **Preview**, and AI agents can no longer read it (see [Stop being live](https://docs.vibebooking.ai/en/go-live#back-to-preview)).

### Do I need my own domain?

No. Without one, your pages are served on our domain (see [Serve on your own domain](https://docs.vibebooking.ai/en/custom-domain)).

### My property is live, but nothing has read it yet

It takes days to weeks before AI reads a newly live page for the first time. A link from your property's site makes the page easier to find (see [When nothing has been read yet](https://docs.vibebooking.ai/en/report#no-reads-yet)).

### Why are some figures not shown?

Some figures depend on your plan. Where a figure is not shown, the console shows a lock and the name of the plan that shows it (see [Read the report](https://docs.vibebooking.ai/en/report)).

# How VibeBooking works with your system

> **Plans**
>
> Everything on this page is available on every plan.

VibeBooking reads a hotel's rooms, rates and availability from your system, and writes the bookings AI assistants make back into it. We build the adapter for your API ourselves.

## What we need from your system

| Function | What we need |
| --- | --- |
| Read rooms, rates and availability | Rate plans, rates and availability by date, minimum stay, closed to arrival or departure |
| Create a booking | One booking per stay, answered with your id. Store our reference on it |
| Tell a refusal from no answer | A clear error when you cannot take the booking |
| Find by our reference | Look up a booking by our reference |
| Read by your id | Whether it exists, whether it is cancelled, and our reference |
| Cancel | Cancel by your id. Cancelling a cancelled booking succeeds |
| Room back on cancel or change | Tell us whether the room goes back. If not, we take no bookings there |
| Record how it is paid | Paid now or pay at the property, and the amount paid |

A timeout or a server error means the booking may have landed, and we treat it that way.

### How a booking goes through

```mermaid
sequenceDiagram
    autonumber
    participant G as Guest or AI assistant
    participant V as VibeBooking
    participant S as Stripe (the hotel's account)
    participant P as Your system
    G->>V: Asks to book
    V->>P: Re-checks rate and availability
    V->>S: Authorises the card
    V->>P: Creates the booking, with our reference
    P-->>V: Your id
    V->>S: Captures the payment
    V-->>G: Confirmation email
```

### Payment

The hotel is the merchant of record and is paid through its own Stripe account. VibeBooking never holds the money and takes no fee. A booking that cannot be written is never charged.

## What we promise

- Every call is idempotent: a retry gives the same result.
- A booking is never created twice.
- If the payment fails, we cancel the booking in your system too.
- We reconcile regularly and flag any difference.
- Guest details live only in the booking service's database, and we send only what is needed.

When your system does not answer:

```mermaid
sequenceDiagram
    participant V as VibeBooking
    participant P as Your system
    participant S as Stripe
    V-xP: Creates the booking
    Note over V,P: Timeout. Not sent again
    V->>P: Looks it up by our reference
    alt Found
        V->>S: Captures the payment
    else Not found
        V->>S: Releases the authorisation
    end
```

## What we send with each booking

| Field | What it holds |
| --- | --- |
| Our booking reference | For example `VB-ABC123`. Also how we search for, read and cancel the booking |
| Room type, rate plan | Your system's ids |
| Check-in, check-out |  |
| Guests | Adults and children |
| Price per night, currency | The total divided by the nights, including any accommodation tax paid at the property |
| Payment | Paid now: the amount paid online and the Stripe payment id; the rest of the total is collected at the property. Pay at the property: all of it is collected there |
| Lead guest's name, email, phone |  |
| Furigana | A name written in kanji |
| Lives abroad | A guest living outside Japan, and whether they are a Japanese national |
| Nationality, passport number | A foreign national with no address in Japan: fields of Japan's guest register |
| Source id | Our id for which AI assistant the booking came through |

Where your system has no field for one of these, we write it in the booking's notes, one per line. The passport is checked at check-in, face to face. Card details never reach your system.

## API styles

Whatever style your API uses, we build an adapter for it if we need to. Our booking side stays the same; each system gets its own adapter.

| Style | Support |
| --- | --- |
| REST (JSON) | In use (Channex, Beds24) |
| SOAP or XML over HTTPS | Built to your specification |
| TravelXML | Built to your specification |
| Authentication | API keys, refresh tokens |
| Transport | HTTPS only |

### OpenTravel mapping

We do not speak OpenTravel (OTA) messages as standard. If your API takes OTA XML (`http://www.opentravel.org/OTA/2003/05`), we send each booking as an `OTA_HotelResNotifRQ`, as below. Element names and codes follow OpenTravel 2017B.

| What we send | OpenTravel element |
| --- | --- |
| Our booking reference | `UniqueID` (`Type="14"`) |
| Room type, rate plan | `RoomType@RoomTypeCode`, `RatePlan@RatePlanCode` |
| Check-in and check-out dates | `TimeSpan@Start`, `TimeSpan@End` |
| Guests | `GuestCount@AgeQualifyingCode` (adults `10`, children `8`) |
| Price per night, currency | `Rate/Base@AmountAfterTax`, `@CurrencyCode` |
| Payment | `Guarantee@GuaranteeType` (`PrePay` when paid online, `None` when paid at the property); the amount paid in `DepositPayments` |
| Lead guest's name, email, phone | `PersonName`, `Email` and `Telephone` under `Customer` |
| Nationality, passport number | `CitizenCountryName`, `Document` (`DocType="2"`) |
| Furigana, lives overseas | No element for these, so they go in `ResGlobalInfo/Comments` |
| Source ID | `POS/Source/BookingChannel` |
| Cancellation | `ResStatus="Cancel"` |

We never send card details (`PaymentCard`).

## Systems we work with

### Channex

| Function | In Channex |
| --- | --- |
| Read | Room types, rate plans, availability, restrictions |
| Create a booking | Booking CRS `POST /bookings` (status `new`, `ota_name` `Offline`) |
| Our reference | `ota_reservation_code` and `meta` |
| Find by our reference | The bookings list, matched on our reference |
| Read by your id | `GET /bookings/:id` |
| Cancel | `PUT /bookings/:id` (status `cancelled`) |
| Room back | `allow_availability_autoupdate_on_cancellation` and `allow_availability_autoupdate_on_modification` both on |
| Paid now | `payment_collect` `ota`, amount as a deposit |
| Pay at the property | `payment_collect` `property` |

Furigana and the guest register items go in the booking notes, one line each, in Japanese for the front desk.

| Guest data | In Channex |
| --- | --- |
| Name | `customer` surname and name, and the room's guest |
| Email, phone | `customer` `mail`, `phone` |
| Furigana | Notes `ふりがな: …` |
| Lives abroad | Notes `居住: 海外`, or `居住: 海外（日本国籍）` for a Japanese national |
| Nationality | Notes `国籍: …` |
| Passport number | Notes `旅券番号: …` |
| A test booking | Notes start with `[TEST]` |

- The Booking CRS application must be installed.
- The room-back settings are off by default; the hotel switches them on in Channex.
- The API is asynchronous: a read right after a create can answer 404. We never take that as no booking.

### How a hotel connects

The hotel pastes a Channex API key into the VibeBooking console. Once connected, Channex appears under **Properties** › **Integrations**.

![The Connect Channex screen, with a field to paste the API key and a Connect button.](https://docs.vibebooking.ai/screenshots/en/channex-key-desktop.webp)
*Pasting the API key to connect.*

![The Connections tab, showing Channex connected.](https://docs.vibebooking.ai/screenshots/en/channex-connected-desktop.webp)
*Integrations, once connected.*

## Adding your system

Email hello@vibebooking.ai.