How we handle GDPR data-subject requests on a deadline
Legal
On a schedule, an agent gathers feedback from support, public reviews, and a Slack channel, clusters it into themes with representative quotes and counts, and creates or updates a Linear issue per theme.

Product feedback arrives everywhere: support threads, public reviews, a Slack channel where people drop what they hear. The same request shows up in all three, worded differently each time, and never gets counted. A theme that a hundred people asked for looks the same as a one-off, because nothing pulls the mentions together.
We run a feedback agent on Kortix that gathers those sources on a schedule, clusters them into themes, and keeps a Linear issue per theme up to date. It reads the feedback and writes to Linear; people still own prioritization. This is how we keep our own roadmap grounded in what users actually ask for.
Feedback is scattered across support threads in Plain, public reviews on G2 and the app stores, and an internal Slack feedback channel. The same underlying request appears in all of them, phrased differently, so it never gets counted. A theme that keeps recurring is indistinguishable from a single loud comment.
The common approaches don't add up to a roadmap. Reading each source by hand is slow and inconsistent, and whoever reads it weighs it differently. A tag in the support tool captures support but not reviews or Slack. A spreadsheet of feature requests goes stale the moment someone stops maintaining it, and it still doesn't tell you how many people asked for the same thing.
On Kortix, a scheduled cron triggers an agent. It spawns an isolated session (a cloud sandbox) with read access to Plain, the public review sources, and the Slack feedback channel, and write access to Linear. It gathers the feedback, clusters it into themes with representative quotes and counts, and creates or updates a Linear issue per theme, so the same request is deduplicated and quantified instead of scattered.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the clustering skill and the weekly trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a feedback clustering agent in this workspace.
Create the agent agents/user-feedback.md. Its job is to turn user feedback into one Linear issue per theme. It may use the Plain and Linear connectors and read the #feedback Slack channel.
Create the skill skills/feedback-clustering/SKILL.md with these rules:
Add a cron trigger feedback-sweep to kortix.yaml. It runs the user-feedback agent every Monday at 06:00 with the prompt "Load the feedback-clustering skill and run one complete feedback sweep into the Feedback team in Linear."
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 your support inbox, your issue tracker and Slack. Credentials are brokered server-side and never enter the agent's machine.
Reads recent support threads, read-only.
Supplies public reviews to cluster with the other feedback.
Creates or updates one issue per feedback theme.
Merge the change request, then start a session with the user-feedback agent and send this prompt. Check the themes it created before you let the schedule take over.
Run one feedback sweep.
The change request added this trigger to kortix.yaml. From now on the agent
runs every Monday at 06: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: feedback-sweep name: Feedback theme sweep on: cron: "0 0 6 * * 1" run: agent: user-feedback prompt: Load the feedback-clustering skill and run one complete feedback sweep into the Feedback team in Linear.The sources stay read-only, and the agent's only write is creating and updating Linear issues. It never sets priority, assigns an owner or closes an issue, even one that looks like a duplicate. People weigh each theme against the roadmap.
Each run ends with a list of the Linear issues it created and updated. This is what a run looks like in the session:
Read 63 pieces of feedback and found 8 themes. Updated 6 existing issues and created 2 new ones in Feedback. The largest theme, bulk export, now has 27 mentions across three sources.
Once it works, paste any of these into the same session.
After each sweep, post the five themes with the most new mentions to #product, with one quote each.
When a theme's Linear issue is marked done, list the Plain threads behind it so support can tell those users.
Also read our App Store and Google Play reviews as a source, the same way as G2.
The agent reads several feedback sources and writes to Linear, so its access is scoped to exactly that:
Feedback that used to sit unread across support, reviews, and Slack now arrives as a set of quantified themes, each a single Linear issue with quotes and a count. The agent does the gathering and counting; the team still owns which themes become roadmap.