How we handle GDPR data-subject requests on a deadline
Legal
The phishing-triage agent we run on Kortix — every 15 minutes it pulls newly reported emails from our phishing-report inbox, inspects headers, links, and attachments for phishing indicators, and posts a risk verdict with a recommended action to our security channel. It only recommends; a human decides whether to block a sender or warn staff.

Security awareness training tells every employee to forward anything suspicious to a phishing-report inbox, and they do — which means that inbox fills up faster than one person can open each message, view the raw headers, hover over every link, and decide whether it's real. The obvious spam never gets that far; the gateway already caught it. What lands in the report inbox is the ambiguous case, the one that needs an actual look, and during a real campaign it arrives in a burst.
We run a phishing-triage agent on Kortix that checks that inbox every 15 minutes, analyzes each reported email, and posts a verdict and a recommended action to our security Slack channel. It reads mail and it recommends; it never blocks a sender, deletes a message, or touches anything else in Gmail.
A secure email gateway filters out the obvious junk, so what a human forwards to the phishing-report inbox is already the hard tier: a plausible-looking invoice, a lookalike login page, a reply-to that doesn't match the display name. Judging it well means checking SPF/DKIM/DMARC results, tracing where a shortened link actually resolves, and noticing an attachment that's a macro document dressed up as a PDF — several checks, every time, before anyone can say whether it's real.
The common approaches don't hold up under volume. A person checks the inbox when they get to it, so a real campaign sits unflagged for hours. A static blocklist of known-bad domains misses this morning's freshly registered lookalike. A rule that auto-quarantines anything reported is fast but wrong often enough that people stop trusting it — and a false block on a legitimate sender is its own incident.
On Kortix, a cron fires every 15 minutes and spawns a fresh agent session with read-only access to the phishing-report Gmail inbox. It pulls every message reported since the last check, examines the sender's authentication results, the reply-to and return-path against the display name, where every link actually resolves, and any attachments, then classifies the risk and drafts a verdict — block this sender, warn everyone who may have gotten the same email, or no action needed — and posts it to the security Slack channel. It changes nothing in Gmail itself.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the phishing-indicators skill and the 15-minute trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a phishing-triage agent in this workspace.
Create the agent agents/phishing-triage.md. Its job is to triage emails that staff report as phishing. It may use the Gmail and Slack connectors. It reads Gmail and never changes it.
Create the skill skills/phishing-indicators/SKILL.md with these rules:
Add a cron trigger phishing-report-check to kortix.yaml. It runs the phishing-triage agent every 15 minutes with the prompt "Load the phishing-indicators skill and triage every new email in label:phishing-report."
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 mailbox that receives phishing reports, and Slack. Credentials are brokered server-side and never enter the agent's machine.

Reads each reported email, its headers, links and attachments.
Posts each verdict and recommended action to the security channel.
Merge the change request, then start a session with the phishing-triage agent and send this prompt. Check each verdict against the reported email before you let the schedule take over.
Triage every new email in the Gmail search label:phishing-report.
The change request added this trigger to kortix.yaml. From now on the agent
runs every 15 minutes, 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: phishing-report-check name: Phishing report check on: cron: "0 */15 * * * *" run: agent: phishing-triage prompt: Load the phishing-indicators skill and triage every new email in label:phishing-report.The agent reads Gmail and posts to Slack. It never blocks a sender, deletes or quarantines a message, or changes a mailbox setting. Each verdict names one action, and a person on security decides whether to take it.
Each reported email gets one verdict in the channel. This is what a run looks like in the session:
Triaged 3 new reports. 1 is critical: a fake IT login page on a lookalike domain, with DMARC failing. The recommended action is to block the sender and warn staff. The other 2 are benign marketing emails, and no action is needed.
Once it works, paste any of these into the same session.
When two or more reports in one day share a sender domain or a link, post one combined alert to #security that lists every report in the group.
Keep a list in memory of every lookalike domain you flag, and mark a new report critical when it uses one of them.
Every Friday at 16:00, post a summary to #security of the week's reports by risk tier, with the three most common indicators.
The agent reads live employee reports of suspected attacks, so its access is scoped and strictly one-directional:
Reports that used to wait for someone to have a free moment now get a verdict within 15 minutes, with the specific indicators laid out and a recommended action attached. The agent never touches a sender or a mailbox; the security team still makes every call, just with the analysis already done.