/
/
Make sure unhappy Zendesk customers hear from their account team
For sales and account teams who want to see which customers gave bad Zendesk ratings and whether anyone has spoken to them since, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Bad satisfaction ratings never reach the account team
A bad Zendesk satisfaction rating should lead to a conversation from the account team, but sales rarely sees those ratings. Checking means grouping ratings by account and searching Chorus for any call since.
Without PopdockAI
- Export bad satisfaction ratings from Zendesk
- Group them by organization by hand
- Search Chorus for a call with each one since
- Miss the accounts nobody has spoken to
With PopdockAI
- Bad ratings are read and grouped by organization or requester
- Chorus is checked for conversations since the earliest bad rating
- Accounts nobody has spoken to are listed
- Partial name matches are labelled and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find the accounts that gave a bad Zendesk satisfaction rating in the last `{lookback-days}` days (default 30) and show whether anyone has spoken to them in Chorus since, covering at most `{max-accounts}` accounts (default 15).
**Step 1: Bad ratings (Zendesk)**
Call `zendesk-get-satisfaction-rating` with score bad, created.from set to today minus `{lookback-days}` days (YYYY-MM-DD) and max-records 200. For each rating, call `zendesk-get-ticket` with its ticket-id to get organization-name, requester-email and subject. Group the ratings by organization-name; ratings with no organization group by requester-email. Keep the rating comment and date. Take the accounts with the most bad ratings first, up to the limit.
**Step 2: Sales conversations since (Chorus)**
For each account, call `chorus-get-engagements` with account-name set to the organization-name and date.from set to the date of the account's earliest bad rating, max-records 50. If nothing comes back, try account-name.contains with the most distinctive word of the name. For accounts grouped by requester-email, call `chorus-get-conversation-participants` with email set to it instead.
For each conversation found, read the meeting-summary and note whether the support experience came up.
**Step 3: Report**
Table, worst first: account, bad ratings, latest rating date, one-line reason (rating comment or ticket subject), conversations since, last conversation date and Chorus user, support raised on the call (yes, no, unclear).
Then list the accounts with bad ratings and no conversation since, as the ones the account team should contact.
**Rules & Guidelines:**
* `zendesk-get-satisfaction-rating` and `zendesk-get-ticket` are on the zendesk server. `chorus-get-engagements` and `chorus-get-conversation-participants` are on the chorus server.
* This prompt is read-only. Do NOT call `zendesk-add-ticket-comment`, `zendesk-update-ticket`, `chorus-add-moment`, `chorus-create-playlist` or any other add, update or export tool.
* Say which Chorus matches came from account-name.contains, since a partial name can match the wrong company.
**Validation:**
* If there are no bad ratings in the period, say so and stop.
* If there are no ratings at all, say satisfaction surveys may not be enabled in Zendesk.
* If Chorus has no conversations for any account, report the Zendesk side only and say so.Who it's for
One answer, three teams that use it
Account executives
Know which of your customers are unhappy
See bad ratings on your accounts and whether anyone has called since, before the renewal is at risk.
Which of my accounts gave a bad Zendesk rating this month, and have I spoken to them since?
Customer success managers
Reach out where nobody has
Accounts with no conversation since a bad rating are listed first, so you know where to start.
List customers with bad Zendesk ratings in the last 60 days that nobody has called in Chorus.
Support managers
Close the loop with sales
Show sales which accounts had a poor support experience and whether it came up on a call.
For the 10 worst Zendesk ratings this quarter, did the support experience come up on any Chorus call?
How it works
What PopdockAI does when you ask
You choose how far back to look and your AI assistant checks each unhappy account for a Chorus conversation since. The worst ratings come first.
01
Ask
You choose how far back to look and how many accounts to cover.
02
Ratings
It reads bad Zendesk satisfaction ratings and groups them by organization.
03
Calls
It checks Chorus for conversations with each account since the earliest bad rating.
04
Report
You get a worst-first table and the accounts nobody has spoken to.
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.
zendesk-get-satisfaction-rating
zendesk-get-ticket
chorus-get-engagements
chorus-get-conversation-participants
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
Unhappy customers hear from their account team quickly
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)
