/
/
Answer requesters with everything they raised in one view
For support and service desk teams who want a person's BugHerd reports and ServiceNow incidents together, just by asking their AI assistant.
On this page
Connector
Connect BugHerd, pick your AI tool and paste the prompt.
The problem
Requesters ask for updates spread across two systems
When someone asks what happened to the problems they raised, you search ServiceNow for incidents and BugHerd for tasks and feedback, each on its own screen. The same issue is often logged in both, so it gets reported twice or one finished side is missed.
Without PopdockAI
- Search ServiceNow for the person's incidents
- Search BugHerd tasks, feedback and the archive separately
- Guess which items describe the same problem
- Report duplicates or miss what was already fixed
With PopdockAI
- Incidents, tasks, feedback and archived tasks are read in one pass
- Linked items are paired and likely duplicates flagged as a judgment
- Open issues sit in one table with finished counts
- It only reads, so 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:** List everything the person with the email `{email}` has reported in the last `{lookback-days}` days (default 90), in both BugHerd and ServiceNow, and show where the two overlap.
**Step 1: ServiceNow side**
Call `servicenow-get-user` with `email` set to `{email}`. If there is no match, note "not a ServiceNow user" and skip to Step 2. Otherwise call `servicenow-get-incident` with `caller` set to the user's name and `opened.from` set to the start of the period.
**Step 2: BugHerd side**
Call `bugherd-get-tasks`, `bugherd-get-feedback` and `bugherd-get-archived-tasks`, each with `requester-email` set to `{email}` and `created.from` set to the start of the period.
**Step 3: Overlap**
How the two systems are linked: a BugHerd task created from an incident carries the incident number (INC...) in its external-id. An incident escalated from BugHerd starts its short-description with "[BugHerd <project name> #<task number>]". Mark a BugHerd task and an incident as the same issue when they are linked that way, or when their titles clearly describe the same problem (say which, and that the second is a judgment).
**Step 4: Report**
1. **Who:** name, department and VIP flag from ServiceNow when known.
2. **Open issues:** one table across both systems: system, number, title, status or state, priority or severity, opened, assigned-to.
3. **Finished in the period:** a count per system.
4. **Overlaps:** the pairs found in Step 3.
**Rules & Guidelines:**
* Tools named bugherd-... are on the bugherd MCP server; tools named servicenow-... are on the servicenow 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 ServiceNow write tool (any tool named servicenow-add-... or servicenow-update-..., including `servicenow-add-incident`, `servicenow-update-incident`, `servicenow-add-problem`, `servicenow-update-problem`, `servicenow-update-change-request`).
**Validation:**
* If neither system has anything for the email, say so and stop.Who it's for
One answer, three teams that use it
Service desk agents
Answer status questions in one reply
When a user chases their issues, give them a full answer across ServiceNow and BugHerd without searching both tools.
What has priya.shah@contoso.com raised in ServiceNow and BugHerd in the last 90 days, and what is still open?
Account managers
Prepare for client check ins
Walk into a client call knowing every issue their contact reported and which ones are already fixed.
Summarise everything tom.reyes@fabrikam.com has reported in BugHerd and ServiceNow this quarter.
Support team leads
Spot issues logged twice
See where the same problem lives in both systems, so the team stops working it in two places.
Which of jo.lee@northwindtraders.com's BugHerd tasks look like the same issue as a ServiceNow incident?
How it works
What PopdockAI does when you ask
You give the requester's email and your AI assistant reads what they raised in ServiceNow and BugHerd. It marks overlaps and tells you when a match is a judgment call.
01
Ask
You give the requester's email and, optionally, how many days to look back.
02
Read
It reads their ServiceNow incidents and their BugHerd tasks, feedback and archived tasks.
03
Match
It pairs linked items and flags likely duplicates as a judgment.
04
Report
You get open issues in one table, finished counts and the overlaps.
What PopdockAI provides
The tools behind the answer
Ready made tools for BugHerd and one secure connection to your AI tool. No code, no exports.
servicenow-get-user
servicenow-get-incident
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
One reply that covers everything they raised
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)
