Latest Activity...
What is the status of this now, after a year and a half?
I can't understand why there are so few vote for this, nor why this has bypassed the common sense of OR programmers. It is a real pain for repeat guests to always have to upload their IDs!
Currently there is no way to get the bookings for a specific guest using the APIs. We are building an app for our reservation team that will take the webhook from our phone system with the caller ID information and locate information about the guest from OwnerRez... ie determine if the caller is a guest... As an extension of this we would like to be able to know the booking information for the reservation team as well so they can just click on a quick hyperlink in the app and be brought right into Ownerrez booking. There is no way to do this at present... It would also be useful to know all of the bookings for a guest so that the reservation team can see if they are a regular, etc... Need an endpoint that will allow for Booking Queries by Guest ID.
Not sure how many of you use the APIs and would vote this up but this is where they told me to put the request...
I think our workaround will be to build out the OR database on our local SQL Server and then just do the queries local. Not ideal but I think I can make it work.
If using Kaba locks, tecnically, I dont think the code created for regular check in could be made to "activate early". The code does start working at 2PM, so if the unt was ready earlier than say the regular check in time (in our case 4PM) then the guest could use their code after 2. For us, the big feature here would be that the guest gets notified by text that the unit is available early. If you wanted the guest to have accsess earlier than 2PM, then with Kaba, im pretty sure another code (ECI) would need to be generated
Another commenter brought up a good point... this only really works on a same day clean/check in.
In the past, OR had our payment policy on the "View more details" link. After the redesign, the prospective guests now have to complete the following tabs before seeing how much they need to pay at the time of booking and 30 days prior to the arrival date.
When guests are not sure they will book, I'd like them to see how much they would owe at the time of booking and 30 days prior to arrival BEFORE they have to complete any of tabs (Contact, Renter Agreement, Travel Insurance).
Currently, they do not see this information on the form. They only see it once they get to the payment tab (which is grayed out until they complete all the other tabs).
The old design was better in this regard.
Please consider including the Payment policy (under the cancellation policy) on the Payment form.
Ruth
I too find the new inbox to be too cumbersome. Bad design. I don't know how other services handle a unified inbox, but I always go to the original.
A related change is that texts of sent messages stopped being selectable in order to copy it, that to select them, it's required to click on the text fields, which sends you to another page where you can select it. Makes no sense.
[This topic has been merged with another topic (Automated way to send text reports (by email)). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (Daily Checklist Report as auto-emailed PDF)]
This would be great
This is my issue, too. I'd like to split the longer stay into 3 equal payments, payable by credit card. I'd like the system to automatically prompt for payment. I'd like the system to let owners decide on a case-by-case basis how many payments, how much up front, and timeframe for payments.
Hi there,
Really appreciate you bringing this up. Your suggestion makes a lot of sense.
For a long time, OwnerRez only supported a cleaning date, and we added cleaning time fairly recently so our integrations with partner cleaning apps could pass that information in. That update was primarily designed to display the time that those systems were already sending us.
What we didn’t account for was exactly what you are pointing out, which is that many users who are not using a third-party cleaning platform still need an easier way to manage this. Currently, if you don’t enter a cleaning time, we default it to 12:00 AM, which isn’t very helpful and creates extra work.
A property-level default cleaning time or a simple option to match the check-out time would solve this nicely, and we’ll ensure this gets in front of the right folks on our product side. Your feedback is spot-on and would be a great quality-of-life improvement.
Thanks so much for taking the time to suggest it!
-Steve
When left blank, the cleaning time will default to 12:00 AM. I have to type in a cleaning time for every reservation. Would it be possible to add a default cleaning time property setting that would populate the default time for each property? Or, could we have a checkbox to set the cleaning time to the check out time?
Hi there!
You can currently request as many photos as you want. No new Feature needed.
I peeked in your account, and I only see one Custom Field set as File upload, and that is called ID Upload.
All you need to do is create another Booking Custom Field, also of the File type, and name it something like 'Selfie with ID' or similar. In the description, specify precisely what you want them to provide.
Can set this as a required field. And then both entry boxes would appear in the Point of Contact Form.
Settings would look something like this:
More info in this support documentation here: https://www.ownerrez.com/support/articles/capture-additional-fields-on-checkout-quote-acceptance#file
Hope that helps!
-Steve
Hi,
You can accomplish this by using two separate "file" type Custom Field definitions. You can find instructions to set those up here: https://www.ownerrez.com/support/articles/capture-additional-fields-on-checkout-quote-acceptance
When you have two required file type Custom Fields, they'll display like this during the booking flow.
We are now requiring guests to provide a clear copy of their ID, plus a photo of them holding their ID. We had to move to this system, due to credit card and ID fraud.
We are requesting a way for guests to upload multiple photos on the renters agreement.
Currently, as soon as you add a second photo, it deletes the first.
Yes, that one. When guests come from Airbnb, their email addresses aren't in the system. But glitches in the channel integration and guest typos can both lead to errors in the guest's name and/or multiple guest records. Because the only two matching criteria the system currently allows for updating guests are name and email, it's impossible to update guest names that don't have an email address. I can also foresee it happening that a returning guest provides a different email address than last time, and if I were matching email addresses OR would assume it's a different guest. Using GuestID is a very simple, surefire way of guaranteeing records are updated instead of added.
I never use the new inbox, it's very cumbersome. It creates multiple threads for channel messages and sms, creating confusion.
Legacy inbox is very intuitive and very convenient. It should be the default messaging system.
Ownerrez mentions that legacy inbox will be removed soon. That will be a big mistake, please keep it.
Hi PM Company L,
We're actively working on a Quality Center feature that we hope to roll out sometime in the first or second quarter of 2026—the exact timing depends on several variables. There are multiple components involved, but a major piece relies on quality metrics from Airbnb, including guest reviews, incident data, and additional information their API provides behind the scenes. We're also planning to integrate our proprietary sentiment analysis metrics, tracking trends both chronologically and by individual property, which should prove valuable.
I believe this feature will satisfy most, if not all, of your request. That being said, I'll mark this request as "In Development" and we will keep you posted as that work progresses!
Hi Elliot,
Do you mean the guest import sheet found here?
https://app.ownerrez.com/imports/excel/guestexcel
That's an interesting idea, but I'm having trouble understanding the use case here. Could I ask you to expand on how you're making use of this import today to correct/clean up the name fields?
Add Guest Sentiment at checkout (from Rezzy), to be used as a trigger for messaging. Here is my use case scenario:
I have a setup where a message I send to guests after check-out asks for their review, unless the guest had problems during their stay, in which case the message is not sent; when I know a guest had problems, in my ERP, I flag the booking (as "Guest Had Problems"), that setups the booking with a "Guest Had Problems" tag in OR via an API call, and that makes the OR message requesting the review not to be sent (using the Tag condition in the Trigger setup).
It would be super helpful if the guest importing spreadsheet included an optional GuestID column so we could correct/clean up the name fields. Airbnb doesn't send emails, so that's useless as an alternative matching criteria.
It also needs to scrape this information and update it constantly since reviews can be modified and removed. So one time review on a property is not going to work. It has to be updated consistently. Perhaps a 24-hour refresh as old reviews are removed and the score is recalculated
Hello OwnerRez team,
I would like to suggest a new feature that generates a customizable report summarizing the Airbnb review performance of my properties.
Feature details:
The report should list each property/unit with:
The unit name or identifier
Overall star rating
Total number of reviews
Star ratings of the last 5 individual reviews
A direct link to the Airbnb listing of the unit
The report should be generated automatically based on a customizable schedule (e.g., every 2 weeks) or according to specific date ranges that I can select.
Benefits:
This would allow me to track guest satisfaction and recent feedback in a clear, organized format.
It would save me time by consolidating all key review metrics into a single report.
Having the link to the Airbnb listing included makes it easy to quickly access the property page if I need to follow up.
Thank you for considering this enhancement. I believe it would greatly help hosts manage their Airbnb reputation more efficiently.
🎉
You bet!
Oh amazing!!! Thank you for pushing out that release today. SO EXCITING!
Today's release should prevent the name of the locks showing if, only if, all lock codes for that booking are the same. So if you have a guest with two different locks but the same code on both, only the number should display.
But if you've got multiple locks associated with the same booking, some of which do not have the same code in use, the lock names still display.
The change released in October consolidated codes that were the same across multiple locks on the same booking, but it was still showing the names of those locks in every event.
Yes! I acknowledged that that portion of the request has been addressed -- thank you!
The second part of my request was for the internal property/door lock name not to be displayed in messages to guests -- or to provide us a way to set an external/public name for the locks which would be inserted instead. That still remains an issue.
Hi Alece,
I believe we've satisfied this request to the best of our ability at this time.
As of today, if you have multiple locks on the same booking that all use the same code, like this:
The door lock relevant field codes you use in your templates should just display the digits, not the lock names.
If you have multiple locks on the same booking and there are some codes different than others though, the names of the locks will still be displayed so that the guest understands there's a distinction between the locks and codes provided.
I've merged this request with a similar one, as we're seeing strong interest from multiple users on this feature.
We completely understand how important it is to have clear visibility into owner account balances and reserves—it's a fundamental part of transparent financial reporting. This is definitely something we want to tackle, though I need to be upfront that it won't be in active development for a while.
Behind the scenes, there are some design and reporting complexities we'll need to work through to get this right, so it's a bit more involved than it might initially appear. Right now, our primary focus is on successfully migrating all users to PMv2, but once that's complete, we have a running list of further enhancements we're eager to dive into—and this feature is absolutely on that list.
We really appreciate your patience as we work through these foundational improvements.
[Another topic was closed as a duplicate of this topic (PM - Owner reserves)]
