Completed
POSSIBLE BUG / GLOBAL SETTING ISSUE - changing check in times - impact on cleaners unable to meet unreasonable deadline
Subject: Editing check‑in time for one reservation updates all future guests across all properties Issue Summary When I manually change the check‑in time for a single guest reservation, the system automatically updates the displayed check‑in time for all future guests across all properties. This behavior suggests either: a bug where reservation‑level edits propagate globally, or a UI issue where a global default is being modified without clear indication. Steps to Reproduce Open an existing reservation Manually edit the check‑in time for that specific guest Save the change Observe that: The updated check‑in time now appears for all future reservations The change applies across multiple properties, not just the one reservation Expected Behavior Editing the check‑in time for a reservation should affect only that reservation. Account‑level or listing‑level default check‑in times should: Be clearly labeled as such Never be modified implicitly by editing a single guest’s reservation Actual Behavior The edited check‑in time propagates globally, impacting: Future guests Multiple properties Displayed check‑in times used by automated messages, calendars, and cleaning workflows Operational Impact This issue has high operational risk, including: Incorrect automated guest messaging Confusion around arrival times Potential cleaning and turnover timing errors Loss of trust with guests and cleaners Because check‑in times are foundational to multiple systems, this behavior is especially concerning. Additional Notes This was not an intentional global change The UI did not clearly indicate that a default or global value was being edited It is unclear whether the change affected: Account‑level defaults Listing‑level defaults Or both Clarification and correction are needed to prevent recurrence. Requested Actions Confirm whether this is a bug or intended behavior Identify which setting was modified (reservation vs listing vs account) Ensure reservation‑level check‑in overrides do not update global defaults Recommend a safe workflow for guest‑specific early/late check‑in adjustments Thank you — this issue affects core scheduling and messaging workflows, so I appreciate it being reviewed by the appropriate team.
Bonnie Hunt 3 days ago
⚠️ Bugs
Completed
POSSIBLE BUG / GLOBAL SETTING ISSUE - changing check in times - impact on cleaners unable to meet unreasonable deadline
Subject: Editing check‑in time for one reservation updates all future guests across all properties Issue Summary When I manually change the check‑in time for a single guest reservation, the system automatically updates the displayed check‑in time for all future guests across all properties. This behavior suggests either: a bug where reservation‑level edits propagate globally, or a UI issue where a global default is being modified without clear indication. Steps to Reproduce Open an existing reservation Manually edit the check‑in time for that specific guest Save the change Observe that: The updated check‑in time now appears for all future reservations The change applies across multiple properties, not just the one reservation Expected Behavior Editing the check‑in time for a reservation should affect only that reservation. Account‑level or listing‑level default check‑in times should: Be clearly labeled as such Never be modified implicitly by editing a single guest’s reservation Actual Behavior The edited check‑in time propagates globally, impacting: Future guests Multiple properties Displayed check‑in times used by automated messages, calendars, and cleaning workflows Operational Impact This issue has high operational risk, including: Incorrect automated guest messaging Confusion around arrival times Potential cleaning and turnover timing errors Loss of trust with guests and cleaners Because check‑in times are foundational to multiple systems, this behavior is especially concerning. Additional Notes This was not an intentional global change The UI did not clearly indicate that a default or global value was being edited It is unclear whether the change affected: Account‑level defaults Listing‑level defaults Or both Clarification and correction are needed to prevent recurrence. Requested Actions Confirm whether this is a bug or intended behavior Identify which setting was modified (reservation vs listing vs account) Ensure reservation‑level check‑in overrides do not update global defaults Recommend a safe workflow for guest‑specific early/late check‑in adjustments Thank you — this issue affects core scheduling and messaging workflows, so I appreciate it being reviewed by the appropriate team.
Bonnie Hunt 3 days ago
⚠️ Bugs
In Progress
Cleaning Opportunity Date Range (Flexible Cleaning Windows) Problem
Currently, turnover cleanings are only displayed and scheduled on the guest checkout date. This assumes all cleanings must be completed immediately after departure, which is not always operationally accurate. In many cases, there is a gap of one or more days between guest stays. While the guest may check out at 10:00 AM, the next guest may not arrive until 1–3 days later. In these situations, cleaners actually have a multi‑day window in which the cleaning can be completed. By restricting cleanings to the checkout day only, the system: Artificially limits cleaner availability Reduces cleaner acceptance rates (especially in Offer Mode) Creates unnecessary scheduling pressure Prevents cleaners from batching jobs efficiently Proposed Solution Introduce a Cleaning Opportunity Window instead of a single fixed cleaning date. Each turnover cleaning should include: Earliest possible start: Guest checkout time Latest possible completion: Next guest check‑in time (or a configurable buffer before arrival) Estimated duration: e.g. 3–5 hours The cleaning should be displayed as available anytime within this date/time range, even if the range spans multiple days. Example Guest checks out: Feb 10 @ 10:00 AM Next guest checks in: Feb 12 @ 4:00 PM ✅ Valid cleaning window: Feb 10 → Feb 12 ❌ Current system only shows: Feb 10 Cleaner‑Facing UX (Suggested) Instead of showing a single date, display: Turnover Cleaning — W House Can be completed anytime between Feb 10 (after 10:00 AM) and Feb 12 (before 4:00 PM) Estimated time: 4 hours Cleaners could then: Accept and select a preferred date/time within the window Accept and allow auto‑assignment to an optimal slot Benefits Increased cleaner acceptance rates More realistic scheduling Better support for professional cleaners Stronger Offer Mode performance Reduced operational friction for hosts This change would significantly improve real‑world cleaning operations, especially for properties with non‑back‑to‑back bookings.
Bonnie Hunt 3 days ago
Feature Request
In Progress
Cleaning Opportunity Date Range (Flexible Cleaning Windows) Problem
Currently, turnover cleanings are only displayed and scheduled on the guest checkout date. This assumes all cleanings must be completed immediately after departure, which is not always operationally accurate. In many cases, there is a gap of one or more days between guest stays. While the guest may check out at 10:00 AM, the next guest may not arrive until 1–3 days later. In these situations, cleaners actually have a multi‑day window in which the cleaning can be completed. By restricting cleanings to the checkout day only, the system: Artificially limits cleaner availability Reduces cleaner acceptance rates (especially in Offer Mode) Creates unnecessary scheduling pressure Prevents cleaners from batching jobs efficiently Proposed Solution Introduce a Cleaning Opportunity Window instead of a single fixed cleaning date. Each turnover cleaning should include: Earliest possible start: Guest checkout time Latest possible completion: Next guest check‑in time (or a configurable buffer before arrival) Estimated duration: e.g. 3–5 hours The cleaning should be displayed as available anytime within this date/time range, even if the range spans multiple days. Example Guest checks out: Feb 10 @ 10:00 AM Next guest checks in: Feb 12 @ 4:00 PM ✅ Valid cleaning window: Feb 10 → Feb 12 ❌ Current system only shows: Feb 10 Cleaner‑Facing UX (Suggested) Instead of showing a single date, display: Turnover Cleaning — W House Can be completed anytime between Feb 10 (after 10:00 AM) and Feb 12 (before 4:00 PM) Estimated time: 4 hours Cleaners could then: Accept and select a preferred date/time within the window Accept and allow auto‑assignment to an optimal slot Benefits Increased cleaner acceptance rates More realistic scheduling Better support for professional cleaners Stronger Offer Mode performance Reduced operational friction for hosts This change would significantly improve real‑world cleaning operations, especially for properties with non‑back‑to‑back bookings.
Bonnie Hunt 3 days ago
Feature Request
Planned
Automated follow ups for scheduled messages
For example when requesting info from a guest and they haven’t provided it to automatically follow up.
Bill Ulammandakh 5 days ago
Feature Request
Planned
Automated follow ups for scheduled messages
For example when requesting info from a guest and they haven’t provided it to automatically follow up.
Bill Ulammandakh 5 days ago
Feature Request
Planned
Create a task from guest message with a quick button
a small little icon next to the guest message where you can click on it, to create a quick task, once its generated , and you go into task section you can see where the task got created from (ie the blue font writing it does with auto guest eta's)
Bill Ulammandakh 11 days ago
Feature Request
Planned
Create a task from guest message with a quick button
a small little icon next to the guest message where you can click on it, to create a quick task, once its generated , and you go into task section you can see where the task got created from (ie the blue font writing it does with auto guest eta's)
Bill Ulammandakh 11 days ago
Feature Request
auto tasks ie allocating to a maintenance person would be greato to have some filters, words contain/must contain/only if / etc that would be amazing.
Bill Ulammandakh 11 days ago
Feature Request
auto tasks ie allocating to a maintenance person would be greato to have some filters, words contain/must contain/only if / etc that would be amazing.
Bill Ulammandakh 11 days ago
Feature Request
Ability to mark a review as received in review analytics
In case where a review doesn’t sync automatically from the platform, ability to mark a review as received along with the rating https://app.prohost.ai/reviews/analytics
Bill Ulammandakh 13 days ago
Feature Request
Ability to mark a review as received in review analytics
In case where a review doesn’t sync automatically from the platform, ability to mark a review as received along with the rating https://app.prohost.ai/reviews/analytics
Bill Ulammandakh 13 days ago
Feature Request
