Feature Requests

Sort by

• Newest Reply
• Newest Topic

I am requesting a change to the door lock generation feature that will have further requirements prior to code generation such as having the credit card on file for a security deposit and also a signed rental agreement. I've had to delete and re-create codes multiple times for last minute bookings. I would assume this would be a simple fix?

An option to select "Blend" on a surcharge for bookings made on OwnerRez - Direct Booking sites that blend the surcharge into the nightly rate so it does not appear as a line item.

I prefer to collect the security deposit by check or other bank transfer to help elminate the risk of a charge back.  I'd like to see any option where the Security Deposit can be set to accept one of these payment options only, even if the guest used credit card for the rent portion of the charges. 

Would love to have a field code for the stored credit card info on file that we can use in templates. We want to be able to send our guests reminders of the scheduled payments and allow them to see what credit card we have on file in case they need to change their credit card info before the scheduled payments occur.

We use notes to document all calls with guest, how our welcome call goes, and any special needs (grocery, ski instructor, etc).

It would be great if there was a HTML link/short cut next to all the other links.

Yes!  OwnerRez now integrates with the Vrbo internal messaging system:

https://www.ownerrez.com/support/articles/vrbo-messaging

So you can schedule message templates using triggers, much as with email messaging.

https://www.ownerrez.com/support/articles/channel-templates 

Hi- Have they come up with a way to send scheduled messages from OR to VRBO guests yet?  I feel like I was able to receive messages from VRBO geusts for a short time and now it's gone.

It would be good to be able to mark a deposit as processed in the list of deposits generated.

I don't process the deposits daily or even weekly. It would be good to know where I left off.

Thanks for the update...very very excited! If not suggested already having ability to sync multiple locks at same property to same generated code (for those with more than one at each property) would be icing on the cake.! Thank you all for your hard work!

Hi!

You can jump to the Feature Request forum every time by using this link - https://www.ownerrez.com/forums/requests 

CRM - put forward and backward arrows so that you can easily navigate from one conversation to the next. This is standard on all mail systems.

It would also be nice to have a link directly to the suggestion forum. It is a bit hard to find, or is that by design. ;)

After discussing with Sifely, they currently have no plans to integrate directly with our system as our users can already access their locks through Jervis Systems. To learn more about using Jervis Systems, please refer to our support document available here.

[This topic has been closed as a duplicate of another topic (Make a rate adjustment per property on our Airbnb API)]

[Another topic was closed as a duplicate of this topic (API Rate Adjustment per Property)]

[This topic has been closed as a duplicate of another topic (Make a rate adjustment per property on our Airbnb API)]

[Another topic was closed as a duplicate of this topic (Control of channel Rate Adjustment at the property level)]

Yes, hopefully later this year, although it may get pushed into early next year.

is there any plan to add booking.com to the unified inbox?

Sure, you can already do that, in Criteria in the Trigger:

Hello!

I have encountered a handful of bookings that are shorter stays (2-3 days), therefore it does not make sense to send them all of my scheduled 6 messages. In some instances, it makes more sense to combine the "check-in text", sent 2 days after their check-in and the "departure reminder text" sent 1 day before their checkout. Would it be possible to create triggers / templates that are based on duration of stay?

Great suggestion, and one we've discussed a lot and have plans to improve upon. 

In the future, we plan to build the inbox as a threaded inbox instead of a guest inbox. This may not exactly match one-to-one with your suggestion here, but it will be similar and will allow us to clearly link the related booking, quote, or inquiry to each thread. It will also keep old conversations from mixing with new ones. 

There's a lot of enhancements planned for the new inbox! You can show your interest in that by voting for that feature too.

I am having the same issue and was reading through this thread that is two years old.  wondering if there has been any advancements made in this area?   I would really like to receive my guests SMS replies to my cell otherwise I am getting them very untimely and it makes me look bad responding so late.  

Thanks!

Shawn

Hi all,

I'm late to the party here, but recently learned of Google Vacation Rentals... my question is, is it best to apply to become part of GVR now, or do we wait until OR has finished the integration and then connect via OwnerRez?  I apologize if I'm way off or if this has been answered already.  

Those of us who started property shares notice that the traffic generated via shared sites/shared properties reflects on the GA of the property share owners. That is skewing the statistics of the share owner's personal site. All traffic for share participants is visible/attributed to the share owner's GA tag. 

Any way to be able to add a separate GA tag to a share or override attributing the share's traffic to the owner's website? 

Thanks

Something confusing I have noticed is how when you have a repeat guest across multiple properties in your portfolio, OwnerRez just lumps all the conversations into one giant thread without any sort of label to delineate what reservation the conversation was related to.

For example:

I have a customer we'll call David. In the past year he has booked 3 different properties in my account's combined portfolio. Each of these properties were tied to a different AirBNB api tied to our OR account (we have 3 AirBNB APIs connected). So when you look at the Conversation for client David, you see this one giant blob of conversation all run together. But this conversation is actually spread across 3 different bookings. What makes it look even more weird is that the conversation reflects the name on the account that the respective API is connected to. So in one part of the conversation the label is "Justus says", a few lines later "Ozark Stays says" and then the most recent one is "Eileen says".

Is there some kind of way a repeat guest conversation can have a line or something to show which actual reservations that portion of the conversation was related to?

Does it technically work right now as is? Yes.

Is it confusing to look at and may cause confusion for hosts? Also yes.

I also have a Schlage lock at my STR with Remote Lock integration. Looking forward to the release as well! 

Wow! We use Schlage Encode locks across all properties and currently rely on RemoteLocks, but a direct integration will be amazing. Thank you for developing this new feature. We look forward to its release!

—Eileen 

gettting this integration with schlage will cement OR as one of the best as I'm hating the Remotelock pricing and sub par options with others! Please bring this to a reality!

Vinh, I couldn't help but drop a screenshot here for you:

Look carefully. 🧐

This is a screenshot from a dev environment, but I thought you and others might be interested in seeing progress!  It's through dev and into dev review and QA now.  No ETA yet, but it's a real thing.

That's great to know! My info must be outdated - thanks for keeping us posted. I agree that incorporating AI into OR would be a hugely beneficial feature!

OMG, YES YES YES. Great, well-written write-up.

I know this was closed already as a duplicate of an existing feature request, but the way you've written up the issue and the suggestions you've incorporated deserve to be seen and promoted. So, OR--please see my reply here as an enthusiastic upvote on Tim's comment/request!