How we handle GDPR data-subject requests on a deadline
Legal
A daily agent that searches news, social platforms, and forums for new mentions of our brand, classifies sentiment, and posts a digest of the notable or negative ones to Slack — each with a suggested response drafted for a human to review.
Brand mentions show up wherever people happen to be talking — a news writeup, a Reddit thread, a tweet, a forum post comparing us to a competitor. Most days nothing needs a response. Some days a single negative post with real reach needs one within the hour, and the team doesn't find out until it's already been seen by everyone else.
We run a brand-monitor agent on Kortix that checks the web every day for new mentions, classifies each one's sentiment, and posts a digest to our marketing Slack channel. It never replies or posts anywhere itself — for anything notable, it drafts a suggested response and leaves the sending to a person.
Brand mentions aren't confined to one platform. They land in news coverage, social posts, and forum threads on no predictable schedule, and most of them don't matter — a passing mention, a neutral comparison, a repost. The ones that do matter are indistinguishable from the noise until someone actually reads them, and by the time a person gets around to checking, a negative post with real reach has often already had its worst hour.
The usual workarounds don't fix this. A Google Alert fires on keyword matches with no sense of sentiment or reach, so every alert looks the same regardless of whether it's a five-word tweet or a widely shared negative review. Checking manually catches yesterday's mentions today, if someone remembers to look. Either way, nothing tracks what's already been seen, so the same viral post gets flagged again tomorrow.
A daily cron re-prompts a persistent agent session. Each run searches the web for new mentions of the brand across news, social platforms, and forums, checks each one against a ledger of mentions it has already reported, classifies the sentiment of anything new, and posts a digest to Slack — a one-line rollup for routine mentions, and a full callout with a suggested response draft for anything notable or negative. It never posts, replies, or comments anywhere; the only output is the Slack digest.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the brand-mention-monitor skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily brand monitor agent in this workspace.
Create the agent agents/brand-monitor.md. Its job is to find new mentions of our brand on the public web and post a daily digest. It may use web search and fetch, and the Slack connector.
Create the skill skills/brand-mention-monitor/SKILL.md with these rules:
Add a cron trigger daily-brand-monitor to kortix.yaml. It runs the brand-monitor agent every day at 06:00 with the prompt "Load the brand-mention-monitor skill and run today's brand-monitor sweep."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
The agent searches the public web with its built-in search and fetch, so the sources need no connector. Open Connectors in your workspace and connect Slack for the digest. Credentials are brokered server-side and never enter the agent's machine.
Posts the daily digest with suggested responses.

Searches threads for new brand mentions, read-only.
Merge the change request, then start a session with the brand-monitor agent and send this prompt. The first run fills the ledger, so check what it logged before you let the schedule take over.
Run one brand-monitor sweep for our brand terms.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 06:00 and picks up from its ledger in memory/. To change the time, edit the cron line, or open
Triggers in the workspace.
triggers:- slug: daily-brand-monitor name: Daily brand monitor on: cron: "0 0 6 * * *" run: agent: brand-monitor prompt: Load the brand-mention-monitor skill and run today's brand-monitor sweep.The agent only searches and reads public pages, and it writes only to one Slack channel. A suggested response appears in the digest as a labeled draft. A person reads it, edits it and decides whether to send it.
Each run ends with one digest in the channel. This is what a run looks like in the session:
Found 15 new mentions: 9 positive, 4 neutral and 2 negative. Flagged 2 as notable, a forum thread with a pricing complaint and a news article that misstates a feature. Each has a drafted response for your review.
Once it works, paste any of these into the same session.
For the next 14 days, add our new product name to the brand terms and post a separate launch digest each evening.
Every Monday, post the count of positive, neutral and negative mentions for each of the last 8 weeks to #marketing.
When a mention describes a product bug, also post its link and excerpt to #support.
The agent watches public conversation about the brand, so its access is scoped to searching and reading, with a single, narrow output:
The team no longer finds out about a negative mention secondhand, and no one re-reads yesterday's viral post because it was flagged twice. The channel gets one digest a day — quiet on quiet days, specific and actionable when something needs a response — and every response that goes out is one a person chose to send.