Skip to main content

How to use AI Coach Analytics

Get a holistic view of your entire team's performance at a glance.

Lais Lara avatar
Written by Lais Lara
Updated this week

Why this new view matters:

  • Easy drill-downs: Jump from the high-level team view to any rep’s individual stats in one click

  • Clearer feedback: View your scorecards and reps side-by-side to spot gaps and wins

  • Targeted coaching: Identify exactly where each rep excels or needs support, providing data-driven coaching.

You can watch this quick video or read the breakdown below:


Accessing the AI Coach Analytics

Just click the Analytics tab in AI Coach and you'll land on the new dashboard.

💡 Note: The new view only shows scorecards with call data to keep things clean. You can still add empty scorecards—they appear with “0”s until calls are logged.

Navigating from team overview to individual performance

Click a rep’s name in the Performance table to open their individual dashboard.

You'll also find a chronological timeline of their meetings, which highlights Risks and Action Items for quick coaching insights.

You'll also find a chronological timeline of their meetings. The individual rep's meeting timeline highlights identified Risks and Action Items for quick coaching insights.

Drill down to specific scorecards

You can deep dive into specific scorecards in two ways:

  1. From the top view in the main dashboard, click on the scorecard you wish to view.

2. From the Performance table, whether on the team view or on the individual rep view, click on any score (e.g., "74%" under "Discovery") to go to that scorecard's dashboard.


Customize your scorecard views

You can create new views by clicking on the dropdown of the view.

You can also edit views by renaming them or dragging and dropping scorecards to change the display order.

💡 Note: Changes you make in one workspace stay in that workspace only.

Use the Performance table for quick insights

The Team Average column shows the benchmark for every scorecard.

Sort any column to surface top performers or weak spots.

Hiding a column from the table does not affect the scorecards, but removing a scorecard from the view will also remove its entire column from the table.

💡 Note: all data shown respects the active date filter (default = last 30 days). Playbook adherence is always compared to the previous period

Best Practices for Success

  • Daily/Weekly pulse checks: Use the new "Zoom-Out" view as your go-to for quick daily or weekly check-ins on overall team health and progress.

  • Tailor views per workspace: Leverage the workspace-specific customizations. For example, your Sales workspace might prioritize "Sales" scorecards, while Customer Success workspace focuses on "Customer Success" scorecards.

  • Coach proactively: Regularly review individual rep timelines, paying attention to highlighted Risks and Action Items to provide timely and targeted coaching.

  • Identify trends with sorting: Use column sorting in the data table to quickly spot top performers for recognition or identify scorecards where the team might be struggling collectively.

  • Monitor adherence over time: Keep an eye on the "previous period" comparison for playbook adherence to understand trends and the impact of any coaching or process changes.

FAQ

Why are some of my scorecards not showing in the new overview?

  • By default, the view only displays scorecards that have existing data. This helps keep the interface clean. If a scorecard has no logged calls against it, it will be hidden.

How do I add a new scorecard that doesn't have data yet?

  • You can still manually create a new pipeline/scorecard view through the standard process. It will then appear in your "Zoom-Out" overview with "0" data until calls are logged against it.

If I rename or reorder scorecards in one workspace, will it change for everyone or in other workspaces?

  • No. Customizations like renaming and reordering are specific to each workspace. Your changes in the "Sales Workspace" will not impact the "Support Workspace," for example.

Did this answer your question?