Settings and activity
261 results found
-
6 votes
Keith
supported this idea
·
-
3 votes
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment Keith
commented
Agreed. Historical data is even required by law in many jurisdictions.
Keith
supported this idea
·
-
6 votesKeith
supported this idea
·
-
4 votes
An error occurred while saving the comment Keith
commented
This already exists
Keith
supported this idea
·
-
10 votesKeith
supported this idea
·
-
5 votes
An error occurred while saving the comment Keith
commented
When you close airbnb leds, it marks the lead in airbnb as declined, I think .
I worry that this will harm our search ranking since they downgrade listings with lots of declines on them.
Keith
supported this idea
·
-
7 votes
An error occurred while saving the comment Keith
commented
I'm surprised there aren't 30 of these requests...maybe there are.
but I've been asking for this for many years.
it's tedious to add and modify taxes on a per listing basis.
Taxes change for a city, we should be able to apply that change to all the listings in that city.
same for all the fees. and we can't currently even modify them. we can only delete and recreate them.
Another confusion. the "doesn't apply to stays longer than" ONLY applies to Airbnb.
so if we have a occupancy tax that doesn't apply to 30 day stays, 31 day airbnb bookings aren't taxed, but booking.com 30 day stays and direct bookings are taxed.
This makes no sense.
Keith
supported this idea
·
-
5 votes
An error occurred while saving the comment Keith
commented
I think what's wanting here is a "bulk send message" that used variable substitution.
Instead of a template/trigger, .. or maybe yes a template, but we want to be able to "send to multiple guests" and then check off the guests to receive the message.
I wouldn't want to make a whole trigger just to send a message about a hurricane, but I would like to send one message about a hurricane to multiple guests who might be impacted.
Keith
supported this idea
·
-
17 votes
An error occurred while saving the comment Keith
commented
This has languished for a couple years? anything going to be done here?
It is kind of ridiculous that we have to have duplicate triggers based on the mechanism the message will be delivered.
Ideally we can configure the outcome:
Direct ONLY
Email ONLY
Direct AND Email
Direct if available, email otherwise
Email if available, direct otherwise(these last 2 should detect if it's a anonymized channel email address and treat those as "no email" since they're effectively the same thing as direct and may end up with duplicate messages in the inbox).
Keith
supported this idea
·
-
8 votesKeith
supported this idea
·
-
10 votes
An error occurred while saving the comment Keith
commented
Agreed. Ideally for any item, we should be able to choose "same for all channel's or unique per channel"
for new channels it should default to the main one.
-
2 votes
An error occurred while saving the comment Keith
commented
I think the channels have different listing name lengths and other criteria, so this would be nice so we can target guests who are more accustomed to specific channels.
It also helps fool google so guests can't just google the name and book through some other channel.
-
36 votes
An error occurred while saving the comment Keith
commented
My guess is that hostfully's partnership with jervis (branded hostfully devices) is going to be the preferred method here, especially given hostuflly will make extra money on this rather than the remotelock integration for which they make nothing.
I'm happy with jervis, but not happy that I'll soon be paying hostfully extra money for no added value. but at least it works well.
-
9 votes
An error occurred while saving the comment Keith
commented
Moreso than that, we should be able to just check/uncheck the triggers to add that property to that trigger.
Keith
supported this idea
·
-
9 votesKeith
supported this idea
·
-
9 votes
An error occurred while saving the comment Keith
commented
This is a good idea. I'd like the same for reviews.
Otherwise repeat guests keep getting the same review over and over.
Keith
supported this idea
·
-
12 votes
An error occurred while saving the comment Keith
commented
this is especially problematic given it's not whitelabeled.
there are many many holes in whitelabeling .. this whole whitelabel system needs to be polished.
An error occurred while saving the comment Keith
commented
Either remove or whitelabel/brand these
Keith
supported this idea
·
-
8 votesKeith
supported this idea
·
-
27 votes
An error occurred while saving the comment Keith
commented
I think this is generally a good idea, but I don't think these transactions will be protected by 3D secure liability shift which we require on all our transactions to avoid chargebacks.
If they are protected then we definitely would like to auto process the balance, but I'm pretty sure the guest needs to confirm the payment to have this protection.
This would be a nice complex condition to add to triggers. "active dates"
This would also allow sending messages only relevant certain dates of the year.. like not sending pool hours in winter time, etc.