Feature Requests

Sort by

• Newest Reply
• Newest Topic

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!!

Hi There - I often have Snowbirds who are at our place for longer periods. Sometimes with Pets. I do charge a "Pet Fee" but I am also wanting to be able to upcharge for Length of Stays accordingly.

For instance, I had a Snowbird last year, well 2 actually I think one was for 67 days and the other was 28. They both booked through VRBO instantly. I charge a flat rate for cleaning and sometimes I have different cleaners some charge an extra $100 some charge an extra $200 for stays of 28 days. Some charge extra for pet cleaning and some don't.

Also, I would like to have more of a deposit if it is booked through a channel. If it comes through on a quote from my Website it is easy to change it although I would have to manually changed the rental agreement maybe? 

If the Channel doesn't allow then maybe a message to booker to call for exact quote.?

Anyway, I think this would be very useful for us!

Thanks,

Sheila

Thanks for this suggestion! This is a great feature request that would definitely improve the guest experience, especially for advance bookings where credit cards may expire before the final payment is due.

Currently, OwnerRez does have field codes for displaying the last 4 digits of credit cards in payment email templates (such as {PAYCCNUM} for payment receipts), but these only work for completed payment transactions. There isn't currently a field code that shows the last 4 digits of the credit card that's on file for upcoming scheduled payments or security deposits.

One possible workaround that may help in some cases today is the {BBACT} field code. This can be added to booking templates and includes booking payment activity history, including the card type (Visa, Mastercard, Amex, etc.) and the last 4 digits used on prior payments. While it doesn't specifically expose the card tied to a future scheduled payment, it may still provide guests with enough information to recognize which card they previously used and determine whether they need to update it.

What you can do today:

1. You can use the Request New Credit Card feature to send guests a secure link to update their payment information if needed. This can be done from Booking > Transactions > Request > Request New Credit Card.

2. You can create custom reminder emails using Email Templates and Triggers to proactively remind guests before scheduled payments to ensure their card on file is still valid.

Your suggestion would enhance this by: - Allowing guests to see the last 4 digits in reminder emails so they know which card will be charged - Displaying it on the payment form itself so guests can verify before submitting - Reducing payment failures due to expired cards

This is definitely worth considering as it would reduce friction for both hosts and guests. 

Guests should be able to see the last 4 digits of the credit card on file for their scheduled final payment and security deposit by having the ability to tag that in a template email and/or using including the last 4 in the form for their final payment. Guests would then know if they need to change their credit card on file. This is especially nice for guests that make reservations far in advance.

[This topic has been merged with another topic (PM - Recurring Expenses). All unique votes have also been merged.]

[Another topic was closed as a duplicate of this topic (Reoccurring Owner Expenses)]

I have some reoccurring monthly owner expenses. I've manually duplicated them through the rest of the year, but we are adding more reoccurring charges as time goes on. Can you add a feature to duplicate these types of expenses rather than manually create them?

Voting for this. Would be great to have an exportable list of triggers and templates that we could then audit with AI

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.

[This topic has been merged with another topic (Due Dates on Tasks). All unique votes have also been merged.]

[Another topic was closed as a duplicate of this topic (Add Dates to Tasks - Scheduled For and/or Due By)]

We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.

[This topic has been merged with another topic (Granular User Permissions for Department-Based Access). All unique votes have also been merged.]

[Another topic was closed as a duplicate of this topic (PM Staff access)]

[This topic has been merged with another topic (Granular User Permissions for Department-Based Access). All unique votes have also been merged.]

[Another topic was closed as a duplicate of this topic (User Setup Options)]

Would love to have more flexibility for user setups. I have a few different people that do different items so giving them full access is just not ideal.