Latest Activity...
HI Sheila!
Since you're API connected to Vrbo, OwnerRez is in full control of the booking. So if you need to add additional charges based on the length of stay, such as for extra cleaning, you can add them to the charges in OwnerRez and then send the guest a request to the guest to pay for the additional charges. We have this support article that goes over changing charges: https://www.ownerrez.com/support/articles/changing-the-charges-for-a-quote#booking-charges
When it comes to other OTAs, it's hard to control the amount that's required at the time of booking. For Vrbo, it should respect the amount that's due at the time of booking that's been set in OwnerRez. But sites that are the merchant of record, like Airbnb, have their own settings, so you wouldn't be able to control what's due up front. You could set channels like Airbnb and Vrbo to request to book, but it still won't allow you to change how much is due up front. Airbnb would still be in control of how much is due, and you can't send quotes to Vrbo guests; they have to book on their site.
I use August locks (owned by YALE) and would also like to see Yale/August integration with OwnerRez.
I've been using Yale locks since 2019 originally through Rently. Now I'm doing it myself and running them all on the Yale App, 28 of them and it works great. It Also integrates with airbnb automatically so that saves me some time. I'm entering all the reservations from VRBO or my own website myself, which takes some keeping up with. I have OwnerRez set to generate the codes. Would love to see this integration in the future.
Hi Abby!
If you want to mark all messages in the inbox as read, you should be able to do so by going to the inbox and clicking the check box on the left-hand side at the very top of the message threads (right under the compose box). Once that's checked, all threads should be checked, and you'll see an open envelope that you can click and mark them all as read:
[This topic has been merged with another topic (Request for Separate Booking Window Lead-Time for Instant Bookings vs. Inquiries). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (Keep days within required lead time available, just not for instant booking)]
We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.
My contact info is info@galvestonrents.com. I would appreciate a dialog if you would regarding this.
Paul
I'm honestly surprised I can't find this feature being requested before...
I'd like a trigger that looks at any field OR custom field and allows us to write a rule:
The real world example for me is lock codes. I use a 3rd party lock software that populate a custom field once the code is set. Sometimes the code can take 20+ minutes to set. I currently have no method of setting a trigger to ONLY send a message once the actual code is set on the lock. I would like to set a trigger that says "If lock code = is known" then send message.
Known/is_known trigger could be used to customize so many things.
I'm looking for something similar. We reduce our management fee if people pay by check. Currently we are using the following workaround (explained by Ask Rezzy):
Discounts in OwnerRez are calculated as a percentage of rent or a fixed amount - they don't target a specific line item like a management fee. There's no built-in way to apply a discount only to the management fee while leaving rent untouched.
What you can do is create a negative surcharge (a surcharge with a negative dollar amount) in the Management Fee category. That would show up as a separate line item discount on the booking charges, distinct from rent. You'd configure it under Settings > Pricing > Surcharges > + Create Surcharge, pick the Management Fee category, and enter a negative fixed amount.
This negative surcharge reeks havok on our line item pivot because it still looks like a "discount" and technically it is a reduced management fee and the rent is not discounted. We would love the ability to set up a custom discount but have it apply to expenses rather than rent!
Hey Austin,
It's not that it's not a priority, it's that Vrbo does not provide us this information via the API. If / when they do, we will absolutely look into getting this added. I'm afraid it's just not possible right now.
We do have Automated Expenses on our roadmap which would help in this area. You can follow this Feature Request for updates:
https://www.ownerrez.com/forums/requests/pm--recurring-expenses
There's no ETA I can provide on Automated Expenses at this time, but it is very much on the dev roadmap.
Can we set our auto reviews/smart reviews for specific properties only, especially the new listings, so reviews are sent as soon as possible after guest checkout? I’d love to help build a strong review base quickly to get the new listings going.
I agree, this would be very helpful and it would not take much space in the DB and it should be an easy edit with minimal effort on the part of OwnerRez as you are just chaging the variable on how far back is displayed. It is a huge pain to try to determine past rates via looking up past bookings as you have to drill down on them to see simply the rate when there are other fees, taxes, etc.
It would be incredibly valuable to have write access to the Description and Accommodations Detail fields via the v2 API. Today these fields are read-only (and only available through the partnership-gated Listings endpoint), which blocks a lot of legitimate use cases for hosts managing their own accounts.
The use case driving this for me:
I manage 40+ short-term rental properties through OwnerRez. I'd like to run a small internal automation that refreshes the seasonal language in my listings on a weekly or monthly cadence — for example, swapping "cozy by the fire" language in January for "porch evenings on the Bourbon Trail" in July, while preserving every factual claim, amenity, and rule. The agent would read the current description, generate a seasonally-updated version, and write it back through OwnerRez so the changes sync to every channel I have connected (Airbnb, VRBO, Booking, direct site).
Without API write access, the only options are manual copy-paste across 80+ fields weekly (which won't get done), or building separate integrations against each channel's API (which isn't realistic for an independent host).
Other use cases I'd expect to be common:
Suggested scope for v1:
PATCH /v2/listings/{id} (or wherever appropriate) accepting description and accommodations_detail fieldsI understand listing content is sensitive and there are real concerns about API misuse (spammy edits, channel sync churn, etc.). Reasonable guardrails — rate limits, account-level toggles, partnership requirements for third-party apps but not for personal access tokens — would address most of those concerns.
Happy to be a beta tester if this gets prioritized. Thanks for considering.
— Brandon Farmer, Bourbon Rentals
Jennifer W How do I reach you??
Any way to have the guest balance and net financials just both display vs having to click each time?
Hi Megan W,
We will be adding a "Requirements" block to the booking overview with some upcoming design changes. Those changes are in testing at this time. Requirements will include Security Deposits and Rental Agreements in the mix. ID uploads will not be included in the first round of this work, but we do have a design outlined to get that included at a later date.
I'll mark this request as Planned with that in mind!
As for the Guest Balance / Net Financials, there are no plans to change those. They'll remain their own buttons.
Would like a dashboard to show booking data. Would be nice to have a current and adjustable to be forward looking dashboard showing booked amount, bookings, booked nights, ADR, Occupancy. and to filter by property. also be able to maybe bar graph show booking, revenue, etc by channel. Net revenue,
the reports dont always show the things easily and we have to cobble together a bunch of different data points.
Want to request booking over page have the following:
Financials section - it confirms security deposit but nothing about rental agreement and DL so I have to check that tab to ensure it's done.
Guest Balance/ Net Financials.
Don't like clicking back and forth on the buttons. Can they both just be listed right on the screen?
It would be useful to be able to tag sources and then use those tags in triggers, reports, etc. For example, tagging sources to indicate that it "provides only masked email address" or "MoR" or "Prohibits Same Day Booking". That way we could create triggers based on characteristics of the source. A simple tag could then make a source eligible (or not) for a trigger.
How will this be different than a Listing Source? Currently we put Owner Stays under their own Listing Source and then can exclude that source for reports and it also allows the owner (or owner guest) to be treated as a guest but with customized messaging, etc. In addition as a booking simply with a different source it flows to our integrated tech like Breezeway and Touch Stay for the rest of the team and guest experience.
Summary
OwnerRez has strong, fast messaging and booking design and data, but the current host workflow is too click-heavy and fragmented.
The most important actions are too hard to reach, the current Inbox is not fast enough for daily use, and communication is split in a way that makes solo-host operation harder than it should be.
I am requesting a redesign that makes the booking page, Inbox, and Activity Timeline faster, more customizable, and better suited to both solo hosts and teams.
Borrow ideas for this redesign from: Front, Missive, Help Scout, Hiver, Freshdesk, Outlook Shared Mailbox, and HubSpot Service Hub.
Why this matters
The host workflow should feel like a command center, not a records archive. Right now, common actions are buried in small far-removed menus, while less-used items are more visible, which adds unnecessary friction when replying to guests or changing a booking.
For a solo host, that means extra time and extra context switching every day.
Borrow ideas for this from: Front, Help Scout, Missive.
Unified inbox request
The Inbox should show all guest messages in one chronological flow, regardless of source. I should not have to choose a channel or source before reading or replying to a message.
Email, SMS, Airbnb, Booking.com, Vrbo, WhatsApp, and similar sources should appear in one stream, with source badges and optional filters available only for narrowing.
Borrow ideas for this from: Activity Timeline behavior, Front, Missive, Help Scout.
Native email handling
Email replies from guests should come into OwnerRez as part of the same unified conversation view, so I can read and reply inside OwnerRez instead of switching to my computer, phone, tablet, or separate email client. The current behavior should move toward true inbound email threads inside the OwnerRez UX.
Borrow ideas for this from: Front, Missive, Outlook Shared Mailbox, Help Scout.
1) Left-nav wireframe
Goal: make the main work surfaces more obvious and easy to reach.
Desired streamlining of left navigation
Timeline should be near the top, because it is a daily work surface.
Bookings should open into a working view, not just a record view.
Solo-host preset should simplify the nav.
Team preset should keep collaboration tools visible.
Borrow ideas from
Front: queue-first layout and operational workflow.
Hiver: lightweight workflow inside a familiar environment.
Missive: conversation-centered navigation.
2) Inbox wireframe
Goal: make the Inbox a fast queue, not a place where the host gets lost.
Proposed inbox layout
Left column: filters, saved views, states, channels, urgency.
Center column: one chronological message queue across all sources.
Right panel: guest context, booking context, recent activity, quick actions.
Top bar: search, sort, assign, snooze, template, bulk actions.
Desired behavior
No required source selection before reading a message.
One click from inbox row to full Timeline.
Clear “waiting on guest,” “waiting on host,” and “urgent” states.
Easy access to templates and quick replies.
Collision warning if another staff member is already acting on the same conversation.
Borrow ideas from
Front: assignment, shared drafts, queue management.
Missive: internal notes and threaded collaboration.
Help Scout: clean customer context and simple replies.
Freshdesk: AI triage and escalation.
Hiver: collision detection and shared inbox discipline.
3) Booking-page wireframe
Goal: reduce clicks for the actions hosts use most.
Proposed booking page layout
Main center panel: booking summary and Activity Timeline.
Right-side action rail: message guest, edit booking, move dates, add charge, refund, mark paid, notes, tasks.
Top pinned actions: the host can choose and reorder the 5 to 8 actions used most.
Secondary actions live in easily-reached, expandable menus.
Desired behavior
Most-used actions should be visible first.
Hosts should be able to pin, hide, reorder, or group actions.
The page should be customizable by host preference or role.
The Activity Timeline should be available without detours.
Borrow ideas from
Help Scout: simple workflow and clear context.
Front: persistent action area and operational speed.
Missive: reply and act without leaving the thread.
Hiver: configurable workflow inside a familiar interface.
4) Activity Timeline wireframe
Goal: make the Timeline the fastest place to work a booking.
Proposed Timeline layout
Center panel: chronological activity feed.
Composer attached directly to the timeline.
Right panel: booking data, guest data, property data, charges, tasks.
Quick actions near the composer.
Badges for message source, due items, and status changes.
Desired behavior
Timeline should not feel hidden or like a deprecated dead end.
It should be the primary working surface for communication and booking context.
If the Timeline is retired, the replacement must preserve the same functionality, accessibility, speed and density.
The Timeline should remain the single place where all sources can be seen together in time order.
Borrow ideas from
Missive: thread-first collaboration.
Front: timeline plus action workflow.
Help Scout: clarity and low-friction customer context.
5) Solo-host mode
Goal: optimize for the person doing everything alone.
Solo-host priorities
Fewer clicks.
More visible quick actions.
Strong template access.
Fast booking edits.
Strong Timeline access.
Simple state indicators.
Less emphasis on staff routing.
Solo-host preset should
Promote reply, change booking, add charge, and task completion.
Reduce collaboration clutter.
Use a compact, action-oriented layout.
Support keyboard shortcuts and fast search.
Borrow ideas from
Help Scout: simple, uncluttered workflow.
Front: quick operational actions.
Missive: fast reply flow.
Freshdesk: AI-assisted triage.
6) Team mode
Goal: support multiple staff without slowing solo users down.
Team priorities
Ownership.
Assignment.
Collision detection.
Internal notes.
Shared drafts.
Queue routing.
Escalation rules.
Team preset should
Show who owns each item.
Prevent duplicate replies.
Support handoffs cleanly.
Keep collaboration inside the thread.
Borrow ideas from
Front: team assignment and operational control.
Missive: internal chat and shared drafts.
Hiver: shared inbox routing.
Freshdesk: escalation and AI triage.
7) Color system wireframe
Goal: use a full-color palette for functional signaling, not decoration.
Proposed color rules
Green should not carry the whole interface.
Use color for state, urgency, channel, payment status, and task type.
Keep the base UI neutral so text remains readable.
Use the same color meaning everywhere.
Why this helps
Faster scanning.
Easier prioritization.
Better recognition of booking state.
Less effort for hosts who process many messages each day.
Borrow ideas from
HubSpot Service Hub: status-driven visual organization.
Freshdesk: categorized workflow cues.
Front: readable operational UI.
Help Scout: clean presentation with functional signals.
Conclusion
OwnerRez's UX should adapt to how hosts actually work, not to how its developers view the product should be built. My core request is for a customizable, streamlined host workflow, not just prettier screens.
Can’t you already just request to be included directly with Marriott?
Hi Bri, We have over 150 listings, and most are luxury villas and condominiums, we would love to be in the Beta.
After discussion, we don't plan to roll this out as a beta.
The work we're doing is building out the API endpoints that our dynamic pricing partners write to. Once those are in place, it's on the partner to integrate from their side and start sending data through.
The work we're doing on our side will be heading into testing very soon!
On my VRBO PPB bookings, the 5% commission VRBO bills me each month doesn't appear in Line Item Pivot, Listing Site Fees, Net, or any other automated OR report. Only the ~2.9% Stripe fee is captured.
Four April bookings, $224.90 of VRBO commission, invisible to OR.
The existing feature request says the math isn't simple. The math is **0.05 × (Gross − Taxes)**. That's it. Calling that "not simple math" doesn't pass a smell test.
The manual VRBO Commission File Import isn't an acceptable workaround — it depends on VRBO publishing the CSV days into the following month (so owner statements wait), it has its own import-failure bug history, and a manual monthly step that silently corrupts statements when forgotten isn't a fix. Airbnb host fees auto-capture per booking with zero intervention. VRBO should too.
In the time that thread's been open, OR has shipped Rezzy AI, v2 API expansion, and integrations with a long list of niche channels.
What's the rationale for deprioritizing this below those? Is it on the roadmap?
This is where I am at so far. It is heavily based on some of my logic but soon there will be a way to configure things. I can take data from OwnerRez and send into Xero
Definitely would love to see this! Also would love to see the hero appear with the date search widget in the middle like it does for multi-property. Not sure if there is a workaround for that?
I’m tired of waiting. I had a call this morning for another option.
Any update on when this might be available? We've been waiting for years!!