How we handle GDPR data-subject requests on a deadline
Legal
A weekly cron reads new NPS/CSAT survey responses from a Google Sheet, clusters them into themes with sentiment and detractor drivers, and posts the score trend and representative quotes to Slack.
NPS and CSAT surveys generate a response every time someone answers, and most of it goes unread. The score gets tracked in a dashboard, but the comment next to it — the actual reason someone gave a 4 instead of a 9 — sits in a spreadsheet row and never gets aggregated with the hundred other comments saying the same thing. By the time a theme is obvious to a human skimming the sheet, it's been building for months.
We run an NPS analysis agent on Kortix that reads new survey responses every week and posts the themes, sentiment, and detractor drivers to our customer-success Slack channel, alongside how the score moved since last week. It only reads the survey sheet; the single output is the Slack post. This is how we keep our own NPS program from turning into an unread spreadsheet.
Every NPS or CSAT response is really two signals: a number and a comment. The number is easy to track — most survey tools already chart it. The comment is where the "why" lives, and it's the part that gets lost. Free-text feedback piles up in a spreadsheet export, one row per response, and nobody reads all of it every week, so the same complaint from a dozen different detractors never gets counted as one thing.
The common approaches don't fix this. A dashboard shows the score moving without saying why. Someone skimming the sheet manually catches the loudest complaint, not the most common one, and does it inconsistently from week to week. And because nothing tracks the theme over time, a driver that's been growing for a month looks identical to one that appeared once and went away.
On Kortix, a weekly cron triggers an agent. It spawns an isolated session (a cloud sandbox) with read-only access to the Google Sheet the survey tool exports responses into, reads the full response history, clusters the free-text comments into themes, tags each response's sentiment and score band, isolates what's actually driving detractors this week, and computes how the score has moved week over week. It posts one summary to Slack with representative quotes. It writes nothing back to the sheet.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the theme analysis skill and the weekly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a weekly NPS analysis agent in this workspace.
Create the agent agents/nps-analysis.md. Its job is to turn NPS and CSAT survey responses into themes, detractor drivers and a score trend. It may use the Google Sheets connector and post to Slack.
Create the skill skills/nps-theme-analysis/SKILL.md with these rules:
Add a cron trigger weekly-nps-analysis to kortix.yaml. It runs the nps-analysis agent every Monday at 09:00 with the prompt "Load the nps-theme-analysis skill and run one complete NPS/CSAT analysis sweep."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect the sheet your survey tool exports into, and Slack. Credentials are brokered server-side and never enter the agent's machine.

Reads the week's survey responses, read-only.
Posts the theme summary with representative quotes.
Merge the change request, then start a session with the nps-analysis agent and send this prompt. Check the themes against a sample of comments before you let the schedule take over.
Run one NPS analysis on the NPS responses sheet.
The change request added this trigger to kortix.yaml. From now on the agent
runs every Monday at 09:00, each run in a new session on its own cloud computer.
To change the time, edit the cron line, or open Triggers in the workspace.
triggers:- slug: weekly-nps-analysis name: Weekly NPS/CSAT analysis on: cron: "0 0 9 * * 1" run: agent: nps-analysis prompt: Load the nps-theme-analysis skill and run one complete NPS/CSAT analysis sweep.The agent reads the sheet and writes one Slack post. It never edits a row, never contacts a respondent and never opens a ticket. What to do about a theme stays with the customer-success team.
Each run ends with one report in the channel. This is what a run looks like in the session:
NPS is 41, down 6 points from last week, because of more detractors rather than fewer promoters. The top detractor driver is slow support replies, with 9 mentions this week, up from 3. Onboarding friction is a new theme with 4 mentions.
Once it works, paste any of these into the same session.
When the sheet has a plan or segment column, add this week's score and top themes per segment to the summary.
On the first Monday of each month, post the top five themes of the last month and how each one moved to #customer-success.
Next to each theme that names a product area, mention the owner of that area from memory so the right person sees it.
The agent reads a live survey export, so its access is scoped and one-directional:
Survey comments that used to sit unread in a spreadsheet now arrive every week as a set of named themes with quotes and counts, next to the score's actual week-over-week move and what's driving it. The agent only reads and reports; the team still decides what to do about each theme.