Latest Activity...
it appears to work with only new bookings, not existing
create tag (any color you like ) and tag automation that applies the tag if RA is not signed?
With the new layout, it should be easy to put a red dot for a booking that doesn't have the RA signed so we know who to reach out to
Unified chat and email and inbox and booking details summary (dates platform price) would be my number 1 request.
Also there is an approx 45? minute delay sometimes between being notified about a chat reply in say airbnb or vrbo right away so you can have conversation and ORez which prevents conversation. Guests find conversation reassuring, ORez needs to pull the data more frequently or get sent it in real time ideally.
I'd like to chime in here and vote for inbound email capability. It's more efficient to work from one inbox, instead of multiple. I find it frustrating to hunt down correspondences. In particular, I'd like to be able to send direct emails to guests and receive that guest's response in the inbox (as opposed to tracking down the previous booking and selecting the message button there... and then receiving the response in a different inbox entirely).
Cheers,
Laura
When a guest sends an inquiry or even instant books, our automated message trigger fires off our standard response (as intended/expected). However, then Rezzy cannot suggest a draft reply to the guest's initial message since theirs is no longer the most recent in the thread. This should be corrected so that Rezzy automatically looks for the last message by the guest in order to draft a reply, regardless of whether or not our triggered templates fired off a reply in between.
Hi Patricia,
As of the release on 2/18/2026 of the remodeled Bookings > Overview page, Tasks are now on that page!
THANK YOU! This was very needed! Appreciate the update.
An update on the features requested. Last week, an update was released to show the payment schedule on the Quote sidebar.
That is correct. There is no 'Staff' access setting to exclude financial information. Only 'Portal' users have restrictions to booking financial info.
A Limited Staff Account in OwnerRez provides access to core booking and guest management functions, but with restrictions compared to full admin access. Here's what a limited staff member can do:
What Limited Staff Can Access:
Staff Member Access > Limited Access
Property Access Options:
When setting up a limited staff member, you can choose to grant them access to:
Staff Member Access > Limited Access
What Limited Staff CANNOT Access:
Limited staff members do not have access to:
This access level is ideal for team members who need to manage day-to-day bookings and guest communications without having full control over your account settings and configuration.
The reservation number should be larger on the updated booking page, The size of the old reservation number was perfect. when doing book keeping and such its easier to read when larger.
Hi Tim,
You're right. Nothing would be as good as having automatically adjusted payment schedules based on the date of booking relative to the arrival date, no question. I was just hoping that there would be some way to minimize the work involved as things sit now.
I don't think you need to have different quote templates. I explain different payment schedules to my guests with every quote, and how the schedule changes based on how far out they're booking, and no one has ever had a problem with it. (I have enough different quote templates for other reasons!)
In your situation, I would have the initial payment set to $500 for every booking, and explain in the booking instructions that an additional payment will be needed by December of each year to bring the total balance paid up to 50% of the booking amount, and if it's December or later, an additional amount will be due immediately afterward, with the balance due X number of days before arrival. The the booking form will indicate a $500 deposit, and a remaining balance of Y amount. You're right, it's not great, but at least it's not wrong and your email explaining the next partial payment will go out immediately for those bookings made in December or later, including a link to the partial payment form, based on your tag which is chosen at booking based on when it comes in. The guest would have to calculate 50% of the balance and make a partial payment, but even if they get it wrong by a little bit, I would expect it would be close enough for your purposes.
I've been racking my brain trying to automate your requirements within the confines of OwnerRez beyond this, and I haven't been able to come up with anything. Which is why this is such a great and important feature request! Here's hoping they come up with something soon!
Robert
Hi OwnerRez Team,
We’d love the ability to filter discount tags by date in the system. This would make it much easier for us to track promotions, analyze performance, and manage campaigns efficiently.
Thanks for considering this!
All true, but at least now you can set a complete workflow and templates based on whatever payment schedule you want (all payments referenced to either arrival, date of booking, or a mix of the two), have it all ready to go (including a special explanation about the schedule being different from the software default), and trigger it once at booking by adding a single tag, and then the whole thing automatically flows from there. In fact, an owner/manager could set up multiple different payment schedules and implement one of them simply by placing a tag on a booking. The manual work is absolutely minimized once the setup is done.
Is it the best solution? No, but it comes very close. The flexibility of tagging things and setting triggers based on tags really opens up almost unlimited possibilities.
In addition, because one can alter the instructions that appear at the top of the booking/payment form, one could place instructions there to instruct guests to wait for an email with detailed instructions, and/or setup all bookings to have a really small initial payment (call it a 'booking deposit' with the initial payment due immediately afterwards, and then have the initial payment amount be sent in an email with a link to make the payment, controlled by the tag you apply to the booking, right after the booking is made). Different schedules could request different percentages for the 'first' (actually second) payment.
Create each process you need and assign it to a tag. It's almost there!
1. This still leaves a confusing/misleading booking process for the guest. While you can modify the text instructions at the top of the booking page, the payment breakdown will always be wrong. Because you have to either choose "everything upfront" or "percentage / set amount" for first payment, that part of the quote/booking process will be "wrong". You can change the wording to say "$500 due now, with the remaining balance split over two payments due xx/xx/xxxx and xx/xx/xxxx." Or whatever the structure is. But beneath that it's going to show the guest either 100% due now or $500 due now and the entire balance due on a particular date. It just won't match.
2. While your process does reduce the amount of work in the work around, it still requires you to tag every booking request that comes in with the appropriate payment tag you've created.
3. If you have different payment structures depending on dates or other aspects, this won't work. OR doesn't allow you to have different quote templates based on criteria other than property. For me, if a guest books over a year out I take $500 upfront and then half in December and the balance xx days before arrival. If it is less than a year out they pay 50% up front and 50% xx day before arrival. So I can't have two different sets of instructions that apply based on tags. I would literally have to remember to go change those payment form instructions twice a year.
Dates seem to be missing for tasks...Due date is needed to be able to help manage the task itself. Particularly important for maintenance type items where we assign to a contractor, etc
All true, but at least now you can set a complete workflow and templates based on whatever payment schedule you want (all payments referenced to either arrival, date of booking, or a mix of the two), have it all ready to go (including a special explanation about the schedule being different from the software default), and trigger it once at booking by adding a single tag, and then the whole thing automatically flows from there. In fact, an owner/manager could set up multiple different payment schedules and implement one of them simply by placing a tag on a booking. The manual work is absolutely minimized once the setup is done.
Is it the best solution? No, but it comes very close. The flexibility of tagging things and setting triggers based on tags really opens up almost unlimited possibilities.
In addition, because one can alter the instructions that appear at the top of the booking/payment form, one could place instructions there to instruct guests to wait for an email with detailed instructions, and/or setup all bookings to have a really small initial payment (call it a 'booking deposit' with the initial payment due immediately afterwards, and then have the initial payment amount be sent in an email with a link to make the payment, controlled by the tag you apply to the booking, right after the booking is made). Different schedules could request different percentages for the 'first' (actually second) payment.
Create each process you need and assign it to a tag. It's almost there!
Agreed! It's frustrating that this request has remained on the back burner for so long.
Please provide a update on cancellation policy by season?
Currently, Airbnb reservation alteration requests do not appear in the OwnerRez inbox. Absolutely zero notifications come through OR for these guest-initiated requests. These requests do show inside Airbnb message threads, which suggests they are being delivered through Airbnb’s messaging system in some form. However, they are not being passed through the OR inbox API. For those of us trying to make OwnerRez our true single source of truth for all communication, this is a meaningful gap.
If this is currently blocked by Airbnb’s API limitations, it would be helpful to confirm that — especially since these requests now appear in Airbnb message threads. If it is technically possible via Airbnb's API, I'd love to see these alteration requests in the OR inbox thread with an actionable button to review/approve/decline. This would allow Rezzy to trigger a Task for human involvement as well.
Others use differing means of workarounds, but for myself and many others, workarounds don't work. Also, workarounds always require extra manual effort. My other problem with ALL workarounds is that the booking process only allows us to set our bookings as one payment or two payments. The language on the booking page our guests see will never match the language in your actual contract if you require multiple payments. You can't change it to match your workaround and I don't want confusion. As it is I have to explain up front to guests that the language in the booking process is not correct due to technical limitations of my software and that the payment schedule in the contract is correct. Who wants to have to do that and what guest isn't going to see that and be like "why don't you get better software?"
I’m not sure if others are already doing this, but I’ve found a workflow that works well for me.
I created a payment reminder email template, then after creating a booking I schedule the reminders to send in line with my payment schedule. It’s working well on my side.
If they pay by bank transfer (offline), my accountants will pick it up during their weekly accounts close. If they pay by card, OwnerRez records and tracks the payment automatically.
As long as we’re reconciling revenue frequently, it shouldn’t be an issue. The key is making sure that when the booking is created, the payment plan is confirmed and the scheduled reminder emails are set up.
Example template below:
When we schedule emails, the table displays very limited information. At a minimum, it should show the scheduled send date/time.
This is a core use case for me: I schedule payment reminders for rolling monthly bookings. I’ve been able to leverage OwnerRez for this workflow, but regardless, if an email is triggered by a scheduled timer, the scheduled date/time should be visible in the table so we can verify what’s queued and when it will send.
This feels like an easy fix and would make scheduled emails far more usable.
Any progress on this one ?
Thanks for that explanation!
It's nuanced...
VRBO is for vacation rentals. Each VRBO listing can be pushed to Expedia as a stand alone property. This is fine for vacation rentals but not hotels.
If you list your hotel units on Expedia directly, your rooms are all nested under 1 "property". From there, Expedia pushes to all their brands like hotels.com etc & to Google Hotels.
As far as I can tell, VRBO listings pushed to Expedia are NOT listed on Google Hotels and Hotels.com for example... Expedia owns like 30+ other sites where we used to get bookings.
Since I switched to listing on VRBO, I no longer get listing visibility in these other Expedia owned sites & each of my hotel rooms are treated like individual properties, rather than rooms at the same property.
VRBO/Expedia has very little documentation about this and offers limited support so it is difficult to understand the full scope of differences...
Can you explain what you mean about not being on Expedia? Via Vrbo, my listings are on Expedia. Is there something I'm missing about this?
Lodgify has an Expedia integration which pushes to Google Hotels. I don't love Expedia (or paying commission) so I'd prefer a direct integration to Google Hotels.
Glad this is being considered for 2026!!
THANK YOU!
We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.
Thank you for your renewed interest in this request, everyone!
We're discussing internally and will provide updates here as they become available. The year is young, and much of our future roadmap planning is still to be determined. You all make strong arguments here, and we will be exploring what options are available to us to see if we can hit the ground running on this any time soon.
