/
/
Find where Zendesk tickets and BugHerd bugs disagree
For support teams who want linked Zendesk tickets and BugHerd tasks compared to find customers left waiting, by asking their AI assistant.
On this page
Connector
Connect Zendesk, pick your AI tool and paste the prompt.
The problem
Linked tickets and bugs move at different speeds
Once a Zendesk ticket is linked to a BugHerd task, the two drift apart. Bugs get fixed with the customer never told, tickets close while the bug is open, and links point at tickets that no longer exist.
Without PopdockAI
- List BugHerd tasks that mention a ticket
- Open each ticket in Zendesk
- Compare the two statuses by hand
- Find broken links only when someone clicks them
With PopdockAI
- Every linked task, feedback item and archived task is read
- Each pair is sorted by what is out of step
- Waiting customers are ordered longest first
- Nothing is changed in either system
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** For the BugHerd project `{project-name}`, compare every task linked to a Zendesk ticket with that ticket and report where they disagree.
How the two systems are linked: a BugHerd task created from a Zendesk ticket carries "zendesk:<ticket id>" in its external-id, and the ticket gets a private note naming the task. When a ticket is raised from a BugHerd task, the task gets a comment naming the ticket. A ticket is open when its status is new, open, pending or hold; solved and closed are finished.
**Step 1: Read the links**
Call `bugherd-get-projects` with `name.contains` set to `{project-name}`. If nothing matches, say so and stop. If several match, list their names and project-id values and ask which one; do not guess. Then call `bugherd-get-tasks`, `bugherd-get-feedback` and `bugherd-get-archived-tasks` with `project-id` and `max-records` 500. Keep tasks whose external-id starts with "zendesk:". For each, call `zendesk-get-ticket` with `ticket-id`.
**Step 2: Classify**
* **Customer waiting on a fix:** ticket open, task open. Show how long since the ticket was created.
* **Fixed, customer not told:** task finished, ticket open.
* **Ticket closed, bug still open:** the customer may come back.
* **In step:** both finished (give a count).
* **Broken link:** the ticket id does not exist.
**Step 3: Report**
One table per class: ticket id, subject, requester, ticket status, task number, task status, severity, days open. Order "customer waiting" by days open, longest first.
**Rules & Guidelines:**
* Tools named bugherd-... are on the bugherd MCP server; tools named zendesk-... are on the zendesk MCP server. If either set of tools is missing, say which server is not connected and stop.
* This prompt is read-only. Do not call any BugHerd write tool (`bugherd-add-task`, `bugherd-add-feedback`, `bugherd-update-task`, `bugherd-move-task`, `bugherd-add-comment`, `bugherd-add-attachment-from-url`, `bugherd-add-project`, `bugherd-update-project`, `bugherd-add-project-member`, `bugherd-add-guest-to-project`) or any Zendesk write tool (`zendesk-add-ticket`, `zendesk-update-ticket`, `zendesk-add-ticket-comment`, `zendesk-make-ticket-comment-private`, `zendesk-add-user`, `zendesk-update-user`, `zendesk-add-organization`, `zendesk-update-organization`, `zendesk-add-organization-member`, `zendesk-add-group`, `zendesk-update-group`, `zendesk-add-group-member`). To tell customers about fixes, use `notify-customers-of-fixes`.
**Validation:**
* If no task links to a ticket, say so and stop.Who it's for
One answer, three teams that use it
Support team leads
Tell customers their bug is fixed
See tickets whose BugHerd task is finished but whose customer has not been told, so agents can follow up.
Which customers on the Fabrikam storefront BugHerd project have a fixed bug but an open ticket?
Web project managers
Find tickets closed on open bugs
Spot tickets marked solved while the bug is still open, before the customer reports it again.
List Zendesk tickets closed while their Northwind website BugHerd task is still open.
Support operations
Clean up broken ticket links
See BugHerd tasks pointing at tickets that no longer exist, along with every pair that is in step.
Reconcile the Contoso intranet BugHerd project with Zendesk and show me any broken links.
How it works
What PopdockAI does when you ask
You name the BugHerd project, and your AI assistant compares every linked task with its Zendesk ticket. It groups the results into tables and changes nothing.
01
Ask
You name the BugHerd project.
02
Read
It reads every BugHerd task linked to a Zendesk ticket, then each ticket.
03
Classify
It sorts pairs into waiting, fixed but not told, closed too early, in step and broken links.
04
Report
You get one table per group, longest waiting first, with nothing changed.
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.
bugherd-get-projects
bugherd-get-tasks
bugherd-get-feedback
bugherd-get-archived-tasks
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
Catch waiting customers before they chase you
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)
