Connectors

/

Chorus

/

Chorus license utilization audit
Report

Find idle Chorus licenses before renewal

For IT and sales operations teams who want to know which Chorus licenses are not being used, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Chorus license utilization audit
Which Chorus licenses haven't been used in the last 60 days?
7 of 85 active Chorus users have recorded nothing in the last 60 days. - Idle: 5 users with zero conversations and zero emails - Email only: 2 users capture email but record no calls, so they are not idle - Too new: Alex Morgan was added 12 days ago - No team: 4 users are on no team Want the list of the 5 idle users?
Chorus
Sample figures. Your results come from your own account.
chorus-get-users
chorus-get-engagements
chorus-get-emails
chorus-get-team-members

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Chorus

Chorus
Run it on your own Chorus data.

Connect Chorus, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Idle Chorus licenses renew unnoticed

Chorus licenses get assigned and then forgotten when people change roles or stop recording. Finding the idle ones means checking each user's calls, captured emails and team membership before renewal comes around.

Without PopdockAI

  • Export active Chorus users
  • Count each person's calls by hand
  • Check captured emails for anyone with none
  • Cross check team membership

With PopdockAI

  • Each active user's conversations are counted
  • Captured emails are checked so email only users are not idle
  • Users on no team are listed
  • New users are called too new to judge, nothing changed

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Audit Chorus licence utilisation over the last `{lookback-days}` days (default 60): which active users hold a licence but are not recording conversations, and which are not attached to any team.

**Step 1: List the users**

Call `chorus-get-users` with `active` set to true and a generous `max-records`. If `{license-type}` was supplied, also set `license-type` to it. Keep `name`, `email`, `role`, `license-type`, `title`, `created-on` and `user-id`.

**Step 2: Measure conversation activity**

For each user, call `chorus-get-engagements` with `user-email` set to their email and `date.from` set to the start of the window. Count the conversations and note the most recent `date`. This is the usage signal that decides the audit.

**Step 3: Measure email capture**

For users with no conversations, call `chorus-get-emails` with `owner-email` set to their email and `sent-time.from` set to the start of the window. Someone with captured emails and no calls is using Chorus differently, not sitting idle, and must not be reported as unused.

**Step 4: Check team attachment**

For each user, call `chorus-get-team-members` with `user-id` set to theirs. Anyone with no team is invisible to team level reporting even if they are active.

**Step 5: Report**

Produce:

* **Unused licences** - active users with no conversations and no emails in the window, as a table of name, email, role, licence type, created date and days since anything. Sort by longest idle first, since a licence that has never been used at all is the clearest recovery.
* **Calls only, emails only** - users active on one channel and not the other, which is a configuration question rather than a licence question.
* **Not on a team** - users attached to no team, with their role.
* **Summary** - total active users, how many are unused, and by licence type.
* **Recommendation** - which licences to reclaim and which users to ask about first.

**Rules & Guidelines:**

* This is read only. Do not call any tool that creates, updates or exports, and do not propose deactivating anyone, since nothing here can do that.
* A newly created user with no activity is not an unused licence. Check `created-on` and exclude anyone created inside the window from the reclaim list, calling them out separately as too new to judge.
* Report zero as zero. Do not omit a user because their count is empty.

**Validation:**

* If `{license-type}` matches no user, list the licence types that are in use and stop.
* If the user list comes back at exactly the `max-records` limit, say the list may be truncated rather than presenting it as complete.

Who it's for

One answer, three teams that use it

IT administrators

Find seats to reclaim

Idle users are listed with their counts, so reclaiming a seat is backed by data.

Which Chorus users have had no conversations or captured emails in the last 90 days?

Revenue operations

Right-size before renewal

Know how many seats are really used before the Chorus renewal conversation.

Audit Chorus license use for the last 60 days ahead of our renewal.

Sales managers

Spot reps who stopped recording

See who on the team has no calls recorded and who sits on no team.

Which Chorus users are on no team or have no recorded calls this quarter?

How it works

What PopdockAI does when you ask

You choose how far back to look and your AI assistant audits Chorus license use. Zero counts are shown as zero and a truncated user list is flagged.

01

Ask

You choose how far back to look, and optionally a license type.

Your AI tool

02

Count

It counts each active user's conversations, then captured emails for those with none.

chorus-get-users
chorus-get-engagements
chorus-get-emails

03

Teams

It checks team membership and lists users on no team.

chorus-get-team-members

04

Report

You get idle users, users too new to judge and users on no team.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Chorus and one secure connection to your AI tool. No code, no exports.

get-data

chorus-get-users

Returns Chorus users, with their name, email, title, role, license type and whether the account is active. Use it for license reviews and for matching reps to their conversations.
get-data

chorus-get-engagements

Returns recorded calls and meetings from Chorus, with the subject, date, duration, participants and the account each conversation relates to. Filter by date range, owner or account to pull the conversations behind a deal or a period.
get-data

chorus-get-emails

Returns emails captured by Chorus, including the subject, body, sender, owner, account and sent time. Filter by account or date range to read the written trail alongside the calls.
get-data

chorus-get-team-members

Returns which Chorus users belong to which team. Pair it with Get Teams and Get Users to roll conversation and coaching data up by team.
Read only.Nothing in Chorus Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

Reclaim idle licenses with evidence

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation