Feature Requests

Sort by

• Newest Reply
• Newest Topic

Thanks, Chris. I'm going to send these details over to our dev team for review. We'll let you know what we find out.

Woo hoo! Added my rooms. Wish I had more than 8 to contribute.

Seems to be working well so far for pulling booking data, and I've already used it to run some light analytics without having to download and export a bunch of CSV reports. :)

One thing that failed this morning, though: I asked it how to respond to a particular question from a guest, and it wasn't able to pull the messaging thread.

The current MCP docs say messages are available read-only, and ChatGPT can see thread_ids on detailed booking records. The MCP schema also exposes GET /v2/messages for retrieving a thread.

However, ChatGPT can't actually make that API call. Its MCP tool definition tells it to invoke api_request, but the OwnerRez server responds:

Unknown tool: api_request. Available: ... api_get, api_write ...

So it looks like the MCP server's current tool names and the tool metadata ChatGPT received may be out of sync. I also don't see a first-class message/thread lookup tool—only booking/property/guest entities—so message retrieval appears to depend on the generic API tool.

Is this an MCP deployment/cache issue, or is there some additional messaging permission/configuration required on the OwnerRez side?

As of yesterday, a new feature will allow the addition of Automated fixed and percentage expenses.

https://www.ownerrez.com/support/articles/property-management-automated-expenses-setup-configuration

I just set a couple of them up on my account to automatically handle Vrbo commissions.  I will add some commentary as I see the results.

Great news! Automated Expenses released today!

OwnerRez's Property Management (PM) premium feature already records the Commission, Tax and Damage Protection (if applicable) expenses on every new booking for you. Automated Expenses takes this further by creating owner expenses on their own. They can be tied to related bookings or set to repeat weekly or monthly, so costs like lawn care, cleanings for owner stays or HOA fees are added without anyone entering them by hand.

Read more about it here - https://www.ownerrez.com/support/articles/property-management-automated-expenses-setup-configuration 

Please! Allow the export if communication history. This can easily help identify tasks and help start projects using CHATGPT Work. 

I just added 72 photos to my new site, each of which is assigned to a room.   After all that work I find out that the system disregards all my rooms and displays a gallery of 72 images.   The captions now make no sense since they used the context of the room and did not repeat the room name in each caption.

This makes no sense ... seems entirely arbitrary.   If the intent is to get customers to pay more for this feature, then this should be set up as an option.   We shouldn't be surprised after defining rooms and photos and then be told that we must masquerade as a multi-property site to get this seemingly obvious feature when we have only one property.

My trial was going smoothly until I hit this absurd and pointless restriction.

This is great news...I plan to set it up today with Claude. Will let you know if I see any problems in the setup process.  Thanks!!!

Thanks, Chris! I'll get that to our docs team for review.

Bri — one note on the ChatGPT setup instructions: I ran into a fairly confusing issue because ChatGPT's latest UI distinguishes between creating a plugin and creating an MCP App, and the current instructions don’t make that distinction clear.

I initially used Add → Create plugin with https://api.ownerrez.com/mcp as directed in the setup instructions article. That created an OwnerRez plugin wrapper, but it never triggered OAuth, exposed no OwnerRez tools, and mostly just offered to open in the desktop app.

What worked was Plugins → Add → Create MCP App, entering the same MCP URL there, and then completing the OwnerRez OAuth flow. That immediately produced the working connection and exposed the MCP tools.

The documentation may also want to call out that Developer Mode must be enabled for custom MCP apps. OpenAI’s own instructions point to a Developer Mode setting, but in my account that toggle wasn’t visible where their docs said it should be—though I already had the capability enabled from adding a previous custom plugin, so Create MCP App was available to me.

So I’d suggest making the ChatGPT steps very explicit: enable Developer Mode if necessary, then use Add → Create MCP App — not Create plugin.

Quick follow up to the release news above. Looks like Claude is having some trouble right now. If anyone is attempting to connect with Claude, you may want to wait until the outage clears.

https://status.claude.com/ 

Talk to your OwnerRez data with Claude and ChatGPT

As of today, you can talk to your OwnerRez data using Claude and ChatGPT!

Before getting started, check out our MCP feature page or our MCP support articles.

Connect your OwnerRez account to an AI assistant and ask it to find information about your bookings, properties, and guests. You can also ask "how do I…" questions, and the assistant can use OwnerRez documentation and support articles to help answer.

This first version is read-only. Your assistant can look up information in your account, but it can't create or change anything yet. We're working on more capabilities and access to more types of information.

To get started, follow the setup guide for your assistant:

• Connecting OwnerRez to Claude
• Connecting OwnerRez to ChatGPT
• Using another assistant? You can connect other assistants that support MCP connectors. Some assistants require a paid plan to add custom connectors.

What's under the covers with our new MCP feature

For the more technical folks, here's what's behind the new connection. 

The MCP server currently supports:

• Searching and looking up bookings, properties, and guests
• Retrieving full booking, property, and guest details, using the same data available through our API
• Reading our API documentation and support articles to answer "how do I…" questions

Again, this release is read-only. Assistants can retrieve information but can't create or change records yet. Tags aren't a built-in lookup in this first version, although an assistant can still read them through the API. We plan to add more record types, including tags, as we expand the connection.

We've also tightened access to API credentials. Only the account owner or a team member with account-wide access can create or manage API tokens and OAuth apps. Team members limited to specific properties can no longer do so, and OwnerRez support staff can't create credentials while working in your account.

Here's where the broader API work stands:

• Released: OAuth 2.1 authorization with read scopes and refresh tokens
• Released: Updated documentation with guidance for AI assistants and an OpenAPI specification
• Released: ETag support and improved pagination to reduce unnecessary requests
• Released: Automatic client registration for AI assistants using Client ID Metadata Documents (CIMD)
• Released: MCP server
• Coming soon: Command-line interface (CLI)
• Coming soon: Write actions through MCP

We're also building API endpoints for more data, including tasks and expenses. As those become available, they'll expand what you can do through the API, MCP server, and upcoming CLI.

Give it a try, and let us know here what you'd like to ask your OwnerRez data!

Seasonal Cancellation Policies are now available for Direct Bookings, Airbnb and Vrbo!

With that, we'll mark this request Released. Thanks to everyone for your continued participation in this thread. If you'd like to read more about Seasonal Cancellation Policies, you can do that by clicking here!

Hi everyone,

Important update on Google Hotels. As of today, the integration is officially in public beta. Anyone who wants in can opt in now. No waitlist, no approval step.

Google is pressing us again on inventory. For them to let us go fully live, the integration has to bring enough properties to be worth their while, and right now we're short of where they need us to be. If we don't close that gap soon, there's a real risk the door closes on the integration entirely, not just for new users.

So if you've been following this thread and thinking about Google Hotels, now's the time. We're no longer doing a gradual, case-by-case rollout. We need you to sign up and go live with us now.

Here's how to get started:
https://www.ownerrez.com/support/articles/google-hotels-setup-connecting 

This is still a beta, so you may run into rough edges. Please send any issues or questions to help@ownerrez.com and we'll jump on them as quick as we can.

A big thank you to everyone who's already been testing. You're the reason we've gotten this far. Let's get it over the finish line together.

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.

Appreciate you flagging this one! The upvote count at the top of the page is one of the biggest signals we use to decide what to build, so if this resonates with others you know, loop them in and have them add their vote.

Currently, users with Limited Staff access can view the Inbox for properties assigned to them, but cannot see the Communication History — the full email/message thread history across a guest's bookings.

This creates a real problem for teams where staff (not full admins) handle day-to-day guest communication: they can't see prior messages exchanged with a guest, so they end up replying without context — repeating questions already answered, missing details the guest already provided, or contradicting something already promised.

Requesting the ability to grant Limited Staff users read access to Communication History (even without full admin rights), so front-line staff can respond to guests with full context of the conversation history, without needing to be given full admin access to the account just for this one thing.

Too many tasks are being automatically created for 100+ properties. A toggle to turn off automatic task creation in Rezzy would be helpful.

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.

Our vacation rental permit requires all adult guests to sign a rental agreement.  We have it manually working in OwnerRez using custom fields and sending the link to each email we collect in the custom fields - but it is not formally supported and has a couple of challenges.  There have been recent form updates in the rental agreement which confuses guests to override the information that the booker initially fills in.  I would like to see a more formal approach to handle multiple renters being able to sign the rental agreement including automated way to send to multiple guests, disabling the bookers contact information so other guests updating their information do not override other details, etc.

This feature can't come fast enough.  Even better if it could be based on each season. 

Example: Booking Window on AirBNB = 100 days for off season, 30 days for CORE season, per property.

I wouldn't care if someone cancels during "shoulder season".

Hi, the OwnerRez amenity lists are built to try to support the common amenities that are included by the major listing channels.  Unfortunately, Airbnb, Vrbo, and Booking.com don't currently see the demand for a basketball hoop that you or I might. We won't be able to add that as an amenity until there is more recognition of it by the channels. They do occasionally add amenities.

Hi OwnerRez Team,

I wanted to reach out with a feature request that would be incredibly helpful for those of us managing extended winter stays and seasonal rentals through OwnerRez.

We understand that OwnerRez currently allows scheduled credit card payments with designated due dates. However, we would love to see similar functionality added for check payments.

For our extended winter rentals, we commonly structure payments as:

• First month’s rent, last month’s rent, and any applicable cleaning fees due at lease signing

• Monthly rent payments due on the 1st of each month thereafter

• Payments made via check rather than credit card

At the moment, because we cannot assign multiple scheduled check payments with individual due dates, the system instead displays the remaining reservation balance as due on a single date. This can create confusion for guests when the payment schedule shown during the acceptance process does not match the payment schedule outlined in their lease agreement.

It would be incredibly helpful if OwnerRez could allow us to manually create scheduled check payment installments, each with its own:

• Payment amount

• Due date

• Payment method designated as check

• Automated reminder email prior to the due date

• Ability to mark the payment as received once the check arrives

Ideally, these scheduled payments would also display clearly within the guest portal and reservation so the guest can see the same installment schedule that appears in their lease agreement.

As more vacation rental managers expand into winter rentals, mid-term stays, and other extended reservations, I think this would be a very useful addition for properties where monthly rent payments are collected outside of traditional credit card processing.

Thank you so much for considering this! We use OwnerRez extensively at Salt & Shine and would love to see more flexibility around extended-stay payment structures.

Best,

Hannah McLaughlin
Director of Operations
Salt & Shine Vacation Rentals

Right, it sounds like they're agreeing -- these LOS surcharges that they push do not work on Airbnb and booking.com.

Like I mentioned they're free to push them to us and surcharges with length of stay/number of nights criteria are fully supported by the OwnerRez API.

But if you want to price this way the only method that would work for Airbnb and booking (and all other channels as well) is to set your one night rate higher and then do a 2+ night LOS discount.

If you do that, you'll accomplish the same effect and it will work everywhere.

Chris, I sent them your question and got this in return: 

"Also, regarding OwnerRez Support's response about the premiums not being accepted on Airbnb, I wanted to mention that we don't offer length-of-stay pricing adjustments for Airbnb and Booking.com because they don't accept the inputs directly from PriceLabs. The property management system handles these changes, which is why this feature is available in PriceLabs. 

To answer that part of the question, if they want specific information from our engineering team, they're welcome to reach out to them directly. Based on what I know, this is handled directly by the channel managers or property management systems, not by us, so we may have limited information. 
I hope this helps. Please let us know if you have any questions.😊"

Not sure if it's coming down to semantics or if there's a genuine misalignment in what's possible. They do have other software partners that allow/accept the LOS premiums as well as discounts. https://help.pricelabs.co/portal/en/kb/articles/length-of-stay-pricing#Availability 

Add basketball hoop as a amenity in the amenity checklist!! 

Ahh you're looking for a length of stay premium, not a discount. This is not supported by many channels, for example Airbnb, so we have not included it in our standard fee type enumeration. How does Pricelabs handle the no Airbnb/Booking.com support question?

However, it is fully supported in a complex type surcharge -- PriceLabs could manage a series of complex surcharges with number of nights criteria through the API just the same as you can create them by hand.

That config, should they choose to implement, would work for channels that support it like Vrbo and direct bookings, and wouldn't work for Airbnb or Booking.com which have no LOS premium support.

Alternatively you could increase your rates to the one night amount and add a 2+ night LOS discount to achieve the same effect on all channels.

Hey Chris! Two different PL support staffers have confirmed via email that it will not work:

”If you’re looking to add a premium for 1-night stays, there is an additional limitation to be aware of: OwnerRez currently supports Length of Stay discount percentages below 0%, but Length of Stay premiums are not supported. This is a limitation on the OwnerRez side rather than PriceLabs.”

What if you put in say -10% instead of 10%? The error message seems like they're taking the sign literally instead of just normalizing to a discount.

Thanks for sharing this idea with the community! Feature requests with more support tend to move up our list faster, so if there's anyone else who'd want this too, point them to this thread and encourage an upvote.

If you're having a specific problem with configuring your Agreement to the built-in system, you can also open a support ticket for direct support with your account.