Gong Utilization & Call Status Dashboard

Report 1 · Feature Utilization

Drop Gong usage CSV(s) here

or click to browse — upload one file for a snapshot, two or more for week-over-week comparison

Report 2 · Call Status

Drop the Call Status report CSV here

or click to browse — powers the Recording tabs. One snapshot file; no week-over-week needed.

How to pull the Feature Utilization report

How to pull the Call Status report

📊

Upload a Gong Feature Utilization export and/or a Call Status report above — each lights up its own set of tabs.

New to this? Open the “How to pull” guides under each upload box above.

View:

Seat filter:

Manager:

General Usage

Call Review

Deal Usage

Coaching

Engage

Forecast

Trainings & Practice

Leaderboard

Recording by User

Recording Reasons

% of selected people using Gong capabilities

Adoption rate by capability across the filtered population.

Days used Gong — distribution

How many people fall into each band of days used.

Seat mix

Paid seats by product line.

Team members

Per-user activity snapshot.

Top reviewers

Users by number of calls reviewed.

Call review usage by user

Deal capability adoption

% of filtered users with at least one action in each deal capability.

Deal usage by user

Manager coaching activity

Managers ranked by coaching actions (comments, scorecards, listens to team calls).

Coaching usage by manager

Engage capability adoption

% of Engage seat holders using each capability.

Engage usage by user

Forecast capability adoption

% of Forecast seat holders using each capability.

Forecast activity by user

Stacked days across submit, review, and analytics actions.

Forecast usage by user

AI feature adoption

% of the filtered population using each newer Gong AI capability.

AI Trainer activity by user

Practices started, trainings started, and trainings submitted per user.

AI usage by user

Power-user leaderboard

Composite score = days used + 0.5×(calls reviewed + listened) + 0.25×(engage actions).

Inactive / at-risk seats

Paid seat holders with 0 days used in the selected period.

Pulling the Gong Feature Utilization Report

Where to go, what to select, and how to set the timeframe so this dashboard can read it.

Who can run it: Tech admin or Business admin. (Non-admins can pull a reduced version with less detail on the Team page.) A paid Gong subscription is required.

Navigate to: Admin center → Settings → Reports → Feature utilization

Choose the format. Leave Send previous format unchecked to get the current format. Only check it if you specifically need the legacy summarized/detailed layout.
Select the team you want data for (the whole org, or a specific team/cohort).
(Previous format only) choose Summarized for an overall adoption picture or Detailed for per-feature breakdowns.
Set the timeframe — this is the important part. See the two approaches below.
Click Send report via email. Gong delivers a .csv file. Drop that CSV into the uploader at the top of this dashboard.

Standard

Last 30 days (snapshot)

The default. Best for a point-in-time read on adoption.

Pick Last 30 days (or the equivalent preset) for the timeframe. Each record summarizes a person's actions across that whole window.

Good for a one-off health check or QBR-style snapshot.
Smooths out day-to-day noise — light users still register activity.
Upload the single CSV and view it under Latest snapshot.
Limitation: rolling 30-day windows overlap, so you can't cleanly compare two of them to measure change.

Recommended for trending

Week-over-week (custom dates)

Discrete, non-overlapping weeks so you can track movement.

Instead of the 30-day preset, use specific start and end dates and pull one report per week, keeping the windows the same length and non-overlapping.

Use a consistent 7-day window — e.g. Mon–Sun — every week.
Pull each week separately: Week A = Jun 2–8, Week B = Jun 9–15, etc. Don't let the ranges overlap.
Run it on the same weekday each time (e.g. every Monday for the prior week) so the cadence stays clean.
Name files so the order is obvious (e.g. gong_2026-06-02.csv, gong_2026-06-09.csv).
Upload two or more weekly CSVs here and switch View to Week-over-week (latest vs prior) to see deltas.

⚠️ 30-day vs. weekly — don't mix them when trending

Counts scale with the length of the window, so a 30-day pull and a 7-day pull aren't comparable. For the week-over-week deltas in this dashboard to be meaningful, every file you compare must cover the same number of days. Pick one cadence (ideally weekly with fixed Mon–Sun ranges) and stick to it. Use the 30-day pull only for standalone snapshots, not as one side of a comparison.

Quick reference

Goal	Timeframe to select	How to upload here
Point-in-time adoption read	Last 30 days (preset)	One CSV → Latest snapshot
Track change over time	Custom dates, fixed 7-day weeks, non-overlapping	2+ CSVs → Week-over-week
Per-feature deep dive (legacy)	Check Send previous format → Detailed	One CSV → Latest snapshot

Recording outcomes

Every calendar event and call by final status.

Most not-recorded — by organizer

Top 12 users by meetings not captured.

Team:

Only users with not-recorded meetings

Recording status by user

Click a column header to sort. Top reason = the user's most frequent not-recorded reason.

Meeting-skip reasons

Why meetings were never scheduled for capture.

Call-skip reasons

Why a recording attempt failed (aborted).

Meeting-skip reasons — detail

Each reason with its description, share of events, and a recommended action.

Call-skip reasons — detail

Aborted recordings by reason.

Pulling the Gong Call Status Report

The report that powers the Recording tabs — where to go, what to select, and what each status means.

Who can run it: Tech admin or Business admin. You need the Calls Data permission enabled in your permission profile. Available on any Gong plan.

Navigate to: Admin center → Settings → Reports → Call Status

Open Admin center → Settings → Reports → Call status.
In the Call status dialog, choose which team's calls to include (whole org or a specific team — works for large teams of 200+).
Select the timeframe for the report.
Click EMAIL REPORT. Gong emails a self-expiring link to the .csv; the link is valid for 30 days. (Data from the previous 24 hours may not appear yet.)
Download the CSV and drop it into the Call Status uploader at the top of this dashboard.

Note: the current report includes meetings and extra call data. Email old report generates the legacy version, which has different columns — use the current report for this dashboard.

What's included

Telephony calls: all recorded calls.
Meetings (web conferences via a calendar provider): recorded meetings; meetings that weren't recorded (privacy settings, exclusion rules, consent, technical issues); cancelled / didn't-happen meetings; and meetings organized by your company or by external participants.

Use it to answer

What's the status of company calls — recorded, skipped, cancelled, or not recorded.
Which calls weren't scheduled to record (external, private, consent not used).
Whether calls are recording as expected, or being missed due to training or technical issues.
Consent opt-out rate.

Status values

The Status column drives the recording KPIs on the Recording tabs.

Status	Meaning
COMPLETED	The call was successfully recorded.
ABORTED	Gong was unable to record the call (see the Call skip code).
CANCELLED	The call was cancelled, or the host chose not to record.
PURGED	The recording was deleted — manually, in bulk, by a rule, or by retention policy.
NOT_SCHEDULED	The call wasn't scheduled to be recorded (see the Meeting skip code).