Latest Activity...
Thanks for your reply and ideas, Steven.
I run a really small one-man operation, and I have a personal connection with my repeat guests. So I have no worry that someone would be impersonating them.
A common instance is when guests extend their stays and they sign a new agreement to reflect that.
I do tell them they can upload any pic, but I'd be hesitant to write that in the instructions so that new guests booking for the first time upload something other than their IDs, which I've had happen, anyway.
Hi Scott,
Totally fair point, and I hear you.
There are definitely a lot of moving parts on our side, and at some point Product has to prioritize based on demand and impact. You have been here long enough to remember when we didn't even have a Guest ID Upload function!
For some visibility, the Photo ID conditional/custom field request is currently sitting at 3 votes, and this agreement-conditions thread is at 7. I know votes aren’t the only factor, but they do influence what rises to the top.
In a perfect world, we’d ship everyone’s “this would make my life easier” feature immediately… but then none of us would ever sleep again. 🙂
That said, I’m always about finding a practical path forward.
Just playing devil’s advocate for a second (because it helps sanity check the workflow): As the host, is there a reason you wouldn’t want an updated ID from a repeat guest occasionally? IDs expire, addresses change, and if you’re using this as a protection layer for yourself, having the most recent one isn’t the worst thing in the world.
Also, “repeat guest” in our systems is basically “same email address”. Guests are not logging in to authenticate that it is indeed the same guest. So if someone uses a shared email, a spouse books, or a friend books on their behalf, it might look like the “same guest,” even though it’s not. The ID requirement is really there to protect you, not just to annoy the guest (even though I know it feels that way).
Now, that doesn’t change your point: it is friction, and friction costs bookings.
A workable workaround (until we can do this properly)
I took a look at your current ID Upload Custom Field description:
“As described in the listing, please upload a copy of your government-issued photo ID (e.g., drivers license, passport).”
You could tweak that to give repeat guests an easy out without breaking the workflow, add something like:
If you’re one of our awesome repeat guests, welcome back!
Our system still requires a photo upload to continue, but you can upload any image (a screenshot, a selfie, or your favorite pet photo works great).
That way:
New guests still upload their ID like normal
Repeat guests don’t have to dig out their wallet and re-take the same picture
You still satisfy the “required field” so they can proceed
And if anyone messages you with “don’t you already have this?”, you can always respond with:
“Yep, you’re not wrong. The system is being a little dramatic, just upload a pic of your favorite cat and you’re good to go.” 😄
Not perfect, but it removes the biggest pain point while we push for a real conditional-field solution.
I sincerely help this gives you some ideas on how you can work around this limitation until we can better implement a solution.
Okay, cool!
Thanks, Steven.
The big thing for me is having different custom fields for my repeat guests when they book so that they don't have to submit their IDs every time. I don't see this being addressed as a fundamental need.
Thank you, Steve. I appreciate hearing your input on this -- including the current workarounds available.
Hi Scott and Alece,
Thanks for raising this again, and I’m sorry this thread didn’t get a more direct status update sooner. I understand why this feels like a basic, must-have workflow, especially when you’re trying to apply different agreements based on guest type or stay length.
At the moment, OwnerRez can only assign different legal agreements based on property and listing site. We don’t yet have a built-in way to automatically choose an agreement based on additional conditions like repeat guest or length of stay (30+ nights).
That said, I will be bringing this back up with our Product team for review and prioritization.
One relevant piece of context is that we’re currently in the middle of developing a Guest Portal, which will allow guests to access a link where they can make changes to their reservation, and eventually even communicate for direct bookings similar to channel bookings. Once that foundation is in place, it opens the door for cleaner, more integrated workflows like conditional agreements.
I don’t have a specific ETA I can share today, but I did want to confirm you’ve been heard.
Workaround available today (conditional agreements via Tags + Triggers)
In the meantime, there is a way to send different agreement links today using a combination of:
Tags (ex: “Returning Guest”, “30+ Night Stay”)
Different Templates that reference different agreements using the BULEASE field code
Triggers that send the appropriate template based on the tag/condition
I recorded a quick walkthrough here that shows the setup:
Enhancing Rental Agreements for Different Stay Lengths - Watch Video
Important note on the Photo ID requirement (separate limitation)
Scott, in your original example you mentioned wanting repeat guests to skip the Photo ID upload, while new guests still must upload it.
That specific part is slightly different than choosing between agreements, because the Photo ID requirement is controlled by a Custom Field. Right now, Custom Fields cannot be applied conditionally, so if the field is required, it will be required for all bookings using that agreement.
I see you already commented on a separate thread about this. That is the right place for that request (and I’d encourage an upvote if you haven’t already):
https://www.ownerrez.com/forums/requests/option-to-remove-collect-photo-id-in-rental-agreement#80418
Thanks again for the persistence here. I know it’s important, and I’ll make sure it gets visibility internally especially to consider as additional features as they work on the new Guest Portal
-Steve
Hi Bri,
Thank you for your quick response.
Yes, exactly — my goal is for guests to feel that when Rezzy is replying, they are actually speaking with me. For this to sound as natural as possible, Rezzy would ideally recognise the languages I speak and adapt accordingly.
My preference would be:
I understand this may not be something that can be implemented immediately, but I think it could be a valuable feature to explore!
Adding a receipt option would be incredibly helpful. Specifically for tax exempt guest you have to submit receipts to their employer and government agencies. These receipts need to have a company logo on it as well as be itemized. With all of the capabilities that Owner Rez offers, it’s disappointing that I have to create these receipts outside of the operating system. Addressing this issue would be very helpful.
I just added this feature request, so it’s very disheartening to see that after a year of issues with this, no attempt at a fix has been made. Sigh. I may just have to switch locks back over. I do not understand why it’s not set up like a trigger, where it will run until it syncs.
Please make it possible to download/export all our communication history. Doing so is in line with OwnerRez's policy on not owning our data and your statement that, "You should be able to take your data with you if you choose to use external services in conjunction with OwnerRez."
Sarah, for this specific reason, I just set all door lock codes to work anytime after 12. If this helps, great. If not, carry on. I just find it easier than managing and by 12, only the cleaners would be on site, so no harm, no foul if they were to peak in.
Often enough, OR Door locks do not sync and a guest shows up, only to be out in the cold with no access to the home while they work to get ahold of our team, so we can let them in. We then sync the door code with no issue and it goes through fine to the Schlage app and door lock. It’s clearly a service issue but they said to put in a feature request, and to get enough votes, in order for them to fix the syncing error.
What happens is, if there is an error or lock goes down for a moment at the exact moment OR chooses to sync, they do not push the lock code through like a trigger until the code syncs. My request is that they keep pushing the code through until it syncs with the Schlage app. If you have these locks, please vote for this request.
Hi Elliot,
I did some testing on my end, and it should use the seasonal rates set for the September season if no seasonal rates are set for the Labor Day season.
Hello!
We offer something similar on our confirm and pay form. You'll first want to add those optional surcharges to the account, making sure to give them a description and explanation to the guest of what they're for. More on how to set those up here: https://www.ownerrez.com/support/articles/optional-surcharge
Once optional surcharges have been configured in the account, guests should see the listed at the top of the confirm and pay form. It should list the ones that are available and the amount, along with the guest's explanation that was entered. If a guest selects to add one of those optional surcharges to their booking, the booking charges on the right-hand side under Price Details should be updated to reflect the add-on:
We use seasons for a variety of key times throughout the year, such as to restrict check-in/out on a holiday and so forth. There are also a few select times of year when we need to require a changeover gap (one night between guest stays) for logistical reasons. Right now, we are unable to add that in the season settings as changeover/gap rules are not available there. Separately we need to execute this in the Rate Calendar > Changeover Rules for each property individually.
The minimum/maximum night settings from the Rate Calendar are already available within Season settings; it's just the Changeover Rules that are left out for some reason. PLEASE add the Changeover Rules options to the Season settings as well, to help consolidate the number of touchpoints we need to remember to make to change settings as needed.
I see the quote expiration date. I have a last-minute inquiry that I've quoted and want it to expire at 2 pm today so that my managers have enough time to schedule their crews. Expiration is currently date only, need that extended to include time (with timezone of the property).
Hi Maartje,
It's super helpful when Rezzy can respond in the guest's native language, but you've got to be able to know what she said without having to copy / paste into a third party translation app! We definitely have plans to add translation options in the inbox in the near future.
Sounds like what you're asking for though is a bit more granular in that you'd like to tell Rezzy what languages specifically are okay to respond in, but limit it to those languages and reply in English (or a specific language of preference) for all others?
I don't know that we could accommodate that in a v1 of this feature, but I do believe that translation tools (once available) will get you and others to the ultimate end goal here.
Rezzy gives the option to reply in English or in the guest's language. I would like Rezzy to reply in the guest's language if it's a language I speak as well ( in my case Dutch, English and French). But I wouldn't like to reply in a language that I don't understand as I won't be able to double check the answer and people will find out it's not really me replying! If that could be an option, that would be great ! Thanks.
This promised feature is so basic and essential, I’m not understanding why no action is being taken on it nor why no reply is provided to request for its status.
I'd love a rental agreement condition based on length of stay so that longer term stays (30+ nights) automatically receive the longer stay rental agreement to sign!
Wow! Love the video response! The more I work with the company, the people, and the technology, the more impressed I am. Thank you.
Apologize for my lack of clarity! In my case, I had a returning guest who needed an extension on the quote expiration date. I would like to trigger a gentle reminder email x days before the quote expires, and possibly the day after it expires. This would allow the expiration date to be extended or shortened while still providing gentle reminders a few days before and after it expires. I was not looking to automatically update the quote's expiration date.
Bri's option works, however it would show a list of all Properties. If you did need it Property by Property you would have to do further filtering.
I think an even better report to run would be the Booking Summary Report.
https://app.ownerrez.com/reports/bookingsummary
This can be run for different periods and set to give a count by Departure date across all listings and give you individual counts as well as a total
Let's take a look:
Understanding the Booking Summary Report for Count of Number of Bookings 📊 - Watch Video
Hope that helps you more easily get the counts you are looking for each month!
-Steve
Hi Jay,
Thanks for the feedback here, that totally makes sense, especially for repeat guests where you want to keep things low pressure but still follow up at the right time.
Just to clarify one piece first, Triggers only control when a message gets sent. They don’t automatically change anything about the booking or the quote itself (like extending the expiration date).
It sounds like there are really two separate needs here:
1) Automatically extending quote expiration dates
OwnerRez doesn’t currently have a way to “auto-extend” a quote expiration based on guest behavior or quote type (like returning guests vs new guests). And in practice, that can get tricky because expiration timing is often a judgment call. For example, should it extend every time the guest opens the quote? Only if they’ve stayed with you before? Only if they replied? Only if dates are still available?
That’s why today it’s more of a manual, case-by-case adjustment, and you can extend it anytime by editing the expiration date directly on the quote.
2) Sending a reminder before a quote expires
This part you can absolutely do today with Triggers, even if the expiration date itself stays the same.
What we’d do is set up a scheduled trigger that goes out “X days after the quote is created” (ex: 3 days after) with a condition that the Quote Status is open. This way if the quote expired or was accepted or anything else it won't send your message. The wording can be a friendly nudge like:
“Just checking in, your quote is still available for now, let me know if you have any questions!”
The only limitation right now, like you mentioned, is that the timing is based on the quote creation date, not the quote expiration date.
But if you set your quote expiration to let's say 5 days, you could send one nudge each day if you really wanted to. And have a different template for each day.
Let me show you how in a quick video:
Managing Quote Expiration and Sending Gentle Reminders - Watch Video
Hey Mitch,
We don't have an ETA at present, but we'll be sure to circle back to this forum thread to provide updates as they become available.
Hey Chris,
If you apply the following filters to your Bookings page List View, does this get you what you need? You can filter it by only confirmed bookings that depart within the date range of your choosing.
The Booking Statistics > Bookings report currently only counts bookings by arrival date, with no option to view counts by departure date instead.
Use Case: I need to verify that my cleaning service is billing me for the correct number of departure cleans each month. A simple count of departures per property for a specified time period (in my case, typically "Last Month") would make this verification quick and straightforward, but there currently exists no report that provides this count.
Current Workaround: I have to export the Bookings Detail Report to Excel and manually create pivot tables to count departures per property - this is time-consuming and unnecessarily complex for such a fundamental operational need.
Requested Enhancement: Add a date criteria toggle (similar to other reports) that allows users to select either "Arrival Date" or "Departure Date" when running the Booking Statistics: Bookings report.
This would benefit any property manager who needs to track turnovers, verify cleaner invoices, or analyze departure patterns.
I would like to extend quote expiration dates (especially for returning guests) versus a standard number of days so I can provide gentle reminders when a quote is about to expire, and the guest has not booked yet. The only current trigger option is the quote creation date.
Hi,
Right now Tax report shows taxes you collect and normally it is the same as "taxes owed", but:
Would be nice to address these issues -- either new report or new column(s) in existing report. Plus a checkbox for problem #2. In this way I don't need to keep in mind that this month I charged renters extra and therefore I need to calc my taxes manually. Ideally these charges should contain taxes (as separate lines), but it seems that Airbnb simply doesn't support this...
Or at very minimum highlight taxes columns in red if OR observes discrepancy between "collected" and "owed".
Thank you,
Michael.
Reviews are very important in Google searches.
Currently, it looks like only the review rating is generated by the default schema, but not the review description. Please add review description (at last the snippet):
Thank you, I did use the seasonality option. It was just what came to mind.
I am not sure options are showing up on platforms, I have never had a response from a guest. We have friends test-driving the system, will be talking to them as we fine-tune. Love the responsiveness here, A+ work!
Emily DG
