/
/
Know what sales told the customer before you answer the ticket
For support agents who want the Chorus calls and emails behind a HubSpot ticket, by asking their AI assistant instead of chasing sales.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Support answers tickets blind to what sales promised
Support picks up a HubSpot ticket without knowing what sales has told the customer. The calls and emails are in Chorus, so agents either chase sales for context or go in blind and repeat or contradict a promise.
Without PopdockAI
- Read the ticket and find its company
- Ask sales what was said recently
- Search Chorus calls and emails by date
- Risk contradicting a promise
With PopdockAI
- The ticket and its company are read in HubSpot
- Chorus calls and emails around the ticket dates are pulled
- Related calls and commitments are highlighted
- It paraphrases only what Chorus recorded and changes nothing
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Give me the conversation context for HubSpot ticket {ticket-id}: what was said to or by this customer in Chorus calls and emails from {window-days} days (default 14) before the ticket was opened until it was closed, or until today if it is still open.
**Step 1: Read the ticket in HubSpot**
Call `hubspot-get-tickets` with record-id = {ticket-id}. If nothing comes back, say so and stop. Note the ticket-name, ticket-description, ticket-status, priority, category, create-date, close-date and company-id.
**Step 2: Find the company**
Call `hubspot-get-companies` with record-id = the ticket's company-id and keep the company-name. If the ticket has no company-id, say "This ticket is not linked to a company, so Chorus cannot be searched" and stop after reporting the ticket.
**Step 3: Carry it across to Chorus**
The window runs from the ticket's create-date minus the window days to its close-date (or today).
* Call `chorus-get-engagements` with account-name = the company-name, date.from and date.to = the window. If nothing comes back, retry with account-name.contains using the distinctive part of the name.
* Call `chorus-get-emails` with account-name.contains set the same way and sent-time.from / sent-time.to = the window.
**Step 4: Report**
1. **Ticket:** name, status, priority, category, opened, closed, and a one-line summary of the description.
2. **Before the ticket:** conversations and emails dated before the create-date, newest first, each with a one-line digest. Flag any that raise the same problem as the ticket.
3. **During the ticket:** conversations and emails after the create-date, with the same digest.
4. **What support should know:** commitments, frustrations or open deals mentioned on the calls that bear on how this ticket is handled.
**Rules & Guidelines:**
* `hubspot-get-tickets` and `hubspot-get-companies` are on the HubSpot server. `chorus-get-engagements` and `chorus-get-emails` are on the Chorus server.
* This is read-only. Do not call any HubSpot write tool (`hubspot-add-contact`, `hubspot-update-contact`, `hubspot-add-company`, `hubspot-update-company`, `hubspot-add-deal`, `hubspot-update-deal`, `hubspot-add-deal-note`, `hubspot-add-company-note`, `hubspot-add-contact-note`, `hubspot-add-ticket`, `hubspot-update-ticket`, `hubspot-add-ticket-note`) or any Chorus write tool (`chorus-add-moment`, `chorus-update-moment`, `chorus-add-playlist-moment`, `chorus-update-playlist-moment`, `chorus-create-playlist`, `chorus-update-playlist`, `chorus-export-recordings`, `chorus-export-scorecards`).
* Paraphrase from the meeting-summary and email body only. Do not invent what was said.
**Validation:**
* If Chorus returns nothing in the window, say "No Chorus conversations with this company between <from> and <to>", noting that Chorus may spell the account name differently.
* If the email body is empty or private, list the email by subject and date only.Who it's for
One answer, three teams that use it
Support agents
Answer with sales context
See what was said before and during the ticket, so your reply matches what the customer was told.
What did sales discuss with Contoso around HubSpot ticket 10442?
Support managers
Check promises before escalating
Commitments or frustrations from calls are called out, so escalations start informed.
Were any commitments made to Fabrikam on Chorus calls before HubSpot ticket 9877 was opened?
Customer success managers
See if a problem came up before
Calls that raised the same problem are listed, so recurring issues are spotted.
Did Northwind Traders mention this problem on any Chorus call before HubSpot ticket 9182?
How it works
What PopdockAI does when you ask
You give a HubSpot ticket ID and your AI assistant pulls the matching Chorus conversations. Both systems are only read.
01
Ask
You give the HubSpot ticket ID.
02
Read
It reads the ticket and its company in HubSpot.
03
Search
It pulls the company's Chorus calls and emails from before the ticket opened until it closed.
04
Report
You get what was said, related calls and any commitments to know about.
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.
hubspot-get-tickets
hubspot-get-companies
chorus-get-engagements
chorus-get-emails
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
Handle each ticket knowing what the customer was told
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)
