Feature Requests

Sort by

• Newest Reply
• Newest Topic

Thanks for putting this feature request together! These ideas grow when more voices weigh in, so if you know other users who'd find this useful, send them the link and ask them to upvote.

Community feedback really helps us prioritize what to build next.

Request: Let notification settings filter on more than one field at once — e.g., "notify this team member only when Category = Maintenance AND Priority = Urgent," not just a single toggle per notification type.

Use case: We want our maintenance lead to see every maintenance task for visibility, but only get actively interrupted (push/email) for the urgent ones — otherwise the volume trains people to ignore the notification entirely.

Request: Allow tasks to auto-assign to a specific team member based on task category (e.g., all "Maintenance" tasks → a designated staff member), similar to how Availability Rules or Triggers work elsewhere in the product.

Use case: We manage properties across 4 markets with different vendors per market. Every maintenance issue currently requires a human to manually open the task and assign it before the vendor can act — that's a delay we're trying to eliminate for urgent issues where minutes matter (no heat, lockouts, etc.).

agreed!

Would love to be able to have my listings easily show up on MisterBandB for more visibility please!

Would love to be able to post on Peerspace for events during the off season please!

Has this changed by any chance, would love to use templates to send out emails and SMS based on the time of the booking/checkin/checkout

Airbnb & VRBO are both doing great on this. Has OwnerRez added this feature?

[This topic has been merged with another topic (More Customization on Booking Page: Hide and Move Columns in List View). All unique votes have also been merged.]

[Another topic was closed as a duplicate of this topic (Allow removing and moving columns on Bookings -> List)]

Thanks Cecilia, this is an excellent request.

While I'm here, I'll share the workaround that I came up with for Cecilia that others may find helpful in the meantime.

I noticed that in my personal account, I actually had some 'unaffiliated reviews' that were clearly from a home that I no longer own. So I knew it could be done

I had a property that I needed to disable, so I found a test subject.

Here is what I did to save the reviews from that property

1. In Quality Center > Reviews > Guest Reviews, I filtered for reviews just for that property
2. Exported those reviews to Excel
3. Disabled the unneeded property
4. Opened the Excel file side by side with the OwnerRez review import template (Tools > Import/Export > Reviews)
5. Copied the data I needed, a column at a time, from the export file to the import file, - not including any property columns.
6. Import the new file - sans property info - back into OwnerRez

Voila. Reviews that will outlive the home.

Thanks for the update Joel...that's very encouraging!

Hi Sheila,

This pairs really well with another Feature Request, so I've merged it into that one.

Thanks for sharing!

[This topic has been merged with another topic (Saving report settings). All unique votes have also been merged.]

[Another topic was closed as a duplicate of this topic (Booking Report)]

Gotcha makes sense. I suppose! 

I understand what you're describing. If I'm understanding correctly, you're not asking for the title to change based on what dates the guest is searching for. You're suggesting an automation that changes the listing title on a specific calendar date or when certain availability conditions are met.

My concern is that this could actually create a different problem.

For example, suppose it's August 3rd and the title automatically changes to something like "Book Now for Labor Day Weekend!" or "Perfect for Back-to-School Getaways." A guest who happens to be searching in August for a Christmas stay would see that same title, even though it has nothing to do with the dates they're booking.

The listing title is shown to everyone browsing your property, regardless of the stay dates they're searching. Because of that, it's generally intended to describe the property itself and its lasting features, not promote a specific event or seasonal opportunity. Airbnb's own guidance recommends using the title to highlight what makes your space unique, rather than trying to tell a temporary story.  https://www.airbnb.com/resources/hosting-homes/a/guidelines-for-writing-your-listing-title-533

I also think event-specific titles could become misleading. For example, if your title says "Minutes from the Bay Area Renaissance Festival," someone booking a stay months after the festival has ended could reasonably expect that event to be happening during their visit. When they discover it isn't, that could lead to a poor review or even a complaint to Airbnb that the listing was misleading. At that point, the feature could end up costing more in lost revenue and damage to your listing's reputation than it ever generated.

So I definitely understand the marketing goal. I just don't think automatically changing the listing title is the right mechanism for accomplishing it. The ideal solution would be for the channels themselves to support content that changes based on the guest's searched travel dates. Unfortunately, that's not something Airbnb, Vrbo, or Booking.com currently expose through their APIs, so it's not something OwnerRez can implement today.

Hello all,

Both an MCP server, and a CLI are in the works. However, there is a series of changes and improvements we need to make first to ensure that these are secure, fast, reliable, and useful. We've already released the first few rounds of changes and we are actively progressing on the next steps. I can't provide an exact estimate of when the MCP will land, but we are constantly moving forward to achieve that goal.

- (Released) OAuth 2.1 with read scopes and refresh tokens
- (Released) Revamped documentation site with agent friendly docs and an openapi spec
- (Coming soon) Etag support and better pagination to reduce unnecessary request cycles
- OAuth and Client ID discovery (CIMD) for agents
- MCP server
- CLI
- And much much more

At the same time we are working on many new API endpoints (like tasks and expenses) to expand the scope of what can be achieved with the API. I encourage everyone interested to subscribe to updates on our Developer forum to receive notifications for API announcements. 

Do these enhancements require an update to the code on update or is it all on the server side?

I'd love to see OwnerRez add a real form builder, something you could send guests at inquiry or booking time, not just during signing, with their answers landing right on the reservation. This doesn't necessarily need to be a whole new feature built from scratch, it could just be a serious upgrade to custom fields: more field types (dropdowns, multiple choice, date pickers, maybe some conditional logic), and the flexibility to use them anytime in the guest journey, not just tied to one specific flow. I've used Google Forms and am now switching to JotForm for this because OwnerRez's custom fields can't cover it, which means one more tool to manage and stitch together. Would be great to have that built in natively and skip the extra step.

Here's my problem: I've got two agreements per property, the primary rental agreement and a secondary recreational equipment/hot tub waiver. When a guest goes to sign either one, the custom fields I've set up for the property show up on the signing page for both agreements. Plus, I have fields that only apply to the main rental agreement, but they're also showing up on the recreational equipment waiver's signing page, which doesn't make sense since they're not relevant there. My guests are getting confused since they're being (re)asked questions on the rec waiver's signing page that have nothing to do with what they're actually signing there. Would love the ability to assign a custom field to a specific agreement template, so it only appears on the signing page for that agreement.

I was hoping was a date trigger to change the description on our OR account. Like it would automatically update it if it is open at a specific date in time, ie say august 3 if open still, OR would update until that holiday is booked.  If that makes sense, it is basically an if statement that checks calendar just like say a gap night offer but instead it updates the title, just a thought until the channel support multiple date driven as explained, and yes, AIR now has limited cancellation on their end which I am not even sure what the "available markets/regions" are but I did just notice that....it's kind of like a whackamole game with these channels as soon as you get used to something they change, delete or add something then we have to adjust!

There are a few things that I don't like about Hosptiable that have kept me from switiching (namely that they charge a commission for direct bookings)...but their MCP is very tempting! I will wait for now, but an update from OR would be great...

I'm about to build my own API connection with Claude since there's still no firm timeline here. Would rather not duplicate effort if native MCP is close, but at this point I need to make a call. Any updates on when it'll actually be live? Even a rough quarter would help me decide whether to invest the time in a custom build or keep waiting. This is becoming a must for me!

Thanks for the suggestion. I can definitely see the value in wanting to highlight different events throughout the year without having to continually edit your listing.

The biggest challenge is that this isn't really something the major OTAs currently support through their APIs. Airbnb, Vrbo, Booking.com, and the other channels don't provide a way for a PMS like OwnerRez to send different titles, headlines, or descriptions based on the dates a guest is searching.

Ideally, what you'd want is something like:

• A guest searching for September 1 to 5 sees "Stay for the Labor Day Festival!"
• A guest searching for October 10 to 12 sees "Perfect for Fall Festival Weekend!"

Unfortunately, the channels only allow a single listing title and description, regardless of the travel dates being searched.

We could potentially do something similar on direct booking websites, where we control the entire experience, but we generally try to avoid creating features that behave differently on direct bookings versus the major channels. Keeping the experience consistent helps reduce confusion for users managing listings across multiple platforms.

Interestingly, the channels have recently begun supporting features like seasonal cancellation policies, where rules can vary by stay dates. So they are moving toward more date-aware functionality in some areas. At the moment, though, listing titles and descriptions don't have that same capability.

It's still a reasonable feature request, and we'll leave it open so others can weigh in. If the channels eventually add support for date-specific listing content, it would certainly become much more feasible for us to implement as well.

Thanks Rex! 

Thanks for bringing this to our attention, it is a bug that has been passed to the Engineers for review and repair. Keep an eye on the Latest Updates page for details when it's released, but we'll get it fixed soon!

Hey PacViewLodging,

This thread was really helpful in shaping some of the lock notification work we've done in recent months.

We've already released the following door lock notifications:

• Any Action Is Attempted by Guest
• Door Lock Code Sync Fails
• First Action Is Attempted by Guest
• Lock Problem
• Low Battery Warning

That covers (from your original post) the low battery alert from item #1 and the "first use" notification from item #4. We've also added logging for these locks directly on the booking overview page, so hosts can see the actions attempted on any locks assigned to that booking, which should help with the log visibility raised in item #2.

Given that, I'm going to mark this request as released. A few of the other ideas that were shared - staff code management, notifications when a lock is used with no active booking/block, and owner block time windows. Those are all valuable ideas, but they're distinct enough in scope and design that we want to track demand for each one individually rather than lumping them all under one general request that covers them all. That helps us see where the real demand is concentrated so we can prioritize what to build next.

So if you're looking for one of those specific pieces, take a look through the Feature Requests forum for an existing thread on it and add your vote, or if one doesn't exist yet, feel free to start one. That's the best way to make sure it stays on our radar and gets weighed against everything else in the queue.

Released this week!

When Airbnb removes a guest review on their side, it now correctly no longer appears in Quality Center star ratings, trends, category scores, or issue cards, and is excluded from hosted-site ratings, the public API review count/average, Google Vacation Rentals feeds, and review widgets. Channel-hidden reviews remain visible in host-facing review management grids.

Hi everyone,

With the new My Stay form in place, and that being the first step in the direction of a fully formed guest portal, I'm going to mark this request as released.

There's a lot of great discussion in this thread about what a more full-featured portal could look like. Those are all valuable ideas, but they're distinct enough in scope and design that we want to track demand for each one individually rather than lumping them all under one general "portal" request. That helps us see where the real demand is concentrated so we can weigh that next to what we already have on the roadmap and prioritize what to build next.

So if you're looking for one of those specific concepts, take a look through the Feature Requests forum for an existing thread on it and add your vote - or if one doesn't exist yet, feel free to start one. That's the best way to make sure it gets on our radar and gets weighed against everything else in the queue.

Thanks for all the input here! This thread genuinely helped shape where we're headed with My Stay and the portal experience.

Hi Megan,

Sorry for the delay here. Hadn't seen your last reply until I came to give you an update on your original post.

No, we do not have plans to display both of those v having to click into each one. You're welcome to open a separate Feature Request for that, but we really prefer it this way to make the best use of the screen real estate available on that booking overview page.

Now that we have the requirements panel rolled out on the overview, I'm going to mark this request released. It does not include ID verification in the requirements yet, but that is on the roadmap and will be coming in the near future. We're trying to track each suggestion for (in particular) the new My Stay portal and associated features individually so we can really see where demand is strongest. That allows us to determine what enhancements we should focus on first.