Feature Requests

Sort by

• Newest Reply
• Newest Topic

This is a request that should be made of Stessa. OR has an open API and this integration would benefit STESSAs business model. I would use this but I would much prefer a wholistic approach to a accounting solution. I have several suggestions and it would be great if OR would hold a virtual user’s forum to set a course for an accounting solution that aligns with ORs business model and allows users to continue to scale their business in OR.

I am a financial professional and could add a lot of input to this discussion and I am sure there are a lot of other users that could do the same. A solid accounting solution could really differentiate OR.

Further, there are several requests on this forum relating to accounting and or QuickBooks, and if they were all consolidated into one, I am sure this would be one of the highest vote getting issues. Can I request OR to consolidate these all into one, and as mentioned above, please create some sort of organized discussion with everybody involved. 

I am going to open a new ticket, called Fix Accounting/Quickbooks - develop Roadmap , and ask that OR group all the accounting related issues and votes into this one issue and prioritize developing a roadmap

Ken,

Thanks for the quick response. Maybe I’m not understanding the current form correctly. On the current form, when the guests submit the contact details form, it takes them to the contact signature page. In cases where we don’t need the rental contract this is confusing for the guest. Also, the overall messaging on the page could be simplified just for contact information gathering. Does that make sense?

right now there’s several instances, many times after check-in, where we request to guests email for the database and we have to wait for them to reply on Airbnb and then we have to copy and paste it into the CRM.

ideally, we would like to create a workflow that when guests make a reservation through Airbnb, we send them a template message did ask them to submit their email for future communications in for the sharing of house, manual recommendations, etc. which will allow us to regularly capture more emails.

Thanks Manel

I would also like to see tags for items/surcharges that are added to a booking.   For example if someone adds a hot tub or pool heat the booking would have the designated tag for those items added to the booking.   This would then allow for triggered communications (emails and sms) based on the tag.  IE I could send a message to the bookings that have a HOT TUB tag on the day of arrival a reminder about hot tub rules and information on how to unlock it.

We already do collect real email addresses from Airbnb guests using that form, so I'm not sure what the purpose here is.

Yes on VRBO native messaging -- which they say they are working on; I understand this is a high priority for lot of people, but it's not a deal-breaker for my business. For me, OR and hospitable (the old smartbnb) have been the twin pillars of my tech stack for years.  No one software checks all the boxes for me.

As for an app, I may be in the minority, but I love the progressive web app because it has the exact same functionality as the desktop version. Notifications would be nice, though. But a stripped-down android app mainly for notifications might be more trouble than it's worth. I don't feel that strongly about notifications, but I get it that it's a big deal for others.

Not sure why it would have been erroring on actual bookings and not just blocks without that filter, but as soon as my next booking comes in... I'll let you know if the Zap works normally or not!

Aha! That makes sense, and explains why I couldn't identify that ID from anywhere. If that's true, than the error should go away with the filter on `is_block`.  

Correct -- I'm currently on version 21 of the Zap (Lord have mercy!) and that's the one that's published and in use. 

In case it helps you dig into it as well, the Zapier support reply did state this as to that number that appears to be a Guest ID in the error I receive:

--

"I can explain the guest ID that you're seeing. Every step in a Zap has a unique ID number. So the number 181738969 is the step ID number of the trigger in your Zap:
 When the trigger comes back empty, there's a placeholder value which is a combination of the step ID and the value it's looking for surrounded by curly brackets. In this case, it would look like {{181738969__guest_id}}. Step 2 of your Zap is taking the step ID and using it in place of the guest ID.
 
The root cause of this is the fact new data coming in from the OwnerRez trigger is not including the guest ID. I have created a bug report and have passed along this information to OwnerRez. Zapier works as quickly as possible to fix bugs once they are identified; however, due to the nature of bugs we are not able to provide an ETA for if and when a solution will be implemented. I have added your email address to the list of impacted users. Once a fix has been implemented, we will send you an email letting you know you can try to use this feature again."

That looks right. I wonder if they are automatically sending some other ID when there is no guest ID in the case of a block. If that is true, than the error should only occur on Blocked Off Time, so adding the filter will eliminate it.

I checked our logs for the past week, and I do see that your Zap is requesting that same non-existent Guest ID quite often. Can you make sure you have published the most recent version of your Zap just to make sure there are no changes left in Draft?

It's pulling the Guest ID field from Step 1 (Booking created in OwnerRez):

Sorry Alece, I hadn't seen your last screenshot.

That error message is indeed coming from OwnerRez, and it means that the Guest ID you are attempting to look up could not be found in OwnerRez. I did a quick check on that ID (181738969) and indeed there is no Guest in your account with that ID. I suspect that some other ID is getting sent to the Guest Lookup action. Can you post a screenshot of the Guest Lookup action in your Zap showing the arguments passed to it?

Perhaps the example the Zapier support staff sent was (mistakenly) a block rather than a booking, so I've gone ahead and added the filter as that's a huge help anyway. BUT the Zap does not work and gets hung up on the same error message I sent you in a previous comment here. Same error message on every new booking that comes in. 

Hi Alece,

Yep. Zapier sent us that ticket and I responded to them.

What you are seeing is an Owner Block trigger. In our backend, Bookings and Owner Blocks are the same structure, so both can fire zap triggers (not to mention other things within OwnerRez). We are going to enhance the integration to include an option on the trigger for whether you want it to fire for blocks or no, but in the mean time, add a Zapier Filter action between your Trigger and your Guest Lookup. Tell it to continue only if  "Is Block" is false:

Just received this back from Zapier support: "The root cause of this is the fact new data coming in from the OwnerRez trigger is not including the guest ID. I have created a bug report and have passed along this information to OwnerRez."

Hopefully this can be corrected quickly between OR and Zapier so that we can effectively make use of this integration!

You already can.  :-)

Couldn't agree more. 

A unified inbox for all communications and a mobile app (feature-request) would be essential.

I am in need of this feature as well.  Has this feature been added as of yet?

AirBnB requires guests to provide Mobile numbers and for 99% of the guests the number provided is their mobile. Is there a system limitation reason that this can't be recorded as the "mobile" instead of 'Home' number.

This would be also be helpful for VRBO and Booking.com as well since the number provided in these platforms is almost in all cases the mobile number.

If there is a system limitation that "Home" is the default number, can that be changed as most people are mobile centric today

Thanks

Please create a simplified version of the "Booking Clean-up" webform to ask guests for emails and have them automatically populate the contact form. This can be used with AirBnB to automate the capture of guests email addresses

+1 Agree

No, you would set up a second, separate Book Now widget for this purpose.

Will this not affect the booking widget already being used on the site? 

The ability to have tick or cross (checkboxes) or radio buttons (yes or no) as well as current text field boxes.

So allow people to check things to allow that to be yes or no, either or that would be translatable to action instead or as well as a text field. 

Hi there OwnerRez 

We love that you have implemented message status colors,  really this is awesome helps a lot to see what is going on. 

Gray for will not run 

Red will not Run

Green sent on 

Please would it be possible to do color for Amber / Orange for "will be sent" this would be helpful just to see which are going to run easier

Thank you for explaining it better than I could!

I'm all over the place checking for messages, notifications. I just now got an email notification that a guest had texted to the OR sms number about 15 mins ago! (which I don't use other than to tell the guest to check their email and don't reply to this # it is an automated message. To please use my cell#) I'm thinking of dropping the sms feature all together because guests don't read not to reply to it.

If I did not see the email notification as quickly as I did, my guest could have been waiting hours for a response for help because I would not have seen the sms message since OR inbox doesn't really work for me visually as well so I don't really check it. I rely on email notifications, my GV #, Airbnb and VRBO's lousy app.

There actually are plans to add push notifications to the web app - Google Apple has announced this will be added to versions of Chrome iOS to make this possible.

Agreed!

Better comms and a good app would be very nice indeed. 

Hey Ken, Justus from OzarkStays here. My retort regarding the usefulness of a unified inbox is that we desperately need a central thread to keep up with all of the comms flowing throw OwnerRez. Let me paint a picture for you of what all is going on in my account.

We’ve got the following as far as connected accounts:

1. ABB & VRBO for our PM clients
2. My personal ABB & VRBO account
3. My business partner’s personal ABB

Then you have email vs channel messages. It’s a lot of moving parts! Yes I get email alerts but the notifications on this Outlook app are heinously bad. And I can’t be logged in to more than one OTA account at a time on my phone via their native apps. I can bounce back and forth between the email and CRM inbox to make sure I don’t miss anything, but I shouldn’t have to.

I want two simple things:

1. A single inbox for all notifications and messages
2. An app with push notifications

I’m not sure why in 2023 we don’t already have a true ios app for OwnerRez and keep pushing this web app as a suitable alternative. (Because if it has some kind of capability to push notifications to me, that’s news)

The unified inbox is the same concept as the channel manager, we all want it centralized. OR is behind the 8 ball on this as compared to other PMS competitors. As it stands, I’m having to shop around services like RueBaRue to make up for OR’s shortcomings in centralizing comms. I appreciate that there are integrations galore, but I would rather not have to approach this in such a bolt-on type way and have 12 different tech stack subscriptions.

I love OR and it's robust features, reliability and everything in between and use it seamlessly across 6 properties.  VRBO messaging, to me, is the ONLY thing it's missing.

That said, I use Hospitable for the VRBO messaging since VRBO app is TERRIBLE (really, just a terrible platform altogether but I digress...) but I was wondering if OR has pursued an API relationship with Hospitable that might be faster than working with VRBO.

The thinking/flow would be something like this:

VRBO message from guest >> Hospitable >> OR CRM

It might not be as fast as a direct API connection between VRBO and OR but it would do the trick.

Has that been explored as potential workaround?

Yeah, it's a big problem. I'm looking at paying an additional $500/mo for Hospitable's inbox or switching to Guesty.