/
/
Build a Chorus coaching playlist in minutes, not an afternoon
For sales managers who want a playlist of real call examples on one topic, spread across reps, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Coaching playlists take an afternoon to build
Building a coaching playlist in Chorus means searching for calls on a topic, listening for the right part and clipping each by hand. It takes hours, and playlists often feature the same rep or clips that miss the moment.
Without PopdockAI
- Search Chorus for calls on the topic
- Listen through each one for the right moment
- Clip each part by hand
- End up with the same rep over and over
With PopdockAI
- The playlist is found or created and calls on the topic found
- Up to five calls are picked across different reps
- Clip timings come from the meeting summary, approximate ones flagged
- Nothing is added until you approve
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Build a coaching playlist called `{playlist-name}` from conversations about `{topic}` in the last `{lookback-days}` days (default 60), by clipping a moment out of each one.
**Step 1: Find or create the playlist**
Call `chorus-get-playlists` with `name.contains` set to `{playlist-name}`. If exactly one matches, use its `playlist-id`. If several match, list them with owner and size and stop, asking which. If none match, call `chorus-create-playlist` with `name` set to `{playlist-name}` and a short description saying what the playlist collects, then call `chorus-get-playlists` again with `name` set to the exact name to read back the new `playlist-id`. You need that numeric id and no other tool will give it to you.
**Step 2: Find the candidate conversations**
Call `chorus-get-engagements` with `subject.contains` set to `{topic}` and `date.from` set to the start of the window. Keep the `conversation-id`, `subject`, `date`, `duration`, `user-name` and `meeting-summary` of each.
**Step 3: Choose the clips**
Pick at most five conversations. Prefer ones whose `meeting-summary` shows the topic actually being handled rather than merely mentioned, and spread them across different `user-name` values so the playlist is not one person. For each chosen conversation decide a start offset in seconds and a length in seconds, using the summary to place it; keep clips between 30 and 120 seconds. If a summary gives you no basis for an offset, say so and use the conversation's midpoint, flagged as approximate.
**Step 4: Confirm before writing**
List the proposed clips as a table: conversation subject, date, owner, start offset, length, and the description you will attach. Ask for approval and stop. Do not write anything until the answer comes back.
**Step 5: Add the moments**
Only after approval, call `chorus-add-playlist-moment` once per approved clip, with `playlist` set to the playlist id from step 1, `call-id` set to that conversation's `conversation-id`, `moment-time` set to the start offset in seconds, `moment-duration` set to the length in seconds, and `description` set to one sentence saying what the clip demonstrates. One call per clip, no retries on a call that already succeeded.
**Step 6: Report**
Say which playlist was used or created, list each clip that was added, and list any that failed with the error.
**Rules & Guidelines:**
* Writing tools allowed here are `chorus-create-playlist` and `chorus-add-playlist-moment`, and only as described. Do not call `chorus-update-playlist`, `chorus-update-playlist-moment`, `chorus-update-moment`, `chorus-add-moment`, `chorus-export-recordings` or `chorus-export-scorecards`.
* Never guess a playlist id. It comes from `chorus-get-playlists` or from reading back a playlist you just created.
* Offsets and durations are in seconds, not minutes. Say the values back in the confirmation table so a mistake is visible before it is written.
**Validation:**
* If no conversations match `{topic}`, report that and stop without creating a playlist.
* If the playlist was created but no clips are approved, say the playlist exists and is empty.
* If a moment fails to add, report the failure and do not retry blindly.Who it's for
One answer, three teams that use it
Sales managers
Give reps real examples to learn from
Build a playlist of colleagues handling a topic well, ready for the next team meeting.
Build a Chorus playlist called Discovery questions from calls in the last 30 days with strong discovery.
Sales enablement
Build training content from real calls
Clips from different reps make onboarding material that reflects how your team sells today.
Create a Chorus playlist of five calls where reps handled security objections this quarter.
Team leads
Share how others handle tough moments
Pick a hard topic and get clips across reps, so the team hears several approaches.
Make a Chorus playlist called Competitor mentions from calls in the last 90 days.
How it works
What PopdockAI does when you ask
You name the playlist, topic and time range, and your AI assistant proposes the clips. It never guesses a playlist id and adds nothing until you approve.
01
Ask
You name the playlist, the topic and how far back to look.
02
Find
It finds or creates the playlist and the conversations that handle the topic.
03
Choose
It picks up to five clips across different reps, with start and length.
04
Confirm
You approve the clips before any are added.
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.
chorus-get-playlists
chorus-create-playlist
chorus-get-engagements
chorus-add-playlist-moment
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.
The outcome
A focused coaching playlist in minutes
Related use cases
More ways to put this data to work
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.

.webp)
