How we handle GDPR data-subject requests on a deadline
Legal
The customer onboarding agent we run on Kortix — a daily cron that checks every new account against its onboarding milestones in Postgres, drafts a nudge email when one stalls, and alerts the owning CSM in Slack with the context to act.
The first thirty days decide most renewals long before the renewal date shows up. An account that gets its workspace live, finishes setup, and hits its first real result in week one tends to stick. An account that signs and then goes quiet — no second login, no setup finished, no teammate invited — is already at risk, and usually nobody notices until the CSM happens to open HubSpot and wonder why an account they haven't heard from in three weeks is still on "customer since" last month.
We run a customer-onboarding agent on Kortix that checks every new account against its onboarding milestones every day, catches the ones that are stalling, drafts a nudge for the customer, and alerts the owning CSM with exactly what's stuck and why. It never changes an account and never sends anything itself — it hands the CSM a head start instead of a surprise churn conversation two quarters later.
A new account's onboarding progress lives in two places that don't talk to each other: the product events and activation milestones sit in Postgres, and the account record — who owns it, when it became a customer — sits in HubSpot. Neither system on its own tells a CSM whether an account is on track. A login count means nothing without knowing what day of onboarding the account is on; a HubSpot record means nothing without knowing whether the account has actually done anything since it signed.
The usual fallback is a CSM manually checking their book of accounts, or a dashboard that shows raw usage numbers with no sense of what "on track" even means for a given account's age. By the time a stalled account gets noticed, it's often past the point where a simple nudge would have fixed it.
On Kortix, a daily cron triggers an agent that reads HubSpot for every account inside its onboarding window and owned by a CSM, checks that account's activation milestones and product events in Postgres, and classifies each one as on track, stalled at a specific milestone, or overdue for full activation. For every stalled or overdue account, it drafts a nudge email addressed to the customer's own missed step and posts an alert to the owning CSM's Slack with the specific context — what's done, what's stuck, and what the nudge says. The draft waits in the CSM's inbox; the CSM decides whether to send it, edit it, or reach out a different way.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the milestones 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 customer onboarding agent in this workspace.
Create the agent agents/customer-onboarding.md. Its job is to track new accounts against their onboarding milestones and alert the owning CSM. It may use the HubSpot, PostgreSQL, Slack and Gmail connectors.
Create the skill skills/onboarding-milestones/SKILL.md with these rules:
Add a cron trigger daily-onboarding-check to kortix.yaml. It runs the customer-onboarding agent every day at 07:00 with the prompt "Load the onboarding-milestones skill and run today's onboarding check."
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 CRM, your product database, Slack and your email. Credentials are brokered server-side and never enter the agent's machine.
Reads accounts in the onboarding window and writes the nudge marker.
Reads activation milestones and product events, read-only.
Alerts the owning CSM with the stall and the drafted nudge.

Merge the change request, then start a session with the customer-onboarding agent and send this prompt. Read the drafts and alerts before you let the schedule take over.
Run today's onboarding check.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 07:00, 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: daily-onboarding-check name: Daily onboarding check on: cron: "0 0 7 * * *" run: agent: customer-onboarding prompt: Load the onboarding-milestones skill and run today's onboarding check.The nudge email stays a draft in Gmail until the CSM reviews, edits and sends it. The agent never contacts the customer. It never changes a plan, a seat count, the deal stage or the owner. Its only HubSpot write is the nudge marker.
Each run ends with one alert per account that needs attention. This is what a run looks like in the session:
Checked 18 accounts in onboarding: 14 on track, 3 stalled and 1 overdue. Drafted 3 nudges, one for each new stall. The overdue account was nudged before, so its CSM got an alert only.
Once it works, paste any of these into the same session.
Every Monday, post to #cs-onboarding how many accounts from each signup week reached each milestone.
When an account reaches full activation, tell its CSM in #cs-onboarding and name the day it got there.
If an account has no product events in its first 3 days, alert its CSM the same day, before core setup is due.
The agent touches new, revenue-relevant accounts, so what it can do is narrow and explicit:
Onboarding stalls that used to surface only when a CSM happened to look now arrive the same day they start, with the exact missed step and a nudge already written. The agent watches every new account and does the noticing; the CSM still decides what to send and when.