/
/
See who is working on a customer ticket
For developers and support leads who want the Azure DevOps work behind a Zendesk ticket, just by asking their AI assistant.
On this page
Connector
Connect Azure DevOps, pick your AI tool and paste the prompt.
The problem
Customers are told nothing is happening when it is
A developer or support lead asked about a ticket searches Zendesk for it, then hunts through Azure DevOps to see whether anyone is working on it. The work item is often missed, so the customer is told nothing is happening.
Without PopdockAI
- Read the ticket and its comments in Zendesk
- Search Azure DevOps for any reference to it
- Check the state and owner of each match
- Miss the work item and tell the customer nothing
With PopdockAI
- The ticket and its comments are read
- Work items that reference it are found
- State and owner are reported for each
- Quoted links are kept apart from title matches, and untracked is said plainly
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find the Azure DevOps work items that track Zendesk ticket `{ticket-id}` and report where the engineering work stands.
**Step 1: Read the ticket (zendesk server)**
Call `zendesk-get-ticket` with `ticket-id` set to `{ticket-id}`. Note the ticket subject, status, priority, requester email and organization name. If no ticket comes back, say so and stop.
Call `zendesk-get-ticket-comment` with `ticket-id` set to `{ticket-id}` and read the comments for any Azure DevOps work item numbers (for example "AB#1234", "work item 1234" or a dev.azure.com link). Keep the numbers you find.
**Step 2: Find the work items (azure-devops server)**
For every work item number found, call `azure-devops-get-work-item` with `id` set to that number.
Then call `azure-devops-get-work-item` with `title.contains` set to `{ticket-id}`, and again with `title.contains` set to the most distinctive words of the ticket subject. Zendesk and Azure DevOps share no key, so a title match is a candidate, not a fact: mark it "possible" and a number found in a comment "confirmed".
For each work item you keep, call `azure-devops-get-work-item-comment` with `work-item-id` set to its id and note whether the ticket is mentioned.
**Step 3: Report**
Give the ticket in one line, then a table of work items: id, title, type, state, assigned-to, priority, changed-date, and "confirmed" or "possible". End with one sentence: is engineering tracking this ticket, and who owns it.
**Rules & Guidelines:**
* `azure-devops-*` tools belong to the azure-devops server and `zendesk-*` tools to the zendesk server. Both servers must be connected; if a tool is missing, say which server is not connected and stop.
* This prompt is read-only. Never call `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` or `zendesk-add-group-member`. Azure DevOps has no write tools here.
* Pass `max-records` set to `{max-records}` on every call (default 50 when empty).
**Validation:**
* If no work item matches, report the ticket as untracked in Azure DevOps. Do not guess.
* If more than 10 candidates match on title alone, show the 10 most recently changed and say how many were left out.
* Dates come from two systems; show both as returned and do not convert time zones.
Who it's for
One answer, three teams that use it
Support leads
Give customers a real update
See the state and owner of the work items behind a ticket, so your reply is accurate.
Is engineering working on Zendesk ticket 5123? Check Azure DevOps.
Developers
Find the work behind a ticket you were asked about
Confirmed links and possible matches are shown separately, so you know which item is really it.
Which Azure DevOps work items reference Zendesk ticket 4790?
Customer success managers
Follow escalations to engineering
Know whether a customer's issue has a work item and who owns it before your next call.
Who owns the Azure DevOps work for Zendesk ticket 4688, and what state is it in?
How it works
What PopdockAI does when you ask
You give a ticket id and your AI assistant finds the engineering work behind it. Nothing in Zendesk is changed.
01
Ask
You give the Zendesk ticket id.
02
Read
It reads the ticket and its comments.
03
Search
It finds Azure DevOps work items that reference it.
04
Report
You get each work item with state and owner, and the strength of each link.
What PopdockAI provides
The tools behind the answer
Ready made tools for Azure DevOps and one secure connection to your AI tool. No code, no exports.
zendesk-get-ticket
zendesk-get-ticket-comment
azure-devops-get-work-item
azure-devops-get-work-item-comment
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
Tell customers who is working on their ticket
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)
