AI guest messaging and upsells for OwnerRez
TravelPal answers each OwnerRez guest in the thread on their booking. You connect it with an API app made under Developer/API Settings.
One OwnerRez connection works in both directions. Each item is explained below.
What TravelPal reads from OwnerRez
OwnerRez fits US property management companies with their own booking site. They sell there as much as on the booking channels.
Properties, and the clock each one runs on
The OwnerRez property record holds these facts: address, coordinates, property type, and how many guests the unit sleeps. It also holds the check-in time, the latest check-in OwnerRez will accept, and the checkout time. OwnerRez also gives a time zone for each property. If your units are in two zones, arrival times and quiet hours are right in each one. They are not set to the office clock. Photos, written descriptions, and the amenity list sit on the separate listing record. They arrive once OwnerRez opens listing content for your account.
Bookings, and the rows in the booking list that are not stays
OwnerRez puts blocked-off time, quote holds, and linked availability in the same booking list as real stays. TravelPal checks what each row is and leaves those rows alone. A cleaning block never gets a guest link or a concierge. A booking is active, pending, or canceled. TravelPal follows that status, not the cancellation time. OwnerRez lets you reactivate a canceled booking. A guest whose booking is active again needs their link and instructions back.
The conversation that belongs to the booking
A thread in OwnerRez belongs to a booking. That is how TravelPal finds a thread, with its history. So a guest is not asked something your team answered last week. OwnerRez has no language or locale field on a guest. So the concierge reads the language from the words the guest wrote. It does not use a setting nobody filled in.
One guest record, not one per booking
A guest in OwnerRez is an address-book contact with its own tags and notes. The same person keeps the same record across stays. Their email and phone number live there, not on the booking. TravelPal joins its returning-guest profile to that record. So a second-time guest is greeted as a returning guest. They do not explain the crib, the late flight, or the dog again.
The calendar, read to decide and never to hold
Before TravelPal mentions a night to a guest, it reads that night from your OwnerRez calendar. It reads the rules too. A night that OwnerRez marks available can still be closed to arrival or blocked by a minimum stay. If OwnerRez leaves a night out of its answer, TravelPal treats it as unknown, not free. TravelPal never reserves a night to protect a sale. OwnerRez publishes no way to take a held night back off the calendar. See how upsells work.
What TravelPal writes back to OwnerRez
Every message goes out through OwnerRez, never around it. So your OwnerRez inbox shows exactly what each guest was told.
Replies in the thread the booking already has
OwnerRez has one way to send a message, and it needs a thread. So there is no choice between email and text. The thread is how the message travels. OwnerRez has channel threads and SMS threads. An Airbnb guest is answered inside Airbnb, and an SMS guest keeps their SMS. If a booking has more than one thread, TravelPal answers in the channel thread first. A guest who reads 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 changes the planned time on the OwnerRez booking. It is written in that property's own time zone, so your cleaners read the real hour. OwnerRez lets TravelPal send the one field that changed, not the whole record. So nothing else your team typed on that booking is rewritten 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. Then the number shows in the OwnerRez reports, filters, and templates your team already uses. They do not have to remember to open another system. You define OwnerRez custom fields, so you tell us which one to write to when you connect.
Every word leaves through OwnerRez
TravelPal sends nothing around OwnerRez. The thread in your own OwnerRez inbox is the full record of what each guest was told. Anyone on your team can read it there. Your team is told by your rules and your quiet hours, not because OwnerRez announces it. The OwnerRez reference promises an event when a guest writes. It does not promise one when one of your own people types a reply.
Connected in four steps
OwnerRez turns on API access for your account. TravelPal does the rest itself.
Create the API app in OwnerRez
Go to Settings, then Advanced Tools, then Developer/API Settings. Create an app there. Then give it access to your own account from its Users tab, with Grant Access To Me. The same screen gives a Personal Access Token. That token can read a portfolio, but it cannot send a message or receive an event. So the app is the way to a working connection.
Ask OwnerRez to open messaging
OwnerRez covers messaging with a partnership agreement. You ask for it in one email to partnerhelp@ownerrez.com with the subject line Messaging API Access. That agreement covers sending and inbound guest messages. Your listing photos, descriptions, and amenities need a second agreement, with the subject line Listing Endpoints Access. Properties, bookings, guests, and the calendar sync without either one.
Authorize TravelPal
Connect the app and TravelPal does the rest. An OwnerRez access token lasts thirty days, which is the policy OwnerRez recommends. TravelPal refreshes it before it ends. So nobody has to note a date or paste a key again.
Events and the first import run themselves
TravelPal subscribes to your booking and message events. Then it imports properties, bookings, guests, and the calendar in the background. Every real stay gets its own private guest link from then on. A block or a quote hold does not. The connection adds nothing to your bill. See what it costs.
TravelPal shows the connection at every step: connected, last update, and any error in plain words. To see the other setup steps, read what onboarding involves.
What the OwnerRez connection will not do
Know the limits of OwnerRez before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Extra nights go to your team, not onto the booking
OwnerRez publishes no value that means booked directly with you. A booking from your own site arrives with the channel field empty. That looks the same as a channel OwnerRez has not named. If software read it as direct, it could move the dates on someone's Airbnb booking. So TravelPal moves no arrival or departure date here at all. Paid check-in and checkout times are clock times, not dates, and TravelPal still writes them. A guest who asks to stay another night reaches your team in their own words. The calendar is already checked.
TravelPal cannot send the first message on OwnerRez
Every OwnerRez message goes in a thread that already exists. OwnerRez gives no way to send a message to an email address or a phone number. So TravelPal cannot start the conversation. The guest writes first, or their booking arrives with a channel thread already attached. From that first message, the concierge answers at any hour.
No team-only note inside the guest thread
The guest can see every message an OwnerRez thread can carry. The only place a guest cannot read is the notes box on the booking. OwnerRez replaces the whole box each time something is written to it, so TravelPal never types into it. Sale notes reach your team in your own channel and by email. So does any question held for a person. 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 this is on purpose. So TravelPal finds a thread through the booking it belongs to. What the concierge learns from your past answers comes from conversations attached to a booking. It cannot see an SMS exchange with no booking, or an inquiry that never became a booking. Put anything you want it to know in the knowledge base.
When TravelPal's AI is not sure, it stops and asks your team instead of guessing. This rule is the same on every system: see the safety 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. You ask for it by email to partnerhelp@ownerrez.com with the subject line Messaging API Access. A second agreement, with the 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 goes in a thread that already exists. There is no way to send to an email address or a phone number. So the conversation starts when the guest writes. It also starts if their booking arrives with a channel thread attached. From that first message, TravelPal answers at any hour.
Which OwnerRez threads does TravelPal answer in?
The one the guest used. OwnerRez has two kinds of thread. The channel thread covers Airbnb, Vrbo, Booking.com, and Expedia bookings. The other is SMS. If a booking has more than one, TravelPal answers in the channel thread first. A guest who reads their Airbnb inbox will never see a text message.
Will TravelPal change my OwnerRez bookings?
Partly. It writes only the planned check-in and checkout times a guest paid for. It writes one field at a time, so nothing else on the booking is touched. It also writes a custom field that you choose. It does not move arrival or departure dates. OwnerRez publishes nothing that separates a booking on your own site from a channel booking. A wrong guess would rewrite a channel booking.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to OwnerRez in how widely they are used.
Updated