Welcome to Sparrow Intel’s public roadmap! Leave us feedback, provide comments, and check on the status of what we’re working on!

Backlog

Next up

In Progress

Testing

Limited Beta Release

Done

Won't Do

Main Roadmap

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.

In Review

Enhanced Task Management

Chad McGuire (Sparrow Intel)

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

Regan Palmer

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.

Enhancing Chirp AI

Becky  McAleer

@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?

Add custom dates and other filters to Dashboard

Ryan Rabideau

Support multiple assignees for tasks pushed to Breezeway

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:<ul><li>Display Airbnb reservation alteration requests within the corresponding Sparrow conversation thread when that information is available from Airbnb.</li><li>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).</li><li>Allow property managers to accept or decline alteration requests directly from Sparrow, without switching to Airbnb.</li><li>Update the displayed status as the alteration is accepted, declined, or withdrawn so the thread reflects the current state of the reservation.</li></ul>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.

Support Displaying and Managing Airbnb Reservation Change Requests in Conversation Threads

Sharlene S

List full name not just first name for all reservations

Mia O

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.

Customize Review Link Position in Messages

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.&nbsp;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.&nbsp;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!

RETURN TO URGENT ATTENTION LIST POSITION IN AIRBNB LISTING QUALITY MONITORING

Amanda Furgiuele

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:<ul><li>Support grouped conditional logic — combine conditions with AND/OR and nest groups within a single rule.</li><li>Support negation — allow a condition to be expressed as NOT / exclusion (e.g., all channels except one, or fire unless a condition is met).</li><li>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.</li></ul>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.

Grouped conditional logic and negation in the rules engine

Tobin Watkinson

Planned

Week over Week Reporting

GX - Patrick Au

View 50 or 100 messages on one page in Conversations

Priority: High
<h3>Problem / context</h3>
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.
<h3>Requested capability</h3>
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.
<h3>Detail / spec</h3>
Proposed mapping:
<ul>
<li>In-home guest (issue raised while the guest is still on site) → high priority</li>
<li>Post-departure negative → medium/high priority</li>
<li>Post-departure positive → low priority</li>
</ul>
<ul>
<li>Priority is set at task creation from the trigger context (in-home status plus sentiment or score).</li>
<li>Ideally the thresholds are configurable rather than hard-coded, so operators can tune what maps to which priority.</li>
</ul>
<h3>Acceptance criteria</h3>
<ul>
<li>An in-home guest issue creates a high-priority Breezeway task.</li>
<li>A post-departure negative creates a medium/high task; a post-departure positive creates a low task.</li>
<li>Priority is written at creation and reflects the trigger, not a static default.</li>
</ul>

Dynamic priority for tasks pushed to Breezeway

Alex Rasky

Description:
Currently, the OTA confirmation code for a reservation is not displayed within the Sparrow Intel conversation view. Property managers frequently need this code to locate the corresponding booking in their PMS or email during investigations, and today they must open the reservation in the OTA to retrieve it.
For example, when a guest reaches out about an issue with their stay, an agent investigating in their PMS needs the OTA confirmation code to pull up the booking. Because the code is not shown in Sparrow, the agent has to leave the platform, open the OTA, find the reservation, and copy the code before continuing, which interrupts the workflow and adds time to every investigation.
Requested Enhancement:
<ul>
<li>Display the OTA confirmation code prominently within each conversation thread when that information is available from the OTA.</li>
<li>Make the code easy to copy for quick lookups in external systems such as a PMS or email.</li>
<li>Complement the existing ability to search by confirmation code, so the code can be both found and referenced from within Sparrow.</li>
</ul>
Benefit:
This would give property managers immediate access to the confirmation code they rely on for booking investigations without leaving Sparrow, reducing platform switching, speeding up issue resolution, and keeping agents focused within a single workflow.

Display OTA Confirmation Code Within the Conversation

Enhance right side panel and add calendar in Conversations

Auto-email invoices to specific users

Carlos Cojab

Message to guest still sending when "Skip if guest already left review" is set

Martins Mackevics

<img data-width="100%" data-align="left" data-featurebase-content-key="6760b3146c4367597735b9da/post/690dad8ee8ab0f00b93a3563/019a5d6c-b298-7453-b382-64d7303db5a1/b64u-aW1hZ2UucG5n.png" src="https://6760b3146c4367597735b9da.featurebase-attachments.com/c/post/690dad8ee8ab0f00b93a3563/019a5d6c-b298-7453-b382-64d7303db5a1/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260802T010000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260802%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=9a081a1dd947711b7ecb65d4efba8540736bdaa9cf1b2b40e578c16e70b3e534" data-featurebase-content-filename="image.png">This screen is stuck for me even on different browsers and multiple refreshes.

Property groups tab doesn't load

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. <img data-width="100%" data-align="left" data-featurebase-content-key="6760b3146c4367597735b9da/post/68704c005c5b6d10279a326f/0197f6a8-b92a-7f1a-915e-e40319e40103/b64u-aW1hZ2UucG5n.png" data-featurebase-content-filename="image.png" src="https://6760b3146c4367597735b9da.featurebase-attachments.com/c/post/68704c005c5b6d10279a326f/0197f6a8-b92a-7f1a-915e-e40319e40103/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260802T010000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260802%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=6ce8552efc533230a8e10ae5bda7e64c5f21c686d9e5f86a3c1128f54217dfca">

Show exact data source in Insights

Jay Harbison

Operators with listings distributed through Vacasa.com receive guest correspondence as email rather than through a native OTA messaging API. Today that email either doesn't land in Sparrow Intel's Conversations inbox or lands without a reliable reply path, so agents have to leave Sparrow to read and respond — breaking the unified-inbox workflow and the AI-assisted reply tooling (Chirp). For example, an agent handling a Vacasa.com guest inquiry must work outside Sparrow to read and answer it, losing threading, reservation context, and Chirp draft assistance.Requested Enhancement:<ul><li>Ingest inbound Vacasa.com guest email into the Conversations inbox, threaded correctly so multiple emails for one reservation group into a single conversation.</li><li>Associate each conversation with the correct guest and reservation/property where data permits (confirmation code, guest name, listing), and label the source clearly as Vacasa.</li><li>Allow agents to reply from within the conversation, delivered back to the guest via the correct email path, with confirmed deliverability (avoiding the "failed to send via Mailgun" class of failures).</li><li>Respect existing email-conversation rules — manual draft, not auto-send — and support Chirp AI draft-on-demand once the thread is captured.</li><li>Build on the in-flight email-conversations capability (attachments, forward, body rendering, guest-name-in-from-line) rather than a parallel path.</li></ul>Benefit: Treating Vacasa.com email as a first-class conversation source would keep agents in a single unified inbox, preserve threading and reservation context, extend Chirp AI assistance to Vacasa threads, and ensure reliable two-way communication with guests — without forcing agents out of Sparrow.

Vacasa.com email ingest + reply

Tyler Sneed

OwnerRez Integration

i.e. trigger an action for a listing quality status change<h4>Problem / context</h4>The rule triggers on a listing quality status change and creates a task. But a task that only says a listing has entered pending removal isn't actionable on its own. The recipient still has to go find out what Airbnb flagged, what the appeal requires, and when it's due, which means leaving the task and logging into the Airbnb account. That defeats the point of routing the task to them.This matters most for pending removal, where the appeal is the work. Operators build appeals by taking each cited issue, explaining why it happened, and documenting the resolution. The person doing that needs the citations in front of them.<h4>Requested capability</h4>When a listing quality status change generates a task, write the appeal detail into the task body so the recipient can act without leaving it.<h4>Detail / spec</h4>Include, where available from the platform:<ul><li>Appeal due date</li><li>Reservation issues cited</li><li>Specific reasons flagged (e.g., check-in, communication, host-encouraged cancellation)</li><li>Current listing quality status and the date it changed</li></ul>The data is already surfaced on the Listing Quality page, so this is a matter of carrying it into the task payload rather than sourcing anything new.Detail should scale to severity. A suspension notice is largely informational, while pending removal needs the full appeal context.<h4>Acceptance criteria</h4><ul><li>A task generated from a pending removal status change includes the appeal due date, cited reservation issues, and flagged reasons.</li><li>A recipient with no Sparrow access can understand what needs to be addressed from the task alone.</li><li>Fields absent from the platform response are omitted cleanly rather than rendering blank or erroring.</li></ul>

Listing Quality Rules

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:<ul><li>Add alerts or notifications for urgent conversations so they are surfaced immediately.</li><li>Allow agents to pin critical conversations so they remain visible and are not lost in the inbox flow.</li><li>Provide better visibility for time-sensitive categories such as maintenance issues, guest emergencies, and operational incidents.</li></ul>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.)

Urgent Message Alerts and Conversation Pinning

Hostfully Integration

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.

Completed

Custom Date Range for Reports

gillian.hannay

Delineate issues by property in reports that contain multiple properties.<img data-width="100%" data-align="left" data-featurebase-content-key="6760b3146c4367597735b9da/post/69012ef985266522f5ab1c82/019a2c9f-2ccc-7c5a-82b4-4e7810bead7b/b64u-dW5uYW1lZCAoMikucG5n.png" data-featurebase-content-filename="unnamed (2).png" src="https://6760b3146c4367597735b9da.featurebase-attachments.com/c/post/69012ef985266522f5ab1c82/019a2c9f-2ccc-7c5a-82b4-4e7810bead7b/b64u-dW5uYW1lZCAoMikucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260802T010000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260802%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=ed1d38ee99c021eac1b172d732eb0c7153e6a506641fa09523b6e6fc127c31e4">

Show Issues by Property in Multi-Property Reports

Show Task Created from Sparrow with link to task management platform

Add OTA Filtering to Properties and Property Groups Summaries

ORL - Ricardo de Martino

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.

Allow users to download/export reviews as spreadsheet

Beds24 Integration

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

Static Feedback Request Links

Derek DeCesere

Ability to include Google Business Profile locations in Property Groups

Add properties and property groups public API endpoints

Improved billing and payment method support

Priority: Medium
<h3>Problem / context</h3>
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.
<h3>Requested capability</h3>
Add guest name, guest phone number, and in-home status to the fields written into Breezeway tasks.
<h3>Detail / spec</h3>
<ul>
<li>Guest name and phone number pulled from the reservation.</li>
<li>In-home status indicating whether the guest is currently checked in and on site, versus pre-arrival or post-departure.</li>
<li>Consistent with the existing enrichment fields (reservation URL, OTA, score or prediction value, confirmation code) rather than a separate surface.</li>
</ul>
<h3>Acceptance criteria</h3>
<ul>
<li>A Breezeway task created from a reservation shows guest name and phone.</li>
<li>In-home status is present and accurate at the time the task is created.</li>
<li>A field team member can contact the guest from the task alone, without opening the PMS or OTA.</li>
</ul>

Rejected

Add guest name, phone number, and in-home status to Breezeway tasks

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!

Native Asana integration

Gabe  Chase

Breezeway Integration

Send Feedback Requests via Text Message

Always display property names and link in weekly insight emails

Priority: Medium-High
<h3>Problem / context</h3>
Property groups are built and maintained by hand today. At scale that breaks down: every newly onboarded unit has to be added to the right groups manually, and every reassignment of a manager, director, or market means finding and updating the affected groups. Operators running large portfolios across multiple PMS instances cannot keep this accurate by hand.
The data already exists. Operators typically maintain these assignments in Guesty as custom fields, since that is where their team structure lives, and then re-enter the same information into Sparrow to build groups. Automating this has been named as one of the biggest missing pieces, because manual maintenance is the only thing standing between the operator and group-level reporting they can trust.
<h3>Requested capability</h3>
Let a user designate a Guesty custom field as the source for a property group type, and populate group membership from it automatically, so new and reassigned units flow into the correct groups without manual upkeep.
<h3>Detail / spec</h3>
<ul>
<li>User designates which Guesty custom field maps to which property group type (for example, a property manager field drives the PM groups).</li>
<li>Membership syncs on a schedule so newly onboarded and reassigned units land in the right groups without intervention.</li>
<li>Must work across multiple Guesty accounts belonging to a single customer, since portfolios built through acquisition commonly run several PMS instances.</li>
</ul>
The obstacle, verified previously: Guesty exposes custom fields through its API as unlabeled tokenized IDs. The Guesty UI shows a readable name, but the API returns an opaque string with no indication of what the field represents, and those IDs differ per customer, differ across a single customer's multiple Guesty accounts, and in observed cases vary property to property within one account. A fixed field reference will not work. It needs either a per-customer configuration step where the user identifies which token maps to which field, or a discovery layer that infers field identity from its values. Either way this is a custom engine, not a simple mapping.
<h3>Acceptance criteria</h3>
<ul>
<li>A user can designate a Guesty custom field as the source for a property group type.</li>
<li>Group membership populates from that field and stays current as units are added or reassigned.</li>
<li>Works across multiple Guesty accounts under one customer.</li>
<li>No per-property manual mapping required.</li>
</ul>

Auto-populate property group membership from PMS custom fields

Beds24 does not log the time of day or timezone for most dates/times. Sparrow Intel is consuming these dates as UTC but that is not always correct.