Settings and activity
24 results found
-
2 votes
Phung Dang shared this idea ·
-
2 votes
-
2 votes
-
2 votes
We'll be looking into it - if we can reproduce, this is more a bug than a feature request.
-
5 votes
-
1 vote
-
4 votes
-
3 votes
-
6 votes
-
7 votes
-
1 vote
-
41 votes
An error occurred while saving the comment -
5 votes
-
6 votes
An error occurred while saving the comment On the property setting page, there's a setting called "Only check-in On," which allows PMs to specify certain days of the week for check-ins. However, this setting is easily overridden on Pricing tab when updating pricing by dragging dates for a certain period, or when a dynamic pricing tool updates price-only to Hostfully.
To address this, I would like to request the following enhancements:
- Maintain "Only check-in On" Setting: Ensure that the "Only check-in On" setting is preserved and not overridden when updating prices manually for multiple days or when using a dynamic pricing tool.
- Enhanced Check-in/Check-out Restrictions: Provide the ability to set up check-in and check-out restrictions on the master calendar for multiple days and multiple properties. Additionally, offer an option to update check-in and check-out days only for certain days of the week.
-
8 votes
An error occurred while saving the comment Current Behavior:
When filtering available properties based on a certain period, the calendar shows all properties that have no leads or blocks on the requested dates. However, when I choose to email the property list, fewer or no properties show up in the email. This is because the properties might have other availability restrictions such as minimum stay, turnover rules, booking lead time, and check-in or check-out restrictions.
Request:
I would like to request that the calendar filter take into account all property availability restriction rules. This way, the filtered list will be accurate and match the properties shown in the available property list email, preventing any confusion when no properties appear in the list.
-
26 votes
An error occurred while saving the comment Property managers often encounter last-minute bookings where guests check in on the same day the booking is made. In such cases, there are typically two triggers:
1/ An instant trigger for the event of NEW_BOOKING,
2/ A time-based event trigger for BEFORE_STAY_STARTS, which allows to fire after the check-in time.
However, when both events are scheduled for the same time, there is currently no hierarchy or guarantee on the order in which these triggers will fire. As a result, the BEFORE_STAY_STARTS trigger might send a message before the NEW_BOOKING event, leading to confusion and operational inefficiencies.
My request is to improve the handling of last-minute bookings and ensure a logical sequence of events. We propose the following enhancements:
1/ Ordered Trigger Execution:
Implement a mechanism to enforce a hierarchy between triggers, ensuring that the NEW_BOOKING event always fires before the BEFORE_STAY_STARTS event when both are scheduled for the same time.
2/ Condition-Specific Triggers for Last-Minute Bookings.
-
10 votes
-
3 votes
-
5 votes
-
18 votes
An error occurred while saving the comment Hostfully does not enable hosts to specify the number of pets allowed in property setting, but Airbnb does. As a result, Hostfully does not communicate the pet number to Airbnb, and Airbnb displays its default value of 5 on the listing.
The property manager would like to be able to define the number of pets so that the information is accurate and does not mislead guests.
Sometimes guests make mistakes when signing the rental agreement. It would be helpful if I could reset the rental agreement in my account, rather than reaching out to Hostfully Support for help.