Main Roadmap

Display all existing tasks for property in Breezeway (or other task management system) in Sparrow

Display on all objects as appropriate - reviews, conversations, predictions, etc.

Receive Negative Predictions Before Guest Departure

As a user, I want to receive negative predictions before a guest checks out. Currently, predictions are sent at the time of departure, which leaves no time to address guest issues. Receiving these alerts earlier would allow me to proactively contact the guest, resolve their problems, and potentially prevent a negative review.

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.

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?

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.

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

Ask Questions

Would like the ability to ask AI questions about our properties and reviews.

Week over Week Reporting

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.

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.

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.

Support multiple assignees for tasks pushed to Breezeway

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

More varied, concise Chirp AI review replies

Problem / context Chirp AI review replies can repeat the guest's review back almost word for word, sound alike from one review to the next, and run longer than they need to. Teams end up rewriting drafts so their public replies don't read as templated. Requested capability Replies that read as written for each review: in the team's own words, different from recent replies, and concise. Detail / spec Chirp AI sees the opening and closing lines of the account's recent posted replies and avoids reusing them. It mentions one or two details from the review in its own words instead of restating the review. Positive reviews get a reply of 2–4 sentences. Negative reviews get an acknowledgement and one concrete next step. Custom review reply guidelines still take priority. Applies to drafts on the Reviews screen, Auto Respond with AI rules and AI Connectors. Acceptance criteria Across an account's recent replies, the most common opening lines make up a smaller share than before. Average reply length drops. Replies no longer copy whole sentences from the guest's review.

Review widget: score-only ("at-a-glance") mode

Request Allow the review widget to be embedded as the rating summary alone: overall score, stars, total review count and the per-channel breakdown, with no review text beneath it. Use case Property managers want a compact rating badge near the top of a property page (beside the title or booking panel) as a trust signal, independent of where full reviews appear on the page. Current behavior Setting the review count to 0 gets close, but the widget still renders the "No reviews to show yet." box under the summary. That reads as though the property has no reviews, which contradicts the score shown right above it. Requested behavior A summary-only display option that renders just the score header. No review list and no empty-state message in that mode. The widget height collapses to fit the header, so it sits cleanly in a sidebar or header area.

Option to make "Scheduled At" required in task creation

Limit team members to specific property groups

Problem / context Team roles control what each teammate can do. But anyone who isn't an Owner still sees every property on the account. Operators with regional managers, owner-relations staff or outside partners can't give those people a view of only the properties they look after. Right now the choice is to show them everything or give them no access at all. Requested capability Let an Owner limit any team member to one or more property groups. That person then sees only the properties in those groups, everywhere in Sparrow Intel. Detail / spec A Property Access setting for each team member under Account → Team Members, with two choices: All properties or Specific property groups. It works with every role: Team Member, Read-Only and Custom. Owners always see everything. A limited user sees the properties in their groups, including any Google and Facebook locations added to those groups. They also see records that aren't tied to any property. Every list, filter, count, dashboard, report and export covers only that user's properties, so "All" means all of theirs. Account-wide settings (rules, templates, review settings, integrations, brand and property groups) are view-only for limited users. If a limited user opens a record outside their access, it shows as not found. When a group's membership changes, including Auto Groups, the user's access updates automatically. Acceptance criteria An Owner can limit a team member to one or more property groups. That team member sees reviews, dashboards and reports only for the properties in those groups. A team member limited to no groups sees no properties, never all of them. When a property is removed from a group, it disappears from that team member's view. Related This follows on from Custom Team Member Permissions, which added the Read-Only and Custom roles.

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. Plan Chirp AI will learn each account's review reply style from the replies the team posts and from how the team edits Chirp AI's drafts. Save every Chirp AI draft. Keep Chirp AI's original draft on each review reply, so it can be compared with the reply the team actually posts. This ships first, because learning needs a few weeks of drafts to compare. Learn the account's style. Every week, summarize the account's style from its posted replies and from what the team changes in Chirp AI's drafts: tone, length, phrases the team adds, and phrases it always removes. Write in that style. New review replies follow the learned style. Custom review reply guidelines win where the two conflict. Keep it visible. Show the learned style in Review Reply Settings, with a switch to turn it off. Acceptance criteria Over time, more Chirp AI drafts are posted as written, and edits to the rest get smaller. Each account can see its learned style and turn it off.

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

OwnerRez Integration

Hide quoted history in guest email replies

Description: When a guest replies to an email conversation, their email client adds every earlier message in the thread below their reply. Sparrow Intel shows that whole chain inside each message, so each reply repeats the full back-and-forth, nested one level deeper every time. Staff have to read past pages of old messages to find what the guest just wrote, and it is hard to tell new text from old. Requested behavior Each email in a conversation shows only the new text the sender wrote. The earlier history is collapsed behind a Show quoted text control under the message, so staff can still expand it when they need it. Signatures and attachments the sender added in their new reply stay visible. This applies to emails already in the inbox, not only new ones. Replies sent from Sparrow Intel still include the previous message for the guest, the way standard email does. Current workaround The guest's new text is at the top of each email, above the first "On [date], [name] wrote:" line. Everything below that line is earlier conversation already shown further up the thread.

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

Operto Integration

Integration with Operto so Sparrow Intel can create maintenance and cleaning tasks in Operto from issues guests report in messages and reviews, using rules like Maintenance Issues and Cleaning Issues from Predictions.

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.

Show Task Created from Sparrow with link to task management platform

Add OTA Filtering to Properties and Property Groups Summaries

Beds24 Integration

PMS integration for Beds24

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.

Send message rule action scheduled relative to the trigger

Add a variant of the send message rule action that schedules the message for a set time after the rule's trigger (for example, when a review or a new post in Conversations comes in), rather than a set time after checkout. Example: If a guest leaves 5-star internal feedback through a feedback request, send them a message 2 days later asking them to leave a public review if they have not already. Note: For cases like this, the "has not already reviewed" check needs to run when the message is due to send, not when the rule triggers, so guests who review during the delay are skipped.

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.