Main Roadmap

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.

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.

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?

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.

Customize Review Link Position in Messages

Allow users to adjust the placement of the Sparrow review link prompt within automated messages sent to guests, rather than it being fixed at the end of the message. This would provide more flexibility in message design and potentially improve guest engagement with review requests.

Expand set of Breezeway departments for task creation

Add hotkeys for operating in Conversations

Reports Feature: Enhancement Request

Include OTA/Booking Channel in Report Filters Add the ability to filter reports by OTA or booking channel. This would allow users to generate reports specific to each channel, making it easier to monitor performance, track ratings, and identify trends for individual OTAs. Enable Multi-Property Selection Allow users to select multiple properties when generating reports. This will provide a consolidated view across multiple listings, making it more efficient to compare performance metrics, identify patterns, and manage operations for multiple properties simultaneously. Clickable Reviews in Reports In the generated reports, make the “Reviews” section clickable so that users can directly access the actual review. This would be helpful in providing more context without needing to manually search for the review.

Turno Integration

Team member performance reporting

i.e. related to "reply rate" or % or reviews replied

Week over Week Reporting

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.

Support multiple assignees for tasks pushed to Breezeway

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.

Dynamic priority for tasks pushed to Breezeway

Priority: High Problem / context Tasks currently arrive in Breezeway at the lowest priority regardless of situation. That is a visibility problem: a guest reporting an issue while still in the home lands at the same priority as a mildly negative post-departure review, so genuinely urgent items are easy to miss in the queue. Priority should reflect how time-sensitive the task actually is. Requested capability Set task priority dynamically based on the guest's stay status and the sentiment of what triggered the task, instead of a single static lowest-priority default. Detail / spec Proposed mapping: In-home guest (issue raised while the guest is still on site) → high priority Post-departure negative → medium/high priority Post-departure positive → low priority Priority is set at task creation from the trigger context (in-home status plus sentiment or score). Ideally the thresholds are configurable rather than hard-coded, so operators can tune what maps to which priority. Acceptance criteria An in-home guest issue creates a high-priority Breezeway task. A post-departure negative creates a medium/high task; a post-departure positive creates a low task. Priority is written at creation and reflects the trigger, not a static default.

RETURN TO URGENT ATTENTION LIST POSITION IN AIRBNB LISTING QUALITY MONITORING

I am requesting an arrow that will help navigate back to the "Urgent Attention Required" list, after clicking on one to view in greater detail. At times I am working from the bottom of the list and have to "x" out of the details of a listing taking me back to the main page. I then have to open the list again to get back to where I started. For functionality, it would be wonderful to just going in and out of that list without returning to the start. I am also wondering the order in which the listings appear in the "urgent attention required list". It is difficult to identify which suspensions and pending removals are new. As I understand, it is in the works already to remove past dated items, but a way to filter based on date would be very helpful in workflow to check day to day changes. Lastly, I am wondering if the suspension date and reactivation date could be visible, just as the appeal and removal date show for the pending removals. It is helpful to have that information at a glance to alert the appropriate parties of the suspension. I did not attach a screenshot, but could provide more context/info as needed! Thank you!

Response Rate and Response Time Reporting Dashboard

Description: There is currently no dashboard for measuring team performance on guest communication. Operators have no built-in way to see agent response times, response rates, and related metrics over time, which makes it hard to monitor service levels, run QA, and identify where response times are slipping. For example, a manager wanting to confirm the team is meeting a 30-minute response-time target, or to compare response performance across agents, has no in-platform reporting to draw on today. Requested Enhancement: Provide a dashboard showing agent response times and response rates. Allow performance to be viewed over time and broken down by agent. Support QA and service-level monitoring with exportable or filterable metrics. Benefit: A response-time and response-rate dashboard would give operators visibility into team performance, support QA audits, help enforce service-level targets, and surface where guest response times need attention.

Enhance right side panel and add calendar in Conversations

Option to make "Scheduled At" required in task creation

Configurable hold window before Chirp AI posts a review response

Chirp AI currently posts review responses as soon as the review is detected, leaving no gap for local teams to see the review first. Add a per-account (ideally per-property-group) hold window — e.g. 2, 12, 24, or 48 hours — between review ingestion and the AI reply being published. During the hold, the generated response sits in a pending state where a team member can edit, approve, or replace it; if nobody acts before the window closes, it posts automatically as it does today. Also surface the configured window in the UI so managers know what timing they're on.

OwnerRez Integration

Reviews Export not working properly on Safari Browser

Urgent Message Alerts and Conversation Pinning

Description: There is currently no way to be actively alerted to urgent conversations, or to pin critical conversations so they stay visible. For issues like maintenance emergencies, guest emergencies, or operational incidents, agents have to notice them in the normal inbox flow, which risks time-sensitive items being missed during busy periods. For example, a maintenance emergency or an upset guest can sit in the general inbox with no way to flag it for immediate attention or keep it pinned to the top until it is resolved. Requested Enhancement: Add alerts or notifications for urgent conversations so they are surfaced immediately. Allow agents to pin critical conversations so they remain visible and are not lost in the inbox flow. Provide better visibility for time-sensitive categories such as maintenance issues, guest emergencies, and operational incidents. Benefit: Active alerting and pinning would ensure urgent, time-sensitive conversations are seen and acted on quickly, reducing the risk of emergencies or critical guest issues being missed. (Note: urgency labeling and filtering can already be configured today via Rules and saved filters; this request covers the net-new alerting and pinning capabilities.)

Hostfully Integration

Always display property names and link in weekly insight emails

Support multiple Breezeway integrations per account

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!

Breezeway Integration

Send Feedback Requests via Text Message

ClickUp Integration

Self-serve Superuser access for your team

If you manage more than one account or PMS instance in Sparrow Intel, grant that same multi-account access to your team yourself, instead of asking the Sparrow Intel team to set it up.

Auto-Decline Inquiries and Trip Requests Before Expiry to Protect Response Rate

Description: Inquiries and trip requests that are not responded to before they expire can negatively affect an operator's OTA response rate. Today there is no automated safeguard, so the team must manually catch and respond to or decline pending requests before they time out in order to protect a 100% response rate. For example, if a trip request comes in near the end of a shift and is at risk of expiring without a response, an agent has to manually decline it in time to avoid a response-rate penalty. Requested Enhancement: Automatically decline inquiries and trip requests shortly before they expire (for example, about an hour before the deadline). Make the timing configurable so operators can set how far ahead of expiry the auto-decline triggers. Ensure this protects the operator's response-rate metric on the OTA. Benefit: Auto-declining before expiry would protect the operator's response rate automatically, removing the need for agents to manually watch for expiring requests and reducing the risk of response-rate penalties.

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.

Show Issues by Property in Multi-Property Reports

Delineate issues by property in reports that contain multiple properties.

Add OTA Filtering to Properties and Property Groups Summaries

Beds24 Integration

PMS integration for Beds24

Show Task Created from Sparrow with link to task management platform

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.

View 50 or 100 messages on one page in Conversations

Add Published/Not Published Field to Reviews for use with Public API

Static Feedback Request Links

Get static feedback request links to send to guests outside of Sparrow Intel.

Ability to include Google Business Profile locations in Property Groups

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.