Connectors

/

Chorus

/

Add a Chorus call summary to a Zendesk ticket
Write
Cross-Connector

Get what customers said on Chorus calls onto their Zendesk tickets

For support teams who want the points a customer raised on a sales call added to the right Zendesk ticket, privately, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Add a Chorus call summary to a Zendesk ticket
Add what Dana from Northwind Traders said about the sync errors on yesterday's Chorus call to Zendesk ticket 48213.
The call and ticket both belong to Northwind Traders, as Dana is on the call. - Heading: From Chorus call on 6 October with Jordan Lee - Point: sync errors started after the 2 October update - Point: about 40 orders a day are affected - Commitment: Jordan promised an update by Friday Shall I add this to ticket 48213 as a private note?
Chorus
Sample figures. Your results come from your own account.
zendesk-get-ticket
chorus-get-engagements
chorus-get-conversation-participants
zendesk-get-ticket-comment

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

What customers say on sales calls never reaches the ticket

Customers often mention a support problem on a sales call, but the agent working the Zendesk ticket never hears about it. Passing it on means finding the call, picking out the relevant points and adding a note without emailing the customer by mistake.

Without PopdockAI

  • Find the right Chorus call for the customer
  • Pick out the points that matter to the ticket
  • Check the call and ticket are the same customer
  • Risk a public reply instead of an internal note

With PopdockAI

  • The ticket and call are read and checked for the same customer
  • A draft note keeps only the points that bear on the ticket
  • Nothing is added until you confirm
  • The note is always private and read back to prove it

The prompt

Use this prompt

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

Prompt
**Objective:** Add what was said about Zendesk ticket `{ticket-id}` on Chorus conversation `{conversation-id}` to the ticket as a private internal note.

**Step 1: Read both sides**

Call `zendesk-get-ticket` with ticket-id set to `{ticket-id}` for subject, status, requester-email and organization-name. Call `chorus-get-engagements` with conversation-id set to `{conversation-id}` for date, subject, user-name, account-name and meeting-summary. If either returns nothing, say which and stop.

**Step 2: Check they belong together**

Call `chorus-get-conversation-participants` with conversation-id set to `{conversation-id}`. They belong together if the ticket's requester-email is a participant (compare case-insensitively), or if the account-name and organization-name clearly name the same company. If neither holds, say so and ask me to confirm before going on.

**Step 3: Draft and confirm**

Draft a note for support agents: a heading line "From Chorus call on <date> with <user-name>", then only the points in the meeting-summary that bear on the ticket's subject, as short bullets, and any commitment made to the customer on the call. Leave out unrelated sales topics. Show the draft and wait for my explicit confirmation.

**Step 4: Write and confirm**

Call `zendesk-add-ticket-comment` once, with ticket-id `{ticket-id}`, body set to the note and public set to false. Then call `zendesk-get-ticket-comment` with ticket-id `{ticket-id}` and public false and confirm the note is there and is not public.

**Rules & Guidelines:**

* `zendesk-get-ticket`, `zendesk-add-ticket-comment` and `zendesk-get-ticket-comment` are on the zendesk server. `chorus-get-engagements` and `chorus-get-conversation-participants` are on the chorus server.
* `zendesk-add-ticket-comment` is the only write, called once, after confirmation, always with public false. A public comment would email the customer.
* Do NOT call `zendesk-update-ticket`, `zendesk-make-ticket-comment-private` or any chorus add, update or export tool.

**Validation:**

* If the meeting-summary does not mention anything related to the ticket, say so and do not write a note.
* If the ticket is closed, say that closed tickets cannot take new comments and stop.

Who it's for

One answer, three teams that use it

Support agents

Get call context on your ticket

What the customer told sales lands as a private note on the ticket you are working, so you do not ask them to repeat it.

Add what Contoso said about the login errors on Tuesday's Chorus call to Zendesk ticket 51734.

Account executives

Hand support issues over cleanly

When a buyer raises a problem on your call, pass the relevant points to support without writing an email.

Put the support points from my Chorus call with Fabrikam today on their open Zendesk ticket 50211.

Support team leads

Keep commitments visible to the team

Any commitment made on the call is captured in the note, so the next agent knows what was promised.

Summarise the commitments from the Chorus call with Northwind Traders into a private note on Zendesk ticket 48990.

How it works

What PopdockAI does when you ask

You name the Zendesk ticket and the Chorus conversation, and your AI assistant drafts an internal note. It asks you if the customer match is unclear and adds nothing until you confirm.

01

Ask

You name the Zendesk ticket and the Chorus conversation.

Your AI tool

02

Check

It reads both and confirms they belong to the same customer by email or company.

zendesk-get-ticket
chorus-get-engagements
chorus-get-conversation-participants

03

Confirm

You see a draft note with only the points that bear on the ticket.

No items found.

04

Add

It adds the note as private and reads it back to confirm it is not public.

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-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.
get-data

zendesk-get-ticket-comment

Returns the comments on a Zendesk ticket, both public replies and internal notes, with their author and when they were posted.
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

Agents see what the customer said on the call

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