Feature Requests

Sort by

• Newest Reply
• Newest Topic

Hi John,

You can pause or even turn Rezzy off for just one booking for exactly the reasons you mention.
https://www.ownerrez.com/support/articles/rezzy-ai-guest-communication#pause

Head to the Inbox and in the Right Hand pane you should see a slider that says Rezzy Responding:
If you click that slider it will give you the following options:


So if you are in a conversation with a guest, you can pause Rezzy for that conversation for an hour as an example.

Then it will resume answering for you if the guest writes in again later.   

Or if it is a guest with an issue and you would perfer to handle the conversation directly, you can pause Rezzy indefinately for just that booking.   

Then later if you decide never mind I do want Rezzy to answer you can just reenable it.

Hope that helps. 

-Steve

Can you provide a way to set Rezzy responses to a certain number? For many reasons, i may not Rezzy to answer while I work on the correct answer. I'd also like to set the number of Rezzy responses by email address. Once a customer becomes an issue, Rezzy needs to stop responding.

Thank you, Bri. I look forward to it !

Hey Maartje,

We've got plans to add support for inquiries, email and WhatsApp in the inbox. Once that work is complete, Rezzy should be able to respond to those. 😃

I don't have an ETA to provide at this time, but I will mark this request as Planned!

You can accomplish this by using a Custom Field!

Step 1: Create a Property-Type Custom Field

1. Navigate to Settings > Custom Field Definitions
2. Click Create Field Definition
3. Configure the field:
   • Type: Select Property (this makes the field specific to each property)
   • Name: Something like "Door Code" or "Entry Code"
   • Merge Code: Create a short code like DOORCODE (OwnerRez will prefix it automatically, making it {PXDOORCODE})
   • Format: Select Plain Text (since you just need the code number)
4. Click Save

Custom Fields > Custom Field Definitions > Types of Field Codes

Step 2: Set the Door Code Value for Your Property

1. Go to Settings > Custom Field Definitions
2. Click on your newly created "Door Code" custom field
3. You'll see a list of all your properties - click Change on the property in question and enter 1234 (or whatever code you want) for the specific property
4. Save your changes

Custom Fields > Property-Type Custom Field View

Step 3: Add the Field Code to Your Email Templates

In any email template where you want the door code to appear, simply insert the field code {PXDOORCODE} (or whatever merge code you created). This will automatically populate with the correct door code for that property.

For example, in your pre-arrival email:

Your door code is: {PXDOORCODE}

Custom Fields > Using Custom Fields

 

Currently only options for manual door lock for a property are:

• Use the guest's phone number
• Generate a random number
• Don't generate, I will assign codes one by one

Would like the option to just set a fixed code for all booking that come in at a specific property. For example: set a permanent property door code of 1234 which is applied to all bookings that come in and populate the appropriate door code field on email templates.

I have also started using it and loving it so far!  Super easy to use and more affordable than Quickbooks.

I've fully switched over to REI hub from stessa and it is working out much better, for anyone who finds themselves here. I'd love to have it integrated with OR though!

Owner Rez needs a “National Park” & “State Park” category for Location. State parks, like Enchanted Rock (TX), Golden Gate (CO) Berkeley Springs (WV) are very popular.
Please vote for the feature, even if you aren’t near SPs & NPs, because people will stay with you, on the way to us. 
Outdoor attractions are a more recession-proof draw, than shopping & golf.
Per “Rezzy” in order to capitalize on AB&B’s “national parks” & geographic feature location search features, we need:
“

• National Park proximity fields
• Distance-to-attraction fields 
• Geographic feature categories (waterfalls, canyons, mountains, etc.)
• Structured "Nearby Places" section similar to Airbnb

Mention that:

• Airbnb has National Park-focused categories
• Many hosts market properties specifically for National Park access
• This is a competitive disadvantage for OwnerRez users
• Water sports and outdoor recreation are major booking drivers

The more users who request this, the more likely OwnerRez will prioritize it. This seems like a feature that would benefit a large portion of their user base!”

Our listing is suffering neglect (as in over a month empty now), due to OwnerRez neglecting National Parks in “Nearby Places”.

People found us on AB&B due to our proximity to 3 national parks (though it took us months, to convince AB&B that the Chesapeake & Ohio National Historic Park, Antietam National Battlefield & Harpers Ferry National Historic Park, were actual national parks, because their AI ain’t I). Because it isn’t an option on OwnerRez, it doesn’t show up on AB&B, no matter how many keywords we use. Please change this ASAP, & please vote for the feature, even if you aren’t near NPs, because people will stay with you, on the way to us. 

To repeat, in the chat with Rezzy about this, they said:“Suggest they add:

• National Park proximity fields
• Distance-to-attraction fields 
• Geographic feature categories (waterfalls, canyons, mountains, etc.)
• Structured "Nearby Places" section similar to Airbnb

Mention that:

• Airbnb has National Park-focused categories
• Many hosts market properties specifically for National Park access
• This is a competitive disadvantage for OwnerRez users
• Water sports and outdoor recreation are major booking drivers

The more users who request this, the more likely OwnerRez will prioritize it. This seems like a feature that would benefit a large portion of their user base!”

Rezzy says it’s a “no-brainer” which is hysterical, coming from something with literally no brain. 
Please vote for this, & make it so, before those of us who literally built around National Park proximity, go broke(r). 

Thanks so much, 

Emily DG
( repeating text because people don’t read past first lines)

We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.

Hi Jeanna,

I'm curious if a Tag Automation for individual Seasons and a corresponding Trigger would accomplish what you're after here.

You can set up a Tag Automation to apply to that Season.

Then, the Tag Automation will automatically apply a tag to a booking that comes in with a date of stay within a particular season. You'd then set up a Trigger to fire to only stays within that Season by adding a condition for the Tag you created.

This would allow you to identify those particular guests and send a message only to them, 80 days before their arrival date. Not exactly 80 days prior to the Season opening, but I think this would get you close.

In the future I think this could work for you by setting up the automation, but given that you have existing bookings that may not have been tagged yet, you would need to tag those bookings manually in order for the Trigger condition to work. Or, if you've already tagged those bookings, you can set the Trigger up as shown above using the Tag already applied to them.

__________________________________

Another feature you might consider are Scheduled Emails, but those would need to be set up on each booking individually. In a booking, you can go to Messages - Select Send a Scheduled Message - then pick the template and the exact date you want it sent on. We'll be expanding on this feature in the future.

We're also currently in development on a feature we're going to call Broadcast that will allow you to send a message to bookings in bulk, all at the same time. I don't believe the Broadcast will be a schedule-in-advance feature, but it would allow you to give a shout to those select bookings in one fell swoop.

 

When creating a quote, It isn't possible to remove the grayscale filter from the footer image since it doesn't allow custom CSS on that page.  Therefore my logo and my wording has come out in black and white instead of color.  It makes my quote look unprofessional.

Please consider allowing custom CSS on the quote creation page or let Ownerrez hosts know a different way to create a quote with proper color showing on our logo and lettering in the footer.

There should be a way to download pdf statements in bulk. 

We would like to have access to reports under the Limited Access. 

Hi,

Rezzy is currently only useful for the very first messages on OTAs. In my workflow, once guests have my direct contact details (email or WhatsApp), they no longer use Airbnb, and Rezzy cannot be used for the rest of the conversation.

In addition, inquiries coming from my own website cannot be answered with Rezzy at all.

Because of this, it’s hard to justify the paid version when Rezzy only covers a small part of guest communication.

It would be very valuable to have:

• Integration with website inquiries
• Integration with email
• Integration with WhatsApp or a Zapier/API workaround

 

This would make Rezzy a true multi-channel communication tool.

Thank you for considering this request.

Maartje

I was poking around this, too. If I'm going to take the hit on charge backs and cancellations I need to capture aa card processing fee. I was nearly there with custom surcharge before I realized, it owuld apply to all payment forms and can't be limited by payment type. Any help there?

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:

• Default to English for all other languages.
• Reply in French when guests write in French.
• Reply in Dutch when guests write in Dutch.

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: