Latest Activity...
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:
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:
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.
I fully agree!
I've been watching this topic go no where for a while. The fact that so many other management systems DO HAVE Inboxing for VRBO, etc. makes me wonder about pointing the finger at VRBO as the route of the problem.
I am considering dropping OR because of the Inbox difficulties and up charges to get basic reporting & SMS. I don't like the extra charges for the basics, it feels dishonest.
Craig
There are plans to develop what's commonly referred to as a "unified inbox", but there are a very great number of pieces to that, as well as serious support concerns if we're handling all your email in both directions. I'm not personally convinced that function would be as useful as many of our clients believe that it would be, but we'll find out - it will happen eventually for sure.
As far as other systems that "integrate" with Vrbo internal messaging, our understanding is that they do this unofficially by what amounts to screen-scraping. Not only is this inherently unreliable, as Vrbo could change their screens at any time, it is also fundamentally more complex. Since Vrbo has announced their willingness to set up a proper integration designed for that purpose some years ago, it makes much more sense to just use that and do it right.
Of course, nobody anticipated that it would take as long as it has. But at any given time, it's "a few more months". So we continue to wait for it. Hopefully not too much longer!
I moved from Guesty because of all glitches and poor support, I'm happy with OR overall and the support is superior, but really do miss guesty's inbox, the ability to sms and auto message to VRBO at no extra charge.
I rarely use OR inbox unfortunately it just doesnt do what I need, I have Google voice # and get my notifications there, and then check my email, Airbnb and VRBO and answer directly in their apps. Or my GV#, I hate that I'm paying extra money to text a guest just to check their email and not to respond to the sms auto number. I feel it's all over the place and not truly unified.
Hey Joel --
Since I shared my previous Zap links, here's an update. I consolidated things into one Zap (combining those actions as you described them):
Create contact in OpenPhone with when booking created in OwnerRez »
It's still not 100% correct, as something with the Guest Lookup continues to error out (though it works fine when testing). For some reason, on every new booking, it sends an error that says, "Guest:Id:181738969 not found". Literally the same ID number every single time -- which isn't even correlated to any guest or booking I have. I cannot figure out where it's pulling that number from, and don't know if there's an issue with the Zap trigger or what. (Have you successfully used Guest Lookup on other Zaps??)
Agree, there are several PM systems that surface VRBO messaging and have for some time. Seems like there's a distinction between the systems I'm aware of that do this are not Integrated partners, but rather, VRBO natively invoices the customers versus how OwnerRez is integrated and we invoice the users. Might be related. But, Hospitable, iGMS, Guesty for Hosts, and some free tools I've used are pulling it off. Clearly a agap.
It does seem strange that with OR status as an Elite connectivity partner with VRBO cant get it but Guesty, Hostfully, etc... have it - unless they are kludging it together in some way?
Just spitballing a possible workaround, but I get VRBO messages sent to me via email, what if there was an OwnerRez email inbox I could forward those emails to and then they would be added to my CRM inbox. This would actually be great for other non-integrated message sources as well to get everything added to one unified OwnerRez inbox. I'm new to OwnerRez so maybe this is something that has been mentioned already.
