How we handle GDPR data-subject requests on a deadline
Legal
The support agent we run on Kortix — connected to Plain, our codebase, and Stripe. It triages and resolves inbound threads, and stops for human approval on anything sensitive.
We run our own customer support on Kortix with an AI agent connected to Plain (our support tool), our codebase, and Stripe. Most support questions need product knowledge, engineering context, and billing data at the same time: a help-center chatbot can quote documentation but can't read the code behind a bug, confirm whether a subscription renewed, or take a scoped action on an account.
This write-up covers how the setup works: the connections, the session model, and the guardrails.
Support volume grows faster than the team. The questions that matter most are the ones a canned macro can't answer: "why was I charged twice?", "this button does nothing", "does your API support X?" Each one needs someone who understands the product, can read the code, and can check the customer's account — usually a senior engineer.
A help-desk bot handles the easy questions but not these. Hiring scales linearly with tickets. And giving a generic AI assistant real access to production systems is hard to justify in a security review.
Our support inbox in Plain is connected to an agent running on Kortix. Every inbound thread spawns its own isolated session with scoped access to the systems a support issue can touch: the product's knowledge, the codebase, and Stripe. It investigates, resolves what it can, and stops at a human for sensitive actions.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the support skill and the trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a support queue agent in this workspace.
Create the agent agents/support-agent.md. Its job is to work the Plain support queue. It may read the codebase and use the PLAIN_API_KEY and STRIPE_SECRET_KEY secrets.
Create the skill skills/support-playbook/SKILL.md with these rules:
Add a cron trigger support-triage to kortix.yaml. It runs the support-agent agent every 15 minutes with the prompt "Load the support-playbook skill and work every new or unanswered thread in Plain."
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 code host. Add your
Plain and Stripe API keys as the PLAIN_API_KEY and STRIPE_SECRET_KEY
secrets. Secrets are encrypted and injected at runtime, scoped to the agents you
grant them to.
Reads new support threads and resolves or drafts replies.
Reads the customer's billing state for each thread.
Searches the code and recent changes behind a bug report.
Merge the change request, then start a session with the support-agent agent and send this prompt. Read its replies and drafts before you let the schedule take over.
Work the Plain support queue once.
The change request added this trigger to kortix.yaml. From now on the agent
checks the queue 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: support-triage name: Support queue triage on: cron: "0 */15 * * * *" run: agent: support-agent prompt: Load the support-playbook skill and work every new or unanswered thread in Plain.The agent reads the codebase and Stripe freely and replies in Plain. A refund, a plan change or any other change to a customer's money or account state stops for a person. An automated session waits at most 30 minutes for a person, then stops without changing anything, and the next run asks again.
Each run ends with a short summary of the threads it worked. This is what a run looks like in the session:
Worked 5 threads. Resolved 3 directly, including a double charge that was one paid invoice and one pending authorization. Drafted 1 bug diagnosis for engineering, and 1 refund request is waiting for approval.
Once it works, paste any of these into the same session.
When three or more threads in one day report the same problem, post one summary to #support with the threads and the likely cause.
After you resolve a thread that the help docs do not cover, draft a help article from your answer and leave it for review.
Every Friday, post to #support the top 5 topics of the week, how many threads you resolved and how many you handed off.
Giving an agent access to the codebase, Stripe, and the support inbox is a security question as much as a product one. The controls on Kortix:
The agent handles the investigation-heavy tickets that used to pull a senior engineer off their work, and when it escalates, it escalates with the diagnosis attached. Customers get an answer to the question at any hour.
The setup relies on four pieces: sandbox isolation to contain each session, a secrets manager to broker tokens, human approval gates for irreversible actions, and memory that improves as threads are resolved.