Developer docs
For developers at booking and property management platforms who are adding the NoGeek booking assistant for their customers. Read this first, then the Quickstart.
What NoGeek adds to your platform#
A booking assistant that sits on each property's website, under the property's name. Guests ask it questions, check dates, get a price and book. It works from your platform's live data and hands the booking to your platform. Your platform stays the system of record for properties, rates, availability, bookings and payments.
The parts#
| Part | What it is | Who runs it |
|---|---|---|
| Chat widget | A chat window on the property's website, added with one script tag. It shows as a bubble in the corner or as part of a page. | We host it. The property or your platform adds the script tag. |
| Assistant | The AI that answers, checks availability, quotes and opens checkout. It only states prices and availability it has just read from your platform. | We run it. |
| Connection to your platform | How the assistant reads property data, availability and prices, hands the guest to checkout (see Payments), and delivers enquiries to your inbox. | We build it with you, from a demo account on your system or from your API. |
| Property configuration | Per-property settings: allowed websites, site knowledge, FAQs, the assistant's name and tone. | We set it up for each property. |
How a launch works#
- Demo account. You give us a demo account on your system, or access to your API, and a contact on your team for technical questions.
- Connection. We map your platform's data and checkout. The connection specification lists what we read and what we need.
- Test property. We run the assistant against a test property on your system until quotes match your checkout to the penny.
- Configure each property. We add each property's website to its allowed websites and give you its property ID.
- Embed. The property, or your platform's website builder, adds the script tag. The assistant goes live on that site.