/
/
See a customer's tickets and website bugs in one view
For support teams who want a customer's Zendesk tickets and BugHerd bug reports side by side, just by asking their AI assistant.
On this page
Connector
Connect Zendesk, pick your AI tool and paste the prompt.
The problem
Support sees the tickets but not the website bugs
When a customer calls about the website, support sees their Zendesk tickets but not the bugs they reported in BugHerd. Searching both systems by email, one person at a time, hides the fact that the same page keeps breaking for the whole organization.
Without PopdockAI
- Search Zendesk for the customer's tickets
- Search BugHerd by email for each colleague
- Match tickets to bugs by hand
- Miss that the same page keeps failing
With PopdockAI
- Tickets and BugHerd reports are read for everyone in scope
- Linked tickets and bugs are shown with both statuses
- Repeating pages or problems are called out
- 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:** Show the website bugs and support tickets of the customer `{email}`, or of everyone in the Zendesk organization `{organization-name}`, over the last `{lookback-days}` days (default 180).
**Step 1: Who is in scope**
* If `{email}` is given, the scope is that address.
* Otherwise call `zendesk-get-organization-member` with `organization-name` set to `{organization-name}` and take every user-email. If neither is given, ask for one and stop.
**Step 2: Zendesk side**
For an email, call `zendesk-get-ticket` with `requester-email` and `created.from` set to the start of the period. For an organization, call `zendesk-get-ticket` with `organization-name` and `created.from`.
**Step 3: BugHerd side**
For each email in scope (up to 25), call `bugherd-get-tasks`, `bugherd-get-feedback` and `bugherd-get-archived-tasks` with `requester-email` and `created.from`.
**Step 4: Report**
1. **Summary:** tickets (open and solved) and BugHerd reports (open and finished).
2. **Linked:** tickets whose BugHerd task is known (external-id "zendesk:<ticket id>"), with both statuses.
3. **Open tickets:** id, subject, status, priority, created.
4. **Open bugs:** task number, title, severity, status, page.
5. **Pattern:** one or two sentences if the same page or problem keeps coming up.
**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`).
**Validation:**
* If nothing is found on either side, say so.Who it's for
One answer, three teams that use it
Support agents
Know the full story before you answer
See a customer's open tickets and the bugs they reported in BugHerd together, so your reply covers everything they have raised.
What has priya@contoso.com raised in Zendesk and BugHerd in the last 60 days?
Account managers
See every website problem an account has hit
Before a check in call, review the tickets and bug reports across everyone at the organization, with repeating problems called out.
Summarize the Zendesk tickets and BugHerd bugs for everyone at Fabrikam over the last six months.
Web project managers
Spot the page that keeps breaking
See when the same page or problem keeps coming up for one customer across tickets and bug reports, so you can fix it once.
Is any page coming up again and again in Northwind Traders tickets and BugHerd bugs this quarter?
How it works
What PopdockAI does when you ask
You give a customer email or a Zendesk organization and a period, and your AI assistant reads both systems for the people in scope. It reports the combined history and changes nothing.
01
Ask
You give a customer email or a Zendesk organization and a period.
02
Scope
It finds the people in scope, reading the organization's members from Zendesk when needed.
03
Read
It pulls their Zendesk tickets and their BugHerd tasks, feedback and archived tasks.
04
Report
You get open and solved counts, linked pairs, open items and any repeating pattern, 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.
zendesk-get-organization-member
zendesk-get-ticket
bugherd-get-tasks
bugherd-get-feedback
bugherd-get-archived-tasks
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
A customer's whole website history before you reply
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)
