A short note for fellow OwnerRez hosts on what's possible when you connect a smart AI chatbot directly to your booking system.
What we did
We got tired of our website chatbot giving generic, half-useful answers. So we wired tawk.to's AI chatbot (ours is named "Scout") up to OwnerRez directly. Now when a guest asks "do you have anything open Memorial Day weekend for two?" — Scout checks real availability, quotes real pricing, and hands back a real booking link. In the chat. In seconds.
No more "Please call our office or email us at …." No missed leads at 11pm on a Saturday. No staff time spent answering questions a bot could have handled.
What it takes (at a high level)
There are really two layers to this build, and they live in different places. Most of the AI work happens inside tawk.to itself. The piece that makes Scout actually useful for booking questions — the live connection to OwnerRez — is a small piece of custom middleware.
Layer 1: The AI side (built inside tawk.to)
If you're using tawk.to, AI is an add-on you turn on in your account. Once it's enabled, you build out the actual chatbot directly inside tawk.to:
- Knowledgebase. Everything your bot needs to know about your property — amenities, policies, location details, FAQs, what makes your place special. You feed this in directly.
- Tone and brand voice. This is done in tawk.to too. Our bot will sounds like our brand because we trained her to in tawk.to's interface, not in code somewhere else.
- Conversational flow and qualifying questions. Before Scout can return accurate pricing from OwnerRez, it has to know three things: which location, how many guests, and are you bringing pets. We have two locations — one allows pets, one doesn't, and pets carry a surcharge — so without those answers, any price Scout gives is wrong. We taught Scout to ask those questions naturally as part of the conversation. That logic lives in tawk.to.
Layer 2: The middleware (the bridge to OwnerRez)
This is the technical piece that lets Scout actually pull live data from OwnerRez. It's a small Node.js app that:
- Takes Scout's request (location, dates, guest count, pets) and translates it into the right OwnerRez API calls.
- Hits OwnerRez's availability and pricing endpoints using your API token.
- Formats the response in a way Scout can hand back to the guest, including a direct booking link.
- Lives on a public URL so Scout can reach it. We host ours on Railway — inexpensive, deploys straight from GitHub, and handles environment variables and secret keys cleanly. Render or Fly.io would work too.
The middleware also carries an OpenAPI schema that tells Scout what it can ask for. That schema is where some of the harder OwnerRez-specific business rules end up encoded — pet rules, occupancy limits, minimum stays, promo code logic — so Scout doesn't have to guess.
How I actually built the middleware