Connectors

/

Chorus

/

Chorus sales follow-up on bad Zendesk ratings
Report
Cross-Connector

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.

Try PopdockAI free
Get a live demo
Chorus sales follow-up on bad Zendesk ratings
Which customers gave us a bad Zendesk rating in the last 30 days, and has sales talked to them since?
9 accounts gave bad ratings, and 4 have had no conversation since. - Worst: Contoso, 3 bad ratings, reason slow response, no call since - Fabrikam: 2 bad ratings, Jordan Lee called on 3 October and it came up - Partial match: Northwind matched Northwind Traders in Chorus Want the full table with the 4 accounts nobody has called?
Chorus
Sample figures. Your results come from your own account.
zendesk-get-satisfaction-rating
zendesk-get-ticket
chorus-get-engagements
chorus-get-conversation-participants

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

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.

Prompt
**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.

Your AI tool

02

Ratings

It reads bad Zendesk satisfaction ratings and groups them by organization.

zendesk-get-satisfaction-rating
zendesk-get-ticket

03

Calls

It checks Chorus for conversations with each account since the earliest bad rating.

chorus-get-engagements
chorus-get-conversation-participants

04

Report

You get a worst-first table and the accounts nobody has spoken to.

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

zendesk-get-satisfaction-rating

Returns Zendesk customer satisfaction (CSAT) ratings with the score, the customer's comment and reason, and the ticket, agent and group they relate to. Filter by score or date to find bad ratings.
get-data

zendesk-get-ticket

Returns Zendesk support tickets with their status, priority, requester, assignee, group and organization. Filter by status, priority, assignee, group or dates to find the tickets you need.
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-conversation-participants

Returns the people who took part in Chorus conversations, with their name, email, title and company. Use it to see who was on a call, and which side they were on.
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

Unhappy customers hear from their account team quickly

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