Pipeline, Reporting & Impact

Reporting data in Chili Piper is only accessible by logging into the product. Admins who want recurring visibility into key metrics, such as daily booking activity or weekly concierge performance, have to remember to check manually. Allow admins to subscribe to any in-app report and receive it as a scheduled email digest on a configurable cadence, such as daily, weekly, or monthly. Proactive reporting delivery drives broader visibility without requiring stakeholders to log in. Ops leaders and executives who aren't in the product daily will engage with data far more consistently when it comes to them rather than requiring them to seek it out.

There's no way to get a quick view of all assignees within a queue alongside when they're next available. Ops and team leads who want to identify reps with no upcoming availability, spot scheduling gaps, or validate queue health have to check each rep individually. Provide a view within Chili Piper that lists all assignees in a given queue or distribution alongside their next available time slot, accounting for Meeting Type constraints such as minimum scheduling windows and date restrictions. Queue health is hard to monitor without aggregate availability visibility. A simple list showing who has availability and when gives ops teams a fast diagnostic view, especially useful before high-volume campaign launches or after a rep's calendar unexpectedly fills up.

Working hours are configured at the user level but there's no aggregate view. Admins who need to verify that all users have working hours set correctly, or audit for inconsistencies across the workspace, have to check each user one by one. Provide an admin-level report that surfaces the working hours configuration for every user in the workspace in a single view, with the ability to filter or sort by team, role, or schedule. Individually checking working hours across large user bases is impractical and error-prone. Misconfigured working hours directly affect availability and routing accuracy, so a workspace-level view is a basic operational need for any admin managing more than a handful of users.

The Meetings Activity page is sorted by scheduled meeting date by default, with no column showing when a meeting was actually booked. Admins who need to understand booking patterns, audit recent activity, or investigate a specific meeting based on when it was created have no way to view or sort by booking date within the page. Chili Piper should add a created date or booking date column to the Meetings Activity page and allow admins to sort by it, in addition to the existing scheduled date sort. Booking date and meeting date serve different analytical purposes. Booking date is essential for understanding recency of activity, auditing what happened on a given day, and answering questions like "what was booked this week?" that the current scheduled-date view doesn't support without manual filtering workarounds.

UTM parameters appear in the Meeting Activity dashboard when they are added to router links or mapped through form submissions, but not when they are passed via the JS API as part of the lead object. Admins using the JS API integration have no way to see UTM data in Meeting Activity, even though the same data is visible when using other supported methods. The inconsistency is confusing and undermines attribution reporting for teams that use the JS API. Chili Piper should surface UTM values in Meeting Activity regardless of how the lead was submitted, including when passed via the JS API. Attribution reporting depends on consistent UTM capture across all entry points. When one supported integration method silently drops UTM data from the activity dashboard, teams cannot trust their meeting attribution data or accurately measure campaign performance.

There's no way to see how a single rep is distributed across multiple active queues at once. Admins who need to audit a rep's total load, identify imbalances, or adjust participation across distributions have to check each queue individually, which is impractical at scale. Provide a rep-centric view that shows a single user's participation and cumulative distribution totals across all active queues in one screen, including meeting counts, lead counts, and queue membership status. A rep's total workload is the sum of all their queue participation, not any single queue in isolation. Without a cross-queue view, admins managing large distribution setups can't make informed decisions about load balancing, and reps who are over- or under-distributed relative to their peers go undetected until it shows up in performance data.

Allow the ability to see which opportunities compose the meetings scheduled/cancelled within distributions. If an admin wants to see which 3 meetings cancelled within a distribution for an AE, for instance, it requires a manual search.

Reporting in Chili Piper is restrictive, requiring data to be exported and processed in external tools to answer basic questions. There is no way to run advanced reports natively within the product. Chili Piper should provide advanced in-product reporting capabilities that allow teams to answer complex questions without exporting data, including filtering, grouping, and custom views. Forcing teams to export data for basic analysis creates friction and reduces adoption of reporting features. Native advanced reporting keeps insights accessible to everyone, not just those comfortable with spreadsheets.