Feature Requests

Sort by

• Newest Reply
• Newest Topic

I second this! Same goes for filtering bookings on the List view, too--about half the time when I hit "back," it doesn't remember my selections and I have to re-select the filters. Fixing these two things would certainly make month-end financials less of a chore. :)

at least sticky filter. Right now filters are not consistently sticky and if I click back form the report I have to reenter criteria

For those with many properties (PM and common widgets), would be helpful to add (optional) columns for Min and Max bedrooms (example: so that whoever searches can select Bedrooms: Between 2 and 4) and not just have 3+ when 12 bd properties are also shown. and a pet friendly filter/check mark.

and traveler provided phone.

Yep if we had the charge changing preview then we could let you recalc charges on Vrbo again. That's a great point!

We turned the change charges on move option off for Vrbo because Vrbo charges can be a bit different than what's in OwnerRez and too many people were accidentally overwriting holiday fees or LOS discounts and running into issues with the new total.

Replying to this thread because it's sort of related, but in addition to this, can you bring back the option to automatically recalculate charges when making changes to Vrbo reservations? That was removed for some inexplicable reason, and now I have to recalculate things manually when a Vrbo guest wants to add a night, which is a step backwards.

Yep, this is in the works now, but no ETA yet.

For the rental agreements, go to the main Bookings display, List view, and Filter for Signed Agreement = No. That'll get your your list.

For photo IDs, unfortunately at present we don't have a perfect way of doing this, but you could probably get something fairly OK by using Tags. Make a "Got ID" tag and tag the bookings that have it, so you can easily identify those that don't.

It just spent an hour trying to find a quick way to determine if I had any missing rental agreements. There didn't seem to be a quick way to do this so I had to go through and check each booking to find three missing agreements. Am I missing something?

Also, we require ID and there is no way to quickly identify if this step has been completed. Could we add a field that could be manually marked and then searched or reported?

Thanks for your time.

Hi Chris,

Thanks for looking into this.

We are currently using Smartbnb to handle automated reviews for Airbnb so would be awesome to be able to have that in Owner Res so we can drop that software.

We write all our reviews and save them and then have Smartbnb choose one to send for us.

Smartbnb has bad review feature that I hope you guys can incorporate as well.

With that you can mark a potential bad guest and it will delay sending that review until the very last minute to give us time to handle the guest.

Scott and Heidi

I'm wondering Randy when you would send that email out? Is this something you'd use just prior to arrival?

That's an excellent idea, which I'll pass along. In the meantime, we just released a new "Tags" feature for bookings that can be tied in to Triggers. So, you could create a "problem" tag, and then build that into the trigger to not send the email if the guest or booking has that tag.

I have a series of messaging triggers that send several follow-up messages to guests after check-in and before/after check-out.

When a guest reports a problem, the communication becomes a bit more touchy. It's awkward to deal with a problem and try to placate the guest and then a few hours later, the guest gets an ebullient message saying, "I hope you're having a five-star stay!" Sometimes in those cases, being silent and just making it through to the end of their stay is the lowest-key way to avoid further issues.

There's already a "Guest has a problem" checkbox in the Notes screen of each booking. It would be great to leverage that so that if the box is checked, then corresponding messaging triggers can be tagged to "do not send if guest has problem." That would make some interactions a little smoother. :)

There's not currently a way to exclude a discount based on existence of a holiday, but that's a great idea -- I'll get that on our dev list.

Right now the only way to do it would be to set season or arrival date criteria on the discount so that it only applies to dates that aren't holidays.

I know how to add a extra charge for a holiday, but how do I prevent a discount to be applied if the dates are during a holiday? I don't see a criteria for doing so. If it does not exist, it would be great to add one.
Example: I have discounts for 3 night weekends, but don't want to run them during holiday weekends. How can I accomplish this?

This is a great idea...I have been looking for workarounds with zapier for a while now. +1

Not at present. It is planned to be added in the future.

Is there a way to set something up to allow guests to purchase the add-on surcharge options after they complete their initial booking? Say we offered a birthday cake, and they didn't buy it when they booked, but then decided it would be easier to have us provide it. Is there a way to set up a page, or an email with the options, to ask them one more time before they check in if they want any of the options?

Unfortunately, the only way to do that is to create a special season for just that one day, and control the checkin/checkout dates in that season.

Is there a way to block specific dates for check-in & out?
- Example: Can Christmas Day be blocked off to not allow check-in & out?

+1

+1

Yes, I agree. I am in setup now and this was very confusing. If you hit the filter, seems like you should only see the relevant seasons.

+1

This is a great idea.

Unless I missed it, would be nice if there was an ability to enable/disable display of abbreviated cancellation refund policy of the widget.

Such as, if renter selects dates outside of refundable period, display:
"If canceled, these dates are not eligible for refund".

if they select dates when refund is possible, display default policy message:
" X% refund if canceled Y days from arrival".

This maybe can be enabled/disabled by owner in case owner has some more elaborate policy such as cancellation fees etc that are hard to fit into a one-liner.

This is a good idea...

I think this is a very important area and open to costly mistakes. I hope you find a way to sort out the issues you're mentioning in your message and implement this soon. Working with rates/ seasons etc without having a security layer like this quite scary, to be honest. Thank you for your consideration.

Those min and max rates are for display purposes only - we auto fill them based on when your rates change or you can override them to say what you want. We thought about doing what you asked in the past. The problem with that is that it tends to lead to bad behavior and confusion. When rates are advertised in quotes, it would be unknown where the rate comes from because what's in the rate engine would be cut off by the min/max. The guest and user (you) would both be confused and ask questions. But it's an interesting idea that we'll continue thinking about!

Hi Steven and Andrew,

Steven, sorry for the delay in responding to you earlier in the summer.

Yes, Zapier is on the roadmap though not high priority because of so many other things. We agree that Zapier and Hubspot would be great integrations and provide some very useful tooling in and around OwnerRez. Zapier has been discussed at many engineering meetings over the last couple years.

Thanks for the nudge!

There are Nightly Rate (min) and Nightly Rate (max) fields for properties but they don't actually control the minimum and maximum per night price.

There are many reasons why rates might be set at wrong values by mistakes (such as overlapping discounts, seasons without prices etc).

So, it'd be great if the Nightly Rate (min) and Nightly Rate (max) fields didn't allow the rates to go less or more than the set range. If the rates go less than Nightly Rate (min) then they could be set to Nightly Rate (min) value.

It'd be terrible to deal with bookings that might mistakenly get a very low per night values.