/
/
Clear support problems before your Salesforce deals close
For sales owners who want to know about unsolved Zendesk tickets on customers with deals closing soon, by asking their AI assistant.
On this page
Connector
Connect Zendesk, pick your AI tool and paste the prompt.
The problem
Deals stall on tickets the sales owner never heard about
A deal about to close in Salesforce can stall on an unsolved Zendesk ticket the owner never heard about. Finding them means matching each opportunity's account to an organization and checking its tickets, which rarely happens late in the quarter.
Without PopdockAI
- List deals closing soon in Salesforce
- Find each account's Zendesk organization
- Check its open tickets one by one
- Hear about the problem on the closing call
With PopdockAI
- Closing opportunities are read for the window you give
- Accounts are matched by id, exact name or domain
- Unsolved tickets are counted and urgent ones listed
- Unmatched deals are reported 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:** For open Salesforce opportunities closing in the next {close-within-days} days (default 60) with an amount of at least {min-amount} (default: any amount), find unsolved Zendesk tickets on the same customer so the sales owner can deal with them before close.
**Step 1: Find open opportunities in Salesforce**
Call `salesforce-get-opportunity` with `closed` set to false, `close-date.from` set to today and `close-date.to` set to today plus {close-within-days} days (default 60). If {min-amount} is given, also set `amount.min` to it. Keep `opportunity-id`, `name`, `account-id`, `account-name`, `amount`, `stage`, `close-date` and `owner`. If nothing comes back, say so and stop.
For each distinct `account-id`, call `salesforce-get-account` with `account-id` to get `name` and `website` for matching.
**Step 2: Match each account in Zendesk**
**How to match a Salesforce account to a Zendesk organization (use this order, stop at the first hit):**
1. Call `zendesk-get-organization` with `external-id` set to the Salesforce `account-id`.
2. If nothing comes back, call `zendesk-get-organization` with `name` set to the Salesforce account `name` exactly.
3. If still nothing, take the domain from the account's `website` (strip `http://`, `https://`, `www.` and any path) and call `zendesk-get-organization` with `domain-names.contains` set to it.
4. If more than one organization matches at any step, list them and treat the account as ambiguous rather than guessing.
5. If none match, report the account as "No Zendesk organization found" and continue with the next account.
Once matched, use the Zendesk organization's own `name` (not the Salesforce account name) as `organization-name` on `zendesk-get-ticket`, since the two systems can spell the company differently.
**Step 3: Pull unsolved tickets**
Zendesk unsolved tickets are those with status `new`, `open`, `pending` or `hold`. The `status` filter on `zendesk-get-ticket` takes one value, so call it once per status and combine the results.
**Step 4: Report**
One table, one row per opportunity, sorted by `close-date` ascending:
| Opportunity | Account | Amount | Stage | Close date | Owner | Unsolved tickets | Urgent/high | Oldest unsolved (days) |
Then, for every opportunity with at least one urgent or high unsolved ticket, list those tickets (`ticket-id`, `subject`, `priority`, `assignee-name`) under the opportunity name. Opportunities whose account has no Zendesk organization go in a final "Not matched" list.
**Rules & Guidelines:**
* Salesforce tools start with "salesforce-" and come from the Salesforce MCP server. Zendesk tools start with "zendesk-" and come from the Zendesk MCP server. Both servers must be connected.
* This prompt is read-only. Do NOT call any write tool on either server, including `salesforce-add-task`, `salesforce-update-task`, `salesforce-add-case`, `salesforce-update-case`, `salesforce-update-account`, `salesforce-update-opportunity`, `zendesk-add-ticket`, `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-update-organization` or `zendesk-update-user`.
* Several opportunities can share one account. Fetch that account's tickets once and reuse them.
**Validation:**
* If `amount` is blank, show it as "No amount" and keep the row.
* If the opportunity's `account-id` is blank, report it as "No account on opportunity" and skip the Zendesk step for it.Who it's for
One answer, three teams that use it
Account executives
Know about support issues before your call
See unsolved and urgent tickets on the deals you are closing, so you can raise them first.
Do any of my Salesforce deals closing this month have unsolved Zendesk tickets?
Sales managers
Protect the quarter's closing deals
Check every deal closing in the window for support problems, with urgent tickets and assignees listed.
Which opportunities closing in the next 30 days over 25,000 have urgent Zendesk tickets?
Support managers
Clear tickets on deals about to close
Know which unsolved tickets sit on accounts with deals closing soon, so your team can clear them first.
List the Zendesk tickets on accounts with Salesforce deals closing before quarter end.
How it works
What PopdockAI does when you ask
You give a closing window, and your AI assistant checks each closing deal for unsolved Zendesk tickets. It reports one table by close date and changes nothing.
01
Ask
You give a closing window, and optionally a minimum amount.
02
Match
It reads closing opportunities and matches each account to a Zendesk organization.
03
Count
It counts unsolved tickets per opportunity and lists urgent and high ones.
04
Report
You get one table by close date, plus opportunities not matched.
What PopdockAI provides
The tools behind the answer
Ready made tools for Zendesk and one secure connection to your AI tool. No code, no exports.
salesforce-get-opportunity
salesforce-get-account
zendesk-get-organization
zendesk-get-ticket
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
Clear support problems before the deal closes
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)
