Every survey answer comes with a little story attached, and almost nobody reads it. The score ends up on a dashboard. The comment beside it, the bit that explains why this customer gave you a 4 and not a 9, sits alone in a spreadsheet row. It never gets added up with the hundred other people saying the very same thing. When a pattern is finally loud enough for someone scrolling the sheet to notice, it has usually been growing for months.

So an agent on Machine now reads the week's new responses and posts the themes, the mood and the main reasons for detractors in our customer-success Slack channel, together with how the score shifted since last week. The survey sheet is read and never changed. The Slack message is the one and only thing it produces. That's how our own NPS program avoids becoming a spreadsheet no one opens.

The problem

Each NPS or CSAT answer tells you two things: a score and a comment. Scores are the easy half, and your survey tool probably graphs them already. The comment holds the reason, and that's the half that disappears. Written feedback stacks up in an export, one line per person, and nobody gets through all of it each week. Twelve detractors can raise the same gripe and it still never gets counted as one issue.

The usual fixes fall short. A dashboard tells you the number moved but not why. A person skimming the sheet notices the angriest comment rather than the most frequent one, and reads a little differently each week. And since no one tracks themes over time, a problem that has been building for a month looks exactly like one that showed up once and vanished.

What we built

A weekly cron wakes an agent on Machine. Each run gets a fresh, isolated cloud computer, or sandbox, that can read (and only read) the Google Sheet our survey tool exports into. The agent goes through the entire response history, groups the written comments into themes, labels each answer with its sentiment and score band, picks out what is really pushing detractors down this week, and works out the week-over-week change in the score. It sends a single summary to Slack with typical quotes. Nothing is written back to the sheet.

How it works

The pattern

Once a week a cron starts a clean session with a read-only connector into the survey Google Sheet. The rules for grouping and scoring live in the agent's skills and memory. It reads the whole history on every run and writes nothing except the Slack post.

Guardrails

The agent works from a live survey export, so its access is narrow and flows one way:

• Isolation. Each run has a sandbox to itself and can reach only the sheet it was given. The Slack post is the only thing that leaves.
• Scoped secrets. The Google Sheets and Slack keys are stored encrypted in the Secrets Manager and only handed to the agents you grant them to, when the sandbox starts.
• Read-only, report-only. Its link to the survey sheet can only read. It can't edit an answer, insert a row or write back a score, and it never contacts a respondent. It reports and stops there.
• Everything is code. Grouping rules, skills and the permissions for each system are versioned files in the repo, changed only through a reviewed change request, never a dashboard toggle.

The outcome

Comments that used to gather dust in a spreadsheet now show up every week as named themes with quotes and counts, right next to the real week-over-week change in the score and the reasons behind it. The agent reads and reports, nothing more. Deciding what to do about each theme is still the team's job.