How we handle GDPR data-subject requests on a deadline
Legal
The escalation-manager agent we run on Kortix — every 15 minutes it scans the Plain queue for SLA breaches, VIP accounts, and high-severity tickets, routes each to the right team, opens a linked Linear issue when engineering is needed, and posts to our escalation Slack channel. It never closes a ticket or promises a resolution.
A ticket that needs to jump the line looks like any other ticket until someone reads it closely: the SLA clock that's about to run out, the account that happens to be one of our biggest, the report that's actually a full outage. In a busy queue, those tickets sit in first-in-first-out order next to everything else, and the person who should be routing them is also the person answering the queue.
We run an escalation-manager agent on Kortix that checks the Plain queue every 15 minutes, finds the tickets that meet our escalation criteria, routes each one to the right internal team, opens a linked Linear issue when it's an engineering problem, and posts the whole thing to our escalation Slack channel. It routes, links, and alerts. It never closes a ticket and never tells a customer when or how their issue will be fixed.
Escalation-worthy tickets don't announce themselves. An SLA breach is a timestamp comparison someone has to actually run. A VIP account is a fact that lives in a spreadsheet or a CRM field, not in the ticket itself. High severity is a judgment call that depends on reading the ticket body, not just its tags. Any one of those, on its own, is easy to miss in a queue moving fast enough that most tickets get handled in the order they arrived.
The common fallback is a person periodically scanning the queue for anything that looks urgent, on top of their regular ticket load. It works until the queue is busy, at which point the SLA-breaching ticket and the VIP account's ticket wait behind ten routine ones, and the bug report that should already be a Linear issue is still just a paragraph in a support thread nobody on engineering has seen.
On Kortix, a cron fires every 15 minutes and spawns a fresh agent session. It reads the current state of the Plain queue, checks every open ticket against three criteria — SLA breach, VIP account, high severity — routes each qualifying ticket to the right internal team, opens a linked Linear issue when the ticket is an engineering problem, and posts one alert per escalation to the escalation Slack channel with the reason, the routed team, and the linked issue. It never closes a ticket, and it never tells the customer anything.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the escalation-routing 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 support escalation agent in this workspace.
Create the agent agents/escalation-manager.md. Its job is to find open Plain tickets that need to jump the line, route them to the right team, and alert the escalation channel. It may use the Linear connector, the Slack channel, and the PLAIN_API_KEY secret.
Create the skill skills/escalation-routing/SKILL.md with these rules:
Add a cron trigger escalation-sweep to kortix.yaml. It runs the escalation-manager agent every 15 minutes with the prompt "Load the escalation-routing skill and run one complete escalation sweep over the open Plain queue."
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 Linear, then add your Plain API
key as the PLAIN_API_KEY secret and connect Slack under Channels.
Credentials are brokered server-side and never enter the agent's machine.
Reads the open queue and routes each escalated ticket.
Opens a linked issue when a ticket needs engineering.
Posts one alert per escalation with the reason and links.
Merge the change request, then start a session with the escalation-manager agent and send this prompt. Check the routing and the linked issues before you let the schedule take over.
Run one escalation sweep over the open Plain queue.
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: escalation-sweep name: Escalation sweep on: cron: "0 */15 * * * *" run: agent: escalation-manager prompt: Load the escalation-routing skill and run one complete escalation sweep over the open Plain queue.The agent can tag and assign a ticket, open a linked Linear issue and post to Slack. It cannot close a ticket, change its status or mark it resolved. It never drafts or sends anything to the customer, and never states when or how an issue will be fixed. The team decides what happens next.
Each escalation gets one message in the channel. This is what a sweep looks like in the session:
Checked 47 open tickets and escalated 3. Two breached the Urgent SLA, and one is a VIP account reporting failed exports. Opened 1 linked Linear issue in Engineering and routed the other two to Billing and Customer Success.
Once it works, paste any of these into the same session.
Also alert #support-escalations when a ticket has less than 25 percent of its SLA window left, marked as at risk rather than breached.
Every weekday at 17:00, post a summary to #support-escalations of today's escalations by reason and by team, with any ticket still unassigned.
Each Monday, list the accounts in the VIP list with no tickets in the last 90 days and ask me in Slack whether to keep them.
The agent has write access to the support queue and the issue tracker, so its authority is scoped tightly to routing and alerting:
Tickets that used to wait behind the rest of the queue for someone to notice now get caught within 15 minutes of qualifying, routed to the team that owns them, and — when it's an engineering problem — turned into a linked issue before anyone has to ask. The agent routes, links, and alerts; the team decides how the ticket actually gets resolved.