How we handle GDPR data-subject requests on a deadline
Legal
The inbox agent we run on Kortix — connected to Gmail, a help doc, and Linear. It labels every inbound email, drafts a reply, or files a task, and stops for approval before anything goes to a customer.

A shared inbox is where a small team's requests pile up: support questions, sales pings, bug reports, and the occasional invoice, all landing in one place with no owner. Sorting them by hand is the first thing that slips when the team is busy, and a message sitting unread for a day is a message the sender assumes was ignored.
We handle this by putting an agent on the inbox. Every inbound email gets read, labelled, and either drafted a reply or turned into a task. This writes up how we run that on Kortix — the connections, the steps, and the guardrails.
The messages that need a fast reply are mixed in with the ones that can wait, and telling them apart takes a person reading each thread. On a small team that person is also doing three other jobs, so triage happens in bursts — everything looks urgent when the inbox is opened once a day, and nothing looks urgent in between.
Filters and rules help with the obvious cases but not the judgment calls: whether a message is a real support issue or a sales lead, whether it needs a reply or a ticket, and what a reasonable answer would be. Those are the parts that actually take time.
Our shared inbox in Gmail is connected to an agent running on Kortix. Every inbound email spawns its own isolated session — a cloud sandbox — with scoped access to what triage needs: the message, our help doc, and Linear. It reads the email, applies a label, and then either drafts a reply in Gmail or files a task in Linear. Anything customer-facing waits for a person before it sends.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the email-triage 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 shared inbox triage agent in this workspace.
Create the agent agents/inbox-triage.md. Its job is to label every new message in the shared Gmail inbox, draft replies from the help doc and file tickets in Linear. It may use the Gmail, Linear and Notion connectors.
Create the skill skills/email-triage/SKILL.md with these rules:
Add a cron trigger inbox-triage-check to kortix.yaml. It runs the inbox-triage agent every 15 minutes with the prompt "Load the email-triage skill and run one complete triage pass over the shared Gmail inbox."
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 Gmail, Linear and Notion. Credentials are brokered server-side and never enter the agent's machine.

Reads and labels new email and drafts replies.
Files a ticket for requests that need follow-up work.
Looks up the help doc for a standard answer.

Merge the change request, then start a session with the inbox-triage agent and send this prompt. Read the drafts and the tickets before you let the schedule take over.
Run one triage pass over the shared Gmail inbox.
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: inbox-triage-check name: Inbox triage check on: cron: "0 */15 * * * *" run: agent: inbox-triage prompt: Load the email-triage skill and run one complete triage pass over the shared Gmail inbox.The agent labels, drafts and files tickets on its own. It never sends a reply, however close the help doc match is. Every customer-facing answer waits in Gmail as a draft for a person to review and send. When the help doc does not answer a question, the agent labels the thread and leaves it.
Each pass ends with labels, drafts and tickets in place. This is what a run looks like in the session:
Triaged 9 new threads. Drafted 3 replies from the Help Center and filed 2 bugs in the Support team. 1 support question had no match in the doc, so it has a label and no draft.
Once it works, paste any of these into the same session.
For each thread labeled triage/sales, post the sender's company and a one-line summary to #sales.
Every Friday, list the support questions this week that had no match in the Help Center and propose a heading for each.
When a thread reads as frustrated or mentions cancelling, add the label triage/urgent and post its link to #support.
Giving an agent access to the shared inbox is a trust question as much as a convenience one. The relevant controls on Kortix:
The inbox stops being a pile to sort and becomes a list already labelled, with replies drafted and tickets filed. The team reviews and sends instead of reading every thread cold, and no message sits unread waiting for someone to notice it.
The setup relies on four pieces: sandbox isolation per email, a secrets manager to broker the Gmail and Linear tokens, a human approval gate before anything reaches a customer, and memory that improves as threads are resolved.