Completed
Custom Date Range for Reports
Currently, reports for properties, property groups, individual cleaners, and individual inspectors can only be generated on a month over month basis. Allow reports to be generated for any custom date range.
gillian.hannay over 1 year ago
Feature Request
Completed
Custom Date Range for Reports
Currently, reports for properties, property groups, individual cleaners, and individual inspectors can only be generated on a month over month basis. Allow reports to be generated for any custom date range.
gillian.hannay over 1 year ago
Feature Request
Completed
Show Issues by Property in Multi-Property Reports
Delineate issues by property in reports that contain multiple properties.
gillian.hannay 11 months ago
Feature Request
Completed
Show Issues by Property in Multi-Property Reports
Delineate issues by property in reports that contain multiple properties.
gillian.hannay 11 months ago
Feature Request
Completed
Allow users to download/export reviews as spreadsheet
Users need the ability to download or export reviews from the platform. This feature should include options to filter reviews by date range (e.g., by month) to support external analysis. The current "all properties all categories" report lacks drill-down capabilities, making it difficult for users to get detailed review information for analysis purposes.
Ryan Rabideau over 1 year ago
Feature Request
Completed
Allow users to download/export reviews as spreadsheet
Users need the ability to download or export reviews from the platform. This feature should include options to filter reviews by date range (e.g., by month) to support external analysis. The current "all properties all categories" report lacks drill-down capabilities, making it difficult for users to get detailed review information for analysis purposes.
Ryan Rabideau over 1 year ago
Feature Request
Limited Beta Release
Native Asana integration
It would be great to have an Asana integration for a task to be created when a review is predicted to be low or anything else!
Gabe Chase over 1 year ago
Integration Request
Limited Beta Release
Native Asana integration
It would be great to have an Asana integration for a task to be created when a review is predicted to be low or anything else!
Gabe Chase over 1 year ago
Integration Request
Enhanced Task Management
Build a Kanban board and basic task mangement system in Sparrow Intel. Allow for basic task management within Sparrow and also provide the option to fully sync tasks with your PMS or Breezeway for more advanced task management. Augment with AI insights for reoccurring tasks, etc.
Chad McGuire (Sparrow Intel) 12 months ago
Feature Request
Enhanced Task Management
Build a Kanban board and basic task mangement system in Sparrow Intel. Allow for basic task management within Sparrow and also provide the option to fully sync tasks with your PMS or Breezeway for more advanced task management. Augment with AI insights for reoccurring tasks, etc.
Chad McGuire (Sparrow Intel) 12 months ago
Feature Request
Planned
Show exact data source in Insights
Chad. We are spending a lot of time searching through Sparrow trying to find the specific Prediction or Review being referenced in the Insights and Predictions. It makes the process significantly more efficient. Currently the hotlinks go to the property and you have to hunt and peck to try and find the Review or Prediction. You don’t know what the source is and sometimes you can’t find the source complaint or comment at all. This would be a significant improvement in the software. If we can’t trace the issue to the source it makes it very difficult for us to undertand exactly what happened and how to try and prevent a repeat.
Jay Harbison about 1 year ago
Feature Request
Planned
Show exact data source in Insights
Chad. We are spending a lot of time searching through Sparrow trying to find the specific Prediction or Review being referenced in the Insights and Predictions. It makes the process significantly more efficient. Currently the hotlinks go to the property and you have to hunt and peck to try and find the Review or Prediction. You don’t know what the source is and sometimes you can’t find the source complaint or comment at all. This would be a significant improvement in the software. If we can’t trace the issue to the source it makes it very difficult for us to undertand exactly what happened and how to try and prevent a repeat.
Jay Harbison about 1 year ago
Feature Request
Enhancing Chirp AI
It would be incredibly valuable if we could feed Chirp AI with feedback on responses, allowing it to learn how we communicate as a brand - picking up on our tone of voice and style of interaction.
Becky McAleer about 1 year ago
Feature Request
Enhancing Chirp AI
It would be incredibly valuable if we could feed Chirp AI with feedback on responses, allowing it to learn how we communicate as a brand - picking up on our tone of voice and style of interaction.
Becky McAleer about 1 year ago
Feature Request
Completed
Static Feedback Request Links
Get static feedback request links to send to guests outside of Sparrow Intel.
Derek DeCesere over 1 year ago
Feature Request
Completed
Static Feedback Request Links
Get static feedback request links to send to guests outside of Sparrow Intel.
Derek DeCesere over 1 year ago
Feature Request
Add custom dates and other filters to Dashboard
@Chad McGuire (Sparrow Intel) - Combining feature requests for enhancing our dashboard into one for better tracking! Feature Request #1: Would like to be able to apply custom filters to the Dashboard to be able to view the KPIs for specific date ranges. Feature Request #2: The Dashboard view is great and we really like all it has to offer here; however, we do a lot of weekly reporting, so we would like the date filter here to also be more granular than monthly. The other thing that was noticed that is not here is an Average Star Rating. We see the Volume numbers and Total Reviews, but there is not an Average Star Rating. Also the only Category that we see here is Cleanliness. Is there a place on the Dashboard to find/filter the other Categories?
Ryan Rabideau over 1 year ago
Feature Request
Add custom dates and other filters to Dashboard
@Chad McGuire (Sparrow Intel) - Combining feature requests for enhancing our dashboard into one for better tracking! Feature Request #1: Would like to be able to apply custom filters to the Dashboard to be able to view the KPIs for specific date ranges. Feature Request #2: The Dashboard view is great and we really like all it has to offer here; however, we do a lot of weekly reporting, so we would like the date filter here to also be more granular than monthly. The other thing that was noticed that is not here is an Average Star Rating. We see the Volume numbers and Total Reviews, but there is not an Average Star Rating. Also the only Category that we see here is Cleanliness. Is there a place on the Dashboard to find/filter the other Categories?
Ryan Rabideau over 1 year ago
Feature Request
Rejected
Add guest name, phone number, and in-home status to Breezeway tasks
Priority: Medium Problem / context Tasks pushed to Breezeway now carry reservation and review context, but not the guest's own details. When a field team acts on a task, especially while the guest is still on site, they need to know who the guest is, how to reach them, and whether they are currently in the home. Without it, the person doing the work has to go back into the PMS or the OTA to find contact details before they can act, which defeats the purpose of enriching the task in the first place. Requested capability Add guest name, guest phone number, and in-home status to the fields written into Breezeway tasks. Detail / spec Guest name and phone number pulled from the reservation. In-home status indicating whether the guest is currently checked in and on site, versus pre-arrival or post-departure. Consistent with the existing enrichment fields (reservation URL, OTA, score or prediction value, confirmation code) rather than a separate surface. Acceptance criteria A Breezeway task created from a reservation shows guest name and phone. In-home status is present and accurate at the time the task is created. A field team member can contact the guest from the task alone, without opening the PMS or OTA.
Alex Rasky about 2 months ago
Feature Request
Rejected
Add guest name, phone number, and in-home status to Breezeway tasks
Priority: Medium Problem / context Tasks pushed to Breezeway now carry reservation and review context, but not the guest's own details. When a field team acts on a task, especially while the guest is still on site, they need to know who the guest is, how to reach them, and whether they are currently in the home. Without it, the person doing the work has to go back into the PMS or the OTA to find contact details before they can act, which defeats the purpose of enriching the task in the first place. Requested capability Add guest name, guest phone number, and in-home status to the fields written into Breezeway tasks. Detail / spec Guest name and phone number pulled from the reservation. In-home status indicating whether the guest is currently checked in and on site, versus pre-arrival or post-departure. Consistent with the existing enrichment fields (reservation URL, OTA, score or prediction value, confirmation code) rather than a separate surface. Acceptance criteria A Breezeway task created from a reservation shows guest name and phone. In-home status is present and accurate at the time the task is created. A field team member can contact the guest from the task alone, without opening the PMS or OTA.
Alex Rasky about 2 months ago
Feature Request
Planned
Grouped conditional logic and negation in the rules engine
The rules engine currently supports only flat, single-condition logic, so operators can't express compound criteria in one rule. There's no way to group conditions with AND/OR, nest groups, or negate a condition (NOT / exclusion). As a result, any logic more complex than a single condition has to be split across multiple near-duplicate rules — which multiplies setup time, invites inconsistencies, and compounds across organizations that mirror rules across many accounts. A common case is targeting multiple OTAs in one rule: today that requires a separate rule per channel because the conditions can't be combined. Requested Enhancement: Support grouped conditional logic — combine conditions with AND/OR and nest groups within a single rule. Support negation — allow a condition to be expressed as NOT / exclusion (e.g., all channels except one, or fire unless a condition is met). Handle channel-specific condition validity within compound rules: Google (GMB) has no cleanliness sub-score, and a normalized Airbnb 4/5 vs. a Booking 8/10 can mean different things against a single threshold — so warn, auto-skip, or scope conditions per channel where a sub-score or scale doesn't apply. Benefit: Grouped logic and negation would let a single rule express what today takes many, cutting duplicate rule creation, reducing inconsistencies across channels and accounts, and lowering setup and maintenance overhead. Multi-OTA targeting becomes a natural outcome rather than a special case, and operators gain the expressiveness to model real-world routing and exclusion logic in one place.
Tobin Watkinson 3 months ago
Feature Request
Planned
Grouped conditional logic and negation in the rules engine
The rules engine currently supports only flat, single-condition logic, so operators can't express compound criteria in one rule. There's no way to group conditions with AND/OR, nest groups, or negate a condition (NOT / exclusion). As a result, any logic more complex than a single condition has to be split across multiple near-duplicate rules — which multiplies setup time, invites inconsistencies, and compounds across organizations that mirror rules across many accounts. A common case is targeting multiple OTAs in one rule: today that requires a separate rule per channel because the conditions can't be combined. Requested Enhancement: Support grouped conditional logic — combine conditions with AND/OR and nest groups within a single rule. Support negation — allow a condition to be expressed as NOT / exclusion (e.g., all channels except one, or fire unless a condition is met). Handle channel-specific condition validity within compound rules: Google (GMB) has no cleanliness sub-score, and a normalized Airbnb 4/5 vs. a Booking 8/10 can mean different things against a single threshold — so warn, auto-skip, or scope conditions per channel where a sub-score or scale doesn't apply. Benefit: Grouped logic and negation would let a single rule express what today takes many, cutting duplicate rule creation, reducing inconsistencies across channels and accounts, and lowering setup and maintenance overhead. Multi-OTA targeting becomes a natural outcome rather than a special case, and operators gain the expressiveness to model real-world routing and exclusion logic in one place.
Tobin Watkinson 3 months ago
Feature Request
Support Displaying and Managing Airbnb Reservation Change Requests in Conversation Threads
Description: Currently, when a guest submits a reservation alteration request through Airbnb (such as a change to dates, guest count, or pricing), the request does not appear in Sparrow Intel. The alteration is visible in the Airbnb conversation thread, but the corresponding Sparrow conversation shows no record of it. For example, if a guest requests to extend their stay by one night, that request and its status are visible in Airbnb but absent from Sparrow. Property managers reviewing the conversation in Sparrow have no indication that a pending alteration exists, which forces them to cross-reference Airbnb to get the full picture of the reservation and switch platforms to take action on the request. Requested Enhancement: Display Airbnb reservation alteration requests within the corresponding Sparrow conversation thread when that information is available from Airbnb. Show the key details of the request, including the type of change (dates, guest count, price), the proposed new values, and the request status (pending, accepted, declined). Allow property managers to accept or decline alteration requests directly from Sparrow, without switching to Airbnb. Update the displayed status as the alteration is accepted, declined, or withdrawn so the thread reflects the current state of the reservation. Benefit: This would give property managers a complete view of each reservation and the ability to act on it without switching between platforms. It would reduce response time on pending alterations, lower the risk of responding to guests without awareness of a pending change, and ensure that Sparrow functions as the single operational surface for guest communication, consistent with how teams already handle trip requests in the platform.
Sharlene S 3 months ago
Feature Request
Support Displaying and Managing Airbnb Reservation Change Requests in Conversation Threads
Description: Currently, when a guest submits a reservation alteration request through Airbnb (such as a change to dates, guest count, or pricing), the request does not appear in Sparrow Intel. The alteration is visible in the Airbnb conversation thread, but the corresponding Sparrow conversation shows no record of it. For example, if a guest requests to extend their stay by one night, that request and its status are visible in Airbnb but absent from Sparrow. Property managers reviewing the conversation in Sparrow have no indication that a pending alteration exists, which forces them to cross-reference Airbnb to get the full picture of the reservation and switch platforms to take action on the request. Requested Enhancement: Display Airbnb reservation alteration requests within the corresponding Sparrow conversation thread when that information is available from Airbnb. Show the key details of the request, including the type of change (dates, guest count, price), the proposed new values, and the request status (pending, accepted, declined). Allow property managers to accept or decline alteration requests directly from Sparrow, without switching to Airbnb. Update the displayed status as the alteration is accepted, declined, or withdrawn so the thread reflects the current state of the reservation. Benefit: This would give property managers a complete view of each reservation and the ability to act on it without switching between platforms. It would reduce response time on pending alterations, lower the risk of responding to guests without awareness of a pending change, and ensure that Sparrow functions as the single operational surface for guest communication, consistent with how teams already handle trip requests in the platform.
Sharlene S 3 months ago
Feature Request