Connecting your platform

The specification we build each platform connection against: what the assistant reads, how it hands a guest to checkout, how enquiries reach you, and how bookings are confirmed back to us.

How we build it#

We build each connection with you. We work from a demo account on your system, from your API if you have one, or from whatever your own booking pages already connect to. You don't need to build anything new for us. We need:

  • A demo account with at least one test property set up the way your customers set theirs up.
  • A contact on your team for technical questions.
  • Your agreement on the checkout model and booking confirmation described below.

The assistant only reads from your platform to answer and quote. It doesn't change rates, calendars or bookings. Bookings are created by your checkout, under your terms.

Read, write and access#

What we need from your platform, in short. The sections below go into detail.

What we needUsed for
ReadProperty and unit content, availability, rates and restrictions (minimum stay, occupancy, cut-offs), extras, promo codes, cancellation policy, activities and slots.Answering, checking dates and quoting. Always needed.
WriteDepending on the model: create a booking or a provisional hold, create an enquiry, and send us booking-confirmed events, by webhook or by letting us poll.Payment in the chat, enquiries in your inbox and the monthly statement.
AccessPartner-level credentials, or a key per property, whichever your platform uses.All of the above.

With checkout hand-off, the default, we don't need to create bookings: your own booking engine does that. See Payments.

What the assistant reads#

Each row is a capability the assistant uses. Where your platform doesn't have one, the assistant works without it. For example, with no extras it simply never offers extras.

Property#

DataWhat the assistant does with it
Name, description, address and locationAnswers questions about the place and where it is.
PhotosShows them in the chat when a guest asks to see the property.
Amenities and facilitiesAnswers questions such as whether there is parking, wifi or a pool.
Check-in and check-out timesAnswers arrival and departure questions.
Policies and rules, such as pets, children and quiet hoursAnswers rule questions and respects restrictions when quoting.
Cancellation policyExplains it before the guest books.
Booking restrictions, such as adults only or members onlyApplies them when offering options.
Instant booking or booking on requestTells the guest whether the booking is confirmed straight away or is a request the property accepts.

Rooms, units and pitches#

DataWhat the assistant does with it
Each type's name, description and photosShows options as cards the guest can browse.
Occupancy: maximum guests, and adults, children and infantsOnly offers types that fit the party.
Minimum stayOnly offers stays that meet it.
Amenities per typeAnswers questions about a specific room or unit.
A from priceGives a starting point before dates are chosen, clearly as a from price.

Availability and prices#

DataWhat the assistant does with it
Availability by date, for the property and for each typeShows a date picker with available dates, and finds alternatives when dates are full.
Arrival and departure rules and cut-offsOnly offers dates a guest can book.
Nightly rates for a party, from your pricing rulesShows per-night prices for the chosen dates.
A quote for a stay: total and line itemsShows the price card. Every price the assistant states comes from this, read at the time.
Longer-stay discountsShows a discount already in the price, or tells the guest how to qualify.

Extras, promo codes and members#

DataWhat the assistant does with it
Extras for a quoted stay, with prices and any included quantityOffers them and re-prices the quote when the guest adds or removes one.
Promo code check against a quoteTells the guest whether a code works and the new total. It never guesses.
Member and club discountsOffers them at checkout to guests who say they are members.
Required booking fields, such as a vehicle registrationMakes sure checkout asks for them.

Activities#

DataWhat the assistant does with it
Activities: name, description, duration, price and group sizeShows what the property offers besides stays.
Time slots with remaining places, and booking lead timeShows bookable slots and quotes them.

Checkout and payment#

When the guest wants to book, the assistant either hands them to your own booking engine with the stay filled in, or, where your platform supports it, takes the booking and payment in the chat through your API and your payment provider. It never takes card details in the conversation. Both models are on the Payments page.

For checkout hand-off we need a booking address that accepts the stay in the link: the property, the room or unit type, arrival and departure dates, and the number of adults, children and infants. Extras and a promo code too, if your booking engine accepts them.

Enquiries and leads#

When the assistant can't finish the job, it offers the guest a short message form. The guest gives their name and email, and the message comes prefilled with their dates, party and question, which they can edit. Each enquiry has a reason:

ReasonWhen
sold_outThe guest's dates or room are full. They can ask about cancellations or nearby dates.
request_to_bookThe property takes booking requests and the guest wants to ask something before paying.
questionThe guest asked something the property's information doesn't answer.
leadThe guest is interested but not ready to book. The property can follow up.
personThe guest asked for a person or a call back.
generalAnything else, including questions about an existing booking, refunds and complaints, which the assistant can't see or change.

We deliver each enquiry into the property's inbox on your platform, so the property replies where it already works, and by email to the property. For the inbox, we need a way to create a message or enquiry on your platform with the guest's name, email, message, dates, party size and the reason.

Booking confirmation#

We need to know which bookings came from the assistant, for the monthly statement we send you, and for per-booking pricing where we have agreed it. Your platform tells us when a booking that started in the chat is confirmed, with:

  • Your booking reference.
  • The reference we pass to your checkout with the stay.
  • The booking total and currency.
  • Its status: confirmed, or cancelled later.

We agree how when we build the connection: a webhook from your platform to us, or us polling your platform for bookings.

Staging and testing#

We build and test against your demo account first. Before any property goes live, we check on a test property that availability, quotes, extras and checkout match what your own booking pages show for the same stay.

Book a 20-minute call