For developers

You don't build the AI. We do.

We build the connection to your system, run the assistant and keep it up to date. Your team gives us access, answers questions and reviews what we build.

Read the developer docs

What we need from you
  • A demo account with a test property set up like your clients' properties
  • API access, if you have an API. If not, we work from what your own booking pages use
  • A contact on your team for technical questions
What we build and run
  • The connection to your system
  • The assistant, its hosting and monitoring
  • Branding for each property, in your clients' colours
  • Updates and support, for as long as you use it
What you review
  • That quotes on the test property match your booking pages
  • The checkout model: hand-off to your checkout, or booking in the chat
  • How enquiries reach your inbox
  • How guest data is handled. See Security and data

We build it with you, at your pace.

We build it with you, on your demo account first. It depends on what your system exposes and which checkout model you choose, so we agree a plan on the first call rather than quote a date here.

Nothing goes live for a client until you have checked it on your test property.

On your clients' websites, it's one line of code.

One script tag. It shows as a chat button in the corner or as part of a page, in the property's colours, with no NoGeek branding.

<script src="https://chat.nogeek.org/loader.js" async
        data-destination="PROPERTY_ID"
        data-white-label="true"></script>

Embed reference

What we map from your system.

If your system holds it and a guest would ask about it, we connect it. Where something is missing, the assistant works without it.

The property
In your platformIn the chat
Property details and photosAnswers about the place, with a details panel
Room, unit and pitch typesShows the options that fit the guest's dates and party
Amenities and facilitiesAnswers “is there parking?” and “can we have a fire?”
Occupancy, minimum stays, house rulesOnly offers what the guest can actually book
Cancellation policyExplains it clearly when a guest asks
Site knowledge and FAQsAnswers local and practical questions
Assistant name, tone and sign-offSounds like the property, not a bot
Booking
In your platformIn the chat
Live availability and cut-offsReal dates, never guessed
Rates and pricing rulesA priced quote in the chat
Extras and add-onsAdds dogs, early check-in or a hamper to the stay
Promo codes and member discountsApplied in the quote
Activities and timed slotsBooks experiences as well as stays
Instant book or request to bookFollows the property's own setting
CheckoutHands the guest to your checkout with the stay chosen, or books and takes payment in the chat
Enquiries inboxFeeds straight into your enquiries, prefilled with the guest's dates, party and question
Guests not ready to bookSold out, still deciding or asking something only the property knows: the chat takes their name and email as a lead instead of letting them leave

Guests book through your checkout, or in the chat.

  • Hand-off to your checkout. The default. We need a booking address that accepts the stay in the link. Your booking engine and payment provider do the rest.
  • Booking in the chat. Built per platform, on your API and your payment provider. The guest chooses, pays and gets confirmation without leaving the chat. It already runs this way on sites where we run the booking engine, including our demo.

The connection specification

Talk to us about your system.

Bring a developer to the call. We'll go through what we'd connect and how.

Developer docs

Book a 20-minute call