Latest Activity...
We have 50 plus properties and so writing and keeping up with all the descriptions is a lot of work.
Something that would really help us would be the ability to include field codes in these descriptions.
For example for all the Property Headlines we could set up:
{PPUBNAME} | {PBEDS} Bedroom, {PBATHS} Bath = Casa Breeze | 5 Bedroom, 6 Bathroom
Or for long and short descriptions we could have a template that said:
Welcome to {PPUBNAME} a {PBEDS} bedroom, {PBATHS} bathroom home in the world class Reserva Conchal Gold and Beach Resort in Guanacaste Costa Rica.
The majority of our property descriptions are the same because all our homes are located within the same resort community so they share the same location and amenities. Being able to incorporate Field Codes (and custom field codes) would make generating these property descriptions so much faster and easier to maintain as they would auto update if we made changed to any of the fields.
I use triggers to offer gap day discounts in an escalating fashion (10% 2 weeks out, 30% 1 week out 50% a couple days out). I’d like to be able to skip the 10/30 if the 50 has already been sent so there aren’t mixed messages….
A way to apply the same change to a bunch of properties or all enabled properties.
For example say I want to add the same text to the exact same field on a handful of properties, e.g. put the exact same information under "Enhanced Cleaning Practices" for a bunch of properties.
It would be great if there was a way to mass-edit / mass-change something on multiple / all properties, without affecting any other parts of the listings.
I've just been going through each one and copy-and-pasting the info but that gets time-consuming.
Sloanish, If I created a tool that integrates with ownerez and your thermostat would you buy it? So you don't have to wait for the zapier integration to happen?
I could potentially help you with this as I am a programmer. Does this need to be done by ownerrez for you do find where your traffic is coming from?
I have not. Hoping those badass programers at OR hop on this sooner rather than later.
Have you figured out a solution to this yet?
There have been plans to integrate with Zapier, which would provide some of these capabilities, but we try not to give ETAs as software companies are infamous for not meeting them and that just annoys people.
We do have an integration with DACK, which comes with some thermostat integration capabilities:
https://www.ownerrez.com/support/articles/DACK
Give them a look!
I just did this using IFTTT. It was super easy; I have an Ecobee thermostadt.
I set up a template and a trigger in OR that sends an email to IFTTT, based on certain conditions (summer season and no one stayed in the place the night before).
This email triggers IFTTT to turn the Ecobee thermostadt to a certain temperature and Hold until the next scheduled transition.
This way, I can set the AC to kick on a few hours prior to a guest's arrival, so they don't arrive to a hot place.
Does the product need to integrate with OR? If so, why?
I wanted to vote for this.
I have Bayweb thermostats which were the only ones available way back when.
I will buy whatever OR decides to integrate with.
OR?
Arrive and Thriv... have you reached out to Breezeway and offered to pay them to work on the integration? Wondering what they said. 🤠
Hey has ownerrez made any committments to integrate with the thermostat yet?
I guess market dependent. In our market too much fraud so renter prefer to pay by CC. As far as credit card fees - cost of doing business and tax deductible. Or just build them into your rates.
Often enough for it to be an inconvenience. I send out an offer for a discounted night if I have gap nights. Most of my business is regional at this house; it's easy for people to extend when they are driving home.
How often do you face these issue for extended stays? Is it frequent?
Can't wait ! Thank you
Does this have to be sent through ownerrez? Why can't you send automated message through Airbnb scheduled message?
That's great - thank you very much, Paul!
Quick update, guys.... We have been in development for a while on updating custom fields so that there is a "file upload" type of field. This will allow you to request an ID (or other types of files or photos) when the guest is booking or when signing the RA after booking on a channel. Basically, anywhere you use custom fields to collect guest information, you'll be able to get files. This is most of the way through development and undergoing some testing.
What we need is
Send Email_Trash_Template to guest where guest is at property_ID and day_of_the_week is Tuesday.
Thank you, but OwnerRez personnel are only human, and a single request in this thread for an update gets easily lost amidst a whole series of discussions on third party products.
There are other forums on OR where the third party discussions can continue and allow this thread to remain for what's its meant for. Please.
How are you liking using clicksend? Is it effective for you?
Have you started using clicksend yet? I'm curious how you like it?
I sense your frustration. I don’t think that business owners discussing workarounds is a bad use for this forum, because every time a topic is added it boosts the visibility of the topic even further. OR knows that this is a very hotly requested feature. I think seeing that there are third partner services could encourage an API integration with the most effective ones. While that’s obviously not a native solution, I think it makes it clear to the powers that be that this topic is quite important to their users. I agree that an update from OR would be very helpful. But let’s keep civil among the operators. We’re all here to learn from and support each other.
Please STOP hijacking this thread with discussion of third party products!
This thread is in the Features Request forum, and these discussions about third party products obscure the repeated requests that have been made to OwnerRez for an update on progress for this most-popular requested feature to be fully integrated into OwnerRez's booking process.
Please move these third-party discussions to another forum.
And OwnerRez — after 8 months, we're all still waiting for an update.
The last I heard from Ken is that there is no update. But no update is not possible. The update is either: A). We stopped working on it, or B) We're working on it, and this where progress is at.
If the update is A, would you please inform us why, and will you resume working on it, and when?
If the update is B, would you please inform us approximately when we should expect this to be available?
Thank you very much!
We signed up for it as well. It looks fantastic. I could use a tutorial on how to set up a static link. Any suggestions? I’m still waiting on a response about some help from them in setting up the link.
Hey Chris,
Any updates on ID collection?
TIA,
Wayne
Hello, I wanted to thank the team for adding the "bad review" feature, where the system will wait until the last moments to review a guest with whom we have had a bad experience.
To ensure that the review goes through, OwnerRez has set the time to submit such review, 20 minutes before since otherwise an error may prevent it from posting. However, this greatly increases the likelihood that we are retaliated against since this time period is plenty for the person to see the email that they got a review and craft their response.
If this is shortened to 2 minutes, then the person that wants to leave us a bad review in return has 2 minutes to see the email, open the link, write everything down, rate the stars and then submit in time, making it highly unlikely they will succeed.
The reasoning from OwnerRez is that by giving 20 minutes for the review to be posted, if there is a system-communication failure, there are 19 minutes left to retry until the review is posted. However, this may point towards a misunderstanding of our main concern as hosts. WE DO NOT WANT TO RISK the retaliation. We would in fact prefer to NOT leave a review if it means that we are opening ourselves up to being retaliated against. Our business is hurt when we do get a bad review.
Therefore, we need to choose between assuming two risks.
a) Shortening the time to 2 minutes, risking our review not posting and seriously minimizing the probability of being retaliated against.
b) Giving 20 minutes in the middle of the day, where most people usually are on their phones, to get their email notification that they were reviewed and have the chance to hit us back.
The worst case scenario is not our review not posting, it is being retaliated against. For those reasons, scenario a seems to be preferrable to b.
Or if anything, just add a third option to "post last minute" instead of waiting 20. Personally, and as much as I appreciate the feature, I don't feel comfortable using the 20 minute buffer.