Match NPS detractors to their support tickets before anyone follows up.
Match Retently NPS detractors to Freshdesk contacts and tickets, then decide who gets a reply on an open ticket, whose resolved ticket needs a second look, and who needs a call from customer success.
Which unhappy NPS customers already have a ticket with us?
Detractors
People
Who follows up
Ticket still open
6
Ticket’s agent
Resolved just before
7
Support lead
No recent ticket
12
Customer success
NPS responses Oct 19–Nov 16, 2026 · UTC dates · Read Nov 16, 15:00 UTC
Thirty of 120 NPS responses were detractors. Six of them have 8 Freshdesk tickets still open or pending, 4 of those people already past the due date, so answer on those tickets first. Seven had a ticket resolved in the two weeks before they scored, 12 have not written to support in 90 days, and 5 have no Freshdesk contact with their email.
WHERE THE RESULT GOES
Google Sheets
Export each data source report to Google Sheets, then add your analysis or checklist to the review Sheet.
Example use case
Ask. Follow up. Take the next step.
✦ AI assistantSample use case
YOU
Which unhappy NPS customers already have a ticket with us?
✦
Thirty of 120 NPS responses were detractors. Six of them have 8 Freshdesk tickets still open or pending, 4 of those people already past the due date, so answer on those tickets first. Seven had a ticket resolved in the two weeks before they scored, 12 have not written to support in 90 days, and 5 have no Freshdesk contact with their email.
01
Ticket still open · 6 detractors8 open or pending tickets · 4 people past due · 1 ticket unassignedReply on the ticket first
Each of these 6 people has at least one Freshdesk ticket with status Open or Pending. Four are past their resolution due time, including a High priority billing ticket for seats that were removed and an overdue payroll export fix. One ticket, an invoice copy request, has no agent. Their comments describe the same problems as the tickets.
NextThe agent who owns each ticket replies on it, acknowledges the score and gives a date for the fix. The support lead assigns the unassigned ticket today. Customer success holds its own email until the ticket is answered, so the customer gets one reply, not two.
02
Resolved just before they scored · 7 detractorsResolved 4 to 13 days before the response · 8 shortlisted on Updated atCheck whether the fix held
Seven people had a ticket resolved or closed in the 14 days before they answered, confirmed with each ticket’s Resolved at time. Their comments say the problem came back, the answer was slow or the ticket was marked solved without checking. An eighth person showed up on Updated at alone: that ticket was resolved in July and only edited on Nov 1, so it stays out of this group.
NextThe support lead reads the 7 ticket conversations and decides for each one whether to reopen it, follow up personally, or log the repeat problem with engineering. The agent who closed the ticket hears the outcome.
03
No recent ticket · 12 detractors5 about price · 4 missing features · 3 otherCustomer success follows up
These 12 people have no open ticket and no ticket created in the 90 days before they answered; three have only older tickets. Five comments are about price or renewal, four ask for features such as per-location overtime rules or tip pooling, and three mention onboarding videos, the mobile app and reports.
NextCustomer success contacts these accounts. Price comments go to the account owner before renewal, and feature requests go to product with the comment text. Support does not need to act.
04
No Freshdesk contact · 5 detractorsPrimary email not found · 1 colleague with an open ticketMatch by hand
Five emails match no Freshdesk contact’s primary email: one personal address, one shared front desk address and three work addresses with no contact. One of them says support was asked three times about calendar sync, and another contact at the same email domain, lakeshoreeats.com, has an open ticket about exactly that.
NextSomeone on support searches Freshdesk for these five by name and company before anyone replies. Additional contact emails are not part of the read, so check them in Freshdesk. Treat the Lakeshore Eats ticket as the likely history only after a person confirms it.
NPS responses Oct 19–Nov 16, 2026 · UTC dates · Read Nov 16, 15:00 UTC
01 · CONNECT YOUR DATA
Your tools. One place to ask.
2 of 3 Free data sources No credit card · Daily refresh
DatapipeYour project
✦Your AI assistantor a report in Sheets / Data Studio
Create your free workspace
Sign up with your company email. Your first project opens on Data sources.
Add the data sources
Choose the accounts for this use case. Authorize access and select the property or site.
Bring your question
Connect your project to a supported AI assistant, or build your source reports.
Email/password signups confirm their email first. Use Google signup with a company account if you prefer.
Retently: Paste your Retently API key from Settings > API, then click Save and check. Datapipe reads survey campaigns, responses and customers, and never changes surveys or recipients. Setup guide ↗
Freshdesk: Paste an agent’s API key from Profile Settings > View API key and enter your Freshdesk subdomain, then click Save and check. Reads follow that agent’s access, and nothing in Freshdesk is changed unless your team allows it. Setup guide ↗
Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.
02 · ASK A USEFUL QUESTION
Start with a prompt. Follow the evidence.
Copy these in order into your connected assistant. Each builds on the answer before it.
01
Find the NPS campaign and its detractors
Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.
From the connected Retently account, read Survey campaigns with Campaign name, Metric type and Responses, and tell me which campaigns use NPS. Then read NPS responses for the last 28 days with Response ID, Customer email, Campaign name, NPS score, Feedback comment and Submitted date. Keep only responses from the NPS campaigns, and count promoters (9–10), passives (7–8) and detractors (0–6) from NPS score, not from the NPS segment label. Report the NPS for the window and how many responses came from other campaigns and were left out. If the same email answered more than once, keep the latest response and tell me.
02
Match detractors to Freshdesk contacts and tickets
Read the full prompt
From the connected Freshdesk account, read Current contacts with Record ID, Name, Email and Company ID, and Current tickets with Ticket ID, Subject, Native status code, Native priority code, Requester ID, Agent ID, Resolution due at, Created at and Updated at. Read Current agents with Record ID and Name. Match each detractor’s Customer email to a contact Email after trimming and lowercasing, and list the detractors with no match separately, with any contact that shares their email domain. For each matched detractor, list tickets whose Requester ID is the contact’s Record ID. Translate status codes: 2 Open, 3 Pending, 4 Resolved, 5 Closed; if you see a code above 5, read Ticket field definitions for its label before deciding whether it counts as open. Do not count tickets from colleagues at the same company as the detractor’s own.
03
Prepare the follow-up list
Read the full prompt
Put every detractor in exactly one group. Open: at least one ticket with status Open or Pending; show the ticket IDs, the agent, and whether Resolution due at is earlier than now. Resolved just before: no open ticket, and a ticket with status Resolved or Closed updated in the 14 days before Submitted date; for each, read Ticket details and statistics by Ticket ID and keep it in this group only if Resolved at falls in those 14 days. No recent ticket: everyone else who matched, with the comment’s theme. Unmatched: no Freshdesk contact. Build one table with email, score, submitted date, comment, group, ticket IDs, agent and the suggested owner, then a short note for each owner. Treat comments as the customer’s words, not proof of cause. Draft everything here; do not reply to customers, change tickets or add notes.
Sort detractors by what support already knows and assign the follow-up.
01
Read the detractors from your NPS campaign in Retently.
02
Match each detractor to a Freshdesk contact and their tickets.
03
Sort detractors by what support already knows and assign the follow-up.
↗
Check the result at your next review.
At next week’s review, the 8 open tickets should each have a reply that mentions the feedback, and none of the 4 overdue people should still be past due. For the 7 resolved tickets, the support lead records which were reopened and why. When the next NPS survey goes out, read the same Customer emails again and count how many of the 25 matched detractors moved to passive or promoter; treat that as a signal for this group, not proof that the follow-up changed the score.
Implementation tips for this use case
Put each detractor in one group. A ticket still open or pending goes to its agent, who replies on the ticket; a resolution due time already passed makes it urgent. For people whose last ticket was resolved or closed in the 14 days before they answered, check Resolved at in Ticket details and statistics for each ticket, one ticket at a time; Updated at alone also moves when someone edits an old ticket. The support lead reviews those tickets and decides whether to reopen them. Everyone else goes to customer success, with the comment theme. Keep unmatched detractors visible for a manual search. Your team sends the replies; the assistant prepares the list.
WHEN YOU NEED MORE CONTEXT
Go a little deeper.
The method and reporting checks behind this example.
How to match Retently NPS detractors to Freshdesk tickets
Read the detractors from your NPS campaign in Retently.
Add the Retently and Freshdesk accounts to one project. In Retently, read Survey campaigns with Campaign name and Metric type, and keep only campaigns whose metric is NPS; CSAT and CES campaigns use other scales. Then read NPS responses with Response ID, Customer email, Campaign name, NPS score, Feedback comment and Submitted date for the last 28 days. Retently returns responses created from the start date to the time of the read, and Submitted date is the UTC date. Count detractors from NPS score, 0 to 6, rather than from the NPS segment label, and keep one row per response.
Match each detractor to a Freshdesk contact and their tickets.
In Freshdesk, read Current contacts with Record ID, Name, Email and Company ID, and match each Customer email to Email after trimming and lowercasing. Freshdesk returns contacts that are not blocked or deleted, and only the primary email is read, so keep unmatched detractors in a separate list. Read Current tickets with Ticket ID, Subject, Native status code, Native priority code, Requester ID, Agent ID, Resolution due at, Created at and Updated at, and join Requester ID to the contact’s Record ID. Status 2 is Open, 3 Pending, 4 Resolved and 5 Closed; codes above 5 are statuses your team added, so read Ticket field definitions to see what they mean. Archived tickets are not included.
Sort detractors by what support already knows and assign the follow-up.
Put each detractor in one group. A ticket still open or pending goes to its agent, who replies on the ticket; a resolution due time already passed makes it urgent. For people whose last ticket was resolved or closed in the 14 days before they answered, check Resolved at in Ticket details and statistics for each ticket, one ticket at a time; Updated at alone also moves when someone edits an old ticket. The support lead reviews those tickets and decides whether to reopen them. Everyone else goes to customer success, with the comment theme. Keep unmatched detractors visible for a manual search. Your team sends the replies; the assistant prepares the list.
See the complete example report
EXAMPLE REPORT
Which unhappy NPS customers already have a ticket with us?
NPS responses Oct 19–Nov 16, 2026 · UTC dates · Read Nov 16, 15:00 UTC
Which unhappy NPS customers already have a ticket with us?
Detractors
People
Who follows up
Ticket still open
6
Ticket’s agent
Resolved just before
7
Support lead
No recent ticket
12
Customer success
WHAT TO LOOK ATThirty of 120 NPS responses were detractors. Six of them have 8 Freshdesk tickets still open or pending, 4 of those people already past the due date, so answer on those tickets first. Seven had a ticket resolved in the two weeks before they scored, 12 have not written to support in 90 days, and 5 have no Freshdesk contact with their email.
Sort detractors by what support already knows and assign the follow-up.
Each of these 6 people has at least one Freshdesk ticket with status Open or Pending. Four are past their resolution due time, including a High priority billing ticket for seats that were removed and an overdue payroll export fix. One ticket, an invoice copy request, has no agent. Their comments describe the same problems as the tickets. Seven people had a ticket resolved or closed in the 14 days before they answered, confirmed with each ticket’s Resolved at time. Their comments say the problem came back, the answer was slow or the ticket was marked solved without checking. An eighth person showed up on Updated at alone: that ticket was resolved in July and only edited on Nov 1, so it stays out of this group. These 12 people have no open ticket and no ticket created in the 90 days before they answered; three have only older tickets. Five comments are about price or renewal, four ask for features such as per-location overtime rules or tip pooling, and three mention onboarding videos, the mobile app and reports. Five emails match no Freshdesk contact’s primary email: one personal address, one shared front desk address and three work addresses with no contact. One of them says support was asked three times about calendar sync, and another contact at the same email domain, lakeshoreeats.com, has an open ticket about exactly that.
Try the example with sample CSVs
Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.
Data method, reporting checks & sources
Add the Retently and Freshdesk accounts to one project. In Retently, read Survey campaigns with Campaign name and Metric type, and keep only campaigns whose metric is NPS; CSAT and CES campaigns use other scales. Then read NPS responses with Response ID, Customer email, Campaign name, NPS score, Feedback comment and Submitted date for the last 28 days. Retently returns responses created from the start date to the time of the read, and Submitted date is the UTC date. Count detractors from NPS score, 0 to 6, rather than from the NPS segment label, and keep one row per response. In Freshdesk, read Current contacts with Record ID, Name, Email and Company ID, and match each Customer email to Email after trimming and lowercasing. Freshdesk returns contacts that are not blocked or deleted, and only the primary email is read, so keep unmatched detractors in a separate list. Read Current tickets with Ticket ID, Subject, Native status code, Native priority code, Requester ID, Agent ID, Resolution due at, Created at and Updated at, and join Requester ID to the contact’s Record ID. Status 2 is Open, 3 Pending, 4 Resolved and 5 Closed; codes above 5 are statuses your team added, so read Ticket field definitions to see what they mean. Archived tickets are not included. Put each detractor in one group. A ticket still open or pending goes to its agent, who replies on the ticket; a resolution due time already passed makes it urgent. For people whose last ticket was resolved or closed in the 14 days before they answered, check Resolved at in Ticket details and statistics for each ticket, one ticket at a time; Updated at alone also moves when someone edits an old ticket. The support lead reviews those tickets and decides whether to reopen them. Everyone else goes to customer success, with the comment theme. Keep unmatched detractors visible for a manual search. Your team sends the replies; the assistant prepares the list.
Only the NPS campaign counts; CSAT and CES campaigns use other scales, and every CSAT score of 1–5 would look like a detractor. Detractors come from NPS score 0–6, not from the segment label, and the NPS is calculated from the responses read. Contacts are matched on their primary email after trimming and lowercasing; unmatched detractors stay visible. “Resolved just before” is confirmed with each ticket’s Resolved at, not Updated at, and colleagues’ tickets are kept apart.
Only the NPS campaign counts; CSAT and CES campaigns use other scales, and every CSAT score of 1–5 would look like a detractor.
Detractors come from NPS score 0–6, not from the segment label, and the NPS is calculated from the responses read.
Contacts are matched on their primary email after trimming and lowercasing; unmatched detractors stay visible.
“Resolved just before” is confirmed with each ticket’s Resolved at, not Updated at, and colleagues’ tickets are kept apart.
Access to the intended Retently account or property.
Access to the intended Freshdesk account or property.
Only the NPS campaign counts; CSAT and CES campaigns use other scales, and every CSAT score of 1–5 would look like a detractor.
For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions.
Retently tells you who is unhappy and in their own words why. Freshdesk tells you whether support already knows: an open ticket, a ticket closed last week, or nothing at all. The same score needs a different reply in each case, and neither tool shows both.
How are Retently responses matched to Freshdesk tickets?
By email. The detractor’s Customer email is matched to a Freshdesk contact’s primary Email after trimming and lowercasing, and that contact’s Record ID is matched to each ticket’s Requester ID. Additional contact emails are not read, so unmatched detractors stay in their own list for a manual search.
Why not use the NPS segment label?
The segment comes from Retently and can be worded differently, and a CSAT or CES campaign returns scores on another scale. Filtering to the NPS campaign and counting 0–6 as detractors from the score keeps the definition the same each time.
Why check Resolved at instead of Updated at?
Updated at changes whenever someone edits a ticket, including old ones. In the example, a ticket resolved in July was edited on Nov 1 and would have looked recent. Resolved at comes from Ticket details and statistics, one ticket at a time, so the assistant reads it only for the short list.
What about tickets from colleagues at the same company?
They are kept apart. A colleague’s open ticket can explain a low score, as with the calendar sync ticket in the example, but a person should confirm that before anyone writes to the customer as if it were theirs.
Does the assistant reply to customers or update tickets?
No. It prepares the grouped list and notes in your conversation. Agents reply on their tickets, the support lead decides on reopening, and customer success contacts the rest.
YOUR NEXT STEP
Try it with your own data.
Start free with up to 3 data sources. No credit card.