AI guest messaging and upsells for OwnerRez
TravelPal connects to OwnerRez with an API app you create under Developer/API Settings, then answers each guest in the thread hanging off their booking, because that thread is the only way OwnerRez sends anything. Properties, bookings, guests, and the calendar sync as soon as the app is authorized. Sending and inbound guest messages sit behind an OwnerRez partnership agreement, asked for in one email to partnerhelp@ownerrez.com.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from OwnerRez
OwnerRez is strongest with US property management companies that sell through their own booking site as hard as they sell through the channels.
Properties, and the clock each one runs on
The physical facts sit on the OwnerRez property record: address, coordinates, property type, how many the unit sleeps, the check-in time, the latest check-in OwnerRez will accept, and the checkout time. OwnerRez also publishes a time zone per property, so a company with units in two zones gets arrival times and quiet hours right in each one instead of running everything on the office clock. Photos, written descriptions, and the amenity list live on the separate listing record, and those arrive once OwnerRez opens listing content for your account.
Bookings, and the rows in the booking list that are not stays
OwnerRez files blocked-off time, quote holds, and linked availability in the same booking list as real stays, so TravelPal checks what each row is and leaves those alone: a cleaning block never gets a guest link or a concierge. A booking is active, pending, or canceled, and TravelPal follows that status rather than the cancellation timestamp, because OwnerRez lets a canceled booking be reactivated and a reinstated guest needs their link and their instructions back.
The conversation that hangs off the booking
A thread in OwnerRez belongs to a booking, and that is how TravelPal finds one, history included, so a guest is not asked something your team answered last week. OwnerRez carries no language or locale field on a guest, so the concierge takes its cue from the words the guest actually wrote rather than from a setting nobody ever filled in.
One guest record, not one per booking
A guest in OwnerRez is an address-book contact with its own tags and notes, so the same person keeps the same record across stays, and their email and phone number live there rather than on the booking. TravelPal joins its returning-guest profile onto that record, which is why a second-time guest is greeted as one and does not re-explain the crib, the late flight, or the dog.
The calendar, read to decide and never to hold
Before a night is mentioned to a guest, TravelPal reads it from your OwnerRez calendar, and it reads the rules with it: a night OwnerRez marks available can still be closed to arrival or locked under a minimum stay. Nights OwnerRez leaves out of its answer are treated as unknown rather than free. Nothing is ever reserved to protect a sale, because OwnerRez publishes no way to take a held night back off the calendar. See how upsells work.
What TravelPal writes back
Every message goes out through OwnerRez, never around it, so your own inbox shows exactly what each guest was told.
Replies in the thread the booking already has
OwnerRez has exactly one way to send a message and it takes a thread, so there is no email rail or text rail to pick between: the thread is the transport. OwnerRez threads are channel threads and SMS threads, which means an Airbnb guest is answered inside Airbnb and an SMS guest keeps their SMS. Where a booking carries more than one thread, TravelPal answers in the channel thread first, because a guest reading their Airbnb inbox will never see a text message.
Sold check-in and checkout times, on the booking
A paid early check-in or late checkout moves the planned time on the OwnerRez booking itself, written in that property's own clock, so the crew turning the unit reads the real hour. OwnerRez accepts the one field that changed rather than the whole record, so nothing else your team typed on that booking is rewritten in order to sell an hour.
Values into the custom fields your team already built
What TravelPal sold can go into a custom field on the booking, so the number lands in the OwnerRez reports, filters, and templates your team already works from instead of in a system they have to remember to open. OwnerRez custom fields are defined by you, so you point us at the one you want written when you connect.
Every word leaves through OwnerRez
Nothing is sent around the system. The thread in your own OwnerRez inbox is the full record of what each guest was told, and anyone on your team can read it there. Handover to a person runs on your rules and your quiet hours rather than on OwnerRez announcing it: the published reference promises an event for a guest's message, not for a reply one of your own people types.
Connected in four steps
OwnerRez switches API access on for your account, and TravelPal does the rest itself.
Create the API app in OwnerRez
Settings, then Advanced Tools, then Developer/API Settings. Create an app there, then give it access to your own account from its Users tab, Grant Access To Me. The same screen issues a Personal Access Token, which is enough to read a portfolio but cannot send a message or receive an event, so the app is the route to a working connection.
Ask OwnerRez to open messaging
OwnerRez covers messaging with a partnership agreement, and it is one email to partnerhelp@ownerrez.com with the subject line Messaging API Access. That agreement is what carries sending and inbound guest messages. Your listing photos, descriptions, and amenities sit behind a second one, subject line Listing Endpoints Access. Properties, bookings, guests, and the calendar sync without either.
Authorize TravelPal
Connect the app and TravelPal takes it from there. An OwnerRez access token runs for thirty days under the policy OwnerRez recommends, and TravelPal refreshes it before it expires, so there is no key for anyone to diary and re-paste.
Events and the first import run themselves
TravelPal subscribes to your booking and message events, then imports properties, bookings, guests, and the calendar in the background. Every booking that is a real stay, rather than a block or a quote hold, gets its own private guest link from then on. The connection adds nothing to the bill: see what it costs.
The dashboard shows the connection the whole way: connected, last sync, and any error in plain words. The rest of going live is covered in what onboarding involves.
What the OwnerRez connection will not do
Every property management system draws its own lines, and the ones OwnerRez draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Extra nights go to your team, not onto the booking
OwnerRez publishes no value that means taken directly with you: a booking from your own site simply arrives with the channel field empty, which looks exactly like a channel OwnerRez has not named. Reading that as direct is how software moves the dates on somebody's Airbnb reservation, so TravelPal moves no arrival or departure date here at all. Paid check-in and checkout times, which are clock times and not dates, are still written. A guest asking to stay another night reaches your team in their own words, with the calendar already checked.
There is no cold open on OwnerRez
Every OwnerRez message rides a thread that already exists, and OwnerRez has no send-to-email and no send-to-phone, so TravelPal cannot start the conversation. The guest writes, or their booking arrives with a channel thread already attached, and from that first message the concierge answers day and night.
No team-only note inside the guest thread
Every message an OwnerRez thread can carry is one the guest can see. The single place a guest cannot read is the notes box on the booking, and OwnerRez replaces that box wholesale each time it is written, so TravelPal never types into it. Sale notes and any question held for a person reach your team in your own channel and by email, and the OwnerRez booking notes stay exactly as your team left them.
Past conversations are reached through bookings
OwnerRez does not publish a way to list an account's threads, and says that is deliberate, so a thread is found through the booking it belongs to. What the concierge learns from your past answers therefore comes from conversations attached to a booking, and a bare SMS exchange or an inquiry that never converted is not visible to it. Anything you want it to know regardless goes straight into the knowledge base.
Where the AI is not sure, it stops and asks your team rather than guessing. That is the same on every system: see the guardrails.
OwnerRez integration FAQ
Does OwnerRez have to approve anything before TravelPal can message my guests?
Yes, for the messaging half. OwnerRez covers sending and inbound guest messages with a partnership agreement, requested by email to partnerhelp@ownerrez.com with the subject line Messaging API Access. A second agreement, subject line Listing Endpoints Access, brings your photos, descriptions, and amenities across. Properties, bookings, guests, and the calendar sync from the day you connect, with or without either one.
Can TravelPal message an OwnerRez guest who has not written yet?
No. Every OwnerRez message rides a thread that already exists, and there is no way to send to an email address or a phone number, so the conversation starts when the guest writes or when their booking arrives already carrying a channel thread. From that first message on, TravelPal answers at any hour.
Which OwnerRez threads does TravelPal answer in?
The one the guest used. OwnerRez runs two kinds of thread: the channel thread, which covers Airbnb, Vrbo, Booking.com, and Expedia bookings, and SMS. Where a booking carries more than one, TravelPal answers in the channel thread first, because a guest reading their Airbnb inbox will never see a text message.
Will TravelPal change my OwnerRez bookings?
Partly. Only the planned check-in and checkout times a guest paid for, written one field at a time so nothing else on the booking is touched, plus a custom field you nominate. It does not move arrival or departure dates, because OwnerRez publishes nothing that separates a booking taken on your own site from a channel booking, and guessing wrong would rewrite a channel reservation.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest OwnerRez in how widely they are used.
Updated